Fixed Assets (FA)

FA Addition Data Model Document

Author: Monika Gupta & Samayeeta Bandyopadhyay

Creation Date: 12-DEC-2015
Last Updated:
Document Ref:
Version: 1A

Organization: Oracle India Private Limited.

1
Document Control

Change Record
1
00

Date Author Versio Change Reference

n

12-Dec- Monika Gupta 1A Initial document

2015 and Samayeeta
Bandyopadhyay

Reviewers

Name Position

Jai Thakkar Manager, Product Support

Anshu Malhotra Project Lead

Audience

Name Position

Product Support Team Internal.

Development Team

2
Table of Contents
Document Control..................................................................................................................................... 2
CHAPTER 1 - Introduction ..................................................................................................................... 5
Introduction to FA Addition .................................................................................................................. 5
Master Setups ....................................................................................................................................... 7
CHAPTER 2: FA Quick Addition............................................................................................................ 34
Introduction ........................................................................................................................................ 34
Steps to perform FA Quick Addition ................................................................................................... 34
CHAPTER 3 FA Detailed Addition ..................................................................................................... 38
Introduction ........................................................................................................................................ 38
Steps to perform FA Detailed Addition ............................................................................................... 38
CHAPTER 4 Addition of Expensed Assets ......................................................................................... 42
Introduction to Expensed Assets ........................................................................................................ 42
Pre-requisite for Expensed Assets ...................................................................................................... 42
Steps to Create an Expensed Asset ..................................................................................................... 43
CHAPTER 5 Addition of CIP Asset Manually ..................................................................................... 45
Introduction to CIP Asset .................................................................................................................... 45
Steps to Create a CIP Asset ................................................................................................................. 45
Adding Source Lines to CIP Assets ...................................................................................................... 48
CHAPTER 6 FA Addition from Accounts Payables ............................................................................ 54
Introduction ........................................................................................................................................ 54
Pre-requisite - Mass Additions Create Rules for Import from Payables to Fixed Assets .................... 54
Steps to perform FA Addition from Payables ..................................................................................... 55
CHAPTER 7 FA Addition from Projects ............................................................................................. 65
Introduction to FA Addition from Projects ......................................................................................... 65
Conditions for Project Information to Be Imported ........................................................................... 65
Steps to perform FA Addition from Projects....................................................................................... 66
CHAPTER 8 Addition Via WebADI..................................................................................................... 71
Introduction ........................................................................................................................................ 71
Pre-requisite Setup in Excel for WebADI ......................................................................................... 71
Steps to perform FA Addition via WebADI ......................................................................................... 72
CHAPTER 9 Addition via API ............................................................................................................. 81

3
Introduction to Addition via API ......................................................................................................... 81
Working addition API sample.............................................................................................................. 81
CHAPTER 10 Flow of Data in Tables ................................................................................................. 83
Tables Associated with Oracle Assets Setup before Additions: .......................................................... 83
Flow of Data in Fixed Asset Tables Associated with Asset Additions: ................................................ 85
Screenshot of a Sample Asset Trace showing flow of data into tables .............................................. 90
E-R Diagram of the Data Flow In Fixed Asset Tables........................................................................... 93
CHAPTER 11 Accounting entries and Create Accounting details ..................................................... 94
Accounting Entries and Creating Accounting details .......................................................................... 94
Tables populated post Create Accounting Assets program run ...................................................... 94
CHAPTER 12 Forms and PLS files ...................................................................................................... 96
List of relevant forms and PLS files along with the latest version number......................................... 96
CHAPTER 13 Common notes to refer for FA Addition ..................................................................... 97
Notes on Mass addition ...................................................................................................................... 97
Notes on Projects to FA ...................................................................................................................... 98
Notes on FA Addition via workbench ................................................................................................. 98
Notes on FA Addition via Web ADI ..................................................................................................... 99
Notes on Expense asset .................................................................................................................... 100

4
 CHAPTER 1 - Introduction

Introduction to FA Addition
The Fixed Assets (FA) module allows you to maintain equipment inventory, depreciation schedules
using the best accounting and tax strategies. It allows you to value assets using different
classifications, such as Construction in Process (CIP) or expensed items. Asset addition is the first and
basic step to bring asset into system. When asset is added into system there are various details
which are also provided while adding asset in the system like type of asset, depreciation method,
book details date from which depreciation should be effective and other asset level details.

The FA Addition is the first stage of the Fixed Assets Life Cycle The Birth of the Asset.

At this stage, the asset is added into the system with all the required information in order to prepare
it for maintenance and depreciation till it finally retires or seizes to be useful.

There are different ways via which an asset can be added into Oracle.

A. Manual
B. Addition from other sources.

The following chart helps to understand it better:

Manual Addition

Detail Quick
Addition Addition

5
 Addition from Other
Sources

Oracle Oracle
WebADI API
Payables Projects

Legacy System

FA MASS ADDITIONS

Review Mass
Addition and Post It

Depreciation rules
are defaulted from
Asset Category

Asset is created after

running Post Mass
Addition

6
Master Setups

Step 1 - Define Your Ledger

You need to define at least ledger before you can implement and use Oracle Assets.

Following steps required for the same:

Define your chart of accounts.

Define your accounting period types and accounting calendar.
Define the functional currency for your ledger.
Define a ledger and assign it a calendar, functional currency and account structure.
Have your system administrator assign your ledger to a responsibility

Please refer to the General Ledger Implementation Guide for the same.

Step 2 Define the three flexfields

1. Asset Category Flexfield

The asset category flexfield allows defining asset categories and subcategories. For example, you
can create an asset category for your computer equipment. You can then create subcategories
for personal computers, terminals, printers, and software. You must assign the major category
segment qualifier to one segment of your category flexfield. The major category segment
facilitates capital budgeting. All other segments are optional.

7
On Clicking on Segments:

8
2. Define Your Location Flexfield

The location flexfield allows specifying and tracking the exact location of your assets. You must
assign the state segment qualifier to one segment of your location flexfield. The state segment
facilitates property tax reporting. All other segments are optional.

9
On Clicking on Segments:

10
3. Define Your Asset Key Flexfield

The asset key flexfield allows defining asset keys that let you name and group your assets so you
do not need an asset number to find them. The asset key is similar to the asset category in that
it allows you to group assets. However, the asset key has no financial impact.

This flexfield lets you assign the same name to many assets so you can find similar assets. You
can provide additional descriptive data to group of assets by project or other functional use. You
can use this flexfield to track your CIP assets.

11
Click on segment and you can define segments needed as per requirement.

12
 Data is stored in table:

Table Affected Table Description

FND_ID_FLEXS Stores registration information about key
flexfields
FND_ID_FLEX_SEGMENTS Stores KFF segment details
FND_ID_FLEX_STRUCTURES Stores KFF structure details
FND_FLEX_VALUES Stores valid values for key and descriptive
flexfield segments
FND_FLEX_VALUE_HIERARCHIES Stores information about child
value ranges for key flexfield segment values.
Each row includes an
identification of the parent value the range
belongs to, as well as the low
and high values that make up the range of child
values.
FLEX_VALUE_SET_ID identifies the value set to
which the parent value
belongs.

Step 3 - Define Your System Controls

Set up your system controls. You specify your enterprise name, asset numbering scheme, and key
flexfield structures in the System Controls window. You also specify the oldest date placed in service
of your assets which signifies the date post which you can have assets put to use

Navigation : Fixed Asset Responsibility -> Setup-> Asset System -> System Controls

This is a one time setup.

13
 Data is stored in table:

Table Affected Table Description

FA_SYSTEM_CONTROLS stores enterprise name, oldest DPIS which can
be use, KFF and asset sequencing details

14
 Step 4 - Define Your Locations

