Search Results splc_code

Overview

OPM_CUSTOMERS is an APPS-owned database view in Oracle E-Business Suite, defined within the GMF (Process Manufacturing Financials) product family. Its documented purpose is to support OPM customer synchronization, presenting Oracle Receivables and Trading Community Architecture (TCA) customer data in a flattened, legacy-oriented format that the Process Manufacturing applications expect. Rather than exposing normalized TCA entities directly, the view reorganizes customer accounts, account sites, site uses, parties, and party sites into a single denormalized row per customer location.

The view is marked VALID in the ETRM metadata and is available in both EBS 12.1.1 and 12.2.2. Its role is primarily integration and reporting: it provides a stable interface through which OPM modules read customer attributes—such as terms, sales representative, FOB point, backorder behavior, and billing/shipping indicators—without requiring those modules to understand the underlying HZ schema. The user search term "custtrade_class" relates to the legacy OPM customer trade classification concept, which the view supports through its customer-type and status derivations, even though trade class is not surfaced as a distinct column in the documented excerpt.

Underlying Base Objects

The view is defined over the following documented referenced objects: FND_PROFILE (package), GL_PLCY_MST (synonym), GMF_AR_CUSTOMER (package), GML_INVALID_CUSTOMERS (synonym), HZ_CUSTOMER_PROFILES (synonym), HZ_CUST_ACCOUNTS (synonym), HZ_CUST_ACCT_SITES_ALL (synonym), HZ_CUST_SITE_USES_ALL (synonym), HZ_LOCATIONS (synonym), HZ_PARTIES (synonym), and HZ_PARTY_SITES (synonym).

The core customer data is drawn from HZ_CUST_ACCOUNTS (aliased C in the view text), joined to HZ_CUST_ACCT_SITES_ALL (A), HZ_CUST_SITE_USES_ALL (S), HZ_PARTIES (PR), HZ_PARTY_SITES (CP), and HZ_LOCATIONS. The GMF_AR_CUSTOMER package supplies derived attributes through its PHONE, TERMS, and SALESREP functions, which resolve phone, fax, telex, payment terms, and sales-representative values from the TCA model. FND_PROFILE supplies the GL$CUST_DELIMITER profile value used to compose customer numbers, and GL_PLCY_MST provides the operating-unit (CO_CODE) lookup. GML_INVALID_CUSTOMERS relates to synchronization filtering. Because the view is built over synonyms, it resolves transparently to the HZ base tables in the APPS schema.

Key Columns

• CUST_ID — Hard-coded to 0 in the view text, present for structural compatibility with OPM customer consumers.
• CUST_NO / ALTCUST_NO — Composed from account number, the configured delimiter, and site location.
• CUSTSORT_NO — Set to the account number for sorting.
• CUST_NAME — The party name from HZ_PARTIES.
• PHONE_NO, FAX_NO, TELEX_NO — Derived via GMF_AR_CUSTOMER.PHONE using site-use context.
• TERMS_CODE and TERMS_VARY — Payment terms resolved from site, party, or account defaults, with an override indicator.
• FOB_CODE — FOB point from the site or account.
• SLSREP_CODE — Sales representative derived from the site or account.
• BACKORDER_IND — Backorder behavior based on the ship-sets-include-lines flag at account and site level.
• INACTIVE_IND, BILL_IND, SHIP_IND — Status and site-use indicators derived from customer, account, and site statuses and site-use codes.
• CUST_TYPE — Customer type derivation, with internal customers mapped to type 2.

Common Use Cases and Queries

Typical use cases include synchronizing OPM customer records with Receivables/TCA, reporting active bill-to and ship-to locations, and validating terms and sales-representative assignment before OPM transactions. Example query:

SELECT cust_no, cust_name, terms_code, slsrep_code, fob_code, backorder_ind, inactive_ind, bill_ind, ship_ind FROM apps.opm_customers WHERE inactive_ind = 0 ORDER BY custsort_no;

To find active shipping locations for a given customer: SELECT cust_no, cust_name, ship_ind FROM apps.opm_customers WHERE cust_name = :party_name AND ship_ind = 1;

Note that trade-class related attributes ("custtrade_class") are not exposed as a distinct documented column; consumers requiring trade classification must derive it from the underlying HZ customer profile or party classification data referenced by HZ_CUSTOMER_PROFILES and the associated TCA tables.