Results for “cm_whse_asc”

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

Overview

CM_WHSE_ASC is the Costing Warehouse Association table in the Oracle E-Business Suite Process Manufacturing Financials (GMF) product family. Its purpose is to allow the Oracle Process Manufacturing (OPM) user to build and maintain an association between costing warehouses and inventory warehouses. This association governs how inventory transactions recorded in a physical (inventory) warehouse are mapped to the costing warehouse used for valuation, cost rollup, and cost analysis in OPM Cost Management.

The table resides in the GMF schema. In the supplied ETRM metadata it is marked VALID and documented with 14 columns for release 12.2.2. From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as a link — it resolves a many-to-many style relationship between costing warehouse definitions and inventory warehouse definitions, keyed by an effective dating component. Practically, however, it also carries descriptive and audit attributes (TEXT_CODE, DELETE_MARK, CREATION_DATE, and similar), so it behaves partly as a satellite around that link. The classification should therefore be treated as a modeling suggestion rather than a strict architectural definition.

Key Information Stored

The table's documented columns define the association and its lifecycle:

• COST_WHSE_CODE — the costing warehouse side of the association. This is a business-key candidate and one of the two warehouse foreign keys.
• WHSE_CODE — the inventory warehouse side of the association. Together with COST_WHSE_CODE it forms the meaningful business identity of a row.
• EFF_START_DATE — the effective start date of the association; the third component of the composite primary key.
• EFF_END_DATE — the effective end date, enabling date-ranged (slowly changing) associations when an inventory warehouse is re-pointed to a different costing warehouse.
• COST_ORGANIZATION_ID and ORGANIZATION_ID — the organization identifiers associated with the costing and inventory sides respectively, supporting multi-org reporting.
• TEXT_CODE — a reference to descriptive text held in CM_TEXT_HDR, allowing annotations on the association.
• TRANS_CNT — a transaction counter column commonly used for concurrency control and change detection during cost processing.
• DELETE_MARK — the logical delete indicator; associations are typically deactivated rather than physically removed.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard Oracle EBS who/when auditing.

The surrogate primary key is CM_WHSE_ASC_PK, defined over (COST_WHSE_CODE, WHSE_CODE, EFF_START_DATE). No separate single-column surrogate is documented; the PK columns therefore also serve as the primary business-key candidate.

Common Use Cases and Queries

The most common requirement is determining which costing warehouse values an inventory warehouse's transactions. A typical pattern joins the association to the warehouse master on both warehouse codes and filters by the transaction date falling within the effective range:

• Cost mapping lookups — SELECT COST_WHSE_CODE, WHSE_CODE FROM GMF.CM_WHSE_ASC WHERE WHSE_CODE = :inv_whse AND :txn_date BETWEEN EFF_START_DATE AND NVL(EFF_END_DATE, :txn_date) AND NVL(DELETE_MARK, 0) = 0.
• Warehouse master enrichment — join IC_WHSE_MST twice, once on COST_WHSE_CODE and once on WHSE_CODE, to resolve warehouse descriptions for reporting.
• Effective-dating audits — identify gaps or overlaps in EFF_START_DATE/EFF_END_DATE ranges per WHSE_CODE, which commonly cause cost rollup discrepancies.
• Interface and conversion validation — confirm that every active inventory warehouse has exactly one current costing warehouse association before running cost processes.

Related Objects

• IC_WHSE_MST — referenced twice: CM_WHSE_ASC.COST_WHSE_CODE → IC_WHSE_MST and CM_WHSE_ASC.WHSE_CODE → IC_WHSE_MST.
• CM_TEXT_HDR — referenced by CM_WHSE_ASC.TEXT_CODE, supplying descriptive text.
• CM_WHSE_ASC_PK — the primary key constraint enforcing uniqueness on (COST_WHSE_CODE, WHSE_CODE, EFF_START_DATE).
• OPM Cost Management tables — costing tables such as CM_ costing detail/bucket tables depend on this mapping when valuing inventory transactions.
• MTL_ / OPM inventory transaction tables — OPM inventory transaction interfaces reference the resulting costing warehouse during cost processor runs.