Results for “cm_apcm_mst_v”

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

Overview

CM_APCM_MST_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMF (Process Manufacturing Financials) product family. Its documented purpose is narrow and specific: it exists to enable a master-detail relationship on the Invoice Price Maintenance form. In Oracle Forms-based EBS applications, master-detail coordination between two blocks normally requires a join view that presents the primary key of the master block alongside descriptive attributes of the detail block. CM_APCM_MST_V serves precisely that function, exposing the purchase order identifier (PO_ID) as the linking key together with human-readable context from the purchase order header.

The view is recorded in ETRM metadata with a status of VALID for both EBS 12.1.1 and 12.2.2. While its primary consumer is the Invoice Price Maintenance form, the view is equally usable as a lightweight reporting object, since it performs a pre-joined, distinct projection of purchase order and invoice number information. It should not be confused with a base table for transactional processing; it is a read-only, form-support construct.

Underlying Base Objects

The documented view text is a two-table equijoin:

• CM_APCM_MST (accessed via a synonym at runtime) — the process manufacturing invoice price maintenance master record. It contributes PO_ID and INVOICE_NO to the projection.
• PO_ORDR_HDR (also via synonym) — the purchase order header table, contributing ORGN_CODE (organization code) and PO_NO (the displayed purchase order number).

The join condition is APCM.PO_ID = POORD.PO_ID, and the query applies SELECT DISTINCT to eliminate duplicate rows that would otherwise arise from a one-to-many relationship between the header and master records. The join is an inner join by construction, so any master row lacking a corresponding purchase order header is excluded from the result set. Both referenced objects are exposed to the APPS schema through synonyms, which is standard practice in EBS and shields the view from direct ownership dependencies on the underlying tables.

Key Columns

• PO_ID — The internal purchase order identifier. This is the master-detail linkage column and the value the user searched for. It is the join key between CM_APCM_MST and PO_ORDR_HDR and is used by the form to coordinate the master and detail blocks.
• ORGN_CODE — The organization code of the purchase order header, identifying the operating unit or inventory organization context in which the PO resides.
• PO_NO — The user-facing purchase order number. This is the descriptive value most often displayed in reports and forms.
• INVOICE_NO — The invoice number associated with the maintenance master record, sourced from CM_APCM_MST. It completes the association between a purchase order and the invoice pricing record maintained on the form.

All four columns are simple scalar attributes with no derived expressions, so the view can be indexed and filtered efficiently through the underlying table indexes on PO_ID.

Common Use Cases and Queries

The most common use is form-driven: the Invoice Price Maintenance form queries the view to populate the master block, and the PO_ID column drives detail block synchronization. Beyond that, the view is convenient for ad hoc reporting that needs purchase order numbers correlated to invoice pricing records without writing the join manually. A typical query follows:

• SELECT po_id, orgn_code, po_no, invoice_no FROM apps.cm_apcm_mst_v WHERE po_no = :p_po_no;
• SELECT po_id, invoice_no FROM apps.cm_apcm_mst_v WHERE orgn_code = :p_org;
• SELECT po_id, po_no FROM apps.cm_apcm_mst_v WHERE invoice_no = :p_invoice;

Because the view is DISTINCT and inner-joined, it is suitable for lookup and validation queries rather than bulk extraction. For large-volume reconciliation, querying CM_APCM_MST directly with an explicit outer join to PO_ORDR_HDR is preferable to avoid silently dropping unmatched master rows. All queries should be schema-qualified against APPS to honor the documented synonym structure.