Results for “cst_distribution_v”

50+ results




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

Overview

CST_DISTRIBUTION_V is a single-organization reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is catalogued under the BOM (Bills of Material) product family but draws its core data from the Cost Management (CST) and Work in Process (WIP) transaction model. The view presents transaction details alongside their accounting distributions for a discrete job or repetitive schedule within a given accounting period. Because it is a single-org view, callers must supply or filter on ORGANIZATION_ID; it does not perform the multi-org security enforcement that the corresponding _ALL or _V multi-org variants would apply through MO_GLOBAL or the organization hierarchy.

The view is primarily consumed by cost accountants, manufacturing analysts, and custom reporting/integration programs that need a flattened picture of material and resource movements posted to a job, together with the value, account, and cost-element information needed for reconciliation or extract. It exposes both the physical transaction (quantity, UOM, date, type, reason) and the accounting side (transaction value, base value, reference account, GL batch, cost element), which makes it a convenient single source for period-end variance, WIP-to-GL reconciliation, and job cost roll-up reports.

Underlying Base Objects

ETRM documents the view as defined over the following referenced objects: BOM_DEPARTMENTS, BOM_RESOURCES, CSI_ITEM_INSTANCES, CST_ACTIVITIES, MFG_LOOKUPS, MTL_MATERIAL_TRANSACTIONS, MTL_SYSTEM_ITEMS, MTL_TRANSACTION_ACCOUNTS, MTL_TRANSACTION_REASONS, MTL_TRANSACTION_TYPES, PO_HEADERS, WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_LINES, WIP_REPETITIVE_ITEMS, WIP_TRANSACTIONS, and WIP_TRANSACTION_ACCOUNTS. Most are exposed to APPS as synonyms over the corresponding base tables.

The driving table in the view text is MTL_MATERIAL_TRANSACTIONS (aliased MMT), joined to MTL_TRANSACTION_ACCOUNTS (MTA) for the accounting lines, MTL_SYSTEM_ITEMS (MSI) for the primary UOM, MTL_TRANSACTION_TYPES (MTT), MTL_TRANSACTION_REASONS (MTR), and MFG_LOOKUPS (LU2) to decode ACCOUNTING_LINE_TYPE. WIP_ENTITIES (WE) supplies the job name and organization, while WIP_LINES (WL), WIP_DISCRETE_JOBS, WIP_REPETITIVE_ITEMS, and WIP_TRANSACTION_ACCOUNTS tie the transaction back to the work order or repetitive schedule context. BOM_DEPARTMENTS and BOM_RESOURCES resolve the department and resource descriptions, and CST_ACTIVITIES supplies the activity. CSI_ITEM_INSTANCES and PO_HEADERS participate in specialized transaction joins (for example, lot/serial and purchase-order references).

Key Columns

Common Use Cases and Queries

The view supports job-cost detail extracts, WIP accounting reconciliation, and cost-element analysis by accounting period. Because it is single-org, queries should always constrain ORGANIZATION_ID and ACCT_PERIOD_ID to keep the result set bounded. A typical extract is shown below.

SELECT organization_id,
       wip_entity_id,
       transaction_id,
       acct_period_id,
       transaction_type_name,
       transaction_date,
       inventory_item_id,
       primary_quantity,
       cost_element,          -- decoded via COST_ELEMENT_ID
       transaction_value,
       base_transaction_value,
       reference_account,
       department_code,
       resource_code
  FROM apps.cst_distribution_v
 WHERE organization_id = :p_org_id
   AND acct_period_id  = :p_period_id
 ORDER BY wip_entity_id, transaction_id;

For cost-element summarisation, group by WIP_ENTITY_ID and the cost-element decode to compare material, resource, overhead, and outside-processing charges within a period. For GL tie-out, filter on GL_BATCH_ID to isolate distributions that have been posted, and reconcile BASE_TRANSACTION_VALUE against the batch totals. When investigating a specific movement, join back to the underlying MTL_MATERIAL_TRANSACTIONS.ROWID (exposed as the view's ROWID column) to retrieve the exact base row. Note that the referenced base objects are the synonyms listed above; any grant or synonym redefinition in a cloned environment should be verified before relying on the view in custom integrations. The view is marked VALID, so no recompilation concerns apply under normal patching and cloning sources.