Results for “end_order_number”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MSC_EXCEPTION_DETAILS is a transactional detail table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) product within the Oracle E-Business Suite Advanced Planning and Scheduling (APS) and Supply Chain Hub modules. The table persists the detail records behind planning exceptions surfaced during a plan run. When APS evaluates supply, demand, resource capacity, and item constraints, it generates exception messages such as late orders, excess inventory, resource overloads, or expedite recommendations. MSC_EXCEPTION_DETAILS holds the attributes that describe each of these exceptions in context, including the offending quantities, dates, item, organization, resource, and the corrective action recorded against the exception.
From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies this object as a link. This suggestion reflects the fact that MSC_EXCEPTION_DETAILS sits at the intersection of multiple business keys — plan, item, organization, resource, department, and source instance — rather than representing a single standalone business entity or a slowly changing descriptive attribute set.
Key Information Stored
The table is keyed by the composite primary key MSC_EXCEPTION_DETAILS_PK, defined as (PLAN_ID, SR_INSTANCE_ID, EXCEPTION_DETAIL_ID). A unique index, MSC_EXCEPTION_DETAILS_U1, provides an alternate business-key candidate on (PLAN_ID, EXCEPTION_DETAIL_ID, SR_INSTANCE_ID). The most significant columns include:
- EXCEPTION_DETAIL_ID — surrogate-style detail identifier, component of both the PK and the unique index.
- PLAN_ID, SR_INSTANCE_ID — identify the plan and the source instance that produced the exception.
- EXCEPTION_TYPE — the classification of the exception (for example, late supply or overload).
- INVENTORY_ITEM_ID, ORGANIZATION_ID — the item and organization against which the exception applies.
- RESOURCE_ID, DEPARTMENT_ID — the resource and department context for capacity-related exceptions.
- QUANTITY, NUMBER1–NUMBER8 — numeric measures such as affected quantity or surplus/shortage figures.
- DATE1–DATE6 — generic date slots carrying exception-specific dates.
- CHAR1, CHAR2 — generic character attributes for exception-specific text.
- ACTION_TAKEN, ACTION_TAKEN_BY, ACTION_TAKEN_DATE — the planner's resolution and its audit trail.
- CAUSE, NEW_EXCEPTION, FIRST_GENERATED_DATE — diagnostic indicators and generation history.
- SUPPLIER_ID, CUSTOMER_ID, ORDER_NUMBER, DEMAND_ID, TRANSACTION_ID — supply/demand and order context.
- Standard WHO/audit columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, and related concurrency fields).
Common Use Cases and Queries
Typical usage centers on exception reporting for a completed plan. Planners query by PLAN_ID and EXCEPTION_TYPE to retrieve unresolved exceptions, joining to MSC_ITEM_EXCEPTIONS for the exception definition and MSC_SYSTEM_ITEMS for item descriptions:
- Exception dashboards filtering on ACTION_TAKEN IS NULL to surface open items for planner review.
- Capacity bottleneck analysis joining RESOURCE_ID and DEPARTMENT_ID to MSC_DEPARTMENT_RESOURCES.
- Trend reporting on FIRST_GENERATED_DATE to measure how long exceptions persist across plan runs.
- Audit queries on ACTION_TAKEN_BY and ACTION_TAKEN_DATE to track planner resolution history.
- Exception volume extracts segmented by ORGANIZATION_ID for supply chain performance reporting.
Related Objects
The documented foreign keys tie MSC_EXCEPTION_DETAILS to several parent objects through their shared business keys:
- MSC_SYSTEM_ITEMS — joined on INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID.
- MSC_DEPARTMENT_RESOURCES — joined on PLAN_ID, ORGANIZATION_ID, RESOURCE_ID, SR_INSTANCE_ID, DEPARTMENT_ID.
- MSC_ITEM_EXCEPTIONS — joined on PLAN_ID, EXCEPTION_TYPE, INVENTORY_ITEM_ID, ORGANIZATION_ID, SR_INSTANCE_ID.
- BOM_DEPARTMENTS — referenced via DEPARTMENT_ID.
- WMS_ZONES_B — referenced via ZONE_ID.
These relationships make MSC_EXCEPTION_DETAILS the analytic detail counterpart to the aggregate exception definitions in MSC_ITEM_EXCEPTIONS.
-
This table stores the details of exceptions generated by Oracle Advanced Planning and Scheduling(APS) and Oracle Supply Chain Hub products.
-
APPS.MSC_SUP_DEM_ENT_CUSTOM_EX_V·↳ MSC_SUP_DEM_ENTRIES·↳ MSC_X_UDE_PEGGING·Explore MSC module →
-
APPS.MSC_SUP_DEM_ENTRIES_UI_V·↳ FND_GLOBAL·↳ MFG_LOOKUPS·↳ MSC_GROUP_COMPANIES·Explore MSC module →
-
APPS.MSC_SUP_DEM_ENTRIES_UI_V·↳ FND_GLOBAL·↳ MFG_LOOKUPS·↳ MSC_GROUP_COMPANIES·Explore MSC module →
-
This table stores the details of exceptions generated by Oracle Advanced Planning and Scheduling(APS) and Oracle Supply Chain Hub products.
-
This table contains exceptions generated in Oracle Collaborative planning
-
- Retrofitted
APPS.MRPBV_PLAN_EXCEPTION_DETAILS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MRP_EXCEPTION_DETAILS·Explore MRP module →
-
Enhanced exception message
APPS.MRP_EXCEPTION_DETAILS_V·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ MRP_EXCEPTION_DETAILS·Explore MRP module →
-
Enhanced exception message
APPS.MRP_EXCEPTION_DETAILS_V·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ MRP_EXCEPTION_DETAILS·Explore MRP module →
-
This table holds transaction data for Oracle Collaborative planning.
-
View: MSC_SUP_DEM_ENTRIES_V 12.1.1
APPS.MSC_SUP_DEM_ENTRIES_V·↳ MSC_SUP_DEM_ENTRIES·Explore MSC module →
-
The staging table used by the collection program to validate and process data for table MSC_SALES_ORDERS.
-
Table to maintain historical information on data loaded into Oracle Collaborative planning.
-
The staging table used by the collection program to validate and process data for table MSC_SALES_ORDERS.
-
This table lists all the supplies for this plan. The supplies created by the planning process are added to this table.
-
- Retrofitted
APPS.MRPBV_PLAN_EXCEPTION_DETAILS·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MRP_EXCEPTION_DETAILS·Explore MRP module →
-
- Retrofitted
APPS.MRPFV_PLAN_EXCEPTION_DETAILS·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ HR_ALL_ORGANIZATION_UNITS·Explore MRP module →
-
- Retrofitted
APPS.MRPFV_PLAN_EXCEPTION_DETAILS·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ HR_ALL_ORGANIZATION_UNITS·Explore MRP module →
-
View: MSC_SUP_DEM_ENTRIES_V 12.2.2
APPS.MSC_SUP_DEM_ENTRIES_V·↳ MSC_SUP_DEM_ENTRIES·Explore MSC module →
-
APPS.MSC_SUP_DEM_ENT_CUSTOM_EX_V·↳ MSC_SUP_DEM_ENTRIES·↳ MSC_X_UDE_PEGGING·Explore MSC module →
-
Table: MSC_SUP_DEM_HISTORY 12.2.2
Table to maintain historical information on data loaded into Oracle Collaborative planning.
-
this view picks up all the valid exception details
APPS.MSC_EXCEPTION_DETAILS_V·↳ MSC_DEMANDS·↳ MSC_EXCEPTION_DETAILS·↳ MSC_FULL_PEGGING·Explore MSC module →
-
this view picks up all the valid exception details
APPS.MSC_EXCEPTION_DETAILS_V·↳ MSC_DEMANDS·↳ MSC_EXCEPTION_DETAILS·↳ MSC_FULL_PEGGING·Explore MSC module →
-
This table holds transaction data for Oracle Collaborative planning.
-
This table contains exceptions generated in Oracle Collaborative planning
-
APPS.MSC_RELATED_EXC_DETAILS_V·↳ MFG_LOOKUPS·↳ MSC_DEMANDS·↳ MSC_DEPARTMENT_RESOURCES·Explore MSC module →
-
APPS.MSC_RELATED_EXC_DETAILS_V·↳ MFG_LOOKUPS·↳ MSC_DEMANDS·↳ MSC_DEPARTMENT_RESOURCES·Explore MSC module →
-
The staging table used by the collection program to validate and process data for table MSC_SUPPLIES.
-
The staging table used by the collection program to validate and process data for table MSC_SUPPLIES.
-
This table lists all the supplies for this plan. The supplies created by the planning process are added to this table.
-
TRIGGER: APPS.MSC_TRG_AUDIT 12.1.1