Search Results ship_to_id

Overview

APPS.MRP_BIS_LATE_ORDERS_V is an Oracle E-Business Suite internal database view owned by the APPS schema. It is registered as a VALID object with the FND Design Data identifier MRP.MRP_BIS_LATE_ORDERS_V and is classified by Oracle as Internal Use Only. Oracle does not support direct access to application data through this object except from standard Oracle Applications programs, and the recommended position for implementers and support analysts is to treat it as a read-only reporting artifact rather than a supported integration interface.

The view belongs to the Oracle Advanced Supply Chain Planning (ASCP) and Material Requirements Planning (MRP) Business Intelligence System (BIS) layer. It consolidates order, schedule, and customer information to expose orders whose dates indicate late or at-risk fulfillment. The presence of both DUE_DATE and EXPECTED_SHIP_DATE allows comparisons between the committed or requested schedule and the projected shipping schedule, which is the classic pattern used to identify late supply or demand. Because the underlying objects are largely MRP and Order Management tables, the row set is refreshed as planning data is regenerated and is typically consumed by BI Publisher reports, Discoverer workbooks, or custom dashboards built for planning and order management teams.

Underlying Base Objects

The view is defined over a mix of synonyms and packages spanning the MRP, INV, OE, and HZ schemas. Documented dependencies include the Trading Community Architecture entities HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES, which supply customer, site, and address attributes. Supply chain and planning data comes from MRP_EXCEPTION_DETAILS, MRP_FULL_PEGGING, MRP_GROSS_REQUIREMENTS, and MRP_SCHEDULE_DATES. Item master information is resolved through the key flexfield view MTL_SYSTEM_ITEMS_KFV, and transactional order data is sourced from OE_ORDER_LINES_ALL.

Three program units, INV_SALESORDER, MRP_GET_BIS_VALUES, and MRP_GET_ORDER, are referenced as packages, indicating that the view invokes PL/SQL logic rather than relying purely on static joins. This is an important behavioral characteristic: row-level values such as order number, schedule dates, or order retrieval may be computed at query time through these packaged functions, which can affect performance and make the view unsuitable for high-volume bulk extraction. The metadata confirms APPS.MRP_BIS_LATE_ORDERS_V is not referenced by any database object, so it sits at the top of its dependency chain within the application schema.

Key Columns

• COMPILE_DESIGNATOR and ORGANIZATION_ID identify the planning compilation and inventory organization context for each row.
• ITEM_NUMBER, ORDER_QUANTITY, and UOM_CODE describe the item and quantity associated with the order line.
• DUE_DATE is the required or scheduled due date; EXPECTED_SHIP_DATE is the projected ship date that drives late-order evaluation.
• ORDER_ID, ORDER_NUMBER, ORDER_LINE_ID, and ORDER_LINE_NUMBER provide the Order Management identifiers for drill-down into OE_ORDER_LINES_ALL.
• CUSTOMER_ID, CUSTOMER_NAME, SHIP_TO_ID, and SHIP_TO_ADDRESS expose Trading Community Architecture customer and ship-to attributes.

Common Use Cases and Queries

The primary scenario is identifying orders whose expected ship date falls after the due date. A representative query filters on this relationship:

• SELECT ORDER_NUMBER, ITEM_NUMBER, DUE_DATE, EXPECTED_SHIP_DATE, CUSTOMER_NAME FROM APPS.MRP_BIS_LATE_ORDERS_V WHERE EXPECTED_SHIP_DATE > DUE_DATE;
• Aggregate late orders by organization: SELECT ORGANIZATION_ID, COUNT(*) FROM APPS.MRP_BIS_LATE_ORDERS_V GROUP BY ORGANIZATION_ID;
• Trend or customer analysis: SELECT CUSTOMER_NAME, ORDER_NUMBER, ORDER_QUANTITY, UOM_CODE FROM APPS.MRP_BIS_LATE_ORDERS_V ORDER BY CUSTOMER_NAME;

Because the view depends on PL/SQL packages and an internal-only designation, access should remain restricted to reporting purposes, and any reliance on the object should be re-validated following application patches or upgrades between 12.1.1 and 12.2.2.