Results for “cm_apcm_mst”

33 results




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

Overview

CM_APCM_MST is the invoice interface master table for Costing within Oracle Process Manufacturing Financials (GMF). It resides in the GMF schema and is documented as VALID in ETRM release 12.2.2 (and applies equally to 12.1.1). The table stores invoice price information that is transferred from Oracle Financials (Payables) into Process Manufacturing Costing. The integration follows a two-stage pattern: invoice data is first loaded into the interim table CM_APCM_INT, validated, and then written to CM_APCM_MST, where it becomes available for cost adjustment and inventory valuation processing.

From a data modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This suggests the table is best modeled as a satellite attached to a purchase-order-line business key, holding descriptive invoice attributes that change over time or per transaction, rather than as an independent hub or link.

Key Information Stored

CM_APCM_MST contains 37 documented columns. The most operationally significant include:

The primary key is CM_APCM_MST_PK, a composite of PO_ID, POLINE_ID, LINE_TYPE, ITEM_ID, AQUI_COST_ID, INVOICE_NO, and INVOICE_LINE_NO. There is no separate surrogate key; the composite primary key also serves as the documented business-key candidate. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and the PROGRAM_/REQUEST_ID set) are also present.

Common Use Cases and Queries

Typical usage centers on reconciling invoice price variance and tracing the cost applied to a purchase order receipt. A common query joins invoice detail to the PO and item:

  • Selecting all invoice lines for a given PO line to review quantity and price variances.
  • Filtering on INVOICE_STATUS or AC_STATUS to find records not yet costed or applied.
  • Joining to CM_TEXT_HDR via TEXT_CODE to retrieve descriptive text attached to the interface record.
  • Reporting by GL_DATE to support period-close analysis of costing adjustments.

Typical SQL pattern: SELECT m.INVOICE_NO, m.INVOICE_LINE_NO, m.ITEM_ID, m.AQUI_COST_ID, m.INVOICE_QTY, m.UNIT_PRICE, m.INVOICE_STATUS FROM GMF.CM_APCM_MST m WHERE m.PO_ID = :po_id AND m.POLINE_ID = :line_id. Filtering on INVOICE_STATUS avoids reading unprocessed staging rows.

Related Objects

  • CM_APCM_INT — the interim staging table populated before validation; CM_APCM_MST receives the validated result.
  • CM_TEXT_HDR — referenced by foreign key via CM_APCM_MST.TEXT_CODE, supplying descriptive text.
  • CM_APCM_MST_PK — the unique index enforcing the composite business key.
  • Oracle Payables invoice tables (AP_INVOICES_ALL, AP_INVOICE_LINES_ALL) — the upstream source of invoice number, line, and amount data.
  • Purchase order line tables (PO_LINES_ALL) and item master (MTL_SYSTEM_ITEMS_B) — providing PO, line, and item context.

These relationships make CM_APCM_MST a central artifact for reconciling Financials-sourced invoice prices against Process Manufacturing costing activity.