Results for “cm_acst_led_v”

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

Overview

CM_ACST_LED_V is a database view owned by the APPS schema in Oracle E-Business Suite, classified under the GMF — Process Manufacturing Financials product family. Its documented description is "Acquisition cost LED view," indicating that it exposes acquisition cost ledger information used by the Process Manufacturing costing engine. The view is marked VALID in the ETRM repository and is documented for environments running EBS 12.1.1 and 12.2.2.

The view serves as a denormalized reporting and integration layer over the acquisition cost ledger table CM_ACST_LED. Rather than requiring report developers or integration components to join the ledger to the cost method master and period status tables manually, CM_ACST_LED_V presents a consolidated projection that combines the ledger rows with their associated cost method and accounting period context. The inclusion of DISTINCT in the view definition ensures that duplicate combinations produced by the underlying joins are collapsed, which is appropriate for a view whose primary purpose is to enumerate the distinct organization, period, cost method, and item combinations that exist in the acquisition cost ledger. This makes it well suited to period-end reporting, cost rollup validation, and inbound interface processing that must verify whether acquisition cost data exists for a given item, period, and cost method.

Underlying Base Objects

The view is defined over three base objects, all referenced through synonyms in the APPS schema:

• CM_ACST_LED — the acquisition cost ledger table, which stores the core acquisition cost records. The view selects ORGANIZATION_ID, INVENTORY_ITEM_ID, PERIOD_ID, and COST_TYPE_ID from this table.
• CM_MTHD_MST — the cost method master table, which defines cost methods and cost types. The view joins on COST_TYPE_ID to resolve the COST_MTHD_CODE and COST_TYPE_ID.
• GMF_PERIOD_STATUSES — the period status table for Process Manufacturing, which supplies the CALENDAR_CODE, PERIOD_ID, and PERIOD_CODE. The join is performed on PERIOD_ID.

The join predicates link LED.COST_TYPE_ID to MTHD.COST_TYPE_ID and MST.PERIOD_ID to LED.PERIOD_ID, effectively combining ledger facts with their cost method classification and accounting period descriptors.

Key Columns

• ORGANIZATION_ID — identifies the inventory organization in which the acquisition cost record resides. This is the primary partitioning key for multi-org reporting.
• CALENDAR_CODE — the accounting calendar associated with the period, sourced from GMF_PERIOD_STATUSES.
• PERIOD_ID — the internal identifier of the accounting period, used as the join key to period status data.
• PERIOD_CODE — the human-readable period name, typically in the form of a period-year combination.
• COST_MTHD_CODE — the cost method code from CM_MTHD_MST, indicating which costing methodology (for example, standard or actual) applies to the record.
• COST_TYPE_ID — the internal identifier of the cost type, linking the ledger row to its cost method master definition.
• INVENTORY_ITEM_ID — the inventory item for which acquisition cost data exists.

Common Use Cases and Queries

Typical scenarios include validating period-close acquisition cost data, identifying which items have acquisition costs in a given period, and feeding downstream cost analysis or reconciliation reports. A representative query listing acquisition cost combinations for an organization and period is:

• SELECT organization_id, calendar_code, period_code, cost_mthd_code, inventory_item_id FROM apps.cm_acst_led_v WHERE organization_id = :org_id AND period_code = :period ORDER BY inventory_item_id;
• SELECT cost_mthd_code, COUNT(DISTINCT inventory_item_id) FROM apps.cm_acst_led_v WHERE period_id = :period_id GROUP BY cost_mthd_code;
• SELECT DISTINCT period_code FROM apps.cm_acst_led_v WHERE organization_id = :org_id ORDER BY period_code;

Because the view already resolves cost method and period descriptors, these queries avoid direct joins to CM_MTHD_MST and GMF_PERIOD_STATUSES, simplifying report SQL and interface logic.