Define valid locations. Your location flexfield combinations tell Oracle Assets what locations are valid
for your company. Oracle Assets uses location for tracking assets and for property tax reporting.

If your location flexfield has dynamic insertion turned off, this is the only place you can define valid
combinations. If dynamic insertion is turned on, Oracle Assets automatically updates the Locations
window with the values you enter in the Assignments window.

In location KFF if dynamic insert is enabled then with without defining location also during asset
creation location can be automatically created

Navigation : Fixed Asset Responsibility -> Setup-> Asset System -> Locations

Locations which are enabled can only be used.

Data is stored in table:

Table Affected Table Description

FA_LOCATIONS stores locations which can be used in asset
assignment window with start and end date for
location use and enable button for location

15
 Step 5 - Define Your Asset Keys

Define valid asset keys. You can use the list of values to choose these combinations for your assets
when you enter them.

If dynamic insertion is disabled for your asset key flexfield, Asset Keys is the only window where you
can define valid combinations. If dynamic insertion is enabled, Oracle Assets automatically updates
the Define Asset Keys window with the values you enter when you add assets.

Navigation : Fixed Asset Responsibility -> Setup-> Asset System -> Asset Keys

Asset Keys which are enabled can only be used.

Data is stored in table:

Table Affected Table Description

FA_ASSET_KEYWORDS Stores distinct asset key which can be used
while asset creation with start and end date and
enable button for asset key. stores valid asset
key flexfield segment value combinations.
Segment values are stored in the SEGMENT
columns. The SEGMENT columns which are used
are not guaranteed to be in any order. The
Application Object Library table
FND_ID_FLEX_SEGMENTS stores information
about which column in this table is used for
each segment

16
Step 6 - Define Your QuickCode Values

QuickCode values are values that you can choose from a list of values when you enter and maintain
assets. You can define the QuickCode values that you want for the following items:

Standard Asset Descriptions

Journal Entries
Mass Additions Queue Names
Property Type
Retirement
Asset Category
Asset Subcategory

These are lookup codes in Fixed Assets which are used at various places. We cannot define a new
quickcode as they are system defined but we can enter values as per our setup.

Navigation : Fixed Asset Responsibility -> Setup-> Asset System -> QuickCodes

17
 Data is stored in table:

Table Affected Table Description

FA_LOOKUPS_B Seeded table and stores user defined value for
quick codes. Each row includes a codes lookup
type and description.
LOOKUP_TYPE identifies a list of QuickCode
values. LOOKUP_CODE identifies the QuickCode
value.
FA_LOOKUPS_TL FA_LOOKUPS_TL contains translated description
columns from the FA_LOOKUPS_B base table to
conform to multilingual standards.

Below are the quick code types commonly used:

Asset Description
Asset Type
Journal Entries
Queue Name
Property Type
Retirement
Asset Category
Asset Subcategory
Unplanned Depreciation Type
Lease Frequency
Lease payment Type
Source Line type

Step 7 - Define Your Fiscal Years

Use the Fiscal Years window to define the beginning and end of each fiscal year since the start of
your company.

Your fiscal year groups your accounting periods. You must define the start and end date of each
fiscal year since the oldest date placed in service.

Navigation : Fixed Asset Responsibility -> Setup-> Asset System -> Fiscal years

Need to define start and end date of each fiscal year. We can setup multiple fiscal year based on
requirement.

18
 Data is stored in table.

Data is stored in table:

Table Affected Table Description

FA_FISCAL_YEAR FA_FISCAL_YEAR stores information about your
fiscal years. Oracle Assets uses this table when
you define calendars and to determine the fiscal
year in which a transaction occurs. Oracle Assets
inserts a row into this table for each fiscal year
name and year you define in the Fiscal Years
form. The master fiscal year name row is in
FA_LOOKUPS with LOOKUP_TYPE FISCAL YEAR.
At the close of each fiscal year, Oracle Assets
automatically inserts a row for the next fiscal
year for that fiscal year name, if that row does
not already exist.

19
Step 8 - Define Your Calendars

Use the Calendars window to set up as many calendars as you need. Calendars break down your
fiscal year into accounting periods. Define your calendars with as many periods as you need
between the range of 1 to 365.

Define a prorate calendar and a depreciation calendar for each depreciation book.

Prorate Calendar - Determines, with the divide depreciation flag, what fraction of the
annual depreciation amount to take each period.
Depreciation Calendar - Determines, with the date placed in service, which depreciation
rate to select from the rate table.

Depreciation books can share a calendar, and you can use the same calendar or different calendar
for your depreciation calendar and prorate calendar for a book or set different calendar for each
book.

There are three period suffix which can be used while defining calendar which are mentioned below:

1. Fiscal : If suffix fiscal is selected then calendar name is suffixed with the fiscal year.

2. Calendar: If suffix Calendar is selected while defining calendar then the period name is
suffixed with actual calendar year

3. None: Here we can use any period suffix

Example:

Suppose Fiscal Year is defined as 2014 and start date is 1-Apr-2013 and end date is 31-Mar-2014.

Calendar name suffix:

1. Fiscal : Period name for period 1-Apr-2013 to 30-Apr-2013 will be Apr-14

2. Calendar: Period name for period 1-Apr-2013 to 30-Apr-2013 will be Apr-13 as calendar year
is 2013

3. None: Here we can have any suffix or custom suffix as per customer

20
 Data is stored in table:

Table Affected Table Description

FA_CALENDAR_TYPES
FA_CALENDAR_TYPES contains general
information about your calendars. Oracle Assets
inserts a row in this table for each calendar you
define. PERIOD_SUFFIX_TYPE is FISCAL if you
append your fiscal year to each PERIOD_NAME in
FA_CALENDAR_PERIODS, or CALENDAR if you
append the calendar year.
NUMBER_PER_FISCAL_YEAR is the number of
accounting periods in your fiscal year

21
FA_CALENDAR_PERIODS FA_CALENDAR_PERIODS stores detail information
for FA_CALENDAR_TYPES. The depreciation
program uses this information to define
CALENDAR_PERIOD_OPEN_DATE and
CALENDAR_PERIOD_CLOSE_DATE in
FA_DEPRN_PERIODS, and to check transaction
dates.

Step 9 - Define Additional Depreciation Methods and Rates

Depreciation methods specify how to depreciate the asset cost. Oracle Assets includes many
standard depreciation methods, and you can define as many methods in the Methods window, as
necessary.

Navigation: Asset Responsibility -> Setup -> Depreciation -> Methods

22
 Data is stored in table:

Table Affected Table Description

FA_METHODS FA_METHODS stores information about your
depreciation methods. The depreciation
program uses this table to identify the
appropriate depreciation rates for tablebased
methods in FA_RATES.
FA_RATES FA_RATES stores the annual depreciation rates
used by the depreciation program to calculate
depreciation for your assets that use lifebased
depreciation methods. When you create a
depreciation method using the LifeBased
Depreciation Methods form, Oracle Assets
inserts a row into this table for each
depreciation rate you define for a year of life
and prorate period
(PERIOD_PLACED_IN_SERVICE). The number of
prorate periods per year for a method is defined
by PRORATE_PERIODS_PER_YEAR in
FA_METHODS. Oracle Assets does not use
FA_RATES to store rate information for straight
line methods because the depreciation program
calculates the rate by dividing the life in years
into 1

Step 10 - Define Conventions

Use the Prorate Conventions window to set up your conventions. Conventions determine how much
depreciation expense to take in the first and last year of life, based on when you place the asset in
service. Oracle Assets lets you set up as many prorate and retirement conventions as you need.

Prorate Conventions - Determines when to start depreciation for the asset. It plays an
important role during period of addition and last period of assets life
Retirement Conventions Determines when to stop depreciation when asset is retired.
Retirement convention can be different from the prorate convention used while asset
addition

