Results for “late_orders”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MRP_BIS_ORDERS_V is an Oracle Applications (APPS) seeded view in the Master Scheduling/MRP product family. It is classified in the ETRM as a VALID view owned by the APPS schema. Its purpose is to aggregate gross requirements data into a summary of order counts by organization, plan, and due date. The view derives its name and column set from the Business Intelligence System (BIS) reporting conventions, which were used to feed summary-level star-schema style reporting in Oracle EBS releases prior to the introduction of the Oracle Business Intelligence (OBIEE) based Supply Chain and Order Management analytics.
The view is most closely associated with late-order reporting. The search term "late_orders" corresponds directly to the LATE_ORDERS column exposed by this view, which counts gross requirement records whose supply is past due relative to the demand date. The view therefore provides a compact, pre-aggregated dataset useful for exception reporting and dashboard-style queries in 12.1.1 and 12.2.2 environments.
Because the view performs a GROUP BY aggregation, it returns at most one row per combination of organization, organization code, compile designator, and due date. This makes it efficient for high-level late-order counts but unsuitable for transaction-level drill-down, which requires querying MRP_GROSS_REQUIREMENTS directly.
Underlying Base Objects
The ETRM metadata documents the following referenced base objects:
- MRP_GROSS_REQUIREMENTS (SYNONYM) — the primary fact source. It stores gross requirements for a plan and is filtered on ORIGINATION_TYPE IN (6, 7), which restricts results to specific order origination categories (commonly discrete job and purchase requisition/order supply references).
- MRP_PLANS (SYNONYM) — the plan header, joined by COMPILE_DESIGNATOR. The view requires PLANS.PLAN_COMPLETION_DATE IS NOT NULL, ensuring only plans that have completed a run are included.
- ORG_ORGANIZATION_DEFINITIONS (VIEW) — supplies the ORGANIZATION_CODE attribute and enforces organization-level security context.
- HR_GENERAL and HR_SECURITY (PACKAGES) — referenced for organizational security enforcement in the application's access model.
The view text joins these objects on ORGANIZATION_ID and COMPILE_DESIGNATOR, then groups by those keys plus the resolved due date. The due date is computed as NVL(TRUNC(ASSEMBLY_DEMAND_COMP_DATE), TRUNC(USING_ASSEMBLY_DEMAND_DATE)), falling back to the using-assembly demand date when the completed assembly demand date is null.
Key Columns
- ORGANIZATION_ID — The inventory organization identifier, the master grouping key.
- ORGANIZATION_CODE — The human-readable organization code from ORG_ORGANIZATION_DEFINITIONS.
- COMPILE_DESIGNATOR — The MRP plan or simulation identifier.
- DUE_DATE — The truncated demand due date derived from the NVL expression in the view text.
- LATE_ORDERS — The count of gross requirements falling into this due-date bucket, enabling late-order exception analysis.
- TOTAL_ORDERS — The metric defined by the COUNT(*) in the view text. In the reported column definition this value is constant (0) in the supplied excerpt, reflecting the literal placeholder in the SELECT list; practically it represents the aggregated count of qualifying gross requirement rows per grouping key.
Common Use Cases and Queries
Typical usage is late-order exception reporting and plan performance monitoring. A representative query:
- SELECT ORGANIZATION_CODE, COMPILE_DESIGNATOR, DUE_DATE, LATE_ORDERS FROM APPS.MRP_BIS_ORDERS_V WHERE LATE_ORDERS > 0 ORDER BY ORGANIZATION_CODE, COMPILE_DESIGNATOR, DUE_DATE;
Developers also use the view as a source for BI publisher reports, custom concurrent programs, and dashboard extracts in 12.1.1/12.2.2. Because the view is APPS-owned and VALID, it can be referenced with standard APPS grants. For detail-level analysis, join MRP_GROSS_REQUIREMENTS directly; for summary KPIs, MRP_BIS_ORDERS_V provides the correct aggregation grain.
-
View: MRP_BIS_ORDERS_V 12.2.2
APPS.MRP_BIS_ORDERS_V·↳ HR_GENERAL·↳ HR_SECURITY·↳ MRP_GROSS_REQUIREMENTS·Explore MRP module →
-
View: MRP_BIS_ORDERS_V 12.1.1
APPS.MRP_BIS_ORDERS_V·↳ HR_GENERAL·↳ HR_SECURITY·↳ MRP_GROSS_REQUIREMENTS·Explore MRP module →
-
VIEW: APPS.MRP_BIS_ORDERS_V 12.1.1
-
VIEW: APPS.MRP_BIS_ORDERS_V 12.2.2
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench