Results for “organization_selection”

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

Overview

MRP_DESIGNATORS_VIEW is a consolidated, read-only view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is registered in the E-Business Suite Technical Reference Manual (ETRM) as a VALID database object belonging to the MRP — Master Scheduling/MRP product family. As its description ("Designator view") indicates, the view presents a unified list of scheduling and planning designators available to the planning engine, spanning both master production scheduling (MPS) and material requirements planning (MRP) contexts, plus distribution requirements planning (DRP) designators stored in the legacy designator table.

The view exists primarily to give reporting, integration, and diagnostic queries a single source for designator metadata without requiring callers to union the two underlying designator tables manually. Because it is a view rather than a table, it holds no data of its own; all values are resolved at query time from its constituent base objects, and it inherits the security and read consistency behaviour of those tables.

Underlying Base Objects

Per the documented metadata, MRP_DESIGNATORS_VIEW is defined over two synonymed base objects:

• MRP_SCHEDULE_DESIGNATORS — the source of schedule designators (MPS/MRP schedule definitions).
• MRP_DESIGNATORS — the legacy designator table, which also carries DRP-related designators.

The view text is a UNION ALL: the first branch selects directly from MRP_SCHEDULE_DESIGNATORS S, and the second branch selects from MRP_DESIGNATORS D. In the second branch, several columns are transformed rather than passed through unchanged: the DESIGNATOR_TYPE column is derived via DECODE(D.DRP_PLAN, 1, 4, 3), and MPS_RELIEF is hard-coded to -1. Because the union is UNION ALL and not UNION, duplicate designator rows are not eliminated, and no implicit de-duplication or sorting is performed. Both branches project identical column lists, which is what allows the union to succeed.

Key Columns

The view exposes fourteen columns. The more significant ones are:

• DESIGNATOR — the designator name or code. It is populated from SCHEDULE_DESIGNATOR in the schedule branch and from COMPILE_DESIGNATOR in the legacy branch.
• ORGANIZATION_ID — the inventory organization to which the designator belongs.
• DESIGNATOR_TYPE — numeric classification of the designator. For schedule designators this is SCHEDULE_TYPE; for the legacy branch it is computed from DRP_PLAN (1 yields 4, otherwise 3).
• MPS_RELIEF — relief flag; taken from the schedule table in the first branch and forced to -1 in the second.
• DISABLE_DATE, USE_NEW_PLANNER, ORGANIZATION_SELECTION, PRODUCTION — planning behaviour and control attributes carried through from both branches.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns for auditing.
• DESCRIPTION — free-text description of the designator.

Common Use Cases and Queries

Typical uses include listing all designators for an organization, identifying DRP-derived designators, and auditing recently changed designator definitions. A representative query is:

SELECT designator,
       organization_id,
       designator_type,
       description,
       disable_date
FROM   apps.mrp_designators_view
WHERE  organization_id = :org_id
ORDER  BY designator;

To isolate DRP-based entries, filter on the computed type:

SELECT designator, organization_id
FROM   apps.mrp_designators_view
WHERE  designator_type = 4;

To audit recent maintenance activity, restrict on the WHO column:

SELECT designator, last_update_date, last_updated_by
FROM   apps.mrp_designators_view
WHERE  last_update_date >= SYSDATE - 30;

Because the view resolves against live planning tables, queries should be executed with the APPS schema or a responsibility whose data grants include the MRP designator tables. Given the UNION ALL construction, consumers should be prepared for potential duplicate designator names across the two source branches.