You must set up your prorate conventions for the entire year. Navigation: Fixed Asset Responsibility
-> Setup-> Asset System -> Prorate Conventions

23
 Data is stored in table:
Table Affected
FA_CONVENTION_TYPES
FA_CONVENTIONS
Table Description
FA_CONVENTION_TYPES stores the name and
descriptions of all the prorate conventions defined
in the system. Oracle Assets inserts one row into
this table for each prorate convention that you
define.
FA_CONVENTIONS stores information about your
prorate conventions. Oracle Assets uses this table
to map a date placed in service to a prorate date.
Oracle Assets inserts one row in this table for each
prorate date you define for a prorate convention.
Oracle Assets uses this table to determine the
24
 prorate date for any date placed in service. Oracle
Assets selects the row where the
DATE_PLACED_IN_SERVICE in FA_BOOKS is
between START_DATE and END_DATE in this table

Step 11 - Define Your Books

Use the Book Controls window to set up your depreciation books. You can set up an unlimited
number of independent depreciation books. Each book has its own set of accounting rules and
accounts so you can organize and implement your fixed assets accounting policies.

There are 3 types of Book that can be defined:

1. Corporate Book: This is the main asset book type used to hold the Fixed Asset Register in
accordance with the corporate policy. The Corporate Book is linked to the appropriate
Ledger for journal postings. It is the book into which invoice lines flow from AP or projects. It
is the main depreciation book from which Journal entries are created for GL

2. Tax Book: This book type is subsidiary to corporate book and is used to hold the same assets
as in the Corporate book but depreciate them differently for tax or legal / fiscal purposes.
When you define a tax book, you must specify an associated corporate book
From the corporate book the transactions can be copied into the Tax Book. It is called tax
book because it is generally used to keep the tax depreciation. One can maintain different
depreciation methods and life from the corporate book for the same assets.
3. Budget Book: This book type is also subsidiary to a corporate book and is used to hold
capital budget information. Multiple Budget books can be linked to one corporate book.

25
Navigation : Fixed Asset Responsibility -> Setup-> Asset System -> Book Controls

Calendar tab stores ledger, fiscal year, depreciation and prorate calendar and depreciation
allocation with current open period and current fiscal year

26
Ledger tab stores ledger, chart of accounts details for the books

27
Accounting Rules tab stores various rules that are applicable for the books

28
 Natural account tab stores retirement account and various accounts which are picked during CCID
creation.

Data is stored in table:

Table Affected Table Description

FA_BOOK_CONTROLS FA_BOOK_CONTROLS contains control
information that affects all assets in a
depreciation book. LAST_PERIOD_COUNTER is
the last period for which you ran the
depreciation program on a book. Oracle Assets
uses it to prevent you from running the
depreciation program multiple times for a
period and to ensure that you run it for
consecutive periods. INITIAL_PERIOD_COUNTER
is the period prior to the one in which you
created this book. INITIAL_DATE is the last date
on which you ran depreciation for this book on
your previous system before you started using
Oracle Assets. ACCOUNTING_FLEX_STRUCTURE

29
 determines which Accounting Flexfield structure
the depreciation book uses. It matches a
CHART_OF_ACCOUNTS_ID in
GL_CODE_COMBINATIONS. Oracle Assets uses it
to configure Accounting Flexfield popup
windows and to run reports that use the
account number. DEPRN_REQUEST_ID is the
concurrent request number for the last time you
ran the depreciation program on a book. Oracle
Assets updates this column as soon as the
depreciation program begins running.
DEPRN_STATUS specifies whether depreciation
is locking the book. Oracle Assets uses
DEPRN_STATUS to prevent you from entering
transactions while depreciation is running. It can
be:
C Completed
E Error
R Running
S Submitted

Step 12 - Define Your Asset Categories

Asset categories let you define information that is common to all assets in a category, such as
depreciation method and prorate convention. Oracle Assets uses this information to provide default
values to help speed asset entry.

Create different categories as per requirement and categories are either capitalized or non-
capitalized

NOTE : Category for which capitalize checkbox is not checked is can be assigned to expensed type
assets only.

Navigation: Fixed Asset Responsibility -> Setup-> Asset System -> Asset Categories

30
After defining the category details above we need to attach asset book to the category and define
the defaulting rules which contains default depreciation rules for the category. The categories can
have 1 to many associations with books but every book to category combination needs to e
maintained if the category needs to be used by the book

NOTE: Before creation of an asset, the Book and Asset Category Assignment should be in place.

31
 Data is stored in table:
Table Affected
FA_CATEGORIES_B
FA_CATEGORIES_TL
Table Description
FA_CATEGORIES_B stores information about
your asset categories. This table provides
default information when you add an asset. The
depreciation program does not use this
information to calculate depreciation. The Asset
Categories form inserts one row in this table for
each asset category you define. The Application
Object Library table FND_ID_FLEX_SEGMENTS
stores information about which column in this
table is used for each segment.
FA_CATEGORIES_TL contains translated
description columns from the
FA_CATEGORIES_B base table to conform to
multilingual standards.
32
FA_CATEGORY_BOOKS FA_CATEGORY_BOOKS provides cost and
reserve accounts for a book and category
combination. The Asset Categories form inserts
a row in this table for each book in which you
use an asset category. For example, if you define
a category for three depreciation books, Oracle
Assets inserts three rows into this table.
FA_CATEGORY_BOOK_DEFAULTS FA_CATEGORY_BOOK_DEFAULTS provides
defaults for the depreciation rules when you
add an asset. The Asset Categories form inserts
a row into this table for each asset category,
depreciation book, and date placed in service
range for which you set up the category.

33
 CHAPTER 2: FA Quick Addition

Introduction
Use the Quick Additions process to quickly enter ordinary assets when you must enter them
manually. You can enter minimal information in the Quick Additions window, and the remaining
asset information defaults from the asset category and book.

Using quick addition we can create below assets:

Capitalized asset : Asset Category has to be capitalized i.e. Capitalize checkbox should be
checked at category level and asst type should be capitalized
CIP Asset: Asset type selected should be CIP
Expense Asset: At category level capitalize check box should be unchecked and asset type
should be expensed

Steps to perform FA Quick Addition

FLOWCHART:

Asset
Assets Asset
Responsibility
Workbench

Enter the data and

Quick Additions
Save

34
1. Navigation: Fixed Asset Responsibility -> Assets -> Asset Workbench -> Quick Addition

2. Click on the Quick Additions Button

35
3. Enter the required information Asset Number, Category, Units, Asset Type, Book name, Cost,
method and Assignment Information.

Once all the required information is inserted, click on Done.

36
4. A popup will appear indicating that the Transaction has been saved.

37
 CHAPTER 3 FA Detailed Addition

Introduction
Detailed Addition provides the option to enter all the required details of the asset instead of just the
basic information like in Quick Addition like manual reserve, salvage value depreciation limit etc

Using detailed addition we can create below assets:

Capitalized asset : Asset Category has to be capitalized i.e. Capitalize checkbox should be
checked at category level and asst type should be capitalized
CIP Asset: Asset type selected should be CIP
Expense Asset: At category level capitalize check box should be unchecked and asset type
should be expensed

Steps to perform FA Detailed Addition

FLOWCHART:

Asset Asset
Responsibility Assets Workbench

Enter the data and

Additions
Save

38
1. Navigation: Fixed Asset Manager Responsibility ->Assets -> Asset Workbench

Here we can give asset number or let system generate an asset number based on the sequence.

39
2. Enter the category and asset type in this screen.

3. Press Continue to navigate to books screen and provide book details, asset cost, accumulated
depreciation and YTD if it is backdated addition. If we do not provide these details then the
system itself will calculate the depreciation expense

