Results for “consignee_id”

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

Overview

WSH_CONSIGNEES_V is a Shipping Execution (WSH) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated list of consignees available to the shipping and receiving functions — both customers and suppliers — by unioning customer accounts and supplier records into a single result set. The view abstracts the distinction between the two entity types through a discriminator column, which allows shipping-related forms, LOVs, and integration interfaces to present a unified picklist of trading partners without issuing separate queries against the customer and supplier models. The column the user searched for, type_flag, is the single-character discriminator that identifies each row as a customer ('C') or a supplier ('V'), enabling downstream logic to branch on entity type while consuming one consistent row shape.

Underlying Base Objects

The view is defined over three documented objects referenced through synonyms in the APPS schema: HZ_CUST_ACCOUNTS, HZ_PARTIES, and PO_VENDORS (the latter itself a view).

• HZ_CUST_ACCOUNTS — supplies customer account rows (CUST_ACCOUNT_ID, ACCOUNT_NUMBER, PARTY_ID).
• HZ_PARTIES — supplies the party name (PARTY_NAME) and is joined to both branches on PARTY_ID, providing a common descriptive key for customers and suppliers alike.
• PO_VENDORS — supplies supplier rows (VENDOR_ID, SEGMENT1, PARTY_ID) in the union's second branch.

Because the two branches are combined with UNION, the view effectively presents a party-centric registry keyed to either a customer account or a vendor record. The join on PARTY_ID ensures that both branches resolve names from the same TCA party model.

Key Columns

• CUSTOMER_ID — the integer identifier of the entity (customer account ID or vendor ID, depending on type).
• PARTY_NAME — a 50-byte truncated party name derived via SUBSTRB(PARTY.PARTY_NAME, 1, 50).
• CUSTOMER_NUMBER — the human-readable account number (customer account number or SEGMENT1 for suppliers).
• TYPE_FLAG — the discriminator: 'C' for customers, 'V' for suppliers.
• TYPE — the descriptive counterpart to TYPE_FLAG: 'CUSTOMER' or 'SUPPLIER'.
• CONSIGNEE_ID — a composite concatenation of the type flag, a hyphen, and the numeric ID (for example, 'C-1234' or 'V-5678'), providing a single-column unique key for LOV rendering and reference.

Common Use Cases and Queries

The view is typically consumed where a unified consignee picklist is needed, such as in receiving or shipping setup and in custom reporting. Filtering on type_flag restricts the list to one entity type, which is the most frequent pattern. For example, to list only customers:

• SELECT consignee_id, party_name, customer_number, type_flag FROM wsh_consignees_v WHERE type_flag = 'C' ORDER BY party_name;
• SELECT type, COUNT(*) FROM wsh_consignees_v GROUP BY type; — yields a quick count split between customers and suppliers.
• SELECT consignee_id, party_name FROM wsh_consignees_v WHERE party_name LIKE 'A%' AND type_flag = 'V'; — restricts to suppliers for vendor-facing LOVs.

Because consignee_id embeds the type flag, applications can round-trip a value selected from the view and recover both the base identifier and the entity type without storing them separately. Where an interface needs the raw key, customer_id combined with type_flag provides the same information in explicit form. The view should be treated as read-only reference data and is subject to the standard Oracle proprietary and confidentiality notices.