Results for “pv_process_rules_vl”

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

Overview

PV_PROCESS_RULES_VL is a bilingual (language-specific) view owned by the APPS schema within Oracle E-Business Suite, belonging to the PV — Partner Management product family. It exposes the header-level definition of process rules used to drive channel and partner management processing logic, such as opportunity routing, deal registration handling, and partner program qualification. The view is a "VL" (view language) object, meaning it joins the transactional base table with its translation table and filters translations by the session language. This design enables Oracle EBS Forms, concurrent programs, and external integrations to retrieve process rule definitions with translated names and descriptions in the user's active language without duplicating rule rows. Because the view presents descriptive attributes alongside operational columns, it is commonly used for reporting, validation lookups, and rule-resolution queries that require a human-readable rule name. Status is documented as VALID in ETRM 12.2.2, and the object is present in both 12.1.1 and 12.2.2 releases.

Underlying Base Objects

Per the documented ETRM metadata, PV_PROCESS_RULES_VL is defined over two referenced base objects, both exposed as synonyms owned by APPS:

• PV_PROCESS_RULES_B — the base table storing transactional and operational attributes of each process rule, keyed by PROCESS_RULE_ID.
• PV_PROCESS_RULES_TL — the translation table storing language-specific PROCESS_RULE_NAME and DESCRIPTION values.

The join is performed on PROCESS_RULE_ID with the translation filtered by T.LANGUAGE = USERENV('LANG'), restricting results to the current session language. The view text selects columns from the B alias and adds DESCRIPTION and PROCESS_RULE_NAME from the T alias, presenting a single flattened row per process rule for the active language.

Key Columns

• PROCESS_RULE_ID — primary identifier of the process rule; used as the foreign key throughout PV rule setup and results tables.
• PARENT_RULE_ID — self-referencing key supporting hierarchical rule structures, allowing child rules to inherit or nest under parent rules.
• PROCESS_TYPE — classifies the business process to which the rule applies, driving which processing engine evaluates it.
• RANK — defines evaluation sequence or priority when multiple rules apply to the same context.
• STATUS_CODE, START_DATE, END_DATE — control rule activation windows and effective validity.
• ACTION, ACTION_VALUE — specify the operation the rule performs and its parameter or target value.
• OWNER_RESOURCE_ID — identifies the resource (such as a partner manager or channel owner) associated with the rule; this column is exposed directly in the view and is the term most frequently searched by users resolving ownership of a rule.
• CURRENCY_CODE — currency context for rules whose action values are monetary.
• PROCESS_RULE_NAME, DESCRIPTION — translated, user-facing labels sourced from the TL table.
• Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) — support auditing, concurrency control, and traceability.

Common Use Cases and Queries

Typical usage includes resolving active rules for a given process type, looking up ownership via OWNER_RESOURCE_ID, and generating rule listings in the user's language. A representative query filtering on ownership and status:

SELECT process_rule_id, process_rule_name, process_type,
       rank, status_code, action, action_value,
       owner_resource_id, start_date, end_date
FROM   apps.pv_process_rules_vl
WHERE  owner_resource_id = :p_resource_id
AND    status_code = 'ACTIVE'
AND    SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1)
ORDER BY process_type, rank;

Because the view automatically filters by USERENV('LANG'), developers should note that a row is returned only if a translation exists for the current session language; use the underlying PV_PROCESS_RULES_TL table directly when cross-language extraction or bulk translation maintenance is required.