Results for “inv_contact”

8 results




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

Overview

IBE_ORDER_LINE_DTL_V is an APPS-owned reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that presents a flattened, denormalized projection of order line detail from the Oracle iStore / Order Capture domain. The view joins order headers in OE_ORDER_HEADERS_ALL to order lines in OE_ORDER_LINES_ALL and enriches each line with item, unit-of-measure, pricing, agreement, payment-term, shipping-method, freight-term, status, and party/address attributes. Its principal design goal is to expose order line information in a single queryable structure without requiring the consumer to reassemble the underlying normalized relationships.

Because the view resolves customer, contact, and address information for the sold-to, invoice-to (bill-to), and ship-to parties, it is particularly useful where the search predicate "shp_contact" applies — that is, resolving the ship-to contact associated with a line. The columns emitting the ship-to party and contact, such as shp_contact.party_name aliased through the view, allow ship-to contact names to be reported alongside ship-to location address components. This makes the view a convenient source for order confirmation, shipping documentation, and customer-facing extracts.

Underlying Base Objects

The documented base objects fall into several functional groups:

The presence of RA_CUSTOMER_TRX_ALL reflects additional invoicing-related joins in the view definition.

Key Columns

  • Order identity: header_id, line_id, order_number, line_number, top_model_line_id, link_to_line_id.
  • Item attributes: item_number, item_description, product_description, licensing_unit, item_type_code.
  • Quantities and UOM: ordered_quantity, shipped_quantity, cancelled_quantity, fulfilled_quantity, order_quantity_uom, UOM_desc.
  • Pricing and dates: unit_list_price, unit_selling_price, request_date, promise_date, schedule_ship_date.
  • Status and structured lines: flow_status_code, line_status, SHIPMENT_NUMBER, OPTION_NUMBER, COMPONENT_NUMBER, SERVICE_NUMBER.
  • Shipping and freight: req_ship_method_code, req_ship_method_desc, freight_terms_code, freight_terms_desc.
  • Agreement and terms: AGREEMENT_ID, agreement_name, full_Agreement_name, PAYMENT_TERM_ID, payment_terms.
  • Sold-to: sold_to_org_id, sold_to_account.party_id, sold_to_party.party_name, sold_to_contact_id, sold_to_contact.party_name, and the derived phone/e-mail value.
  • Bill-to: invoice_to_org_id, inv_cust_party.party_name, inv_acct_site.cust_account_id, invoice_to_contact_id, inv_contact.party_name, bill_to_location, and bill-to address lines.
  • Ship-to: ship_to_org_id, shp_cust_party.party_name, shp_acct_site.cust_account_id, ship_to_contact_id, shp_contact.party_name, ship_to_location, and ship-to address lines.

Common Use Cases and Queries

The view supports order-line reporting, integration extracts, and customer-facing documents. A frequent pattern filters on ship-to contact details, since the view resolves shp_contact.party_name and the ship-to location.

Ship-to contact lookup by order:

  • SELECT order_number, line_number, item_number, shp_cust_party.party_name ship_to_party, shp_contact.party_name ship_to_contact, ship_to_location FROM apps.ibe_order_line_dtl_v WHERE order_number = :p_order_number;

Lines grouped by requested shipping method:

  • SELECT req_ship_method_code, req_ship_method_desc, COUNT(*) FROM apps.ibe_order_line_dtl_v GROUP BY req_ship_method_code, req_ship_method_desc;

Shipped versus ordered quantity by item:

  • SELECT item_number, SUM(ordered_quantity) ordered_qty, SUM(shipped_quantity) shipped_qty FROM apps.ibe_order_line_dtl_v GROUP BY item_number;

Because derivation of phone/e-mail depends on the IBE_ORDER_UTIL_PVT program unit, and party resolution spans several HZ tables, query performance benefits from filtering on indexed columns such as order_number or header_id. The view is read-only and should be treated as a reporting surface rather than a target for DML.