Results for “action_value”

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

Overview

The PV_ENTITY_RULES_APPLIED table is a logging and audit table within the Oracle E-Business Suite Partner Management (PV) module. Its documented purpose is to store the rules that were applied when selecting an entity, where the entity is either an opportunity or a partner. In practical terms, it captures the outcome of rule evaluation performed by the Partner Management rule engine, recording which process rule matched and under what conditions, so that users and administrators can trace why a given opportunity or partner was assigned, qualified, or routed in a particular way.

Unlike transactional configuration tables, this is an append-oriented history table. Every time the rule engine evaluates a set of PV_PROCESS_RULES_B rules against an entity, a row may be written here to record the winning rule, its parent rule, the action taken, and the process status. The heuristic Data Vault classification mined from the foreign-key structure is link. That classification is a modeling suggestion: the table functions as an associative or intersection record connecting an entity (opportunity or partner), a process rule, and an optional parent process rule within a single evaluated context.

Key Information Stored

The table contains 38 documented columns on the 12.2.2 physical schema. The most operationally significant columns are:

• ENTITY_RULE_APPLIED_ID — surrogate primary key, backed by the PV_ENTITY_RULES_APPLIED_PK constraint and the unique index PV_ENTITY_RULES_APPLIED_U1.
• ENTITY and ENTITY_ID — identify the subject of rule evaluation (opportunity or partner) and its internal identifier.
• PROCESS_RULE_ID — foreign key to PV_PROCESS_RULES_B, the rule that was applied.
• PARENT_PROCESS_RULE_ID — foreign key to PV_PROCESS_RULES_B, identifying the parent rule in a rule hierarchy.
• ACTION_VALUE and PROCESS_TYPE — the action produced by the rule and the classification of the process executed.
• WINNING_RULE_FLAG and LATEST_FLAG — indicate whether this was the winning rule in a competing evaluation and whether the row represents the most current application.
• PROCESS_STATUS — outcome status of the rule application.
• ENTITY_DETAIL — descriptive detail about the entity at the time of evaluation.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org / security-group data isolation.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER.
• Concurrent program context: REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• Descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical uses include rule-engine audit reporting, troubleshooting why a partner or opportunity did not qualify for a program, and tracking rule effectiveness over time. A representative query retrieves the winning rules applied to a specific opportunity:

• SELECT r.ENTITY_RULE_APPLIED_ID, r.ENTITY, r.ENTITY_ID, p.RULE_NAME, r.ACTION_VALUE, r.PROCESS_STATUS FROM PV_ENTITY_RULES_APPLIED r, PV_PROCESS_RULES_B p WHERE r.PROCESS_RULE_ID = p.PROCESS_RULE_ID AND r.ENTITY_ID = :entity_id AND r.WINNING_RULE_FLAG = 'Y';
• Filtering on LATEST_FLAG = 'Y' isolates the most recent application per entity.
• Joining on SECURITY_GROUP_ID restricts results to the caller's security group.
• Grouping by PROCESS_TYPE or ACTION_VALUE supports volume and outcome reporting for rule tuning.

Related Objects

• PV_PROCESS_RULES_B — referenced twice, via PROCESS_RULE_ID and PARENT_PROCESS_RULE_ID; the definition of the rules being logged.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security.
• AML_RULE_APPLIED_ATTRS — dependent child table referencing ENTITY_RULE_APPLIED_ID; stores attribute-level detail for each applied rule.
• PV_ENTITY_RULES_APPLIED_PK / PV_ENTITY_RULES_APPLIED_U1 — primary key constraint and unique index on ENTITY_RULE_APPLIED_ID.