Results for “oe_pc_conditions”

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

Overview

OE_PC_CONDITIONS is a transactional configuration table owned by the ONT schema within Oracle Order Management (ONT). It stores the individual condition rows that belong to a constraint defined in OE_PC_CONSTRAINTS. In the Oracle EBS constraint and validation framework, a constraint expresses a validation rule, and each condition row supplies one attribute-level or record-set-level predicate that the constraint evaluates. The table is central to the Processing Constraints engine used to qualify when an order, line, or fulfillment action may be created, updated, deleted, or transitioned.

The object exists in both Oracle EBS 12.1.1 and 12.2.2. In 12.2.2 the table is edition-enabled, as evidenced by the presence of the ZD_EDITION_NAME column and the composite unique index OE_PC_CONDITIONS_U1 (CONDITION_ID, ZD_EDITION_NAME). Under the heuristic Data Vault classification mined from its foreign key structure, OE_PC_CONDITIONS leans toward a satellite: it is a descriptive, dependent child of a parent constraint hub, carrying attribute detail rather than defining an independent business entity.

Key Information Stored

The surrogate primary key is CONDITION_ID, enforced by OE_PC_CONDITIONS_PK. The business-key candidate is the pair (CONDITION_ID, ZD_EDITION_NAME) in unique index OE_PC_CONDITIONS_U1, with ZD_EDITION_NAME distinguishing the edition in Release 12.2.

• CONDITION_ID — primary key and the join column to the translation table.
• CONSTRAINT_ID — foreign key to OE_PC_CONSTRAINTS; the parent constraint this condition belongs to.
• VALIDATION_ENTITY_ID — foreign key to OE_AK_OBJECTS_EXT, identifying the entity being validated.
• VALIDATION_TMPLT_ID — foreign key to OE_PC_VTMPLTS; the validation template applied.
• RECORD_SET_ID — foreign key to OE_PC_RSETS; the record set against which the condition is evaluated.
• SCOPE_OP — the scope operator governing how the condition is applied.
• GROUP_NUMBER — groups conditions logically within a constraint.
• SYSTEM_FLAG and MODIFIER_FLAG — identify Oracle-seeded versus user-defined conditions and whether modification is permitted.
• ENABLED_FLAG — indicates whether the condition is active.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range for the condition.
• ZD_EDITION_NAME — edition identifier for 12.2 edition-based redefinition.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns.

Common Use Cases and Queries

Functional analysts interrogate this table to trace why an order entry action is blocked, and to audit which conditions attach to a given constraint. A typical query joins conditions to their parent constraint:

• Review conditions by constraint: SELECT condition_id, constraint_id, group_number, enabled_flag FROM oe_pc_conditions WHERE constraint_id = :constraint_id ORDER BY group_number.
• Active conditions: filter on ENABLED_FLAG = 'Y' and on SYSDATE between START_DATE_ACTIVE and END_DATE_ACTIVE.
• Translation lookup: join to OE_PC_CONDITIONS_TL on CONDITION_ID to retrieve the user-facing condition text in the session language.
• Seed versus custom: use SYSTEM_FLAG and MODIFIER_FLAG to separate Oracle-delivered conditions from customer-defined ones.
• In 12.2, edition-aware queries should include the ZD_EDITION_NAME predicate to target the correct edition.

Reporting use cases include documenting the complete constraint-condition hierarchy and auditing configuration changes across environments.

Related Objects

• OE_PC_CONSTRAINTS — parent table; joined via OE_PC_CONDITIONS.CONSTRAINT_ID.
• OE_PC_VTMPLTS — validation templates; joined via VALIDATION_TMPLT_ID.
• OE_PC_RSETS — record sets; joined via RECORD_SET_ID.
• OE_AK_OBJECTS_EXT — validation entities; joined via VALIDATION_ENTITY_ID.
• OE_PC_CONDITIONS_TL — translation table; joined via CONDITION_ID.