Professional Documents
Culture Documents
Asset Tables
High-Level Overview
FA_ADDITIONS_TL - This table maintains the asset description and language, fields include:
Asset_ID Description
Language Etc.
Source_Lang
Asset_ID
Asset_Number (unique number with in system and may or may not be the same
value as the asset_id depends upon your numbering convention)
Tag_Number (unique number with in system)
NOTE: That the asset category or asset key values are captured from this table, you will
however capture the ID number and will need to link to the respected Key Flexfield tables to
capture the actual values. This will be discussed in the Key Flexfield Tables section.
The Asset_ID and Book_type_code are key fields when extracting details this identifies
which asset record(s) and depreciation book the details should come from. This table
maintains detail that can often change due to retirements, cost adjustments, or other financial
adjustments. Therefore, in order to contain the correct information, there are two fields that
should always be included when capturing data from this table these two fields will capture
the latest financial information for an asset:
Transaction_Header_id_out
Date_Ineffective
Without the above lines, it is possible for Oracle to return more than one row for an asset,
depending on the transactions that have occurred on the asset.
NOTE: Depreciation details are NOT captured on this table, this information housed on
depreciation tables which will be discussed in a later section.
The Asset_ID and Book_type_code are key fields when extracting details this identifies
which asset record(s) and depreciation book the details should come from. This table
maintains detail that can often change due to retirements and/or transfers. Therefore, in order
to contain this information, there are two fields that should always be included when
capturing data from this table these two fields will capture the latest financial information for
an asset:
Transaction_Header_id_out
Date_Ineffective
Without the above lines, it is possible for Oracle to return more than one row for an asset,
depending on the transactions that have occurred on the asset.
Actual segment values are not maintained on this table the internal IDs numbers are
maintained and then a link the respected Key Flexfield tables are required to capture the
actual segment values. This is discussed in the Key Flexfield section.
Oracle assets do not house accounting combinations this is maintained in Oracle General
Leger therefore, a link into General Ledger is required to capture accounting combination
information. This is discussed in the General Ledger Key Tables for Assets sections.
Select FAD.Asset_Number,
FAD. Description,
FAB.Date_Placed_In_Service,
FAB.Cost,
FDH.Location_ID,
FDH.Code_Combination_ID
From FA_ADDITIONS FAD,
FA_BOOKS FAB,
FA_DISTRIBUTION_HISTORY FDH
Where FAD.asset_id = FAB.asset_id
AND FAB.book_type_code = OPS CORP
AND FAB.transaction_header_id_out is null
AND FAB. date_ineffective is null
AND FAB.asset_id = FDH.asset_id
AND FAB.book_type_code = FDH.book_type_code
AND FDH.transaction_header_id_out is null
AND FDH. date_ineffective is null
There are two main tables that house the monthly calculated depreciation for all assets.
These two tables work as follows: For every depreciation period, Oracle creates a new record
for every asset/book combination as long as the combination is depreciating. Meaning once
an asset is fully depreciated Oracle will stop creating records for that asset for future
depreciation periods, even though it is still active.
These tables will grow quickly, depending upon the number of assets it is critical to ensure
that you designate enough table space for these two tables.
The Asset_ID and Book_type_code are key fields when extracting details this identifies
which asset record(s) and depreciation book the details should come from.
The Asset_ID and Book_type_code are key fields when extracting details this identifies
which asset record(s) and depreciation book the details should come from.
Book_type_code
Period_Name
Period_Counter (identifies the depreciation period)
The Book_type_code is the key field when extracting details this is used to identify which
depreciation period to capture data for.
When capturing depreciation details he results should reconcile to the Oracle Journal Entry
Reserve Ledger report or the Tax Reserve Ledger report both are standard reports. If you do
not reconcile, the extract script is incorrect.
To only report on active assets, enter the following in the where clause for the FA_BOOKS
table:
AND FA_BOOKS.preiod_counter_fully_retired is null
FA_ASSET_KEYWORDS
FA_CATEGORIES_B
FA_CATEGORY_BOOKS
FA_CATEGORY_BOOK_DEFAULTS
FA_LOCATIONS
Code_Combination_ID Segment6
Segment1 Segment7
Segment2 Segment8
Segment3 Segment9
Segment4 Segment10
Segment5
Prior to R12 the ID field was called the Asset_Key_CCID, Oracle has changed the name to
Code_Combination_ID which is the same name used in Oracle General Ledger for accounting
information therefore it may be confusing when discussing the required data that needs to
be captured it is critical to know from what table the data is housed to avoid any confusion.
FA_CATEGORIES_B - This table maintains the segment values that have been defined for
the Category Flexfield. This table does not maintain descriptions descriptions for key
flexfield segment values are maintained on FND tables, which will be discussed in a later
section. The information housed on this table corresponds to the Asset Category
Combinations form (Navigation Path: Navigator, Setups, Asset System, Asset Categories).
This table houses fields such as:
Category_ID Segment4
Segment1 Segment5
Segment2 Segment6
Segment3 Segment7
Category_ID CIP_cost_acct
Book_type_code Deprn_expense_acct
Asset_clearing _acct Deprn_reserve_acct
Asset_cost_acct Etc.
CIP_clearing_acct
The Category_ID and Book_type_code are key fields when extracting details this identifies
which asset record(s) and depreciation book the details should come from.
Category_ID Deprn_method
Book_type_code Life_in_months
Start_DPIS Prorate_convention_code
End_DPIS Retirement_prorate_convention
Depreciate_flag Etc.
The Category_ID and Book_type_code are key fields when extracting details this identifies
which asset record(s) and depreciation book the details should come from.
Location_ID Segment4
Segment1 Segment5
Segment2 Segment6
Segment3 Segment7
The Location_ID is the key field when extracting details this identifies which asset record(s)
and depreciation book the details should come from.
FA_BOOK_CONTROLS - This table maintains the depreciation book details that have been
defined for the Depreciation Book. The information housed on this table corresponds to the
Book Controls form (Navigation Path: Navigator, Setups, Asset System, Book Controls). This
table houses fields such as:
Book_type_code Set_of_books_id
Book_type_name Etc.
GL_CODE_COMBINATIONS - This table maintains the segment values that have been
defined for the Accounting Flexfield. This table only houses the segment values NOT
descriptions descriptions for key flexfield segment values are maintained on FND tables,
which will be discussed in a later section.
Code_combination_ID Segment4
Account_type Segment5
Detail_posting_allowed_flag Segment6
Detail_budgeting_allowed_flag Segment7
Segment1 Segment8
Segment2 Segment9
Segment3 Segment10 Segment30
Ledger_id Chart_of_accounts_id
Name Currency_code
Short_name Etc.
Description
Ledger_id Chart_of_accounts_id
Name Currency_code
Short_name Etc.
Description
GL_JE_HEADERS - This table maintains the header details for a journal entry. The
information housed on this table corresponds to the Book Controls form (Navigation Path:
Navigator, Journals, Enter, [Query Journal]). This table houses fields such as:
JE_Header_id JE_Category
JE_batch_id JE_Source
Ledger_id Currency_Code
Period_Name Etc.
Vendor_id
Vendor_name
AP_INVOICES_ALL - This table maintains the invoice detail information entered in the system
is owned by Payables, contain fields such as:
Invoice_id Invoice_amount
Vendor_id Vendor_site_id
Invoice_num Description
Set_of_books_id Etc.
Invoice_currency_code
When requiring invoice details link the FA_ASSET_INVOICE table to this table to capture
additional desired details.
Copyright 2010 Chi-Star Technology
-33-
Other Application Key Tables
PA_PROJECTS_ALL - This table maintains the project related detail information entered in
the system is owned by Projects, contain fields such as:
Project_id
Name
Description
Etc.
PA_TASKS - This table maintains the task details for a project entered in the system is
owned by Projects, contain fields such as:
Task_id
Project_id
Task_number
Task_Name
Description
Etc.
NOTE: Use the PA tables when project related information is required to be extracted for
assets.
Copyright 2010 Chi-Star Technology
-34-
Other Application Key Tables
HR_EMPLOYEES - This table maintains the task details for a project entered in the system
is owned by Projects, contain fields such as:
Employee_id
Employee_num
Full_name
First_name
Middle_name
Last_name
Etc.
NOTE: Use this table when assets have been assigned to an employee. You will link the
FA_DISTRIBUTION_HISTORY table to this table to capture the employee information.
Meetings (Semi-Annual)
OAUG Conference
OpenWorld Conference
http://assetsig.oaug.org
LinkedIn: http://www.linkedin.com/groups?gid=2202521