Results for “dept_line_id”

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

Overview

MSC_PDR_LATE_ORDER_EXC_V is an APPS-owned database view in the Oracle E-Business Suite Advanced Supply Chain Planning (MSC) module. It exposes late-order planning exceptions produced by the Planner Workbench and related exception-generation processes, presenting them in a flattened, user-facing format suitable for reporting, integration, and custom inquiry screens. The "PDR" prefix associates the view with the Planner Desktop Report / personalized planning exception framework, and the "_EXC_V" suffix confirms it is an exception view. Its purpose is to surface orders whose demand satisfaction date falls after the due date (classified under exception types 24 and 26, for which a lateness quantity in days is calculated) alongside related exception categories 10, 13, 14, 15, 16, and 30.

The view is a read-only reporting construct. It does not store data; it joins pre-aggregated exception detail rows to system item and item category information, then filters results by the parameters defined for the currently connected user. Because of that user-based filtering, the view behaves as a personalized, session-sensitive query rather than a global exception table.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, MSC_PDR_LATE_ORDER_EXC_V references the following base objects:

• MSC_EXCEPTION_DETAILS_V (VIEW) — aliased as PP; the primary source of exception rows.
• MSC_SYSTEM_ITEMS (SYNONYM) — aliased as MSI; provides plan-level item context and is joined on PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, and INVENTORY_ITEM_ID.
• MSC_ITEM_CATEGORIES (SYNONYM) — aliased as MIC; supplies SR_CATEGORY_ID and category-set context.
• MSC_PDR_PARAMETERS (SYNONYM) — restricts output to plans, organizations, source instances, and category sets configured for the current user.
• MSC_PLANS (SYNONYM), FND_GLOBAL (PACKAGE), and MSC_GET_NAME (PACKAGE) — supporting objects referenced by the view and its dependencies.

The view text confirms inner joins across MSC_EXCEPTION_DETAILS_V, MSC_SYSTEM_ITEMS, and MSC_ITEM_CATEGORIES, with all output filtered by MSC_PDR_PARAMETERS for FND_GLOBAL.USER_ID.

Key Columns

The view projects a broad set of exception and planning attributes, including:

• EXCEPTION_TYPE_TEXT, EXCEPTION_TYPE — the displayed and coded exception classification.
• ORGANIZATION_CODE, ORGANIZATION_ID — the planning organization.
• ITEM_SEGMENTS, INVENTORY_ITEM_ID — concatenated and surrogate item identifiers.
• RESOURCE_CODE, RESOURCE_ID — the constrained resource where applicable.
• ORDER_NUMBER, SUPPLY_TYPE — the affected order.
• DUE_DATE, DMD_SATISFIED_DATE — the dates used to compute lateness; for exception types 24 and 26 the view returns TRUNC of the difference, otherwise TO_DATE(NULL).
• QUANTITY, QUANTITY_BY_DUE_DATE — affected and date-qualified quantities.
• PROJECT_NUMBER, TASK_NUMBER — project/task context.
• SUPPLIER_NAME/SUPPLIER_SITE and CUSTOMER_NAME/CUSTOMER_SITE — concatenated party strings.
• ORDER_PRIORITY — order urgency.
• PLANNER_CODE (planner_code_id) — the planner identifier commonly used to filter results by buyer/planner responsibility.
• BUYER_NAME — the assigned buyer.
• PLAN_ID, SR_INSTANCE_ID, CATEGORY_SET_ID, SR_CATEGORY_ID — planning and source-instance keys.

Common Use Cases and Queries

Typical usage involves filtering exceptions by planner, organization, or item to drive late-order dashboards. A representative query isolating a single planner's late orders is:

• SELECT ORDER_NUMBER, ITEM_SEGMENTS, ORGANIZATION_CODE, DUE_DATE, DMD_SATISFIED_DATE, QUANTITY, PLANNER_CODE FROM MSC_PDR_LATE_ORDER_EXC_V WHERE PLANNER_CODE = :planner_code_id AND TRUNC(DUE_DATE) BETWEEN :from_date AND :to_date ORDER BY DUE_DATE;
• SELECT ORGANIZATION_CODE, EXCEPTION_TYPE_TEXT, COUNT(*) FROM MSC_PDR_LATE_ORDER_EXC_V GROUP BY ORGANIZATION_CODE, EXCEPTION_TYPE_TEXT;
• SELECT SUPPLIER_NAME, ORDER_NUMBER, DUE_DATE, DMD_SATISFIED_DATE FROM MSC_PDR_LATE_ORDER_EXC_V WHERE EXCEPTION_TYPE = 24 ORDER BY DUE_DATE;

Because output is scoped by MSC_PDR_PARAMETERS for the connected user, queries executed from a background concurrent program or an integration account may return no rows unless parameters exist for that FND_GLOBAL.USER_ID. This is the most frequent cause of unexpected empty results.