Results for “mrp_aggregate_rates”

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

Overview

MRP_AGGREGATE_RATES is a table in the MRP schema (Master Scheduling/MRP product) that stores suggested aggregate repetitive rates of production. During repetitive manufacturing planning, Oracle MRP computes aggregate rates that represent the recommended daily quantity of an item to be produced on a repetitive schedule, keyed by the plan (compile designator), organization, item, and the first unit completion date of each rate period. The table therefore acts as a plan-time output store, populated by the MRP/MPS planning programs and consumed by repetitive planning, scheduling, and reporting functions.

Heuristically, the mined foreign-key structure classifies this object as satellite-leaning in a Data Vault modeling sense. This is a suggestion rather than a documented designation: the table describes measurable attributes (rates, dates, processing days, plan status) of a parent business entity — the item/organization plan combination — rather than acting as a pure hub of distinct business keys or a link between multiple hubs. Modelers treating this as a satellite would attach it to a hub representing the inventory item (qualified by organization and compile designator) and a rate-date relationship, with the descriptive rate attributes retained as satellite payload.

Key Information Stored

The table contains 23 documented columns. The primary key, MRP_AGGREGATE_RATES_PK, is a composite of INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, and FIRST_UNIT_COMPLETION_DATE. A unique index, MRP_AGGREGATE_RATES_U1, covers the same four columns in the order ORGANIZATION_ID, COMPILE_DESIGNATOR, INVENTORY_ITEM_ID, FIRST_UNIT_COMPLETION_DATE, making these columns the business-key candidate for the object.

The most significant columns hold:

• INVENTORY_ITEM_ID — the inventory item for which the aggregate rate is suggested; participates in the foreign key to MRP_SYSTEM_ITEMS.
• ORGANIZATION_ID — the organization in which the repetitive rate applies.
• COMPILE_DESIGNATOR — identifies the MRP/MPS plan that produced the rate row.
• FIRST_UNIT_COMPLETION_DATE and LAST_UNIT_COMPLETION_DATE — the completion-date window covered by the rate bucket.
• FIRST_UNIT_START_DATE and LAST_UNIT_START_DATE — the corresponding start-date window for the units.
• PROCESSING_DAYS — number of manufacturing days available in the period.
• DAILY_RATE — the suggested aggregate production rate per day.
• MINIMUM_FIRM_RATE — the minimum rate that should be firmed for the bucket.
• FIRM_PLAN_STATUS_TYPE — the firm plan status associated with the rate.
• REVISION — the item revision applicable to the rate.
• PROJECT_ID and TASK_ID — project and task context where the rate is project-referenced.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the planner run that created the row.

Common Use Cases and Queries

The table is typically queried to review suggested repetitive rates for a given plan and organization, to compare minimum firm rates against suggested daily rates, and to report rate capacity across date buckets. A representative query pattern joins to MRP_SYSTEM_ITEMS to resolve the item:

• Filter by COMPILE_DESIGNATOR and ORGANIZATION_ID to return all suggested rates for a specific MRP plan run.
• Order by INVENTORY_ITEM_ID and FIRST_UNIT_COMPLETION_DATE to display a time-phased rate schedule per item.
• Compare DAILY_RATE against MINIMUM_FIRM_RATE to highlight buckets where firming is required.
• Aggregate DAILY_RATE across items to model plant-level repetitive capacity loading.
• Join on REQUEST_ID to trace rates back to the concurrent request that generated them.

Related Objects

• MRP_SYSTEM_ITEMS — referenced through the foreign key on INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR; the primary parent for item context.
• MRP_AGGREGATE_RATES_PK — the composite primary key constraint defining row uniqueness.
• MRP_AGGREGATE_RATES_U1 — the unique index reinforcing the business-key candidate columns.
• MRP planning and repetitive scheduling concurrent programs — populate this table during plan compilation via the audit columns (REQUEST_ID, PROGRAM_ID).
• Repetitive schedule and rate reporting views in the MRP product — consume DAILY_RATE and date-window columns.