Results for “pos_supp_prof_ext_ocv”

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

Overview

POS_SUPP_PROF_EXT_OCV is a VALID APPS-owned database view within the Oracle E-Business Suite iSupplier Portal (POS) product family. It was delivered as part of the Supplier Data Hub project and serves as the Supplier Profile Extension Classification View. Its purpose is to present a unified, language-aware list of classification values that populate supplier profile extension regions for suppliers maintaining their records through iSupplier Portal or for internal buyers reviewing supplier registrations.

The view operates as a consolidation layer rather than a transactional object. It normalizes classification entries drawn from disparate sources — Oracle lookups, trading community (HZ) classification categories, territory definitions, and application message repository entries — into a single two-column shape consisting of a composite CODE and a display MEANING. Each source is distinguished by a short two-character prefix, allowing consuming forms, OAF pages, and reports to identify the provenance of any given row without inspecting the underlying tables. The view honors the session language through USERENV('LANG'), so multilingual deployments return translated meanings automatically.

Underlying Base Objects

The documented base objects referenced by the view are FND_LOOKUP_VALUES, FND_NEW_MESSAGES, FND_TERRITORIES_TL, HZ_CLASS_CATEGORIES (each accessed via APPS synonyms), POS_PRODUCT_SERVICE_UTL_PKG, and the generated type SYS_PLSQL_B4736A10_495_1. The structure of the view text reveals a series of UNION ALL branches:

• FND_LOOKUP_VALUES filtered on LOOKUP_TYPE = 'POS_SUPP_PROF_EXT_BASE' (VIEW_APPLICATION_ID = 0), prefixed 'BS:'.
• FND_LOOKUP_VALUES filtered on LOOKUP_TYPE = 'VENDOR TYPE' (VIEW_APPLICATION_ID = 201), prefixed 'ST:'.
• FND_LOOKUP_VALUES filtered on LOOKUP_TYPE = 'POS_BUSINESS_CLASSIFICATIONS' (VIEW_APPLICATION_ID = 0), prefixed 'BC:'.
• FND_LOOKUP_VALUES joined to HZ_CLASS_CATEGORIES on LOOKUP_TYPE = CLASS_CATEGORY (VIEW_APPLICATION_ID = 222), prefixed 'HZ:' and keyed as LOOKUP_TYPE:LOOKUP_CODE.
• FND_TERRITORIES_TL, prefixed 'AC:', returning TERRITORY_CODE and TERRITORY_SHORT_NAME.
• FND_NEW_MESSAGES rows, prefixed 'AP:', selecting MESSAGE_TEXT for named messages such as POS_PAY_NEW and POS_HT_B_PURCHASING (application 177), and PON_AUC_NEG_R and PON_AUCTS_PAY_PROC_CARD (application 396), each constrained by LANGUAGE_CODE and APPLICATION_ID.

The inclusion of POS_PRODUCT_SERVICE_UTL_PKG and the SYS_PLSQL type indicates the view participates in PL/SQL-based classification assembly logic used by iSupplier Portal.

Key Columns

• CODE — The composite identifier. Format is a two-character source prefix followed by a colon and the native code (for example, 'BS:SUPPLIER', 'ST:VENDOR', 'HZ:CATEGORY:CODE', 'AC:US', 'AP:PURCHASING'). The prefix is the primary mechanism for distinguishing source systems.
• LANGUAGE — The session language (or LANGUAGE_CODE for FND_NEW_MESSAGES rows), ensuring values are returned in the user's environment language.
• MEANING — The translated display value: lookup meaning, territory short name, or message text depending on the branch.

Common Use Cases and Queries

Typical uses include populating supplier profile extension LOVs, validating classification values submitted through iSupplier registration, and reporting on available classifications across business units. Relevant to the user's interest in FND_NEW_MESSAGES, the 'AP:' branches source their MEANING directly from FND_NEW_MESSAGES.

• List all classifications: SELECT CODE, MEANING FROM APPS.POS_SUPP_PROF_EXT_OCV ORDER BY CODE;
• Retrieve only message-sourced rows: SELECT CODE, MEANING FROM APPS.POS_SUPP_PROF_EXT_OCV WHERE CODE LIKE 'AP:%';
• Isolate territory entries: SELECT CODE, MEANING FROM APPS.POS_SUPP_PROF_EXT_OCV WHERE CODE LIKE 'AC:%';
• Filter to HZ classification categories: SELECT CODE, MEANING FROM APPS.POS_SUPP_PROF_EXT_OCV WHERE CODE LIKE 'HZ:%';