Search Results transaction_costed_date

Overview

The view AX_CST_ACTUAL_COST_DETAILS_V1 is a Global Accounting Engine (AX) reporting and integration view in Oracle E-Business Suite. It exposes the detailed actual-costing rows generated when inventory transactions are processed, with a particular focus on sending and receiving transactions of an inter-organization transfer. In this context, an inter-organization transfer generates a cost relief (sending) transaction in the shipping organization and a cost receipt (receiving) transaction in the destination organization. The view surfaces the per-element actual cost values, prior and new costs, and any resulting variance for those transfer lines.

Because the AX product interfaces the subledger costing results into the Global Accounting Engine, this view functions as a normalized presentation layer over the underlying cost detail table. It allows AX accounting programs, reconciliation queries, and downstream reporting to retrieve transfer-related cost detail without embedding direct dependencies on internal costing structures. The view is documented as not implemented in this database, meaning the metadata describes the object definition even where the physical view may not be instantiated in a given environment; deployments that have the AX costing integration enabled will include it.

Underlying Base Objects

Per the ETRM metadata, the view is defined solely over the base table MTL_CST_ACTUAL_COST_DETAILS:

• MTL_CST_ACTUAL_COST_DETAILS — the transaction-level actual cost detail table that stores one row per transaction, cost element, and level type, capturing the costed amounts and variances produced by the costing engine.

The view is a column-projected selection over this single base table; no joins, unions, or additional referenced objects are documented. Consequently, the row granularity of the view matches the base table exactly: one record per transaction identifier and cost element (and level type) combination. All key and audit columns present in the base table are passed through unchanged.

Key Columns

The following columns are exposed by the view and carry the primary costing semantics:

• TRANSACTION_ID — the inventory transaction identifier. This is the central linkage to transfer transactions in the sending and receiving organizations.
• ORGANIZATION_ID — the inventory organization in which the costed transaction occurred. For inter-org transfers, separate rows exist for the sending and receiving organizations.
• INVENTORY_ITEM_ID — the item being transferred and costed.
• COST_ELEMENT_ID / LEVEL_TYPE — the cost element (material, material overhead, resource, overhead, outside processing) and the costing level at which the amount applies.
• ACTUAL_COST — the actual cost amount computed for the transaction line at this element and level.
• PRIOR_COST and NEW_COST — the cost values before and after the transaction, which support revaluation and cost-update analysis.
• VARIANCE_AMOUNT — the difference generated by the costed transaction, typically relevant to transfer price or revaluation differences.
• INSERTION_FLAG and USER_ENTERED — flags indicating how the row was created and whether the cost was user-provided.
• LAYER_ID — the cost layer to which the transaction is associated, where layer costing applies.
• TRANSACTION_COSTED_DATE and TRANSACTION_ACTION_ID — the date the transaction was costed and the action type (for example, transfer send versus transfer receive).
• Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) — standard EBS who-columns identifying the concurrent request and user that produced the row.

Common Use Cases and Queries

Typical usage includes reconciling inter-organization transfer costs between sending and receiving organizations, auditing the actual cost and variance produced for transfer transactions, and feeding AX accounting entries.

A representative query retrieving transfer cost detail for a given transaction follows:

• SELECT transaction_id, organization_id, inventory_item_id, cost_element_id, actual_cost, prior_cost, new_cost, variance_amount, transaction_costed_date FROM ax_cst_actual_cost_details_v1 WHERE transaction_id = :p_transaction_id;

To isolate sending versus receiving actions for a transfer organization pair:

• SELECT organization_id, transaction_action_id, SUM(actual_cost) FROM ax_cst_actual_cost_details_v1 WHERE transaction_id = :p_transaction_id GROUP BY organization_id, transaction_action_id;

And to review variances across a costing period:

• SELECT organization_id, inventory_item_id, variance_amount FROM ax_cst_actual_cost_details_v1 WHERE transaction_costed_date BETWEEN :p_start AND :p_end AND variance_amount <> 0;

The view is read-only in practice and should be joined to transaction and item master tables via TRANSACTION_ID and INVENTORY_ITEM_ID for descriptive reporting.