Results for “source_ind”

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

Overview

CM_ACST_LED is the Actual Costing Ledger table in the Oracle E-Business Suite Process Manufacturing Financials (GMF) module. It is owned by the GMF schema and holds a VALID status. As its description states, the table serves as a depository for all actual costing transactions generated by Process Manufacturing costing runs. These transactions originate from several operational sources, including Production Batch material details (PM_MATL_DTL), POC resource details (PM_OPRN_DTL), and related production activity streams. Each row represents a single actual costing transaction line that has been captured during the costing process and remains available for inquiry, reporting, and downstream accounting reconciliation.

From a dimensional modeling perspective, the heuristic Data Vault classification derived from the foreign key structure is link. This reflects the table’s role as a transaction-level association between independent entities such as items, warehouses, cost methods, cost components, and periods. Modelers may treat CM_ACST_LED as a link entity connecting these hubs rather than as a standalone hub or satellite.

Key Information Stored

The table contains 35 documented columns in the 12.2.2 schema. The surrogate primary key is ACTRANS_ID, enforced by the unique index CM_ACST_LED_PK, which is also the sole documented business-key candidate. Key columns include:

• ACTRANS_ID — Surrogate primary key uniquely identifying each actual costing transaction.
• TRANSLINE_ID — Line-level identifier for the originating transaction detail.
• SOURCE_IND — Indicator of the source system or process that generated the transaction.
• TRANS_DATE — Date of the costing transaction.
• ITEM_ID — Item associated with the costing transaction.
• WHSE_CODE — Warehouse in which the transaction occurred.
• CALENDAR_CODE and PERIOD_CODE — Costing calendar and period attribution.
• COST_MTHD_CODE — Costing method applied to the transaction.
• COST_CMPNTCLS_ID and CMPNTCOST_ID — Cost component class and component cost references.
• COST_AMT and TRANS_QTY — Monetary cost amount and associated transaction quantity.
• ACPROC_ID — Actual costing process control reference.
• COST_TYPE_ID, COST_LEVEL, and COST_ANALYSIS_CODE — Cost type, costing level, and analysis code classification.
• POST_TO_SUBLEDGER — Flag controlling whether the transaction posts to the subledger.
• DELETE_MARK — Soft-delete indicator.

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) support concurrency and traceability.

Common Use Cases and Queries

Typical scenarios include reconciling actual costing results, investigating cost variances by item or period, and auditing subledger posting eligibility. A common query retrieves costing transactions for a given item and period:

• SELECT actrans_id, item_id, whse_code, period_code, cost_amt, trans_qty FROM cm_acst_led WHERE item_id = :item_id AND period_code = :period;
• Join to IC_ITEM_MST to resolve item descriptions, and to CM_CLDR_DTL for calendar validation.
• Filter on POST_TO_SUBLEDGER = ’Y’ and DELETE_MARK = 0 for active, postable transactions.
• Aggregate COST_AMT by COST_CMPNTCLS_ID to analyze cost component distribution.

Related Objects

CM_ACST_LED participates in numerous foreign key relationships across the GMF schema:

• CM_ACPR_CTL — joined via ACPROC_ID for actual costing process control.
• CM_ALYS_MST — joined via COST_ANALYSIS_CODE.
• CM_CLDR_DTL — joined via CALENDAR_CODE and PERIOD_CODE.
• CM_CMPT_DTL — joined via CMPNTCOST_ID.
• CM_CMPT_MST_B and CM_CMPT_MST — joined via COST_CMPNTCLS_ID.
• CM_MTHD_MST — joined via COST_MTHD_CODE.
• IC_ITEM_MST_B and IC_ITEM_MST — joined via ITEM_ID.
• IC_WHSE_MST — joined via WHSE_CODE.
• CST_COST_TYPES — joined via COST_TYPE_ID.
• CM_ACST_LED_EFC — a dependent table referencing ACTRANS_ID.