Search Results poline_id

Overview

The CM_APCM_MST table is a core data object within the GMF (Process Manufacturing Financials) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as the validated invoice interface master table for Costing. Its primary role is to store finalized invoice price information that originates from Oracle Financials, specifically from the Accounts Payable module. The data flow is a two-step process: invoice data is first staged in the CM_APCM_INT interface table. After undergoing validation routines, the cleansed and approved data is then written to the CM_APCM_MST table. This master repository of invoice costs is subsequently used by the GMF Costing engine for critical financial calculations, including material cost updates and inventory valuation.

Key Information Stored

The table's structure is designed to uniquely identify and store cost details for individual invoice lines. Its primary key (CM_APCM_MST_PK) is a composite key, underscoring the granularity of the data. The key columns, which also represent the core information stored, include:

• PO_ID & POLINE_ID: Links the invoice cost to its originating purchase order and specific line.
• LINE_TYPE: Categorizes the type of line on the invoice.
• ITEM_ID: Identifies the inventory item being invoiced.
• AQUI_COST_ID: References the acquisition cost identifier.
• INVOICE_NO & INVOICE_LINE_NO: The unique identifier for the supplier invoice and its specific line number.

This combination ensures a unique record for each validated invoice line item cost. The table also contains a foreign key column, TEXT_CODE, which links to the CM_TEXT_HDR table for storing associated textual notes or descriptions.

Common Use Cases and Queries

The primary use case for CM_APCM_MST is supporting cost management and financial reporting within Process Manufacturing. Data in this table is essential for reconciling purchase order costs with final invoice amounts and for calculating accurate landed costs. A common reporting requirement is to trace the invoice costs for a specific item or purchase order. A sample query pattern would join CM_APCM_MST to inventory and purchasing tables:

SELECT msn.segment1 AS Item, poh.segment1 AS PO_Number, apcm.invoice_no, apcm.invoice_line_no
FROM gmf.cm_apcm_mst apcm
JOIN inv.mtl_system_items_b msn ON apcm.item_id = msn.inventory_item_id
JOIN po.po_headers_all poh ON apcm.po_id = poh.po_header_id
WHERE msn.segment1 = '<ITEM_CODE>'
ORDER BY apcm.invoice_no;

Technical consultants may also query this table to investigate data integrity issues between the interface (CM_APCM_INT) and master tables, or to audit cost flows for period-end closing procedures.

Related Objects

CM_APCM_MST exists within a specific data flow and has key dependencies. The most directly related objects are:

• CM_APCM_INT: The staging table from which validated data is sourced. Data migration scripts or concurrent programs move records from INT to MST.
• CM_TEXT_HDR: The table referenced by the TEXT_CODE foreign key, storing descriptive text associated with the invoice cost record.
• GMF Costing Engine & APIs: Downstream costing processes and proprietary GMF APIs read from CM_APCM_MST to perform cost updates and calculations. The table is integral to the landed cost and inventory valuation subledgers within GMF.