Results for “msc_sup_dem_entries”

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

Overview

MSC.MSC_SUP_DEM_ENTRIES is a transaction-level table in Oracle Advanced Supply Chain Planning (MSC) that stores supplier and demand transaction data used by Oracle Collaborative Planning. It serves as the persistence layer for the exchange of schedule, order, shipment, and commitment information between a planning organization (the publisher) and its trading partners — suppliers, customers, contract manufacturers, and internal organizations (the subscribers). Each row represents a discrete supply/demand transaction line, such as a new schedule, a purchase order acknowledgment, a shipment notice, or a demand forecast, published or received through the collaborative planning process.

Because the table records associations between two parties (publisher and subscriber) relative to a plan and an item, a Data Vault modeling heuristics would classify MSC_SUP_DEM_ENTRIES as a link table: it materializes the relationships between publishers, subscribers, plans, and inventory items, and carries descriptive and transactional context as attributes. In the native EBS schema, this role is fulfilled by the composite primary key constraint MSC_SUP_DEM_ENTRIES_PK, defined over (TRANSACTION_ID, PLAN_ID), and reinforced by the unique index MSC_SUP_DEM_ENTRIES_U1 on the same column pair.

Key Information Stored

The documented physical schema of MSC_SUP_DEM_ENTRIES in ETRM 12.2.2 contains 173 columns. The most operationally significant columns are the following:

• TRANSACTION_ID and PLAN_ID — the composite surrogate/business key; PLAN_ID also serves as a foreign key to MSC_PLANS, scoping each transaction to a specific plan.
• INVENTORY_ITEM_ID — foreign key to ICX_POR_ITEMS, identifying the item being transacted.
• PUBLISHER_ID, PUBLISHER_SITE_ID, SUBSCRIBER_ORG_ID — the publishing and receiving organizations that define the collaboration relationship.
• SUPPLIER_ID, SUPPLIER_SITE_ID, CUSTOMER_ID, CUSTOMER_SITE_ID — trading partner identities for supplier- and customer-facing transactions.
• QUANTITY, TP_QUANTITY, UOM_CODE, TP_UOM_CODE — quantities and units of measure as stated by the publisher versus the trading partner.
• ORDER_NUMBER, LINE_NUMBER, RELEASE_NUMBER, RELEASE_STATUS — the underlying order/document reference.
• BUCKET_TYPE and BUCKET_TYPE_DESC — the schedule bucket (e.g., firm, forecast) the transaction belongs to.
• NEW_SCHEDULE_DATE, NEW_SHIP_DATE, NEW_DOCK_DATE, PROMISED_DATE — key planning dates.
• PROCESSED_FLAG, VMI_FLAG, ACK_FLAG, ACCEPTANCE_REQUIRED_FLAG — status and control flags that drive collaboration workflows.
• Standard audit and multi-org columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, plus ATTRIBUTE1 through ATTRIBUTE15 for extensibility.

The surrogate key is the composite (TRANSACTION_ID, PLAN_ID); there is no single-column surrogate. The unique index MSC_SUP_DEM_ENTRIES_U1 confirms this combination as the business-key candidate.

Common Use Cases and Queries

MSC_SUP_DEM_ENTRIES is queried primarily for collaborative planning reconciliation, supplier schedule reporting, and exception analysis. Typical patterns include:

• Retrieving all transactions for a plan and item: SELECT * FROM MSC.MSC_SUP_DEM_ENTRIES WHERE PLAN_ID = :plan_id AND INVENTORY_ITEM_ID = :item_id;
• Identifying unprocessed inbound transactions for acknowledgment processing: SELECT TRANSACTION_ID, PUBLISHER_ID, ORDER_NUMBER, QUANTITY FROM MSC.MSC_SUP_DEM_ENTRIES WHERE PROCESSED_FLAG = 'N';
• Analyzing schedule changes by bucket and date to detect exceptions against promised dates.
• Joining to MSC_PLANS and ICX_POR_ITEMS to enrich transactions with plan and item descriptions for reporting.

Because the table is high-volume, queries should always be filtered by PLAN_ID or TRANSACTION_ID to leverage the primary key index.

Related Objects

The following objects are most directly related to MSC_SUP_DEM_ENTRIES, based on the documented foreign keys and collaboration model:

• MSC_PLANS — joined on MSC_SUP_DEM_ENTRIES.PLAN_ID = MSC_PLANS.PLAN_ID; scopes transactions to a plan.
• ICX_POR_ITEMS — joined on MSC_SUP_DEM_ENTRIES.INVENTORY_ITEM_ID = ICX_POR_ITEMS.INVENTORY_ITEM_ID; supplies item context.
• MSC_SUP_DEM_ENTRIES_PK / MSC_SUP_DEM_ENTRIES_U1 — the primary key and unique index constraints enforcing transaction uniqueness.
• Collaborative planning concurrent programs and the MSC planning engine, which read and write rows during plan runs and data refreshes.
• Standard MSC planning views and concurrent program outputs that aggregate these transactions for schedule and demand reporting.

No direct API is documented in the ETRM metadata; access is typically through planning concurrent programs and SQL reporting.