Results for “disposition_type”

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

Overview

The MRP_SCHEDULE_CONSUMPTIONS table resides in the MRP schema and belongs to the Master Scheduling/MRP product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores consumption history for the master schedule, capturing the transactional record of how forecast or schedule demand has been relieved (consumed) against actual demand, orders, or dispositions during the planning cycle. In manufacturing environments, consumption logic is central to avoiding double-counting of demand: when a sales order or work order materializes, the corresponding forecast quantity must be reduced or "consumed" from the master schedule.

Under a heuristic Data Vault classification mined from its foreign key structure, this table is satellite-leaning. That is, it behaves primarily as a descriptive satellite attached to a parent business entity (keyed informally through DISPOSITION_ID to WIP_ENTITIES), recording the measurable, time-stamped attributes of consumption events rather than acting as a pure hub or link. This classification is a modeling suggestion derived from the FK topology, not a documented EBS constraint.

Key Information Stored

The table contains 18 documented columns. The most significant include:

• TRANSACTION_ID — the surrogate primary key uniquely identifying each consumption record.
• DISPOSITION_ID — foreign key to WIP_ENTITIES; identifies the disposition entity associated with the consumption.
• DISPOSITION_TYPE — classifies the nature of the disposition (for example, sales order, work order, or job).
• RELIEF_TYPE — indicates the method or basis by which the schedule was relieved.
• LINE_NUM — line sequence within the consumption detail.
• ORDER_DATE — the date of the originating order driving the consumption.
• ORDER_QUANTITY — the quantity ordered that triggers the relief.
• RELIEF_QUANTITY — the actual quantity consumed or relieved from the master schedule.
• SCHEDULE_DATE — the schedule bucket or date against which consumption occurs.
• REQUEST_ID — the concurrent request that generated or processed the record.
• PROGRAM_ID / PROGRAM_APPLICATION_ID / PROGRAM_UPDATE_DATE — the concurrent program context and its last execution timestamp.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns supporting traceability and user accountability.

The surrogate key is TRANSACTION_ID. Candidate business keys are not formally documented as unique indexes in the supplied metadata, so no reliable natural key can be asserted beyond the disposition/order/line combination.

Common Use Cases and Queries

Planners and supply chain analysts use this table to audit forecast consumption, reconcile master schedule relief, and explain variances between scheduled and actual demand. A typical query joins the consumption history to WIP_ENTITIES to resolve the disposition context:

• Reconciling relief quantities by schedule date for a given order.
• Auditing which concurrent program (REQUEST_ID, PROGRAM_ID) produced a consumption record.
• Reporting consumption history for a specific disposition entity via DISPOSITION_ID.
• Tracing demand relief across order dates for consumption-rule analysis.

An illustrative pattern: SELECT c.TRANSACTION_ID, c.ORDER_QUANTITY, c.RELIEF_QUANTITY, c.SCHEDULE_DATE FROM MRP.MRP_SCHEDULE_CONSUMPTIONS c WHERE c.DISPOSITION_ID = :entity_id ORDER BY c.SCHEDULE_DATE;

Related Objects

The most significant relationship is the foreign key MRP_SCHEDULE_CONSUMPTIONS.DISPOSITION_ID → WIP_ENTITIES, which anchors each consumption record to a work-in-process entity. Related planner-facing objects include the master schedule and forecast tables within the MRP schema, and the concurrent program and request infrastructure that populate REQUEST_ID and PROGRAM_ID. Reports and planning workbench views frequently join this table to disposition and demand entities to present relief history alongside the master schedule.