Results for “input_type”

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

Overview

MRP_PLAN_SCHEDULES is a Master Scheduling/MRP (MRP) application table owned by the MRP schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold supply and demand schedules for Master Production Scheduling (MPS), Material Requirements Planning (MRP), and Distribution Requirements Planning (DRP) plans. It therefore acts as the planning engine's registry of which source schedules feed a given plan, tying plan runs to their input designators at the organization and plan-level granularity.

Under a heuristic Data Vault classification mined from the foreign-key structure, MRP_PLAN_SCHEDULES is best modeled as a link entity. It does not carry descriptive history of its own; instead it associates planning designators and organizations with a compiled plan. Treating it as a link is a modeling suggestion only — the physical object remains a conventional relational table with standard EBS who-columns and a descriptive attribute set.

Key Information Stored

The table contains 31 documented columns. The most operationally significant are the composite identifier columns and the audit/context columns inherited from the EBS standard column set.

• ORGANIZATION_ID — the inventory organization owning the plan schedule record; part of the primary key.
• COMPILE_DESIGNATOR — identifies the compiled plan run that this schedule belongs to; part of the primary key.
• INPUT_ORGANIZATION_ID — the organization supplying the source schedule; part of the primary key and a foreign-key component.
• INPUT_NAME — the designator name of the input schedule (for example a plan or schedule designator); part of the primary key and a foreign-key column.
• PLAN_LEVEL — the planning level at which the input is consumed; completes the primary key.
• INPUT_TYPE — categorizes the nature of the input schedule.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the request that created or last modified the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns reserved for customer-defined extensions.

The surrogate primary key is MRP_PLAN_SCHEDULES_PK, defined over ORGANIZATION_ID, COMPILE_DESIGNATOR, INPUT_ORGANIZATION_ID, INPUT_NAME, and PLAN_LEVEL. A unique index, MRP_PLAN_SCHEDULES_U1, is defined over the identical column set and represents the business-key candidate. In practice the primary key is a natural composite key rather than a system-generated surrogate, so join predicates must include all five components to guarantee uniqueness.

Common Use Cases and Queries

Typical uses include identifying which input designators contributed to a plan run, reconciling MPS/MRP/DRP plan composition, and auditing plan-level input configuration. A representative query lists all input schedules for a compiled plan:

• SELECT ORGANIZATION_ID, COMPILE_DESIGNATOR, INPUT_ORGANIZATION_ID, INPUT_NAME, PLAN_LEVEL, INPUT_TYPE FROM MRP.MRP_PLAN_SCHEDULES WHERE COMPILE_DESIGNATOR = :designator AND ORGANIZATION_ID = :org_id;
• Join to MRP_DESIGNATORS or MRP_SCHEDULE_DESIGNATORS on INPUT_NAME and INPUT_ORGANIZATION_ID to retrieve descriptive designator attributes.
• Filter by REQUEST_ID or PROGRAM_ID to trace which concurrent planning request produced a given set of schedule rows.
• Report by PLAN_LEVEL to summarize how many input schedules are consumed at each planning level.

Related Objects

The FK metadata identifies two referenced designator tables, and the surrounding MRP schema supplies the principal related objects used in reporting and integration.

• MRP_DESIGNATORS — referenced on INPUT_NAME (and INPUT_ORGANIZATION_ID); the primary source of designator descriptive data.
• MRP_SCHEDULE_DESIGNATORS — also referenced on INPUT_NAME and INPUT_ORGANIZATION_ID; provides schedule-specific designator context.
• MRP_PLAN_SCHEDULES_PK / MRP_PLAN_SCHEDULES_U1 — the primary key constraint and unique index enforcing business-key uniqueness on the five identifier columns.
• MRP_ORG_PLANS and MRP_PLANS — plan definition tables commonly joined on COMPILE_DESIGNATOR and ORGANIZATION_ID to resolve plan names.
• MRP_GROSS_REQUIREMENTS / MRP_SUGGESTED_SUPPLIES — planning output tables keyed by COMPILE_DESIGNATOR and ORGANIZATION_ID, frequently correlated with the schedules defined here.

Because the table is a scheduling link rather than a transactional fact store, related reporting is generally performed through designator and plan dimension tables rather than by extensive direct querying of MRP_PLAN_SCHEDULES itself.