2013 09 18usercommwebinarseries10pdf

Understanding
Asset Tables
High-Level Overview
Core Asset Tables

Depreciation Tables
Key Flexfield Tables
Other Key Asset Tables
General Ledger Key Tables
Subledger Accounting Key Tables
Other Application Key Tables
Key FND Tables
Great Sources for Information
Copyright 2010 Chi-Star Technology

-2-
Core Asset Tables
The core asset tables house the main information for all assets. In order to have an
understanding technically about assets, we will also discuss the forms and functional side as
well. Oracle being an integrated application, it is difficult to be only technical or only
functional, it is ideal to have an understanding of both to better achieve your desired results.

-3-
Core Asset Tables
FA_ADDITIONS
The FA_ADDITIONS table is still available at the APPS level, however in order to accommodate
multiple language platforms, Oracle has created a separate table that maintains the language
and asset description. The information housed on these table correspond to the Asset Details
form (Navigation Path: Navigator, Assets, Asset Workbench, [Query Asset], Open (Button)).
The following additions table houses the following details:
FA_ADDITIONS_B This table maintains the descriptive information on assets, fields such as:
Asset_ID Asset_Keywords_CCID
Asset_number Serial_Number
Tag_number Asset_Type
Asset_Category_ID Etc.
FA_ADDITIONS_TL - This table maintains the asset description and language, fields include:
Asset_ID Description
Language Etc.
Source_Lang

-4-
Core Asset Tables
Oracle uses internal IDs to link information for a record from multiple tables. The Asset_ID is
the main ID number that is used to link to tables within Assets to capture details for an asset
record. With that said, it should be understood that every asset could have up to 3 unique
identifiers:
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.

-5-
Core Asset Tables
FA_BOOKS - This table maintains the financial information for an asset by book. The
information housed on this table correspond to the Books form (Navigation Path: Navigator,
Assets, Asset Workbench, [Query Asset], Books (Button)). The FA_Books table houses fields
such as:
Asset_ID Deprn_Method_Code
Book_Type_Code Life_In_Months
Cost Depreciate_Flag
Date_Placed_In_Service Etc.
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

-6-
Core Asset Tables
The above fields should be included in the where clause of all SQL scripts extracting data
from the FA_BOOKS table, the lines should read as follows:
and fa_books.transaction_header_id_out is null

and fa_books.date_ineffective is null
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.

-7-
Core Asset Tables
FA_Distribution_History - This table maintains the distribution information for an asset by
book. The information housed on this table correspond to the Assignments form (Navigation
Path: Navigator, Assets, Asset Workbench, [Query Asset], Assignments (Button)). This table
houses fields such as:
Asset_ID Code_Combination_ID depreciation expense account combination

Distribution_ID Location_ID
Book_Type_Code Etc.
Employee_ID
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

-8-
Core Asset Tables
The above fields should be included in the where clause of all SQL scripts extracting data
from the FA_DISTRIBUTION_HISTORY table, the lines should read as follows:
and fa_distribution_history.transaction_header_id_out is null

and fa_distribution_history.date_ineffective is null
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.

-9-
Core Asset Tables
Linking the Core Tables
This is an example of extracting descriptive, financial and distribution information for an asset
record(s):
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

-10-
Depreciation Tables
The depreciation tables house the main depreciation information for all assets and books. In
order to have an understanding technically about assets, we will also discuss the forms and
functional side as well. Oracle being an integrated application, it is difficult to be only
technical or only functional, it is ideal to have an understanding of both to better achieve your
desired results.
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.

