Results for “oe_pc_exclusions_u1”

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

Overview

OE_PC_EXCLUSIONS is an Order Management (ONT) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schemas that supports the Processing Constraints framework. Processing Constraints allow an administrator to restrict which operations (for example, update, cancel, or delete) can be performed on an order or order line when a defined condition is met. Constraints are scoped to responsibilities; OE_PC_EXCLUSIONS records the exceptions to that scoping rule, storing the responsibilities that are deliberately not constrained by a particular constraint assignment.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. It is best understood as a dependent detail table rather than an independent hub or link: it exists only to qualify a parent constraint assignment, and it carries no business identity of its own.

Key Information Stored

The documented physical schema in 12.2.2 contains 24 columns. The most consequential are:

• ASSIGNMENT_ID — Foreign key to OE_PC_ASSIGNMENTS, identifying the processing constraint assignment whose scope is being narrowed. This is part of the composite primary key.
• RESPONSIBILITY_ID — Identifies the responsibility that is excluded from the constraint. This is the other half of the composite primary key.
• APPLICATION_ID — The application owning the responsibility, included in the alternate unique index and used to disambiguate responsibility IDs across application boundaries.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns providing the audit trail for each exclusion row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, available for customer-defined context and segment values.

Two unique keys are documented. The primary key, OE_PC_EXCLUSIONS_UK, is the composite of (ASSIGNMENT_ID, RESPONSIBILITY_ID). The alternate unique index OE_PC_EXCLUSIONS_U1 is (ASSIGNMENT_ID, RESPONSIBILITY_ID, APPLICATION_ID). This U1 index is the more complete business-key candidate in multi-application deployments, since the same responsibility ID may recur under different applications, whereas the two-column primary key alone does not guarantee that distinction. Note that neither key is a surrogate; the table has no single-column synthetic identifier, so the exclusion is identified purely by the combination of parent assignment and responsibility.

Common Use Cases and Queries

The primary use case is administrative verification of the effective scope of a processing constraint. Before or after changes are made in the Processing Constraints setup UI, implementers query this table to confirm exactly which responsibilities are exempt.

• Listing all exclusions for a specific constraint assignment:

  SELECT responsibility_id, application_id
  FROM   ont.oe_pc_exclusions
  WHERE  assignment_id = :assignment_id;

• Determining whether a given responsibility is excluded from a constraint:

  SELECT COUNT(*)
  FROM   ont.oe_pc_exclusions
  WHERE  assignment_id = :assignment_id
  AND    responsibility_id = :responsibility_id;

• Comparing the excluded set against the responsibilities assigned in the parent record to detect an over-broad or contradictory configuration.
• Audit and migration reporting, using CREATION_DATE and LAST_UPDATE_DATE to identify recently changed exclusions, and the ATTRIBUTE columns for any customer-defined tracking.

Exclusions are typically maintained through the Order Management Processing Constraints setup forms rather than by direct DML; ad hoc inserts bypass the validation logic and can produce inconsistent constraint behavior.

Related Objects

The following objects are most significant in relation to OE_PC_EXCLUSIONS:

• OE_PC_ASSIGNMENTS — The parent table, joined on OE_PC_EXCLUSIONS.ASSIGNMENT_ID = OE_PC_ASSIGNMENTS.ASSIGNMENT_ID. This is the sole documented foreign key.
• OE_PC_CONSTRAINTS — Defines the constraints themselves and supplies the conditions that assignments reference.
• OE_PC_ASSIGNMENTS (requeried for constraint scope) — Holds the responsibility and application context against which exclusions are evaluated.
• FND_RESPONSIBILITY_VL / FND_RESPONSIBILITY — Resolves RESPONSIBILITY_ID to a user-facing responsibility name for reporting.
• OE_PC_CONSTRAINT_VIOLATIONS and the Processing Constraints runtime APIs in the ONT schema — Consume the resolved constraint and exclusion sets when validating order operations.
• OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — The transactional order tables whose operations are ultimately governed by the constraint and exclusion configuration.