Results for “attribute_category_code”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The JA_AU_SOURCE_ADDITIONS_V view is an Asia/Pacific Localizations (JA) database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as a retrofitted view, meaning its definition was aligned with the Oracle Fusion-style data model during the upgrade and retrofit process. Its functional purpose is to expose the set of fixed assets that also appear as balance-change source records in the Australian localization tables, joining asset-master detail from FA_ADDITIONS to the balance-change source rows in JA_AU_BAL_CHG_SOURCE.
In practice, the view acts as a reporting and integration surface for Australian asset additions. It allows the Australian localizations and any downstream extensions to retrieve the asset identity, descriptive attributes, and retirement information for assets that have balance-change source activity. Because the view is DISTINCT, it returns a de-duplicated list of asset/source combinations, which is suitable for presentation layers and for driving selection lists in localization reports rather than for transactional processing.
Underlying Base Objects
The view is defined over two referenced base objects, both of which are synonyms in the APPS schema:
- JA_AU_BAL_CHG_SOURCE — the Australian balance-change source table. It supplies
ASSET_IDandDATE_RETIREDto the view and is the driving object that determines which assets are eligible to appear. - FA_ADDITIONS — the Oracle Assets additions entity. It supplies all remaining descriptive and classification columns: asset number, tag number, description, category, attribute category, asset key CCID, asset type, and manufacturer/model/serial information.
The two objects are combined with an inner join on ASSET_ID (S.ASSET_ID = A.ASSET_ID), so an asset appears in the view only when it has a matching row in both the balance-change source and the additions table. The documented metadata lists both base objects as synonyms, and the schema owner is APPS in the 12.2.2 documented view metadata, consistent with 12.1.1 deployments.
Key Columns
- ASSET_ID — Primary asset identifier, the join key between the two base objects.
- DATE_RETIRED — Retirement date sourced from
JA_AU_BAL_CHG_SOURCE. This is the column most frequently referenced by users searching on "date_retired" and is central to identifying when an asset was disposed of or retired for Australian reporting purposes. - ASSET_NUMBER and TAG_NUMBER — User-facing asset identifiers used in listings and cross-references.
- DESCRIPTION — Free-text asset description from
FA_ADDITIONS. - ASSET_CATEGORY_ID and ATTRIBUTE_CATEGORY_CODE — Asset category and descriptive flexfield context, enabling category-level filtering and attribute reporting.
- ASSET_KEY_CCID — The accounting flexfield combination identifier for the asset key account.
- ASSET_TYPE — Classification of the asset (for example, capitalized or expensed) per Oracle Assets conventions.
- MANUFACTURER_NAME, MODEL_NUMBER, and SERIAL_NUMBER — Physical identification attributes for the asset.
Common Use Cases and Queries
The view is typically queried to reconcile Australian additions against the asset register, to list assets with retirement dates, and to feed localization extracts. A representative query filtering on the retirement date is:
SELECT asset_id, date_retired, asset_number, tag_number, description FROM ja_au_source_additions_v WHERE date_retired IS NOT NULL ORDER BY date_retired DESC;SELECT asset_number, tag_number, asset_type, manufacturer_name, serial_number FROM ja_au_source_additions_v WHERE asset_category_id = :category_id;SELECT asset_id, asset_key_ccid, attribute_category_code, date_retired FROM ja_au_source_additions_v WHERE asset_id = :asset_id;
Because the view is DISTINCT and read-only, it supports query and reporting workloads only; all maintenance must be performed against the underlying JA_AU_BAL_CHG_SOURCE and FA_ADDITIONS objects.
-
- Retrofitted
APPS.JA_AU_SOURCE_ADDITIONS_V·↳ FA_ADDITIONS·↳ JA_AU_BAL_CHG_SOURCE·Explore JA module →
-
- Retrofitted
APPS.JA_AU_SOURCE_ADDITIONS_V·↳ FA_ADDITIONS·↳ JA_AU_BAL_CHG_SOURCE·Explore JA module →
-
- Retrofitted
APPS.JA_AU_SOURCE_ADDITIONS_BOOKS_V·↳ FA_ADDITIONS·↳ JA_AU_BAL_CHG_SOURCE·Explore JA module →
-
Price index values of each price index
-
Capital budget information entered manually or uploaded from the FA_BUDGET_INTERFACE table
-
General price index information
-
Capital budget information entered manually or uploaded from the FA_BUDGET_INTERFACE table
-
Budget assets used to run depreciation projections and reports
-
- Retrofitted
APPS.JA_AU_SOURCE_ADDITIONS_BOOKS_V·↳ FA_ADDITIONS·↳ JA_AU_BAL_CHG_SOURCE·Explore JA module →
-
Bonus rule information used by the Depreciation program
-
Percentage of Investment Tax Credit (ITC) to recapture for early retirements
-
Balancing charge applications
-
Range of dates for all fiscal years
-
Capital Gains Tax information
-
Seeded and user-defined ceilings for depreciation expense, investment tax credit cost basis, and depreciation cost basis
-
Range of dates for all fiscal years
-
Production information for units of production assets entered manually or uploaded from FA_PRODUCTION_INTERFACE
-
Investment tax credit (ITC) rate information
-
Percentage of Investment Tax Credit (ITC) to recapture for early retirements
-
General calendar information
-
View: OKX_QTE_SLS_CREDITS_V 12.1.1
Sales credits given to Sales persons
APPS.OKX_QTE_SLS_CREDITS_V·↳ ASO_SALES_CREDITS·Explore OKX module →
-
General price index information
-
- Retrofitted
APPS.JA_AU_ADDITIONS_ALLOCATIONS_V·↳ FA_ADDITIONS·↳ FA_BOOKS·↳ JA_AU_BAL_CHG_APPLIED·Explore JA module →
-
Bonus rule information used by the Depreciation program
-
Price index values of each price index
-
General ceiling information
-
Annual depreciation rates for all flat-rate methods
-
Seeded and user-defined values for QuickCodes (base MLS table)
-
Capital Gains Tax information
-
Contains the depreciation rates to be used when calculating the reserve amount to be transferred with an asset which is being moved out of a group.
-
Balancing charge applications
-
Bonus rate information used by the Depreciation program
-
Balancing charges information imported from external systems
-
View: JA_AU_FA_ADD_ADJ_V 12.1.1
- Retrofitted
APPS.JA_AU_FA_ADD_ADJ_V·↳ FA_ADDITIONS·↳ FA_BOOKS·↳ JA_AU_BAL_CHG_APPLIED·Explore JA module →
-
System-wide controls that affect all assets
-
Asset transaction history for all books
APPS.FA_TRANS_HIST_TRX_WEB_V·↳ FA_ADDITIONS·↳ FA_ASSET_HISTORY·↳ FA_BOOK_CONTROLS·Explore OFA module →
-
Budget assets used to run depreciation projections and reports
-
When you define a mass revaluation request using the Extended MassRevaluation form, the form inserts a row that storesthe default revaluation rules. Each revaluation has one masterrow in this table and as many detail rows inIGI_MHC_IDX_RE
-
Mass depreciation adjustment request information
-
Balancing charge source information
-
View: FA_LOOKUPS_VL 12.2.2
APPS.FA_LOOKUPS_VL·↳ FA_LOOKUPS_B·↳ FA_LOOKUPS_TL·Explore OFA module →
-
- Retrofitted
APPS.FA_TRANSACTION_HISTORY_TRX_V·↳ FA_ADDITIONS_B·↳ FA_ADDITIONS_TL·↳ FA_ASSET_HISTORY·Explore OFA module →
-
Annual depreciation rates for all flat-rate methods
-
Names and descriptions for prorate conventions
-
General ceiling information
-
Depreciation method information
-
- Retrofitted
APPS.JA_AU_ADDITIONS_ALLOCATIONS_V·↳ FA_ADDITIONS·↳ FA_BOOKS·↳ JA_AU_BAL_CHG_APPLIED·Explore JA module →
-
Names and descriptions for prorate conventions
-
View: OKX_QTE_SLS_CREDITS_V 12.2.2
Sales credits given to Sales persons
APPS.OKX_QTE_SLS_CREDITS_V·↳ ASO_SALES_CREDITS·Explore OKX module →
-
Mass revaluation request rule information