Results for “fulfilled_quantity”

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

Overview

The IBE_ORDER_LINE_DTL_V view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and maintained within the IBE – iStore product family. According to the ETRM metadata (validated across EBS 12.1.1 and 12.2.2), it is a VALID view described as "Stores information about details of an order line." Functionally, it presents a denormalized, reporting-oriented projection of an iStore order line, joining order headers and lines to item master, unit of measure, agreement, payment terms, shipping method, freight terms, and the full set of party/contact/address relationships required for order presentation. This makes it the primary read-only interface through which iStore storefront pages, order confirmation screens, and downstream reporting tools obtain line-level order detail without directly querying Oracle Order Management base tables.

Underlying Base Objects

The view text confirms the following documented base objects:

• OE_ORDER_HEADERS_ALL (OH) and OE_ORDER_LINES_ALL (OL) — the transactional order header and line records.
• MTL_SYSTEM_ITEMS_VL (MSI) — item number, description, product description, and licensing unit.
• MTL_UNITS_OF_MEASURE_TL (MSIT) — unit of measure descriptions.
• OE_LOOKUPS (OLKP1, OLKP2, OEL) — decoded line status, freight terms, and shipping method meanings.
• OE_AGREEMENTS_VL (OAV) and RA_TERMS_TL (TERM) — agreement names/revisions and payment terms.
• OE_SHIP_METHODS_V — shipping method reference data.
• HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS — the Trading Community Architecture (TCA) tables supplying sold-to, invoice-to (bill-to), and ship-to parties, contacts, and addresses.
• IBE_OE_CONTACTS_V (VIEW) and IBE_ORDER_UTIL_PVT (PACKAGE) — iStore-specific contact resolution and phone/email retrieval logic.
• RA_CUSTOMER_TRX_ALL and OE_PROFILE — invoicing reference and profile option access.

The view therefore sits atop both Order Management transactional tables and TCA party model entities, which is why it is a convenient single source for party, contact, and address detail on an order line.

Key Columns

• HEADER_ID, LINE_ID, ORDER_NUMBER, LINE_NUMBER — order and line identity keys.
• ITEM_NUMBER, ITEM_DESCRIPTION, PRODUCT_DESCRIPTION, LICENSING_UNIT — item attributes from MTL_SYSTEM_ITEMS_VL.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, CANCELLED_QUANTITY, FULFILLED_QUANTITY, ORDER_QUANTITY_UOM, UOM_DESC — quantities and units.
• UNIT_LIST_PRICE, UNIT_SELLING_PRICE — pricing amounts.
• REQUEST_DATE, PROMISE_DATE, SCHEDULE_SHIP_DATE — scheduling dates.
• FLOW_STATUS_CODE, LINE_STATUS — workflow and decoded line status.
• SOLD_TO_ORG_ID, SOLD_TO_CONTACT_ID, SOLD_TO_PARTY.PARTY_NAME — sold-to party and contact.
• INVOICE_TO_ORG_ID, INVOICE_TO_CONTACT_ID, INV_CONTACT.PARTY_NAME — the invoice-to (bill-to) party and contact, plus BILL_TO_LOCATION, ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY from INVADDR.
• SHIP_TO_ORG_ID, SHIP_TO_CONTACT_ID, SHP_CONTACT.PARTY_NAME — ship-to party and contact.
• AGREEMENT_ID, AGREEMENT_NAME, FULL_AGREEMENT_NAME, PAYMENT_TERM_ID, PAYMENT_TERMS — commercial terms.
• REQ_SHIP_METHOD_CODE, REQ_SHIP_METHOD_DESC, FREIGHT_TERMS_CODE, FREIGHT_TERMS_DESC — logistics attributes.

Note that bill_to_contact (searched by the user) is represented in this view through the INVOICE_TO_CONTACT_ID and INV_CONTACT.PARTY_NAME columns, together with the INVADDR address block labeled BILL_TO_LOCATION.

Common Use Cases and Queries

The view is used by iStore order review pages, order confirmation, and custom reporting to retrieve priced, contact-enriched line detail. A typical query resolving bill-to contact information is:

• Bill-to contact lookup: SELECT ORDER_NUMBER, LINE_NUMBER, ITEM_NUMBER, INVOICE_TO_CONTACT_ID, PARTY_NAME FROM APPS.IBE_ORDER_LINE_DTL_V WHERE ORDER_NUMBER = :p_order;
• Order line status report: select ORDER_NUMBER, LINE_NUMBER, ITEM_NUMBER, ORDERED_QUANTITY, LINE_STATUS, PROMISE_DATE filtered by FLOW_STATUS_CODE.
• Shipping and freight analysis: aggregate by FREIGHT_TERMS_CODE and REQ_SHIP_METHOD_CODE.
• Contact/address verification: join SOLD_TO, INVOICE_TO, and SHIP_TO contact columns to confirm party roles for an order.

Because the view already resolves TCA party names, address lines, and lookup meanings, it eliminates the need for multi-table joins in iStore reporting and integration extracts.