Search Results oe_pc_exclusions_uk

Overview

The OE_PC_EXCLUSIONS table is a core data object within the Oracle E-Business Suite (EBS) Order Management (ONT) module, specifically for versions 12.1.1 and 12.2.2. It functions as a critical component of the pricing constraint architecture. Its primary role is to define exceptions within constraint assignments by storing a list of responsibilities that are explicitly excluded from being governed by a specific pricing constraint. This allows for granular control over constraint enforcement, enabling administrators to apply business rules broadly while carving out exceptions for specific user roles or functional areas.

Key Information Stored

The table's structure is designed to map exclusions to specific constraint assignments. Its key columns, as defined by its primary key, are:

• ASSIGNMENT_ID: A foreign key column that links the exclusion record to a specific constraint assignment defined in the OE_PC_ASSIGNMENTS table. This identifies the constraint from which responsibilities are being excluded.
• RESPONSIBILITY_ID: Stores the identifier (typically corresponding to FND_RESPONSIBILITY.RESPONSIBILITY_ID) for the Oracle EBS responsibility that is exempt from the constraint. The combination of ASSIGNMENT_ID and RESPONSIBILITY_ID must be unique, as enforced by the OE_PC_EXCLUSIONS_UK primary key constraint.

Common Use Cases and Queries

This table is central to administrative setups and troubleshooting scenarios involving pricing constraints. A common use case is auditing which responsibilities are exempt from a particular pricing rule, such as a discount cap or a mandatory attribute requirement. For instance, a "Master Discount" constraint might be assigned to all order entry responsibilities, but the "VP Sales" responsibility could be excluded to allow for override authority. A typical diagnostic query would join to the constraint assignment and responsibility tables to produce a readable report:

• Sample Query: SELECT a.constraint_id, e.responsibility_id, r.responsibility_name FROM oe_pc_exclusions e, oe_pc_assignments a, fnd_responsibility_vl r WHERE e.assignment_id = a.assignment_id AND e.responsibility_id = r.responsibility_id ORDER BY a.constraint_id;

This data is primarily managed through the Order Management pricing constraint forms and APIs, not via direct SQL manipulation.

Related Objects

OE_PC_EXCLUSIONS has a direct and essential relationship with the core constraint assignment table, as documented in the provided metadata:

• OE_PC_ASSIGNMENTS: This is the primary parent table. The foreign key OE_PC_EXCLUSIONS.ASSIGNMENT_ID references OE_PC_ASSIGNMENTS. An assignment record must exist before responsibilities can be excluded from it. This relationship is fundamental to the constraint exclusion model.
• FND_RESPONSIBILITY: While not listed as a formal foreign key in the provided excerpt, the RESPONSIBILITY_ID column logically references FND_RESPONSIBILITY.RESPONSIBILITY_ID to resolve the responsibility name and application.