-11-
Depreciation Tables
FA_DEPRN_DETAIL
This table maintains the depreciation information on assets at the distribution level by book
and period counter. The distribution level is made up by the employee_id,
code_combination_ccid and location_id from the FA_DISTRIBUTION_HISTORY table. Since
the data is at the distribution level, if you maintain assets that have multiple distributions (i.e.
the depreciation is split between multiple Cost Centers) then this table will show the asset
Cost, Depreciation, YTD Depreciation, Accumulated Depreciation for the asset for each
distribution line. Oracle will allocate the appropriate amount of cost to each distribution,
therefore not duplicating the asset cost. Data is also maintained at the period counter, the
period counter is a numeric value that represents a period. This table does not know SEP-
2009, it requires a period_counter, which needs to come from the FA_DEPRN_PERIODS table.
SEP-2009 equals 10987 this is the counter which is required to capture the depreciation
details from this table for SEP-2009. This table houses fields such as:
Asset_ID Depreciation_amount (monthly depreciation)
Book_type_code YTD_depreciation
Period_Counter (identifies the depreciation period) Deprn_reserve (Accumulated Depreciation)
Cost Distribution_ID
which asset record(s) and depreciation book the details should come from.

-12-
Depreciation Tables
FA_DEPRN_SUMMARY
This table maintains the depreciation information on assets at the asset level by book and
period counter. Data is maintained at the period counter, the period counter is a numeric
value that represents a period. This table does not know SEP-2009, it requires a
period_counter, which needs to come from the FA_DEPRN_PERIODS table. SEP-2009 equals
10987 this is the counter which is required to capture the depreciation details from this table
for SEP-2009. Notice that this table does not maintain distribution level detail, this is the main
difference between the two depreciation tables. The impact of not maintaining distribution
level details is if you maintain assets that have multiple distributions (i.e. the depreciation is
split between multiple Cost Centers, then this table will show the asset Cost, Depreciation,
YTD Depreciation, Accumulated Depreciation for the asset for each distribution line). This
table will not split the asset(s) between distributions. This table houses fields such as:
Asset_ID Depreciation_amount (monthly depreciation)
Book_type_code YTD_depreciation
Period_Counter (identifies the depreciation period) Deprn_reserve (Accumulated Depreciation)
Cost

-13-
Depreciation Tables
FA_DEPRN_PERIODS
This table maintains the depreciation calendar information for each depreciation book. This is
the mapping between a period name and period counter, period name of SEP-2009 equals
period counter 10987. This table houses fields such as:
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.

-14-
Depreciation Tables
Linking the Core Tables to Depreciation Tables
record(s):
Where FAD.asset_id = FAB.asset_id

AND FAB.asset_id = FDD.asset_id
AND FAB.period_counter_fully_retired is null
AND FAB.book_type_code = FDD.book_type_code
AND FDD.period_counter = (select MAX(period_counter)
from fa_deprn_detail fdd2
where FDD.asset_id = fdd2.asset_id
and FDD.book_type_code = fdd2.book_type_code)

-15-
Depreciation Tables
TIPS:
When capturing depreciation details, the script needs to have logic built-in in order to capture
the desired details.
Remember Once an asset is fully reserved it stops creating records in future periods,
therefore, in order to capture accurate details you need to capture the last (MAX) record for all
asset records for a specified book. This will capture asset depreciation details for assets that
are fully reserved. If this information is not captured, then the extract will not reconcile with
standard oracle reports.
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
This will remove retired asset from the output.

-16-
The Key Flexfield tables house the information associated with the key flexfield segments
defined in the application for all assets. In order to have an understanding technically about
assets, we will also discuss the forms and functional side as well. Oracle being an integrated
application, it is difficult to be only technical or only functional, it is ideal to have an
understanding of both to better achieve your desired results.
FA_ASSET_KEYWORDS
FA_CATEGORIES_B
FA_CATEGORY_BOOKS
FA_CATEGORY_BOOK_DEFAULTS
FA_LOCATIONS

-17-
FA_ASSET_KEYWORDS - This table maintains the segment values that have been defined
for the Asset Key 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 Key Combinations
form (Navigation Path: Navigator, Setups, Asset System, Asset Keys). This table houses
fields such as:
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.

-18-
Asset Category
Oracle splits Asset Category information into three tables:
FA_CATEGORIES maintains segment value information

FA_CATEGORY_BOOKS maintains the default accounts associated to the asset category
FA_CATEGORY_BOOK_DEFAULTS maintain the depreciation default rules associated to
the category and book_type_code
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