Here we are making an amortized asset addition.

In Amortization the changes are effective from a particular date which is the amortization date.
In this case the depreciation will be charged from current open period. In the below case, the
amortization start date is 01-Apr-2014.

40
4. Click on Continue to navigate to assignment screen. Enter asset location, expense account and
employee to whom asset is to be assigned. Provide the details and save the changes.

41
 CHAPTER 4 Addition of Expensed Assets

Introduction to Expensed Assets

Items that do NOT depreciate; the entire cost is charged in a single period to an expense account.
Oracle Assets tracks expensed items, but do not create journal entries for them. Oracle Assets does
not depreciate expensed assets, even if the Depreciate check box in the Books and Prepare Mass
Additions windows is checked for that asset.

Pre-requisite for Expensed Assets

Category defined should be of non-capitalize type.

Below is the screenshot for the same:

42
Steps to Create an Expensed Asset

FLOWCHART:

Asset Asset
Assets
Responsibility Workbench

Enter expense
category and asset Quick
type will be expensed Addition/Additions
automatically

Follow the same steps for FA Quick Addition for Expensed Asset Addition. Select the Asset type as
Expensed.

43
The asset type should be expensed, the moment expensed category is entered asset type by default
will become expensed. We can run the Generate asset trace program to check how data gets
populated in table.

44
 CHAPTER 5 Addition of CIP Asset Manually

Introduction to CIP Asset

A construction-in-process (CIP) asset is an asset you construct over a period of time. Create and
maintain your CIP assets as you spend money for raw materials and labor to construct them. Since a
CIP asset is not yet in use, it does not depreciate and is only in the corporate book. You can enable
the CIP in tax check box to have CIP asset also maintained in the tax book. When you finish building
the CIP asset, you can place it in service and begin depreciating it. You can track CIP assets in Oracle
Assets.

Steps to Create a CIP Asset

FLOWCHART:

Asset Asset
Assets
Responsibility Workbench

Enter asset type as Quick

CIP Addition/Additions

45
1. Navigation: Fixed Asset Manager Responsibility ->Assets -> Asset Workbench -> Quick Additions
or Additions (Detailed Additions)

2. Provide details and select asset type as CIP. CIP asset will be added with cost 0 by default as it is
construction in process and will not depreciate until it is CIP asset

46
3. Click Done and asset will be created.

For the above addition FA_ADJUSTMENTS table will not be populated.

47
Adding Source Lines to CIP Assets
You can track information about where assets came from, including sources such as invoice lines
from your accounts payable system and capital assets from Oracle Projects.

The source lines can be added for the CIP assets using two methods:

a. Manual Source Line Addition

There is a provision to manually enter the source line for the CIP asset.

Query the CIP asset from the Asset Workbench.

48
Click on the Source Lines button to add the source lines manually.

Enter the required details and click on Done.

49
 Query the CIP asset once again to check that the source line has been successfully added.

b. Adding Source lines from Payables or Projects using Add to Asset functionality

Data moved from Payables and Projects to Fixed Assets can be viewed from Prepare Mass
Additions. At this point, the Add to Asset functionality can be used to add a line to a CIP
asset as a cost adjustment.

50
Open the Prepare Mass Additions and select the line to be added to CIP. Once done, click on
Add to Asset Button.

Enter the CIP asset number to which the line is to be added and click on Find.

51
Select the line and click on Done.

The line will be added to the Cost Adjustment Queue

52
Run Post Mass Additions to add the source line to CIP asset. Query the CIP asset to check that
the Source line has been successfully added.

53
 CHAPTER 6 FA Addition from Accounts Payables

Introduction
Mass Additions lets you add assets and perform cost adjustments directly into Oracle Assets from
invoice information in Payables. The Create Mass Additions for Oracle Assets process sends valid
invoice line distributions and associated discounts from Payables to an interface table in Oracle
Assets.

The Mass Additions Create process is used to transfer invoice distributions in Payables to Fixed
Assets for tracking as an expensed asset, a CIP asset, or a capitalized asset

Pre-requisite - Mass Additions Create Rules for Import from Payables to

Fixed Assets
Mass Additions Create will only create mass addition lines under certain circumstances. Please check
that you have invoice lines that satisfy the following criteria.

Conditions for ASSET Invoice Line Distributions to be imported:

1. The line is charged to an account set up as an Asset account.

2. The account is set up for an existing Asset Category as either the Asset Clearing Account or
the CIP Clearing Account.
3. The Track as Asset check box is checked. (It is automatically checked if the account is an
Asset account).
4. The invoice is approved.
5. The invoice line distribution is posted to Oracle General Ledger from Payables.

The General Ledger date on the invoice line distribution is on or before the date you specify for the
Mass additions create (FAMACR ) program. If you use the multiple organizations feature, your
Payables operating unit must be tied to the same General Ledger as the corporate book for which
you want to run Conditions for EXPENSED Invoice Line Distributions to be imported:

1. The invoice line distribution is charged to an Expense account.

2. The Track As Asset box is manually checked.
3. The invoice is approved.
4. The invoice line distribution is posted to Oracle General Ledger from Oracle Payables.
5. The General Ledger date on the invoice line distribution is on or before the date you specify
for the FAMACR program.
6. Your installation of Payables must be tied to the same General Ledger as the corporate book
for which you want to run FAMACR.

54
Steps to perform FA Addition from Payables

FLOWCHART

Payables Run Mass Assets

Responsibility Additions Create Responsibility

Change Queue Review data and Mass Additions ->

Name to POST make changes Prepare Mass
Additions

Mass Additions ->

Post Mass
Additions

The Create Mass Additions for Oracle Assets process sends valid invoice line distributions and
associated discounts from Payables to an Interface table (FA_MASS_ADDITIONS) in Oracle Assets.
Then the lines can be reviewed to determine whether to create assets from those lines.

When Mass Addition Lines move from AP to FA, in R12, the tax and VAT lines are automatically
merged with the parent item line. Hence, lines from AP come in pairs in FA - A parent line along with
an associated child line (VAT, tax etc).

There is a feature available now to disable the Auto Merge function. The relevant note associated is
added to the List of important notes in the last chapter of this document.

55
SCREENSHOTS:

1. Create the invoice in the Payables Responsibility

2. Follow the conditions that need to be met for data to flow from Payables to Fixed Assets and
enter an asset account in distributions

56
3. Validate the invoice

Invoice is Validated.

57
4. Perform Accounting

5. Now, run the Mass Additions Create Program to move the data from Payables to Assets

58
6. Generate the Mass Additions Create Report to see the data that was moved to Assets:

7. In the Fixed Assets Responsibility ,navigate to Prepare Mass Additions to review the data
moved from Payables to Assets

59
8. Query the Book to which the invoice data was moved from Payables.

9. The mass addition line will be visible

60
10. Click on the Open button to view the details and make changes if required.

At this stage all the data is stored in the interface table: FA_MASS_ADDITIONS in the New
Queue.

11. Once all the data has been reviewed and required data changed , change the queue to POST and
save the work.

61
 Now the data is ready to be moved to the FA tables.

12. In order to post the data to FA tables, navigate to the Post Mass Additions

13. Select the parameters and run the program

62
14. Now, the asset has been created and can be reviewed from the Asset Workbench

63
64
 CHAPTER 7 FA Addition from Projects

Introduction to FA Addition from Projects

We can collect CIP costs for capital assets you are building in Oracle Projects. When you finish
building CIP asset, you can capitalize the associated costs as asset lines in Oracle Projects and send
them to Oracle Assets as mass addition lines. When you run the Interface Assets process, Oracle
Projects sends valid capital asset lines to the Mass Additions interface table in Oracle Assets. You
review these mass addition lines in Oracle Assets and determine whether to create assets from
them.

