Results for “flow_status_code”

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

Overview

The APPS.MRP_ATP_SCHEDULE_TEMP_V view is a reporting and integration interface within the Oracle E-Business Suite Master Scheduling/MRP module. It exposes the working contents of the ATP scheduling temporary table together with derived descriptive attributes, allowing callers to inspect the availability check results produced during Available-to-Promise (ATP) processing. The object carries a status of VALID and is owned by the APPS schema.

In discrete EBS release terms the same definition is shipped under 12.1.1 and 12.2.2; the product classification and column set are stable between the two releases. The view is not an end-user form-backed entity but a technical surface used by scheduling engines, concurrent programs, and custom extensions that need to read the intermediate state of an ATP or order scheduling run without writing directly to the underlying temporary table.

The presence of the DELIVERY_LEAD_TIME column is significant for users investigating delivery scheduling behaviour, since it records the lead time applied between shipment and arrival for each processed line. Because the source is a temporary/staging structure, rows in the view are scoped by SESSION_ID and are transient in nature, typically persisting only for the duration of the scheduling or ATP invocation that populated them.

Underlying Base Objects

The documented base objects referenced by the view definition are:

• MRP_ATP_SCHEDULE_TEMP (exposed through a SYNONYM) — the primary source of scheduling rows. Column aliases such as MAST identify this table in the view text and supply the majority of the projected attributes.
• OE_ORDER_LINES_ALL (SYNONYM) — joined via its alias to contribute order-line level information, notably SCHEDULE_STATUS_CODE.
• MFG_LOOKUPS (VIEW) — used to resolve lookup codes into their user-facing meanings, producing the ERROR_MESSAGE column from ERROR_CODE.

The join to MFG_LOOKUPS provides the descriptive translation of the error code returned for a scheduling attempt, while the link to OE_ORDER_LINES_ALL aligns each temporary row with its corresponding order line. The MRP_ATP_SCHEDULE_TEMP synonym resolves to the APPS-owned staging table where the scheduling engine writes its working set of rows before results are consumed or purged.

Key Columns

• SESSION_ID — identifies the invoking session and is the principal filter for retrieving rows belonging to a specific run.
• ORDER_HEADER_ID / ORDER_NUMBER / ORDER_LINE_ID / ORDER_LINE_NUMBER — identify the sales order and line being scheduled.
• INVENTORY_ITEM_ID / INVENTORY_ITEM_NAME / ITEM_DESC — the item under consideration.
• ORGANIZATION_ID / ORGANIZATION_CODE / SOURCE_ORGANIZATION_ID — the supplying and shipping organizations.
• QUANTITY_ORDERED / UOM_CODE / AVAILABLE_QUANTITY / REQUESTED_DATE_QUANTITY — demand quantity and ATP result quantity.
• REQUESTED_SHIP_DATE / REQUESTED_ARRIVAL_DATE / LATEST_ACCEPTABLE_DATE — customer date constraints.
• DELIVERY_LEAD_TIME / INTRANSIT_LEAD_TIME — lead times applied to derive arrival from ship dates; delivery lead time is the interval between scheduled ship and arrival.
• SCHEDULED_SHIP_DATE / SCHEDULED_ARRIVAL_DATE / GROUP_SHIP_DATE / GROUP_ARRIVAL_DATE / PROMISE_DATE — scheduling outcomes returned by ATP.
• SHIP_METHOD / FREIGHT_CARRIER / SHIP_METHOD_TEXT — transportation attributes influencing lead time.
• ERROR_CODE / ERROR_MESSAGE — diagnostic information where scheduling failed, with the message resolved from MFG_LOOKUPS.
• SCENARIO_ID — identifies the planning scenario associated with the row.

Common Use Cases and Queries

A typical diagnostic query retrieves the scheduling results for a session and highlights lead-time-driven dates:

• Investigating why an order line could not be promised on the requested date by selecting SCHEDULED_ARRIVAL_DATE, LATEST_ACCEPTABLE_DATE, and ERROR_MESSAGE for a given ORDER_NUMBER.
• Auditing the delivery lead time applied per line, for example: SELECT order_number, inventory_item_name, requested_ship_date, delivery_lead_time, scheduled_ship_date, scheduled_arrival_date FROM mrp_atp_schedule_temp_v WHERE session_id = :p_session_id ORDER BY order_number, order_line_number;
• Isolating failed lines using: SELECT order_number, order_line_number, error_code, error_message, exception1 FROM mrp_atp_schedule_temp_v WHERE error_code IS NOT NULL;
• Comparing requested versus available quantity to assess shortage impact before releasing the schedule.

Because the view is backed by a temporary staging table, consumers should always constrain queries by SESSION_ID and treat results as scoped to a single scheduling invocation. Retention is short-lived, so the view is appropriate for runtime inspection and troubleshooting rather than historical reporting.