Results for “department_line_code”

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

Overview

MRP_EXCEPTION_SUMMARY_V is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP module, documented in ETRM for releases 12.1.1 and 12.2.2 with a status of VALID. Its stated purpose is to present an "enhanced exception message" — that is, a denormalized, reporting-friendly projection of planning exception data that has been enriched with descriptive attributes drawn from adjacent manufacturing tables and lookup definitions. The view is defined over the MRP_FORM_QUERY entity and resolves raw numeric foreign-key values stored there into human-readable codes and meanings, making it suitable for planner-facing reports, concurrent program outputs, and integration extracts.

The enhancement is achieved principally through outer joins to BOM_DEPARTMENTS, BOM_RESOURCES, and WIP_LINES, and through inner and outer joins to MFG_LOOKUPS for exception type, exception version, and resource type translation. The view also invokes the MRP_GET_PROJECT package to resolve project and task identifiers. A row filter of MFQ.NUMBER13 = 1 restricts output to the current or active exception record set, which is important to note when building queries, since historical exception rows are excluded.

Underlying Base Objects

The view is defined over MRP_FORM_QUERY (synonym), which supplies the driving exception rows, and joins to the following documented base objects:

• MFG_LOOKUPS (view) — supplies exception type text via lookup type MRP_EXCEPTION_CODE_TYPE, the version meaning via MRP_EXCEPTION_VERSION, and resource type descriptions via BOM_RESOURCE_TYPE.
• BOM_DEPARTMENTS (synonym) — outer-joined on DEPARTMENT_ID = MFQ.NUMBER9 to provide DEPARTMENT_CODE.
• BOM_RESOURCES (synonym) — outer-joined on RESOURCE_ID = MFQ.NUMBER10 to provide RESOURCE_CODE.
• WIP_LINES (synonym) — outer-joined on LINE_ID = MFQ.NUMBER11 to provide LINE_CODE.
• MRP_GET_PROJECT (package) — called as MRP_GET_PROJECT.PROJECT and MRP_GET_PROJECT.TASK to resolve project and task numbers from MFQ.NUMBER6 and MFQ.NUMBER7.

Because the department, resource, and line joins are outer joins, exception rows that do not reference a departmental or production-line context are still returned, with the corresponding code columns null or defaulted. The DEPARTMENT_LINE_CODE column is computed as NVL(DEPT.DEPARTMENT_CODE, LINE.LINE_CODE), so it reflects whichever context is populated for a given exception.

Key Columns

• EXCEPTION_TYPE — numeric exception code derived from MFQ.NUMBER2; translated by MFG_LOOKUPS.
• EXCEPTION_TYPE_TEXT — the lookup meaning for the exception code, i.e., the displayed exception message.
• COMPILE_DESIGNATOR, ORGANIZATION_ID, VERSION, EXCEPTION_COUNT — plan identification and count of affected entries.
• INVENTORY_ITEM_ID, ITEM_SEGMENTS, PLANNER_CODE — the item in exception and its concatenated segments and planner.
• PROJECT_ID, PROJECT_NUMBER, TASK_ID, TASK_NUMBER — project and task resolution via MRP_GET_PROJECT (from NUMBER6 and NUMBER7).
• DEPARTMENT_ID, RESOURCE_ID, LINE_ID — identifiers of the responsible department, resource, and production line.
• DEPARTMENT_LINE_CODE — the resolved department code or, failing that, the production line code; this is the column most often targeted by users searching for "department_line_code."
• RESOURCE_CODE, RESOURCE_TYPE, RESOURCE_TYPE_CODE — resource identification and its type meaning.
• ORGANIZATION_CODE, BUYER_NAME, PLANNING_GROUP, CATEGORY_ID — additional planning context.
• QUERY_ID, DISPLAY, ROW_ID — internal query and row identifiers used by the MRP exception workbench.

Common Use Cases and Queries

Typical uses include extracting open planning exceptions by organization or planner, reporting exceptions by responsibility area using DEPARTMENT_LINE_CODE, and feeding exception data into custom dashboards or downstream systems. The following query lists active exceptions with their resolved department or line code:

• SELECT organization_code, inventory_item_id, exception_type_text, planner_code, department_line_code, resource_code, exception_count FROM apps.mrp_exception_summary_v WHERE organization_id = :org_id ORDER BY exception_type_text, inventory_item_id;
• SELECT department_line_code, exception_type_text, COUNT(*) FROM apps.mrp_exception_summary_v GROUP BY department_line_code, exception_type_text ORDER BY 3 DESC;
• SELECT project_number, task_number, exception_type_text FROM apps.mrp_exception_summary_v WHERE project_id IS NOT NULL;

Because DEPARTMENT_LINE_CODE is a resolved expression rather than an indexed base column, filtering directly on it can inhibit index usage; filtering on DEPARTMENT_ID, LINE_ID, or ORGANIZATION_ID where possible generally yields better performance. All access should respect the APPS schema privileges and standard EBS security and MOAC (multi-org) policies.