If you use Oracle Projects to build CIP assets, you do not need to create CIP assets in Oracle Assets.
For costs that originate in Oracle Payables, you should send CIP costs to Oracle Projects, and
capitalized costs to Oracle Assets.

Conditions for Project Information to Be Imported

For Oracle Projects to send asset lines to Oracle Assets, the asset line must meet these specific
conditions:

1. The actual date in service must fall in the current or a prior Oracle Assets accounting period
2. The CIP costs for summarized asset lines must be interfaced to Oracle General Ledger
3. The CIP costs for supplier invoice adjustments must be interfaced to Oracle Payables
4. A CIP asset must be associated with the asset line

A list of things to do in PA (Project Accounting)

1. Distribute all Expenses

2. Distribute Burden Costs
3. Post to GL (everything) and Tieback.
4. Summarize the costs (Update or Refresh Project Summary Amounts)
5. PRC: Generate Asset Lines
6. PRC: Interface Assets

It is after all the above has been completed that the lines will be sent to the FA_MASS_ADDITIONS
interface table.

65
In PA, there are two ways to define a Capital Project:

1. If you check the Require Complete Asset Definition box in the Setup Project
Types form, the asset lines will be sent to FA in the POST queue.
2. If you do not check the Require Complete Asset Definition box, the lines will
be sent over to FA in the NEW queue, and you will have to Prepare Mass
Additions lines fully before putting it in the POST queue.

Then in FA, run Post Mass Additions (FAMAPT) to create the assets.

Steps to perform FA Addition from Projects

FLOWCHART

Specify in
Create Project Define Asset service/Retireme
nt date

Generate Asset
Collect Cost
Lines

Review Cost and Review asset cost

Make line and make
adjustments adjustment

Interface Assets to
Oracle Assets

66
SCREENSHOTS

To interface assets lines from PA to FA:

1. Run concurrent program PRC: Interface Assets to Oracle Assets process

Once the concurrent request gets completed the lines will be interfaced to FA and we will be
able to check the same in FA_MASS_ADDITIONS table

67
2. Query it in mass additions window

3. Check the project details

68
 4. Run post mass addition to create asset.

Asset will be created after running post mass addition.

Data in table will look like:

FA_TRANSACTION_HEADERS

TRANSACTION TRANSACTION TRANSACTION

BOOK_TYPE_CODE DATE_EFFECTIVE
HEADER_ID TYPE_CODE DATE_ENTERED

31-DEC-1998 14-AUG-2015
ADB CORP 816201 CIP ADDITION
00:00:00 15:06:50

For CIP asset when depreciation is run the depreciation charged will be 0 until the asset is
capitalized.

For capitalizing CIP asset navigation followed will be:

Navigation: Asset responsibility -> Assets -> Capitalize CIP asset

CIP asset moves from Payables/Projects to Fixed Assets in pairs. The mass addition line appears in
Prepare Mass Additions in Oracle assets as a merged parent with a cost amount equal to zero. The
merged child includes the same description as that of the parent but includes the cost.

69
Select the asset and click capitalize

70
 CHAPTER 8 Addition Via WebADI

Introduction
Web ADI is a Browser based application, which enables users to log in to the Oracle Database, and
upload ADI spreadsheets, without having to have the ADI application loaded locally on the users
machine, or having it set up on a central server and users accessing it through Citrix.

For Web ADI to work, interfaces are set up. These interfaces are Macro driven spreadsheets, in
which specific cells are linked to database table columns, and match to fields in the Standard Oracle
Forms.

FA Addition integrator is used for mass upload of asset and populates addition interface tables

Pre-requisite Setup in Excel for WebADI

1. In the Excel go to Tool->Macro->Security --> trusted source tab. Enable the 'Approve Access
to Visual Basic Project' checkbox In Excel:
2. Open Excel.
3. Click the Office Button (top-left most button in the window)
4. Click the Excel Options button.
5. Click Trust Center in the menu on the left.
6. Click Trust Center Settings in the window on the right.
7. In the new window that opens click Macros in the menu on the left.
8. Check the box next to Trust Access to the VBA project object model.
9. Click OK.
10. Close all Office applications and re-open.

71
Steps to perform FA Addition via WebADI

FLOWCHART

Assets Mass Additions -> Enter all the

Responsibility Additions parameter values
Integrator

Mass Additions -> Enter data in the WebADI

Prepare Mass document and document is
Additions Upload created

Review the data Change the Mass Additions ->

and make Queue Name to Post Mass
changes POST Additions

72
SCREENSHOTS

1. Move to Assets Responsibility and Navigate to Asset Integrator

Navigation : Mass Additions -> Additions Integrator

73
2. Select the Book to which the asset is to be added and click on Continue.

3. Select the excel version in your system and click on Next

4. Select the Layout for the WebADI sheet as per your requirement and click on Next

5. The file will be downloaded

74
6. Open the file and on the Security Warning section click on the Options

7. For the Security Alert Macro : Enable the content so that the document can be
created

75
8. A popup will appear indicating that the document is being created

Document is created.

76
9. Enter the required data in the mandatory fields of the WebADI document.
Change the value of the Queue Name field to New

10. Now move to Add-Ins in the Menu Bar. Then Click on Oracle.

77
 11. Click on Upload to Upload the asset

12. A pop-up message will appear for the upload parameters

Select the options as per the requirement and click on Upload.

78
13. A pop-up will appear indicating that the asset is being uploaded

14. Once the row/rows is uploaded, the pop-up message will indicate the same

Now, the asset data has been loaded into the interface table : FA_MASS_ADDITIONS
in the New Queue.

79
15. For reviewing the asset and posting the same to the FA tables, please follow the
steps 7 to 14 of Additions from Accounts Payables section of this document.

80
 CHAPTER 9 Addition via API

Introduction to Addition via API

You can use the Additions API to add assets directly via PL/SQL rather than through the normal
Oracle Assets interfaces. The Additions API uses the FA_ADDITION_PUB.DO_ADDITION procedure.
You can use this API if you have a custom interface that makes it difficult to use with the existing
asset additions interfaces in Oracle Assets. Normally APIs are used in case of data conversion and
when bulk data is uploaded time to time.

Working addition API sample

Here when we load data via addition API in FA_TRANSACTION_HEADERS table calling interface is
populated as CUSTOM and if you are using apps schema to run the API then last updated by will be
populated as -1.

Rest everything will be same as normal asset creation from front end.

API parameters:

The Additions API procedure is called: FA_ADDITION_PUB.DO_ADDITION ().

The following table provides the arguments, types, value, and descriptions of the elements of the
FA_ADDITION_PUB.DO_ADDITION procedure.

Each argument has a prefix of P, X, or PX. These prefixes mean the following:

P - indicates an In argument
X - indicates an Out argument
PX - indicates an argument that is both In and Out

Rec groups for addition API which can be sued to add different type of data

Trans_rec_type: contains transaction type, transaction sub type, amortization start

date,calling interface and whos details
Asset_hdr_rec_type: contains asset_id and book_type_code
Asset_desc_rec_type: contains asset description like tag number, parent asset id,serial
number,asset_number and manufacturer details
Asset_type_rec_type: contains asset type like capitalize,cip,expense etc
Asset_category_rec_type: contains asset category details

81
 Asset_fin_rec_type: contains details like ,dpis,costlife of asset,deprn method,salvage value,
prorate convention, conversion date and global attributes
Asset_deprn_rec_type: contains ytd,deprn reserve and reval reserve
Asset_dist_rec_type: contains distribution details like unit assigned, assigned to expense
ccid and location ccid
Inv_rec_type: contains invoice information associated to asset like fixed asset cost ,invoice
number, po number, vendor id, payable cost, batch id, reserve details attribute values
Inv_rate_rec_type: contains conversion rate details and is normally used for MRC, have SOB
id, exchange rate, inv indicator is populated if mrc is used