-19-
FA_CATEGORY_BOOKS - This table maintains the account default values that have been
defined for the Category Flexfield. This table is only required when needing the capture the
default accounts associated with an asset category only the depreciation expense account
is entered for an asset, all other accounts are derived from this table. 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 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

-20-
FA_CATEGORY_BOOK_DEFAULTS - This table maintains the depreciation default rules
that have been defined for the Category Flexfield. This table is only required when needing
the capture the depreciation default rules associated with an asset category. The information
housed on this table corresponds to the Asset Category Combinations form (Navigation Path:
Navigator, Setups, Asset System, Asset Categories, Default Rules (Button)). This table houses
fields such as:
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

-21-
FA_LOCATIONS - This table maintains the segment values that have been defined for the
Location 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 Location Combinations form (Navigation
Path: Navigator, Setups, Asset System, Locations). This table houses fields such as:
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.

-22-
Linking the Core Tables to Depreciation Tables to Key Flexfield Tables
record(s):
Where FAD.asset_category_id = FAC.category_id
AND FAD.asset_key_ccid = FAK.code_combination_id
AND FAD.asset_id = FAB.asset_id
AND FDH.location_id = FAL.location_id

-23-
This section will go over some other tables that are often required to capture desired details.
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.

-24-
FA_ASSET_INVOICES - This table maintains the source line details that have been
integrated from other applications. This table maintains many id numbers from other Oracle
Applications. This table does not maintain the actual values, therefore in order capture details
such as Vendor, Project you would need to link to the respected application and table to
capture the desired details. The information housed on this table corresponds to the Source
Line form (Navigation Path: Navigator, Assets, Asset Workbench, [Query Asset], Source Lines
(Button)). This table houses fields such as:
Asset_id Project_id
PO_Vendor_id Task_id
Asset_invoice_id Etc.
Invoice_id

-25-
General Ledger Key Tables for Assets
This section will go over some of the General Ledger key tables that might be required to
capture desired details for Assets.
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

-26-
Linking the Core Tables to Depreciation Tables to Key Flexfield Tables to General
Ledger
record(s):
Where FAD.asset_category_id = FAC.category_id
AND FAD.asset_key_ccid = FAK.code_combination_id
AND FAD.asset_id = FAB.asset_id
AND FDH.location_id = FAL.location_id
AND FDH.code_combination_id = GCC.code_combination_id

-27-
GL_LEDGERS - This table maintains the ledger details. In R12 the term was changed from
Set of Books to Ledger. However, it was not changed everywhere in the system. Therefore, in
Assets there is a field on the FA_BOOK_CONTROLS for Set of Books this is the Ledger. The
information housed on this table corresponds to the Book Controls form (Navigation Path:
Navigator, Setups, Financials, Accounting Setup Manager, Accounting Setups). This table
Ledger_id Chart_of_accounts_id
Name Currency_code
Short_name Etc.
Description

-28-
GL_LEDGERS - This table maintains the ledger details. In R12 the term was changed from
Set of Books to Ledger. However, it was not changed everywhere in the system. Therefore, in
Assets there is a field on the FA_BOOK_CONTROLS for Set of Books this is the Ledger. The
Navigator, Setups, Financials, Accounting Setup Manager, Accounting Setups). This table
Ledger_id Chart_of_accounts_id
Name Currency_code
Short_name Etc.
Description

-29-
Journal Entries
Oracle houses journal entry information on three tables: Batches, Headers, and Lines. These
tables can be accessed if journal details are required for the desired results. To capture the
batch detail, you need to work backwards = Lines > Headers > Batches
GL_JE_BATCHES - This table maintains the batch details for a journal entry. The
Navigator, Journals, Enter, [Query Batch]). This table houses fields such as:
JE_Batch_id Status
Name Etc.
GL_JE_HEADERS - This table maintains the header details for a journal entry. The
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.

-30-
GL_JE_LINES - This table maintains the line 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 Entered_Dr
JE_Line_Num Entered_Cr
Ledger_id GL_SL_Link_id
Code_Combination_id GL_SL_Link_Table
Period_Name Etc.
Description

