Results for “pv_partner_program_type_vl”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PV_PARTNER_PROGRAM_TYPE_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the PV – Partner Management product family and exposes the set of partner program types that can be associated with partner programs in the Channel/Partner Management model. A program type represents a classification or category of partner program, such as a rebate, discount, or incentive program, and provides the descriptive scaffolding used when partner agreements, program definitions, and program enrollments are created.
The VL suffix indicates that the view is a translation-enabled view: it joins the base ("_B") table, which holds language-independent attributes and primary keys, with the translation ("_TL") table, which holds language-dependent text. The view therefore returns the program type name and program type description in the session's current language as determined by USERENV('LANG'). The view is documented as VALID and is a standard reporting surface for program type reference data.
Underlying Base Objects
The documented view text joins two synonyms:
- PV_PARTNER_PROGRAM_TYPE_B – the base table containing the language-independent columns: PROGRAM_TYPE_ID (primary key), ACTIVE_FLAG, ENABLED_FLAG, OBJECT_VERSION_NUMBER, and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).
- PV_PARTNER_PROGRAM_TYPE_TL – the translation table containing PROGRAM_TYPE_NAME and PROGRAM_TYPE_DESCRIPTION, keyed by PROGRAM_TYPE_ID and LANGUAGE.
The join condition is PPTB.PROGRAM_TYPE_ID = PPTTL.PROGRAM_TYPE_ID AND PPTTL.LANGUAGE = USERENV('LANG'). This is a one-to-one join; for a given session language each enabled program type returns exactly one row. Row identity is preserved through the base table ROWID, projected as ROW_ID, which allows the view to be used in updateable contexts and in conjunction with Oracle Forms-based setup screens.
Key Columns
- ROW_ID – ROWID of the underlying base-table row; supports row-level addressing.
- PROGRAM_TYPE_ID – Surrogate primary key identifying the program type.
- PROGRAM_TYPE_NAME – Translated, user-visible name of the program type.
- PROGRAM_TYPE_DESCRIPTION – Translated description; this is the column most frequently targeted by searches such as "program_type_description".
- ACTIVE_FLAG – Indicates whether the program type is currently active for use.
- ENABLED_FLAG – Indicates whether the program type is enabled for selection in the application.
- OBJECT_VERSION_NUMBER – Optimistic locking token used by the framework.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns tracing row creation and modification.
Common Use Cases and Queries
The view is typically used to populate LOVs, reports, and integration extracts that must display the program type description in the user's language. A common pattern is to filter on enabled or active rows before presenting the list:
- Lookup of a description by ID or name:
SELECT program_type_id, program_type_name, program_type_description FROM apps.pv_partner_program_type_vl WHERE enabled_flag = 'Y' ORDER BY program_type_name; - Search on description text:
SELECT program_type_id, program_type_name, program_type_description FROM apps.pv_partner_program_type_vl WHERE UPPER(program_type_description) LIKE '%REBATE%'; - Joining to program definitions:
SELECT pp.program_id, pv.program_type_name, pv.program_type_description FROM apps.pv_partner_programs pp, apps.pv_partner_program_type_vl pv WHERE pp.program_type_id = pv.program_type_id; - Audit trail review:
SELECT program_type_id, program_type_name, creation_date, last_update_date, last_updated_by FROM apps.pv_partner_program_type_vl ORDER BY last_update_date DESC;
Because the view is language-filtered through USERENV('LANG'), multilingual implementations should ensure the calling session's language is set appropriately before relying on the returned description text.
-
APPS.PV_PARTNER_PROGRAM_TYPE_VL·↳ PV_PARTNER_PROGRAM_TYPE_B·↳ PV_PARTNER_PROGRAM_TYPE_TL·Explore PV module →
-
APPS.PV_PARTNER_PROGRAM_TYPE_VL·↳ PV_PARTNER_PROGRAM_TYPE_B·↳ PV_PARTNER_PROGRAM_TYPE_TL·Explore PV module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PV Tables and Views 12.2.2
PV User - custom entries
-
eTRM - PV Tables and Views 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PV Tables and Views 12.2.2
PV User - custom entries
-
eTRM - PV Tables and Views 12.1.1