Note: Refer metalink note: Oracle Assets Additions API Documentation Supplement (Doc
ID 232070.1) for more details

82
 CHAPTER 10 Flow of Data in Tables

Tables Associated with Oracle Assets Setup before Additions:

Table Name Table Details Linking Columns
between tables
FA_BOOK_CONTROLS Contains all the information that is inserted at the Book_Type_Code
Book Controls level. Deprn_Allocation_
A new row is added to this table for every newly Code
created book. Deprn_Calendar
Significant Fields: Prorate_Calendar
1. Deprn_Allocation_Code Signifies if
depreciation is to calculated on monthly
basis or daily basis
Values are:
a. E Evenly
b. D Daily
2. Deprn_Calendar Links to
FA_CALENDAR_TYPES.Calendar_Type.
3. Prorate_Calendar - Links to
FA_CALENDAR_TYPES.Calendar_Type
FA_BOOK_CONTROLS_ Contains all information that is inserted at the Book_Type_Code
HISTORY Book Controls level and record of any changes
made to the Book.
A new row is added to this table for every newly
created book.
It also stores date recorded changes made at the
Book Controls level to the Book.

FA_CATEGORIES_B Contains the information on the Asset Category as Category_ID

entered at the Asset Categories level.
A new row is added to this table for every new
category added.

FA_CATEGORIES_TL Contains language and description information of Category_ID

the Category
FA_CATEGORY_BOOKS This book contains the Asset Category and Book Category_ID
Combination information. Book_Type_Code
For every new book added to a category, a new
row is added to this table.
NOTE: One category can have multiple books
associated with it but one book can be associated
with only one category at a time.
FA_CATEOGORY_BOOK_ This book stores the Default Rules information Category_ID
DEFAULTS that is entered for the Category and Book Book_Type_Code
Assignment like Default depreciation method, Prorate_Convention
prorate convention code etc. _Code

83
 A new row is added to this table for every new Deprn_Method
Asset Category and Book Assignment, once the
default rules are entered.
There can be one default rule set up at a time for
an Asset Category and Book Combination. If it is to
be changed, then the earlier entry is end dated
and the new entry becomes effective from the
next date.
FA_FISCAL_YEAR This table holds the Fiscal Year information for Fiscal_Year_Name
every new Fiscal Year added to the system, the
start date and end date.

FA_CALENDAR_TYPES This table contains the information on the Calendar_Type

Depreciation and Prorate Calendars defined. Fiscal_Year_Name
FA_CALENDAR_PERIODS This table contains information on the periods for Calendar_Type
the Depreciation/Prorate Calendar Period_Name

FA_CONVENTIONS This table contains information on the Prorate Prorate_Convention

Conventions defined. _
Code
Prorate_Date
FA_METHODS This table contains information on the various Method_ID
depreciation methods defined Method_Code

Method_Code links
to
FA_CATEGORY_BOO
K_DEFAULTS.Deprn
_Method
FA_RATES This table holds the information on the rates Method_ID
defined for Depreciation methods.
Links to FA_METHODS.Method_ID
FA_EMPLOYEES This table contains the information on the Employee_ID
Employees to be assigned to Assets.
Significant Fields:
1. Employee_ID
2. Employee_Number
3. Name
FA_LOCATIONS This table contains the location information for Location_ID
the Asset Assignments.
Significant Fields:
1. Location ID
GL_CODE_ Includes information on Code Combination ID and Code_Combination_
COMBINATIONS Segments ID
FA_SYSTEM_CONTROLS Contains information on the System Controls Company_Name
Setup done at the Oracle Assets Implementation

84
 Flow of Data in Fixed Asset Tables Associated with Asset Additions:
Table Name Table Details Linking Columns
between tables
FA_ADDITIONS_B This table holds the basic asset information like: Asset_ID
Asset_ID
Asset_Number
Asset_Type
Asset_Category_ID Links to FA_CATEGORIES_B

One row is added to this table for every asset at its

creation.

FA_ADDITIONS_TL This table holds the Asset Description and Asset_ID

Language details.
One row is added to this table for every asset at its
creation.

FA_TRANSACTION_ This table holds all the transaction information for Transaction_Header
HEADERS the asset. _ID
Unique field is the Transaction_Header_ID Book_Type_Code
For every asset addition, two rows are added to Asset_ID
this table of two types of Transaction_Type_Code
1. Addition
2. Transfer In
For CIP Assets, an addition row is added of
Transaction_Type_code:
3. CIP Addition

This table also holds a vital field Calling_Interface

which helps to determine from which source the
asset has been created. The values under it are:
1. FAXASSET Created from Asset
Workbench which means via Quick
Addition or Detailed Addition
2. FAMAPT Created using Mass Additions
which means via Mass Additions Create
from Payables, Projects or WebADI from
Asset Integrator. (The details on whether
it is created from WebADI or Payables can
be determined from subsequent tables)
3. CUSTOM Created using API

FA_ASSET_HISTORY This table stores asset history information in terms Asset_ID

of any changes made to the following:
1. Category_ID
2. Units

85
FA_DISTRIBUTION_ This table holds the Asset Assignment information Distribution_ID
HISTORY that is entered during asset additions under
Assignments: Employee_ID
Assigned To Employee_ID (Links to Location_ID
FA_EMPLOYEES table) Code_Combination_
Location Location_ID (Links to FA_LOCATIONS ID
table)
Depreciation expense account Transaction_Header
Code_Combination_ID (Links to _ID_in
GL_CODE_COMBINATIONS) Transaction_Header
_ID_Out
This table adds a new row for every change that is
applied on any of the three assignments.
For every change, it sets a new
Transaction_Header_ID_Out for the first row
(signifying the end of the first
Distribution/Assignments) and adds a new row
with a new Transaction_Header_ID_In. In this way
it links to the FA_TRANSACTION_HEADERS table.

Along with the above, for every new row

(signifying a change in the Assignments) a new
Distribution ID is generated.

FA_ADJUSTMENTS This table stores all the accounting entries Transaction_Header

corresponding to the Financial Transactions _ID
performed on the Asset. Book_Type_Code
The significant fields are: Asset_ID
1. Transaction_Header_ID Links to Distribution_ID
FA_TRANSACTION_HEADERS table Period_Counter_Cre
2. Source_Type_Code Signifies the type of ated
transaction. In this case ADDITION
3. Adjustment_Type The account to which
the entry is passed. For Addition, there are
two accounts to be hit:
a. Cost
b. Cost Clearing
4. Debit_Credit_Flag Signifies whether a
Debit Or Credit is performed on the
account.
5. Adjustment_Amount The amount that is
accounted. In this case, the cost of the
asset.
6. Distribution_ID Links to the
FA_DISTRIBUTION_HISTORY (Signifying the
Assignments to which the asset is
associated with)
7. Period_Counter_Created The period in

86
 which the asset is added. This links to the
FA_DEPRN_PERIODS.Period_Counter.

For Addition, this table creates two rows as per

the two accounting entries associated with
Addition:
1. Cost
2. Cost Clearing

FA_BOOKS This table holds all the Books level information Book_Type_Code
associated with the Asset: Asset_ID
Cost Prorate_Convention
Adjusted Cost _Code
Salvage Value Deprn_Method_Co
Date Placed In Service de
Prorate_Convention_Code Links to
FA_CONVENTIONS
Deprn_Method_Code links to
FA_METHODS.Method_Code
Life_In_Months
Depreciate_Flag Yes/No. This helps to determine
if the asset is depreciable or not depending on
which the depreciation for the asset will run.

This table adds a new row for every change that is

