Results for “pv_enty_select_criteria”

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

Overview

PV_ENTY_SELECT_CRITERIA is a Partner Management (PV) module table that stores entity selection criteria. In Oracle EBS 12.1.1 and 12.2.2, it defines the individual rule rows that determine which partner entities (customers, prospects, or other party records) are eligible for processing within a given partner process rule. Each row associates a process rule with a specific attribute and an operator/selection type combination, forming the conditional logic that the Partner Management engine evaluates at runtime.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. This is consistent with the table's role: it hangs off a parent process rule (via PROCESS_RULE_ID) and an attribute (via ATTRIBUTE_ID), and is itself referenced by dependent detail tables such as PV_SELECTED_ATTR_VALUES. Treated as a satellite, it captures descriptive selection attributes tied to the process-rule business key rather than acting as a true hub or link.

Key Information Stored

The table contains 34 documented columns. The most operationally significant are:

• SELECTION_CRITERIA_ID — the surrogate primary key (PV_ENTY_SELECT_CRITERIA_PK) that uniquely identifies each criterion row.
• PROCESS_RULE_ID — foreign key to PV_PROCESS_RULES_B; identifies the parent process rule to which the criterion belongs.
• ATTRIBUTE_ID — foreign key to PV_ATTRIBUTES_B; identifies the partner attribute being evaluated.
• SELECTION_TYPE_CODE and OPERATOR — together define how the attribute value is tested (for example, equality, range, or inclusion logic).
• RANK — orders criteria within a rule, controlling evaluation sequence or priority.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield segment columns, allowing extensible configuration.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-org / data-secured visibility.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns capturing the request that last populated or updated the row.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER for optimistic locking.
• ZD_EDITION_NAME — supports edition-based redefinition in 12.2.x.

The unique index PV_ENTY_SELECT_CRITERIA_U1 on (SELECTION_CRITERIA_ID, ZD_EDITION_NAME) is the business-key candidate, distinguishing criterion identity together with the edition of the partner model.

Common Use Cases and Queries

Common scenarios include auditing which criteria are attached to a process rule, replicating partner segmentation logic for reporting, and troubleshooting why a set of entities was (or was not) selected during a partner batch.

• List all criteria for a rule:
  SELECT selection_criteria_id, attribute_id, selection_type_code, operator, rank FROM pv.pv_enty_select_criteria WHERE process_rule_id = :rule_id ORDER BY rank;
• Join to attribute definitions to display attribute names:
  SELECT c.selection_criteria_id, a.attribute_name, c.operator FROM pv.pv_enty_select_criteria c JOIN pv.pv_attributes_b a ON c.attribute_id = a.attribute_id WHERE c.process_rule_id = :rule_id;

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

• PV_PROCESS_RULES_B — parent process rule (PROCESS_RULE_ID).
• PV_ATTRIBUTES_B — defines the attribute evaluated (ATTRIBUTE_ID).
• FND_SECURITY_GROUPS — controls data-secured visibility (SECURITY_GROUP_ID).
• PV_SELECTED_ATTR_VALUES — child detail rows holding concrete attribute values for each criterion (SELECTION_CRITERIA_ID).
• RA_BATCHES_ALL — receivables batches referencing a selection criterion (SELECTION_CRITERIA_ID).
• AR_SELECTION_CRITERIA — receivables-side criteria sharing the same key column (SELECTION_CRITERIA_ID).