Results for “firm_planned_status_type”

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

Overview

The MRP_REPETITIVE_SCHEDULES table in the MRP schema stores current repetitive manufacturing schedules as understood by Oracle Master Scheduling/MRP. Repetitive scheduling is used when an item is produced at a relatively constant daily rate over a defined horizon rather than through discrete work orders. Each row represents a scheduled repetitive build for a specific inventory item, organization, and compile designator, tied to a Work in Process entity and a schedule identifier. The table is populated and maintained by the MRP planning engine as well as by WIP repetitive schedule transactions, and it reflects the production rate, start and completion dates, and the current status of each schedule.

From a Data Vault modeling perspective, the heuristic classification of this table is a link. Because MRP_REPETITIVE_SCHEDULES exists to associate inventory items, organizations, WIP entities, repetitive lines, and revisions, it behaves as a transactional junction rather than a descriptive hub or a slowly changing satellite. The surrogate-style composite primary key MRP_REPETITIVE_SCHEDULES_PK (INVENTORY_ITEM_ID, COMPILE_DESIGNATOR, ORGANIZATION_ID, WIP_ENTITY_ID, SCHEDULE_ID) reinforces this link interpretation, with the unique index MRP_REPETITIVE_SCHEDULES_U1 covering the same business-key columns.

Key Information Stored

The most operationally significant columns include the primary key components and the scheduling attributes that drive repetitive planning:

• INVENTORY_ITEM_ID — the item being built; part of the composite primary key.
• ORGANIZATION_ID — the inventory organization owning the schedule; part of the primary key.
• COMPILE_DESIGNATOR — distinguishes planning compilations; part of the primary key.
• WIP_ENTITY_ID — the WIP entity associated with the repetitive schedule; part of the primary key.
• SCHEDULE_ID — unique schedule instance identifier; part of the primary key.
• REPETITIVE_LINE — the production line used (foreign key to WIP_LINES).
• FIRST_UNIT_START_DATE / FIRST_UNIT_COMPLETION_DATE — start and completion of the first unit.
• LAST_UNIT_START_DATE / LAST_UNIT_COMPLETION_DATE — start and completion of the last unit.
• DAILY_RATE — the units produced per day, the core driver of repetitive planning.
• PROCESSING_DAYS — number of working days over which the rate applies.
• REVISION — item revision being built (foreign key to MTL_ITEM_REVISIONS_B).
• STATUS_CODE and FIRM_PLANNED_STATUS_TYPE — schedule status and firm/planned classification.
• COMPLETED_UNITS — units already completed against the schedule.
• DEMAND_CLASS — demand classification carried from planning.
• PROJECT_ID / TASK_ID — project and task association where applicable.

Audit columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, and related) capture who created or updated the row and the concurrent program that produced it. The unique index MRP_REPETITIVE_SCHEDULES_U1 over the five primary key columns serves as the documented business-key candidate.

Common Use Cases and Queries

Typical reporting scenarios include repetitive schedule load by line, daily capacity utilization, and comparison of planned versus completed units.

• Retrieve active repetitive schedules for an organization and item:

SELECT schedule_id, repetitive_line, daily_rate,
       first_unit_start_date, last_unit_completion_date,
       status_code, completed_units
FROM   mrp.mrp_repetitive_schedules
WHERE  organization_id = :org_id
AND    inventory_item_id = :item_id;

• Join to WIP_LINES to report volume by production line:

SELECT l.line_code, r.daily_rate, r.daily_rate * r.processing_days AS scheduled_units
FROM   mrp.mrp_repetitive_schedules r,
       wip.wip_lines l
WHERE  r.repetitive_line = l.line_id
AND    r.organization_id = :org_id;

• Compare completed versus planned output per schedule to identify shortfalls.
• Identify schedules pending firming by filtering FIRM_PLANNED_STATUS_TYPE.
• Feed capacity and rate-based reporting for lines and resources.

Related Objects

• MRP_SYSTEM_ITEMS — joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR; validates the planned item.
• WIP_LINES — joined on REPETITIVE_LINE; supplies production line attributes.
• MTL_ITEM_REVISIONS_B — joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, and REVISION; resolves the item revision.
• WIP_ENTITIES — related through WIP_ENTITY_ID for discrete WIP context on the schedule.
• MRP_SCHEDULE_DATES and MRP_ITEM_SCHEDULES — related planning schedule objects that consume repetitive schedule results.
• MTL_SYSTEM_ITEMS_B — master item definition referenced through the inventory item.

These relationships confirm MRP_REPETITIVE_SCHEDULES as a central junction in repetitive planning, linking items, organizations, lines, and WIP entities across the Master Scheduling/MRP and Work in Process modules.