Results for “cst_xla_cost_updates_ref_v”

16 results




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

Overview

The view APPS.CST_XLA_COST_UPDATES_REF_V is a standard reference view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, owned by the APPS schema and catalogued under the BOM (Bills of Material) product family. Its documented description is "Standard Cost update sources", indicating that it exposes the cost update and inventory adjustment account information required when standard costing updates are processed and subsequently accounted through the Subledger Accounting (XLA) framework. The XLA prefix in the object name reflects its role as a source for the Create Accounting program, which resolves the correct accounting references for cost update events.

Functionally, the view acts as a lightweight, read-only projection over the cost update header data. Rather than surfacing the full breadth of the underlying cost update record, it isolates the cost update identifier and the inventory adjustment account, making it convenient for reporting, validation, and integration routines that need to identify the accounting destination associated with a given standard cost update. Because it is a view and not a table, no data is physically duplicated; queries always reflect the current state of the underlying cost updates.

Underlying Base Objects

The view is defined over a single documented base object:

  • CST_COST_UPDATES — referenced in the ETRM metadata as a SYNONYM resolved to the underlying cost update table in the CST (Cost Management) schema.

The view text is a simple projection:

No joins, filters, or aggregation are applied. Consequently, the view returns exactly one row per cost update defined in CST_COST_UPDATES, and all columns presented are pass-through values from that table. This simplicity ensures deterministic performance and makes the view safe for use in high-volume accounting extraction and reconciliation queries.

Key Columns

  • COST_UPDATE_ID — The unique identifier of the standard cost update. This is the primary key of the underlying cost update record and serves as the join key to other cost update and cost adjustment tables. It is the column most often used in WHERE clauses and in correlations to cost update history or accounting event data.
  • INV_ADJUSTMENT_ACCOUNT — The inventory adjustment account associated with the cost update. This account is used when the revaluation arising from the standard cost update is posted, particularly for adjustments affecting inventory valuation. The value is typically a concatenated accounting flexfield combination (or an account identifier resolvable to one), representing the debit/credit target for inventory revaluation adjustments.

Because the view exposes only these two columns, its meaning is tightly scoped: it maps a cost update to the account that carries its inventory adjustment impact.

Common Use Cases and Queries

The view is most commonly used when investigating how a standard cost update was accounted. Analysts searching for the term inv_adjustment_account typically reach this view while tracing the accounting flexfield assigned to cost update revaluation. Typical scenarios include verifying the adjustment account before running Create Accounting, reconciling cost update events to General Ledger balances, and building ad-hoc reports that list cost updates together with their adjustment accounts.

A representative query listing all cost updates and their adjustment accounts is:

  • SELECT cost_update_id, inv_adjustment_account FROM cst_xla_cost_updates_ref_v ORDER BY cost_update_id;

To retrieve the adjustment account for a specific cost update:

  • SELECT inv_adjustment_account FROM cst_xla_cost_updates_ref_v WHERE cost_update_id = :p_cost_update_id;

The view may also be joined to cost update history tables on COST_UPDATE_ID to associate adjustment accounts with specific update runs, dates, or organization scopes. Because the view is a direct projection of CST_COST_UPDATES, any record returned reflects the live account assignment in effect for that cost update, making it suitable for pre-accounting validation and post-accounting audit alike.