applied on the Books Level for the asset.
For every change, it sets a new
Transaction_Header_ID_Out for the first row
(signifying the end of the first Books entry) and
adds a new row with a new
Transaction_Header_ID_In. In this way it links to
the FA_TRANSACTION_HEADERS table.
FA_DEPRN_SUMMARY This table gives the Depreciation Summary Book_Type_Code
Information for the asset. Period_Counter
It contains a row for every period associated with Event_ID
the Asset as per its addition.
Significant Fields:
1. Period_Counter Links to
FA_DEPRN_PERIODS
2. Deprn_Source_Code This signifies the
data entered at the Books Level for the
Asset and the date entered by the
Depreciation Run. Values:
a. Books Shows data added at Book
Level

b. Deprn Shows data added by the

Depreciation Run

87
 3. Deprn_Run_Date
4. Deprn_Amount Amount that
depreciated
5. YTD Depreciation The total depreciation
amount for the asset from the beginning
of the current fiscal year till the current
period.
6. Depreciation_Reserve The total
depreciation of the asset till current
period.
7. Adjusted_Cost The adjusted cost on
which the depreciation is calculated.
8. Deprn_Adjustment_Amount Includes
any value relevant to catch-up calculation
for the asset
9. System_Deprn_Amount The actual
depreciation amount calculated by the
System
10. Event_ID Links to the
XLA_EVENTS.Event_ID.
FA_DEPRN_DETAIL This table stores Depreciation Information for the Book_Type_Code
asset based on Distribution_ID and Asset_ID
Period_Counter. Distribution_ID
1. Distribution_ID Links to Period_Counter
FA_DISTRIBUTION_HISTORY.Distribution_I
D
2. Period_Counter Links to
FA_DEPRN_PERIODS.Period_Counter

It contains the same information as

FA_DEPRN_SUMMARY table.

FA_ASSET_INVOICES This table contains information specific to Asset Prorate_Convention

added via External Sources. _Code
Significant Fields: Prorate_Date
1. Source_Line_ID Associated with the
Source lines for the asset based on the
external source from which it is added
2. Invoice_ID If asset is added from
Payables
3. Invoice_Number If asset is added from
Payables
4. Feeder_System_Name Indicates the
source of the asset addition. Values are:
c. Spreadsheet For WebADI upload via
Asset Integrator
d. Payables For upload from Payables
using Create Mass Additions

88
 e. Projects For upload from Projects

FA_DEPRN_PERIODS Contains the Depreciation periods information Period_Counter

from the period when the book was created till
the current open period.
Significant Fields:
1. Period Counter
2. Period Open Date
3. Period Close Date
4. Deprn_Run Y means that the
Depreciation has run for this period

The depreciation of the asset is run for these

periods.

FA_MASS_ADDITIONS This is an Interface table that holds the Mass_Addition_ID

information of the Asset Addition from Other Queue_Name
Sources. This table is common to addition from Posting_Status
Payables and Projects. From Payables and
Projects, the information is first stored to this
interface table and then moved to the Fixed Asset
base tables after the Post Mass Additions program
is run.
Significant Field:
1. Mass_Addition_ID - Every line generated
from the external source is assigned this
2. Posting_Status Signifies the posting
status of the line
3. Queue_Name
5. Feeder_System_Name - Indicates the
source of the asset addition. Values are:
f. Spreadsheet For WebADI upload via
Asset Integrator
g. Payables For upload from Payables
using Create Mass Additions
h. Projects For upload from Projects
FA_MASSADD_DISTRIBUT This table contains the Distribution/Assignments Massadd_Distributi
IONS information for the asset as provided from the on_ID
external source Mass_Addition_ID
Significant Fields: Employee_ID
1. Massadd_Distribution_ID Location_ID
2. Mass_Addition_ID Links to Deprn_Expense_CCI
FA_MASS_ADDITIONS.Mass_Addition_ID D
3. Deprn_Expense_CCID Links to
GL_CODE_COMBINATIONS.Code_Combina
tion_ID
4. Location_ID Links to
FA_LOCATIONS.Location_ID

89
 5. Employee_ID Links to
FA_EMPLOYEES.Employee_ID

Screenshot of a Sample Asset Trace showing flow of data into tables

1. Manual Addition

90
2. Addition from other sources

91
92
E-R Diagram of the Data Flow In Fixed Asset Tables

93
 CHAPTER 11 Accounting entries and Create Accounting details

Accounting Entries and Creating Accounting details

For all Fixed Assets Addition types, the accounting entry remains the same:

Account Name Debit / Credit

Cost DR
Cost Clearing CR

Tables populated post Create Accounting Assets program run

Post running create accounting data in XLA table and accounting

XLA_EVENTS

BUDGETA
EVENT_ EVENT_ST PROCESS_S
EVENT ENTITY EVENT_ RY CREATE CREATIO
TYPE ATUS TATUS
_ID _ID DATE CONTROL_ D_BY N_DATE
CODE CODE CODE
FLAG

01-MAY- 18-MAY-
30209 26608 ADDITIO
P P 2015 N 11510 2015
3 5 NS
00:00:00 15:56:58

Once create accounting is run events are in P/P status and below tables are populated with data.

XLA_AE_HEADERS -> Stores details when data is transferred to GL and GL transfer status code and
based on ae_header_id and xla_ae_lines table is populated which also covers accounting entries

ACCOUN
GL_TRAN
EVENT_T ACCOUN GL_TRAN JE_CATEG TING
AE_HEADE EVENT LEDGER SFER
YPE TING SFER ORY ENTRY_S
R_ID _ID _ID STATUS_C
CODE DATE DATE NAME TATUS
ODE
CODE

01-MAY- 18-MAY-
30209 ADDITIO
70023 2050 2015 Y 2015 Addition F
3 NS
00:00:00 16:27:24

94
 XLA_AE_LINES

GL_TR
ANSFE
CODE
AE_HEAD AE_LINE_N LEDGE ENTERE ENTERE ACCOUN ACCOUNTED R
COMBINA
ER_ID UM R_ID D_DR D_CR TED_DR _CR MODE
TION_ID
_COD
E

70023 1 2050 2679 49300 49300 S

70023 2 2050 107584 49300 49300 S

CURREN GL_
AE_HE CY DISPLAY FUNDS_ GAIN_OR SL_L
AE_LINE LEDGE DESCRIP GL_SL_LI
ADER_I CONVER ED_LINE STATUS _LOSS INK
_NUM R_ID TION NK_ID
D SION NUMBER CODE FLAG TAB
TYPE LE

Addition
Cost - XLAJ
70023 1 2050 1 N 120085
31-MAY- EL
15

Addition
Cost
XLAJ
70023 2 2050 Clearing 2 N 120086
EL
- 31-
MAY-15

Here, this table also shows the accounts getting affected like asset cost is debited and asset clearing
account in credited

95
 CHAPTER 12 Forms and PLS files

List of relevant forms and PLS files along with the latest version number
Form version as per latest
Form/PLS Name FMB/PLS Name
RPC(Aug-15)

Asset workbench 120.208.12010000.126 FAXASSET.fmb

Mass Addition 120.133.12010000.81 FAXMADDS.fmb

FA_MASSADD_CREATE_PKG 120.14.12010000.31 FAMADCB.pls

FA_MASSADD_PKG 120.32.12010000.10 FAMAPTB.pls

FA_CHK_BOOKSTS_PKG 120.20.12010000.8 FAXCKBKB.pls

FA_ASSET_CALC_PVT 120.138.12010000.85 FAVCALB.pls

FA_CALC_DEPRN_BASIS1_PKG 120.67.12010000.38 faxcdb1b.pls

FA_INS_DETAIL_PKG 120.7.12010000.19 FAXINDDB.pls

