Search Results order_by_code_int




Overview
Explore in AI Chat

Overview

APPS.WSH_DSNO_ORDERS_COMM_V is an internal Oracle E-Business Suite view owned by the APPS schema. It is registered in FND Design Data under the application short name WSH and has a status of VALID. The object is a view, not a table, and is documented with the explicit Oracle warning stating that it is intended for internal use only and that Oracle Corporation does not support access to application data through this object except from standard Oracle Applications programs. Consequently, it should be treated as a supporting structure for Oracle-shipped functionality rather than as a public integration or reporting interface.

Functionally, the view consolidates shipping and delivery information with order header data and communication-related attributes of the "order by" party. Its column set spans identifiers (DELIVERY_ID, CONTAINER_INSTANCE_ID, ORDER_HEADER_ID, ORDER_BY_ADDRESS_ID), source and reference fields (SOURCE_CODE, SALES_ORDER_NUMBER, ORDER_BY_CODE_INT, ORDER_BY_EDI_LOC_CODE), trading partner references (ORDER_BY_TP_REF_1 and ORDER_BY_TP_REF_2), and a full set of address, contact, telephone, and invoice naming attributes. This combination positions it within the delivery/shipment notification (DSNO) area of Oracle Shipping Execution, where it can supply the party and address details associated with an outbound order.

Underlying Base Objects

The view is defined over a mixture of shipping, trading partner, and Oracle Trading Community Architecture (TCA) objects. The documented referenced base objects are ECE_TP_HEADERS, HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_PARTY_SITES, HZ_RELATIONSHIPS, WSH_DELIVERY_ASSIGNMENTS_V, WSH_DELIVERY_DETAILS, and the package WSH_ECE_VIEWS_DEF. Most of these are exposed within the APPS schema as synonyms.

The HZ_* objects supply the TCA party, customer account, account site, site use, location, organization contact, party site, and relationship information that produces the ORDER_BY_* columns. ECE_TP_HEADERS, a trading partner header table associated with Oracle e-Commerce Gateway, supports the trading partner reference fields such as ORDER_BY_TP_REF_1 and ORDER_BY_TP_REF_2 along with ORDER_BY_EDI_LOC_CODE. WSH_DELIVERY_DETAILS and WSH_DELIVERY_ASSIGNMENTS_V provide the delivery and container context, including DELIVERY_ID and CONTAINER_INSTANCE_ID. The WSH_ECE_VIEWS_DEF package indicates that the view is generated or governed by the e-Commerce Gateway view definitions used by Shipping Execution.

Key Columns

  • DELIVERY_ID — identifier of the delivery associated with the order line context.
  • CONTAINER_INSTANCE_ID — the container instance (LICN) tied to the delivery.
  • ORDER_HEADER_ID — the order header key linking back to the sales order.
  • SOURCE_CODE — indicates the source system or origin of the order data.
  • SALES_ORDER_NUMBER — the human-readable sales order number.
  • ORDER_BY_ADDRESS_ID, ORDER_BY_CODE_INT, ORDER_BY_EDI_LOC_CODE — the address identifier, internal code, and EDI location code for the order-by location.
  • ORDER_BY_TP_REF_1 / ORDER_BY_TP_REF_2 — trading partner reference values sourced from the ECE trading partner header data. These are the columns most relevant to the search term "order_by_tp_ref_2".
  • ORDER_BY_NAME through ORDER_BY_COUNTY — the order-by party's name and structured address fields, including country, state, province, and county.
  • ORDER_BY_CONTACT_LAST_NAME, ORDER_BY_CONTACT_FIRST_NAME, ORDER_BY_CONTACT_JOB_TITLE, ORDER_BY_AREA_CODE, ORDER_BY_TELEPHONE — contact person and telephone details.
  • INVOICE_NAME — the invoice name associated with the party.

Common Use Cases and Queries

The view is typically consumed by Oracle Shipping Execution and e-Commerce Gateway processes that need to emit or display the order-by party, address, contact, and trading partner reference information alongside delivery details. Analysts may query it for troubleshooting where a specific trading partner reference such as ORDER_BY_TP_REF_2 must be traced to a delivery or order header.

A representative query filtering on the second trading partner reference is shown below:

  • SELECT delivery_id, container_instance_id, order_header_id, sales_order_number, order_by_tp_ref_1, order_by_tp_ref_2, order_by_name, order_by_city FROM apps.wsh_dsno_orders_comm_v WHERE order_by_tp_ref_2 = :p_tp_ref_2;
  • SELECT order_header_id, sales_order_number, order_by_code_int, order_by_edi_loc_code, invoice_name FROM apps.wsh_dsno_orders_comm_v WHERE delivery_id = :p_delivery_id;
  • SELECT d.delivery_id, d.sales_order_number, d.order_by_name, d.order_by_address1, d.order_by_postal_code FROM apps.wsh_dsno_orders_comm_v d WHERE d.source_code = :p_source_code;

Because the object is flagged Oracle Internal Use Only, any direct querying should be limited to diagnostic and support purposes. Custom integrations or reports should rely on supported APIs or public views instead of this internal view.