Results for “gsa_indicator”

50+ results




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

Overview

WSH_CUSTOMERS_ACTIVE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the WSH – Shipping Execution product family. Although it is catalogued under Shipping Execution, the view functions as a lightweight customer master reference that exposes a curated projection of active customer account data sourced from the Oracle Receivables / Trading Community Architecture (TCA) model. Its status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and the definition is identical across both releases, making it a stable integration point for custom reports, concurrent programs, and external interfaces.

The view addresses a recurring requirement in shipping and order management flows: the need to resolve a customer identifier, customer number, display name, and GSA (General Services Administration) indicator without navigating the extensive join paths of the TCA tables. Because it pre-joins HZ_PARTIES and HZ_CUST_ACCOUNTS and restricts output to active accounts, it reduces the risk of returning obsolete or inactive customer records.

The user search term "gsa_indicator" corresponds directly to the GSA_INDICATOR column, which is the distinguishing attribute of this view. This column surfaces the GSA flag maintained on the party record, filtered by party type, and is used to identify customers eligible under U.S. federal GSA schedule purchasing arrangements.

Underlying Base Objects

The view is defined over two synonym-referenced base tables in the TCA model:

The two objects are joined on CUST_ACCT.PARTY_ID = PARTY.PARTY_ID, with an additional predicate restricting results to rows where CUST_ACCT.STATUS = 'A' (active). This inner join means only parties that have at least one active customer account are returned; parties without a corresponding active account are excluded entirely. The synonym references indicate the view resolves through the APPS synonyms for the underlying HZ tables.

Key Columns

  • CUSTOMER_NAME – derived via SUBSTRB(PARTY.PARTY_NAME, 1, 50). The byte-based substring enforces a maximum of 50 bytes, which can truncate multibyte customer names.
  • CUSTOMER_NUMBER – the customer account number from HZ_CUST_ACCOUNTS.ACCOUNT_NUMBER, the human-readable key commonly used in order entry and shipping documents.
  • CUSTOMER_ID – the numeric CUST_ACCOUNT_ID, the primary identifier used for foreign-key relationships in shipping and order tables.
  • GSA_INDICATOR – computed with NVL(DECODE(PARTY.PARTY_TYPE,'ORGANIZATION',PARTY.GSA_INDICATOR_FLAG,'N'),'N'). The flag is returned only for organization parties; person parties and null values resolve to 'N'.

Common Use Cases and Queries

Typical scenarios include populating customer list of values, validating GSA eligibility during order or shipment processing, and supplying reference data to outbound interfaces.

List active customers with their GSA status:

  • SELECT customer_id, customer_number, customer_name, gsa_indicator FROM apps.wsh_customers_active_v WHERE gsa_indicator = 'Y';

Resolve a name from a customer number:

  • SELECT customer_name FROM apps.wsh_customers_active_v WHERE customer_number = :p_number;

Because the view is not indexed itself, queries benefit from the indexes on HZ_CUST_ACCOUNTS and HZ_PARTIES. Note that the STATUS = 'A' filter means inactive accounts are never returned; applications requiring historical customers must query the base TCA tables directly.