Search Results commitment_number

Overview

OEFV_SALES_ORDER_LINES is a Retrofit view within the Oracle E-Business Suite Order Entry (OE) module. It exposes sales order line information in a flattened, reporting-friendly format by joining the core order line table with header, pricing, project, customer, and lookup-related data. The "OEFV" prefix indicates an Order Entry flex/view object intended for operational reporting and integration rather than transactional processing. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a convenient single-source access point for order line details required by downstream reporting, extracts, and interfaces.

The view's "Retrofitted" description and the ETRM note "Not implemented in this database" indicate that it is a documented metadata artifact and may not be deployed in every environment. Its definition is therefore most relevant as a reference for the expected column set and join logic rather than as a guaranteed runtime object.

Underlying Base Objects

No base objects are explicitly documented in the ETRM metadata; however, the view text references aliases such as LINE, HEADER, PARA, ORG, PRICE_LIST, AGREEMENT, UOM, PAYTERMS, CUSTRX, OPTION_PARENT, MODEL, SERVICE, CYCLE, SITE, CONTACT, INTERMEDIATE_SITE, IRULE, ARULE, REQ, PROJ, and PROJTASK. These correspond to standard OE and related tables — principally OE_ORDER_LINES_ALL (LINE) and OE_ORDER_HEADERS_ALL (HEADER) — joined to supporting master and reference tables. The view therefore sits logically on top of the OE order line and header entities, augmented with descriptive attributes from inventory organizations, price lists, agreements, units of measure, payment terms, customers, and project/task data.

Key Columns

For users searching on commitment_number, the relevant column exposed is LINE.COMMITMENT_ID, which is the foreign key to the commitment reference associated with the order line. Related identifiers include LINE_ID, HEADER_ID, INVENTORY_ITEM_ID, WAREHOUSE_ID, ORG_ID (operating unit), PRICE_LIST_ID, AGREEMENT_ID, TERMS_ID, and LINK_TO_LINE_ID (option parent line). Quantity and pricing columns include ORDERED_QUANTITY, SHIPPED_QUANTITY, INVOICED_QUANTITY, CANCELLED_QUANTITY, SELLING_PRICE, and REVENUE_AMOUNT. Date fields such as PROMISE_DATE, SCHEDULE_DATE, DATE_REQUESTED_CURRENT, and LATEST_ACCEPTABLE_DATE support scheduling analysis. Descriptive joins surface ORDER_NUMBER, item concatenation (_KF:INV:MSTK:ITEM), UOM, payment terms, customer transaction numbers, and lookup meanings for ship method, priority, source type, item type, and open flag.

Common Use Cases and Queries

Typical usage includes order line reporting, commitment reconciliation, and integration extracts. A representative query filtering on commitment follows:

• SELECT ORDER_NUMBER, LINE_NUMBER, COMMITMENT_ID, ORDERED_QUANTITY, SELLING_PRICE FROM OEFV_SALES_ORDER_LINES WHERE COMMITMENT_ID IS NOT NULL;
• Order status and scheduling reports using OPEN_FLAG, PROMISE_DATE, and SCHEDULE_DATE.
• Pricing and agreement analysis joining PRICE_LIST.NAME and AGREEMENT.NAME.
• Project-driven order extracts using PROJ.NAME and PROJTASK.TASK_NUMBER.

Because deployment is not guaranteed, confirm existence in the target schema before relying on the view; otherwise replicate its logic from the underlying OE tables.