-31-
Subledger Accounting Key Tables
Subledger Accounting Key Tables for Assets
This section will go over some of the Subledger Accounting key tables that might be required
to capture desired details for Assets.
XLA_AE_HEADERS - This table maintains the subledger accounting entry header
information interfaced from the subledger Create Accounting program, contain fields such as:
Event_id Period_Name
AE_Header_id Accounting_Batch_id
Ledger_id Description
JE_Category_Name Etc.
Application_id
XLA_AE_LINES - This table maintains the subledger accounting entry lines information
interfaced from the subledger Create Accounting program, contain fields such as:
AE_Header_id Entered_Dr
Ledger_id Entered_Cr
Application_id Currency_Code
AE_Line_Num GL_SL_Link_id
Code_Combination_id GL_SL_Link_Table
Description Etc.

-32-
Other Applications Key Tables for Assets
This section will go over some of the other applications key tables that might be required to
capture desired details for Assets.
PO_VENDORS - This table maintains the vendor information defined in the system is owned
by Purchasing, contain fields such as:
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.
-33-
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.
-34-
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.

-35-
Key FND Tables
FND Tables for Descriptions
This section will go over some of the key fields and tables needed to capture key flexfield
descriptions.
APPLSYS.FND_FLEX_VALUES_TL - Key fields from this table:

Description
Flex_value_meaning
APPLSYS.FND_FLEX_VALUES - Key fields from this table:

Flex_value_id
APPLSYS.FND_ID_FLEX_SEGMENTS - Key fields from this table:

Flex_value_set_id

-36-
Key FND Tables
Linking to capture descriptions
This is an example of extracting description for an account value:
Step1 SELECT AFIFS.flex_value_set_id

FROM applsys.fnd_id_flex_segments AFIFS
WHERE AFIFS.id_flex_code LIKE 'GL%'
AND AFIFS.segment_name = 'ACCOUNT'
Step2 SELECT AFFV.flex_value_id

FROM applsys.fnd_flex_values AFFV
WHERE AFFV.flex_value_set_id = flex_value_set_id retrieved from step 1
Step3 SELECT AFFVT.description, AFFVT.flex_value_meaning

FROM applsys.fnd_flex_values_tl AFFVT,
WHERE AFFVT.flex_value_id = flex_value_id retrieved from step 2
flex_value_meaning = the key flexfield description

-37-
Great Source for
Information

-38-
Asset Special Interest Group (SIG)
FREE to join group:
Meetings (Semi-Annual)
OAUG Conference
OpenWorld Conference
http://assetsig.oaug.org
LinkedIn: http://www.linkedin.com/groups?gid=2202521

-39-
Questions?
Questions after the fact
Send email to: brian.bouchard@ntenergy.com

-40-

2013 09 18usercommwebinarseries10pdf

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

2013 09 18usercommwebinarseries10pdf

Загружено:

Авторское право:

Доступные форматы

Understanding

Core Asset Tables

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

and fa_books.transaction_header_id_out is null

Copyright 2010 Chi-Star Technology

Asset_ID Code_Combination_ID depreciation expense account combination

Copyright 2010 Chi-Star Technology

and fa_distribution_history.transaction_header_id_out is null

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Where FAD.asset_id = FAB.asset_id

Copyright 2010 Chi-Star Technology

This will remove retired asset from the output.

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

FA_CATEGORIES maintains segment value information

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

APPLSYS.FND_FLEX_VALUES_TL - Key fields from this table:

APPLSYS.FND_FLEX_VALUES - Key fields from this table:

APPLSYS.FND_ID_FLEX_SEGMENTS - Key fields from this table:

Copyright 2010 Chi-Star Technology

Step1 SELECT AFIFS.flex_value_set_id

Step2 SELECT AFFV.flex_value_id

Step3 SELECT AFFVT.description, AFFVT.flex_value_meaning

flex_value_meaning = the key flexfield description

Copyright 2010 Chi-Star Technology

Copyright 2010 Chi-Star Technology

FREE to join group:

Copyright 2010 Chi-Star Technology

Send email to: brian.bouchard@ntenergy.com

Copyright 2010 Chi-Star Technology

Вам также может понравиться