Results for “cost_txn_currency_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_FI_AMOUNT_DETAILS_AR is a Projects (PA) module table in Oracle EBS 12.1.1 and 12.2.2 that stores the amount details information for a forecast item. It is a child detail table within the Project Forecasting / Forecast Items framework, holding the exchange-rate-adjusted monetary and quantity breakdowns that support forecasted cost, revenue, and transfer price calculations across multiple currency perspectives. The "_AR" suffix indicates an archival/audit companion structure, which explains the presence of purge-related and audit columns such as PURGE_BATCH_ID, PURGE_RELEASE, and PURGE_PROJECT_ID. In the documented 12.2.2 physical schema the table contains 62 columns.

From a Data Vault modeling perspective (heuristic, mined from the foreign key structure), this object is classified as standalone. The absence of any table with a foreign key pointing into PA_FI_AMOUNT_DETAILS_AR confirms it functions as a leaf-level detail/audit table rather than a hub or link, so it should be treated as a satellite-style detail store rather than a relationship hub.

Key Information Stored

The most significant columns fall into three groups: identifying keys, quantity/line attributes, and the multi-currency amount stack.

• FORECAST_ITEM_ID — foreign key to PA_FORECAST_ITEMS; the business parent of each amount detail row.
• PURGE_BATCH_ID — foreign key to PA_PURGE_BATCHES_ALL, tying the row to an archival/purge run.
• PURGE_RELEASE, PURGE_PROJECT_ID — archival identifiers that scope the archived forecast data.
• LINE_NUM, LINE_NUM_REVERSED — the forecast line reference and its reversal counterpart.
• ITEM_DATE, ITEM_UOM, ITEM_QUANTITY — the dated quantity basis for the amount detail.
• REVERSED_FLAG, NET_ZERO_FLAG — status flags marking reversal and net-zero outcomes.
• TXN_RAW_COST, TXN_BURDENED_COST, TXN_REVENUE, TXN_TRANSFER_PRICE — transaction-currency amounts under COST_TXN_CURRENCY_CODE, REVENUE_TXN_CURRENCY_CODE, and TP_TXN_CURRENCY_CODE.
• PROJECT_RAW_COST, PROJECT_BURDENED_COST, PROJECT_REVENUE, PROJECT_TRANSFER_PRICE — project-currency equivalents with their rate dates, rate types, and exchange rates.
• PROJFUNC_* and EXPFUNC_* columns — project functional and expenditure functional currency views of the same cost, revenue, and transfer price amounts, each carrying its own rate date, rate type, and exchange rate.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

The documented metadata does not expose a single-column surrogate primary key or a declared unique index, so no surrogate/business-key distinction can be asserted from the provided facts; FORECAST_ITEM_ID with LINE_NUM is the most likely composite business identifier.

Common Use Cases and Queries

Typical usage centers on reconciling forecasted versus actual amounts, auditing purge history, and producing multi-currency forecast reports. A representative query joins the detail to its parent forecast item:

• Forecast amount reconciliation: SELECT d.FORECAST_ITEM_ID, d.LINE_NUM, d.ITEM_DATE, d.PROJFUNC_RAW_COST, d.PROJFUNC_REVENUE FROM PA_FI_AMOUNT_DETAILS_AR d WHERE d.FORECAST_ITEM_ID = :item_id ORDER BY d.LINE_NUM;
• Currency conversion drill-down: compare TXN_* to PROJECT_* and PROJFUNC_* amounts to validate applied PROJECT_COST_EXCHANGE_RATE and PROJECT_REVENUE_EXCHANGE_RATE.
• Purge audit: SELECT PURGE_BATCH_ID, COUNT(*) FROM PA_FI_AMOUNT_DETAILS_AR GROUP BY PURGE_BATCH_ID; to trace archived forecast volume per purge run.
• Reversal/net-zero analysis: filter on REVERSED_FLAG = 'Y' or NET_ZERO_FLAG = 'Y' to isolate corrected or zeroed forecast lines.

Related Objects

• PA_FORECAST_ITEMS — parent table via FORECAST_ITEM_ID; the primary join for forecast context.
• PA_PURGE_BATCHES_ALL — referenced via PURGE_BATCH_ID; anchors archival batch processing.
• PA_FORECAST_ITEM_DETAILS — the operational counterpart of this archival detail structure.
• PA_FI_AMOUNT_DETAILS — the non-archival "_AR"-less sibling holding the same amount detail semantics.
• PA_PROJECTS_ALL / PA_PROJECTS — project master referenced through PURGE_PROJECT_ID and the project currency columns.
• Forecasting APIs and concurrent programs that populate REQUEST_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.