Results for “implement_processing_days”

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

Overview

MRP_SUGG_REP_SCHEDULES is a table in the MRP (Master Scheduling/MRP) schema of Oracle E-Business Suite, holding suggested repetitive schedules produced by the MRP, MPS, and DRP planning engines. When the planner runs a repetitive planning cycle, the calculation engine generates recommendations that propose daily rates, processing days, and start/completion dates for items produced on repetitive manufacturing lines. This table persists those suggestions before they are reviewed, accepted, or released into Work in Process as actual repetitive schedules.

The table acts as a staging area between planning outputs and execution. A record in MRP_SUGG_REP_SCHEDULES does not represent an authorized production schedule; it represents a planner recommendation awaiting disposition. Rows link back to the originating recommendation through TRANSACTION_ID and to the target repetitive line through REPETITIVE_LINE, and they are keyed to a specific item and organization.

The mined Data Vault classification for this object is a link, reflecting that it sits at the intersection of recommendations, repetitive lines, and item/organization definitions rather than being an independent hub. In modeling terms, it is best treated as a transactional association between planning recommendations and manufacturing resources.

Key Information Stored

The table contains 31 documented columns. The most operationally significant are:

• TRANSACTION_ID — Foreign key to MRP_RECOMMENDATIONS; identifies the parent planning recommendation that generated this suggested schedule. This is the primary correlation key for tracing back to the planner workbench.
• REPETITIVE_LINE — Foreign key to WIP_LINES; the repetitive manufacturing line on which the schedule would be executed.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — Composite foreign key to MRP_SYSTEM_ITEMS, defining the planned item and its manufacturing organization.
• COMPILE_DESIGNATOR — Part of the composite item key, distinguishing configured or designator-specific item variants.
• FIRST_UNIT_START_DATE, LAST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_COMPLETION_DATE — The proposed schedule window for the repetitive run.
• DAILY_RATE and PROCESSING_DAYS — The suggested production rate and the number of working days over which it applies.
• FIRM_PLANNED_STATUS_TYPE — Indicates whether the recommendation is firm or planned.
• LOAD_FACTOR_RATE and LOAD_TYPE — Capacity loading parameters used by the repetitive planning algorithm.
• IMPLEMENT_* columns (IMPLEMENT_DATE, IMPLEMENT_DAILY_RATE, IMPLEMENT_FIRM, IMPLEMENT_PROCESSING_DAYS, IMPLEMENT_WIP_CLASS_CODE, IMPLEMENT_LINE_ID, IMPLEMENT_DEMAND_CLASS) — The planner-adjusted values captured at the moment of implementation into WIP.
• RELEASE_STATUS and RELEASE_ERRORS — Track whether the suggestion has been successfully released and any error text from a failed release attempt.
• STATUS and UPDATED — Workflow and synchronization flags between planning and execution.

Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN follow standard EBS conventions. The metadata does not document a single-column surrogate primary key; the effective business key is the combination of TRANSACTION_ID, REPETITIVE_LINE, and the item/organization/designator tuple. SOURCE_ITEM_ID provides a reference to the originating item when the suggestion was derived from a substitute or source relationship.

Common Use Cases and Queries

Planners and developers consult this table to inspect suggested repetitive schedules before release, to diagnose failed release attempts, and to audit historical recommendations. A typical query retrieves all pending suggestions for a given item and organization:

• Join to MRP_SYSTEM_ITEMS on (INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) to resolve item descriptions and planning attributes.
• Filter on RELEASE_STATUS and RELEASE_ERRORS to isolate suggestions that failed to release into WIP, which is a common workflow-support scenario.
• Join to MRP_RECOMMENDATIONS on TRANSACTION_ID to tie each suggestion back to the originating planner recommendation and its disposition.
• Compare DAILY_RATE against IMPLEMENT_DAILY_RATE to detect planner overrides at implementation time.
• Aggregate PROCESSING_DAYS and DAILY_RATE by REPETITIVE_LINE and date range to build capacity-loading reports.

Because the table is populated by concurrent planning programs, it should be queried with attention to the organization and compile designator context; results without these filters can conflate suggestions across multiple manufacturing entities.

Related Objects

The following objects are the most significant in relation to MRP_SUGG_REP_SCHEDULES, based on documented foreign key relationships and standard MRP/WIP integration:

• MRP_RECOMMENDATIONS — Parent recommendation table, joined on TRANSACTION_ID. Use this to trace suggestion provenance and planner disposition.
• WIP_LINES — Repetitive line definition, joined on REPETITIVE_LINE. Provides line capacity, department, and scheduling attributes.
• MRP_SYSTEM_ITEMS — Item/organization master, joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR. Supplies planning and sourcing attributes.
• WIP_REPETITIVE_SCHEDULES — Target execution table populated when a suggestion is implemented and released to Work in Process.
• MRP_REPETITIVE_SCHEDULES — Planning-side repetitive schedule view used for comparison against suggested values.
• MRP_ITEM_SOURCING and MRP_SAFETY_STOCKS — Supporting planning inputs that influence the generated daily rate and processing days.
• WIP_MOVE_TRANSACTIONS and MTL_MATERIAL_TRANSACTIONS — Downstream execution tables consulted when reconciling released suggestions against actual production.

Together these objects form the planning-to-execution chain that MRP_SUGG_REP_SCHEDULES bridges, making it an essential reference point for any reporting, workflow customization, or integration that touches suggested repetitive manufacturing output in Oracle EBS 12.1.1 and 12.2.2.