Search Results oe_sch_order_lines_v




Overview
Explore in AI Chat

Overview

The APPS.OE_SCH_ORDER_LINES_V view is a scheduling-oriented presentation layer over Oracle Order Management order line data in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a curated set of columns from OE_ORDER_LINES_ALL together with descriptive and denormalized attributes resolved from customer, item, and lookup sources, giving planners, shipping personnel, and integration developers a single queryable object for order line scheduling and shipment information. Rather than querying the transactional base table and joining to numerous reference objects manually, consumers can select directly from this view to obtain shipment-relevant attributes such as SCHEDULE_SHIP_DATE, SCHEDULE_ARRIVAL_DATE, PROMISE_DATE, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, SHIPPING_METHOD_CODE, and SHIPMENT_PRIORITY_CODE. This makes the view particularly valuable for reporting on fulfillment timing, shipment prioritization, and integration feeds into warehouse management, transportation, or advanced planning systems. Because it is defined in the APPS schema and carries VALID status, it is a supported reference point for custom reports, Oracle Reports, BI Publisher data models, and interface programs. Users searching for "shipment_priority" will find the corresponding attribute exposed here as SHIPMENT_PRIORITY_CODE, which carries the priority designation applied to the order line shipment.

Underlying Base Objects

The view is defined primarily over OE_ORDER_LINES_ALL, from which it draws the majority of its columns via the L alias, including line identifiers, dates, quantities, flags, and codes. It joins to OE_ORDER_HEADERS for header-level context such as order number and sold-to information. Descriptive values for shipping methods, freight terms, and shipment priority are resolved through lookup views including OE_LOOKUPS, OE_FND_COMMON_LOOKUPS_V, and AR_LOOKUPS, while OE_TRANSACTION_TYPES_TL supplies translated transaction type names. Customer and site information is sourced from the Oracle Trading Community Architecture (TCA) objects, specifically HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCOUNT_ROLES, and HZ_RELATIONSHIPS. Inventory and item context is provided by MTL_SYSTEM_ITEMS_VL and MTL_PARAMETERS. Finally, FND_GLOBAL provides session context such as organization and user identifiers, and the OE_SYS_PARAMETERS package supplies Order Management system parameter values used in the view logic.

Key Columns

Common Use Cases and Queries

A frequent requirement is to report open order lines by shipment priority for a given ship-from organization. The following query illustrates this pattern:

SELECT line_id, header_id, shipment_priority_code, schedule_ship_date, ordered_item, shipping_quantity, ship_from_org_id
FROM apps.oe_sch_order_lines_v
WHERE ship_from_org_id = :p_org_id
AND schedule_status_code IN ('SCHEDULED','READY_TO_RELEASE')
ORDER BY shipment_priority_code, schedule_ship_date;

Integration developers use the view to extract scheduling details for downstream warehouse or transportation systems, filtering by ORG_ID and date ranges. Planners use it to identify lines with imminent SCHEDULE_SHIP_DATE values that remain unscheduled, or to analyze demand distribution by DEMAND_BUCKET_TYPE_CODE. Because the view resolves lookup and customer descriptors, it also supports reporting without additional joins. When writing queries, always qualify the view with the APPS schema and constrain by ORG_ID to respect multi-organization access, and consider the operating unit context established through FND_GLOBAL for consistent results.