FA_ADDITION_PVT 120.42.12010000.27 FAVADDB.pls

FA_CDE_PKG 120.90.12010000.67 FACDEB.pls

FA_CIP_PUB 120.18.12010000.5 FAPCIPB.pls

FA_ASSET_VAL_PVT 120.69.12010000.84 FAVVALB.pls

FA_ADDITION_PUB 120.27.12010000.24 FAPADDB.pls

96
 CHAPTER 13 Common notes to refer for FA Addition

Notes on Mass addition

Understanding Mass Additions Create (APMACR) and Troubleshooting from FA Perspective (Doc ID
1070597.1)

R12.1 Mass Additions Create (APMACR) Non-Recoverable Tax Lines From Payables (AP) Not
Transferring To Fixed Assets (FA) After Patch 9001504 (Doc ID 1155907.1)

Automatic Preparation Of Mass Additions In Release 12 (Doc ID 558059.1)

R12 Poor Performance In Mass Additions Create (FAMACR) (Doc ID 1459644.1)

AP Invoices In Mass Additions Create Transferring For Disabled Categories (Doc ID 1596100.1)

Mass Additions Not Interfacing Freight Lines (Doc ID 748822.1)

Prepare Mass Additions After Merge the Parent Line is Still in New Status and Queue (Doc ID
356220.1)

How to Bring AP Invoice Attachments Through The FA Mass Additions Process? (Doc ID 283163.1)

How is Default Date Placed In Service (DPIS) in Mass Additions Determined? (Doc ID 1016162.102)

Post Mass Additions Concurrent Program Ends In Error For No Reason After The First Row (Doc ID
1342515.1)

Troubleshooting Assistant: Create Mass Additions From Payables (AP) to Fixed Assets (FA) (Doc ID
1609542.2)

Troubleshooting Assistant: FAMAPT - Post Mass Additions (Doc ID 1610669.2)

How To Include Non recoverable Tax In Mass Additions In R12? (Doc ID 559980.1)

How To Update Mass Addition Line to Future DPIS if the Invoice Date in AP is from the Current FA
Period? (Doc ID 423124.1)

Mass Additions Create FAQ's (Doc ID 125614.1)

Mass Additions Post Errors With ORA-01476: Divisor Is Equal To Zero (Doc ID 1934519.1)

Mass Additions Post (FAMAPT) FAQs (Doc ID 133277.1)

General Guidelines for Preparing Mass Additions (FAXMADDS) (Doc ID 200082.1)

How to Disable the 'Auto-Merge' Feature for Create Mass Additions in R12.1? (Doc ID 1540186.1)

97
Notes on Projects to FA
Interfacing From Oracle Projects to Oracle Assets (Doc ID 103217.1)

Interfacing Asset Lines from Projects, Adjustment Line Changes Description To All in FA (Doc ID
795743.1)

Interfacing From Oracle Projects to Oracle Assets (Doc ID 103217.1)

Oracle Assets FAQ: Capital Projects Integration (Doc ID 69358.1)

Assets Created in Projects and Interfaced to FA Do Not Appear in Mass Additions (Doc ID 1086268.6)

Mass Addition Line With 0 Cost Created After Running PRC: Interface Assets To Oracle Assets From
Oracle Projects (Doc ID 312031.1)

Notes on FA Addition via workbench

Performance Issue When Trying To Save A New Asset Addition Record In Asset Workbench
FAXASSET (Doc ID 360512.1)

ASSET ADDITION ERRORS IN ASSET WORKBENCH - BOOKS FORM WITH APP-48024 (Doc ID
1048670.6)

In Asset Workbench Is Not Possible Find an Asset After It Is Added Using Quick Addition Feature
(Doc ID 214412.1)

Unable To Add Assets Using Asset Workbench (Doc ID 1255105.1)

Troubleshooting The Asset Workbench Form (FAXASSET) (Doc ID 784285.1)

R12 Asset Workbench (FAXASSET): Quick Additions Errors With 'Please choose an existing
combination' And 'FRM-41106' Before Saving The Asset (Doc ID 789396.1)

R12 Asset Workbench (FAXASSET): Errors With 'APP-OFA-48392: You cannot assign reserve to an
asset placed in service in the current period' (Doc ID 1187923.1)

How to Add Assets With Future 'Date Placed In Service' in Fixed Assets? (Doc ID 1664862.1)

Unable To Save Data In Assets Invoices DFF In Asset Workbench (Doc ID 553110.1)

98
Notes on FA Addition via Web ADI
Web ADI Upload Errors With 'Invalid Value For Unit Of Measure' (Doc ID 1565062.1)

Cannot Enter Parent Asset Number In Web ADI List of Values (Doc ID 1514570.1)

Missing Web ADI Assets Layout (Doc ID 1474521.1)

R12 Web Adi: Upload Fails With "0: Please Choose An Existing Combination" (Doc ID 1376295.1)

Unable to Upload Amortized Assets Using Web ADI (Doc ID 1447998.1)

How To Add DFF In Web ADI For The Fixed Assets Addition Integrator In R12? (Doc ID 863503.1)

Web ADI Create Document: oracle.apps.bne.exception.BneFatalException: A system error has

occurred (Doc ID 1429824.1)

Loading Asset Data Through Web ADI is Taking Long Time (Doc ID 1323339.1)

Web ADI Unable To Upload Context-Sensitive DFF Data Using Additions Integrator (Doc ID
1662381.1)

How To Enter Descriptive Flexfield Values (DFF) In Web ADI? (Doc ID 953563.1)

R12 Web ADI Errors With "No Rows Uploaded" and "One Row Was Invalid" (Doc ID 957848.1)

Assets FAQ - Web ADI (Doc ID 883250.1)

How To Define a Custom Layout for the Web ADI Asset Addition Integrator in Oracle Assets? (Doc ID
1227673.1)

Web ADI and Create Assets/Additions Functionality: What Patches to Apply? (Doc ID 311045.1)

Web ADI Asset Key Flexfield Column is not Mandatory (Doc ID 754599.1)

WEB ADI: Mass Additions Post Process Not Picking Up Any Records to Post (Doc ID 734430.1)

MASS_ADDITION_ID is NULL When Load Asset with WEB ADI (Doc ID 1932921.1)

Web ADI: FA Additions Integrator: You Do Not Have Permission To Access This Functionality (Doc ID
311565.1)

Is Web ADI Certified for UTF8? (Doc ID 373704.1)

Web ADI Additions Integrator Creating Blank Worksheet (Doc ID 1356469.1)

99
Notes on Expense asset
R12 Upgrade For SLA Processes Expensed Asset Transactions (Doc ID 1168929.1)

R12 Prepare Mass Additions (FAXMADDS): Asset Type "Expensed" Missing In The List Of Values
(LOV) (Doc ID 1272710.1)

How To Add Expensed Asset in AP Through Create Mass Additions? (Doc ID 296713.1)

Can the Expensed Assets Be Uploaded Using Web ADI Addition Integrator With Asset Clearing
Account of Expense Type in R12? (Doc ID 1299934.1)

Is it Possible to Add an Expensed Mass Addition to a Non Expensed Asset? (Doc ID 1319284.1)

"Expense Type" Asset Does Not Generate Journals in GL (Doc ID 1472995.1)

How To Copy Expensed Assets To Tax Books (Doc ID 302881.1)

System Creates Journal Entries For Asset Type Expense Addition (Doc ID 456100.1)

How To Expense Existing CIP Assets Vs Capitalization? (Doc ID 333579.1)

Events Are Created For Expensed Assets In SLA (Doc ID 944909.1)

Unable To Add 'Expense' Source Line To A 'Capitalized' Asset (Doc ID 302882.1)

How to change an asset category to expensed (Doc ID 1062440.6)

100