Results for “atp_refresh_number”
32 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MSC_SALES_ORDERS is a table in the MSC schema belonging to the Advanced Supply Chain Planning (ASCP) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores sales order demand and reservations collected from source application instances, acting as a planning-side staging and reference store rather than a transactional order entry table. Records are populated during the data collection and planning cycle, when order management and shipping data are transferred into the MSC schema for use by the planning engine, memory-based planner, and related analytical processes.
The table's role is to consolidate demand and reservation details across one or more source instances so that planners can view committed customer demand, available-to-promise activity, and reservation state alongside supply and forecast data. The columns SALES_ORDER_NUMBER, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, CUSTOMER_ID, and REQUIREMENT_DATE make the object a key reference for supply and demand analysis at the line level.
Under the heuristic Data Vault classification mined from the foreign key structure, MSC_SALES_ORDERS is satellite-leaning. It combines descriptive demand and reservation attributes with a composite key that includes the source instance identifier, suggesting it functions primarily as a satellite attached to source-instance and demand hubs rather than as a pure hub or link table. Existing models should treat the collection timestamp and source instance columns as change-tracking attributes in this satellite view.
Key Information Stored
The composite primary key MSC_SALES_ORDERS_PK is defined on DEMAND_ID and SR_INSTANCE_ID. DEMAND_ID is the planning-internal demand surrogate, while SR_INSTANCE_ID identifies the source application instance from which the record was collected. Together they form a candidate business key for identifying a specific demand row across the collected dataset.
- DEMAND_ID — surrogate identifier for the demand record within the planning schema.
- SR_INSTANCE_ID — source instance that supplied the order; required for multi-instance collections.
- INVENTORY_ITEM_ID and ORGANIZATION_ID — the planned item and destination organization.
- DEMAND_SOURCE_TYPE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, and DEMAND_SOURCE_DELIVERY — identify the originating sales order structure.
- SALES_ORDER_NUMBER and LINE_NUM — human-readable order and line reference.
- CUSTOMER_ID, SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID — customer and site information for shipping and billing.
- REQUIREMENT_DATE, PROMISE_DATE, and SCHEDULE_ARRIVAL_DATE — demand timing anchors used by planning.
- PRIMARY_UOM_QUANTITY, RESERVATION_QUANTITY, COMPLETED_QUANTITY — demand and reservation quantities.
- PARENT_DEMAND_ID — self-referencing link to a parent demand row.
- ATP_REFRESH_NUMBER and REFRESH_NUMBER — collection cycle control values.
- DEMAND_VISIBLE, FORECAST_VISIBLE, AVAILABLE_TO_MRP — planning visibility flags.
Common Use Cases and Queries
Typical usage involves verifying that a sales order has been collected into the planning schema, reconciling order demand against reservations, and reporting on outstanding customer demand by date and organization. A basic pattern joins item and organization attributes:
- Filter by SALES_ORDER_NUMBER or DEMAND_SOURCE_HEADER_ID to locate a specific order line.
- Group by ORGANIZATION_ID and REQUIREMENT_DATE to review demand backlog and scheduled demand.
- Compare PRIMARY_UOM_QUANTITY with RESERVATION_QUANTITY and COMPLETED_QUANTITY to identify shrinkage or over-reservation.
- Filter on AVAILABLE_TO_MRP or DEMAND_VISIBLE to isolate demand that planning will consider.
Because collection refreshes the table, queries should account for REFRESH_NUMBER and LAST_UPDATE_DATE to distinguish current rows from earlier snapshots.
Related Objects
The documented FK metadata indicates the only explicit self-referencing relationship is PARENT_DEMAND_ID → MSC_SALES_ORDERS.DEMAND_ID combined with SR_INSTANCE_ID, which models hierarchical demand structures such as configuration or ATO parent lines. Beyond this, the object is most commonly joined with the following MSC objects using the item, organization, and demand identifiers listed above:
- MSC_SALES_ORDERS (self-join via PARENT_DEMAND_ID and SR_INSTANCE_ID) — parent-child demand resolution.
- MSC_SYSTEM_ITEMS — item master attributes via INVENTORY_ITEM_ID.
- MSC_ORG_ORGANIZATION_DEFINITIONS — organization details via ORGANIZATION_ID.
- MSC_GROUPS — collected customer records via CUSTOMER_ID.
- MSC_SR_INSTANCE — source instance definition via SR_INSTANCE_ID.
- MSC_DEMANDS — consolidated demand view joined on DEMAND_ID.
- MSC_SUPPLIES — supply side comparison on demand identifiers.
- MSC_ACCOUNTING_PERIODS or planning calendars — date buckets for REQUIREMENT_DATE.
- MRP planning collections programs — the standard collection process that loads and refreshes this table.
Planning and exception reporting templates in the MSC schema depend on this object whenever committed customer demand must be viewed alongside forecast, supply, and reservations in a single planning result set.
-
This table stores sales order demand and reservations from source application instances.
-
This table stores sales order demand and reservations from source application instances.
-
The staging table used by the collection program to validate and process data for table MSC_SALES_ORDERS.
-
The staging table used by the collection program to validate and process data for table MSC_SALES_ORDERS.
-
VIEW: MSC.MSC_SALES_ORDERS# 12.2.2
-
VIEW: MSC.MSC_SALES_ORDERS# 12.2.2
-
TABLE: MSC.MSC_SALES_ORDERS 12.1.1
-
TABLE: MSC.MSC_SALES_ORDERS 12.2.2
-
eTRM - MSC Tables and Views 12.1.1
This table contains the mapping between user-defined zone and included regions
-
eTRM - MSC Tables and Views 12.2.2
This table contains the mapping between user-defined zone and included regions