Results for “quantity_available”

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

Overview

MRP_AVAILABLE_TO_PROMISE is an Oracle EBS table in the MRP (Master Scheduling/MRP) schema that stores available-to-promise (ATP) information for master scheduled parts. It provides the authoritative record of ATP query results — the quantities that can be committed to customer orders or demand at specific schedule dates, given the current master production schedule, supply, and demand picture. In the Oracle EBS 12.1.1 and 12.2.2 releases, this table is typically populated by the ATP processing logic (the ATP/Planning engine) when scheduling or rescheduling requests are executed, and it is consulted by order entry and scheduling flows to validate whether requested quantities can be promised by a given date.

Under the heuristic Data Vault classification derived from its foreign key structure, the object leans toward a satellite. This should be read as a modeling suggestion rather than a documented physical design assertion: it carries descriptive, time-stamped measures (such as available quantity and status) that describe an entity (the inventory item at a given organization and compile designator) at a point in time, rather than acting primarily as a hub or a many-to-many link.

Key Information Stored

The table documents 17 physical columns, of which the most significant are:

• TRANSACTION_ID — the surrogate primary key (MRP_AVAILABLE_TO_PROMISE_PK). It uniquely identifies each ATP record and is also a business-key candidate via MRP_AVAILABLE_TO_PROMISE_U2.
• INVENTORY_ITEM_ID — identifies the master scheduled item for which ATP information is held; participates in the foreign key to MRP_SYSTEM_ITEMS.
• ORGANIZATION_ID — the inventory organization context; also part of the MRP_SYSTEM_ITEMS foreign key.
• COMPILE_DESIGNATOR — distinguishes the planning compile/instance under which the ATP data was generated; a component of the MRP_SYSTEM_ITEMS foreign key.
• SCHEDULE_DATE — the date for which the available quantity applies. Together with INVENTORY_ITEM_ID, COMPILE_DESIGNATOR, and ORGANIZATION_ID, it forms the business-key candidate MRP_AVAILABLE_TO_PROMISE_U1.
• QUANTITY_AVAILABLE — the ATP quantity available for the item on the given schedule date.
• STATUS — status indicator for the ATP record.
• UPDATED — flag indicating whether the row has been updated by the ATP process.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns tracking who created and last modified the record and when.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the request and program that generated or last refreshed the row.

The distinction between the surrogate key (TRANSACTION_ID) and the business-key candidates (U1 on item/designator/organization/date; U2 on TRANSACTION_ID) is central to understanding uniqueness constraints when writing joins or de-duplication logic.

Common Use Cases and Queries

ATP reporting typically retrieves the latest available quantity for an item/organization at or after a requested date. A representative query pattern joins the table to MRP_SYSTEM_ITEMS on the documented composite key:

• ATP lookup for order promising: filter by INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, and SCHEDULE_DATE to return QUANTITY_AVAILABLE for a promise date check.
• Time-phased ATP reporting: order results by SCHEDULE_DATE to render an ATP profile across a horizon, aggregating QUANTITY_AVAILABLE by date for planning dashboards.
• Stale data identification: use PROGRAM_UPDATE_DATE, LAST_UPDATE_DATE, or UPDATED to find ATP rows not refreshed by the most recent plan run.
• Audit and lineage: reference REQUEST_ID and PROGRAM_ID to trace which concurrent request produced a given ATP snapshot.

A common join form is: SELECT a.INVENTORY_ITEM_ID, a.ORGANIZATION_ID, a.SCHEDULE_DATE, a.QUANTITY_AVAILABLE FROM MRP.MRP_AVAILABLE_TO_PROMISE a, MRP.MRP_SYSTEM_ITEMS s WHERE a.INVENTORY_ITEM_ID = s.INVENTORY_ITEM_ID AND a.ORGANIZATION_ID = s.ORGANIZATION_ID AND a.COMPILE_DESIGNATOR = s.COMPILE_DESIGNATOR;

Related Objects

• MRP_SYSTEM_ITEMS — the referenced parent; joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR (per the documented foreign key).
• MRP_AVAILABLE_TO_PROMISE_PK / _U1 / _U2 — the primary and unique indexes enforcing record identity and business uniqueness.
• Planning and scheduling engine objects in the MRP schema (e.g., planning schedules and compile-designator-driven plan tables) that populate this table during ATP processing.
• Order Management / scheduling validation logic that consumes ATP quantities for promise-date validation.
• Standard EBS audit and concurrent program tables referenced implicitly via the REQUEST_ID and PROGRAM_ID columns.