Search Results pv_enty_select_criteria

Overview

The PV_ENTY_SELECT_CRITERIA table is a core data object within the Oracle E-Business Suite Partner Management (PV) module, specifically in releases 12.1.1 and 12.2.2. It serves as the master repository for defining entity selection criteria. These criteria are rule-based conditions used to programmatically identify and select partner entities, such as partner sites or contacts, for various automated processes. The table's primary role is to store the definition of a selection rule, which is then referenced and executed by the Partner Management engine to filter and target specific partner records based on defined attributes and values.

Key Information Stored

The table stores the fundamental metadata for each unique selection criterion. Its structure is centered on a unique identifier and key foreign key relationships that define the rule's context and logic. The most critical column is the SELECTION_CRITERIA_ID, which serves as the primary key (PV_ENTY_SELECT_CRITERIA_PK) and uniquely identifies each rule definition. Other essential columns include PROCESS_RULE_ID, which links the criterion to a specific business process rule defined in PV_PROCESS_RULES_B, and ATTRIBUTE_ID, which links to PV_ATTRIBUTES_B to specify which partner attribute (e.g., partner status, country, classification) the criterion evaluates. The table itself holds the rule definition, while the specific values to compare against are stored in the related PV_SELECTED_ATTR_VALUES table.

Common Use Cases and Queries

This table is central to automated partner management workflows. A common use case is the execution of a mass update or communication campaign where the system must select all partners in a specific region with a certain status. The criteria defined in this table enable that dynamic selection. For troubleshooting or reporting, common queries involve joining to related tables to see the full rule definition. A sample SQL pattern to list all selection criteria with their associated process rule and attribute would be:

• SELECT esc.SELECTION_CRITERIA_ID, prb.RULE_NAME, ab.ATTRIBUTE_NAME
• FROM PV_ENTY_SELECT_CRITERIA esc,
• PV_PROCESS_RULES_B prb,
• PV_ATTRIBUTES_B ab
• WHERE esc.PROCESS_RULE_ID = prb.PROCESS_RULE_ID
• AND esc.ATTRIBUTE_ID = ab.ATTRIBUTE_ID;

Another critical query involves identifying criteria that are not yielding expected results by examining the joined attribute values.

Related Objects

The PV_ENTY_SELECT_CRITERIA table has documented foreign key relationships with several key Partner Management tables, forming the backbone of the rule definition framework.

• PV_PROCESS_RULES_B: The PROCESS_RULE_ID column in PV_ENTY_SELECT_CRITERIA references PV_PROCESS_RULES_B. This links a selection criterion to the overarching business process rule that uses it.
• PV_ATTRIBUTES_B: The ATTRIBUTE_ID column in PV_ENTY_SELECT_CRITERIA references PV_ATTRIBUTES_B. This defines which specific partner attribute the selection criterion is based upon.
• PV_SELECTED_ATTR_VALUES: The SELECTION_CRITERIA_ID primary key is referenced by the PV_SELECTED_ATTR_VALUES table. This is a critical one-to-many relationship where PV_SELECTED_ATTR_VALUES stores the actual permissible values (e.g., 'ACTIVE', 'USA', 'GOLD') for the attribute specified in the parent criterion record.