Results for “oe_pc_vtmplt_cols”

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

Overview

OE_PC_VTMPLT_COLS is a table in the ONT (Order Management) schema of Oracle E-Business Suite, valid in both release 12.1.1 and 12.2.2. It stores the attribute validation pairs for validation templates that are based on column values. In practical terms, this table is the detail-level component of the Order Management validation template framework, where each row defines a single rule that compares an order attribute (column) against an operator and a target value.

Within the validation template model, OE_PC_VTMPLT_COLS functions as the child of the header table OE_PC_VTMPLTS, linked through the VALIDATION_TMPLT_ID foreign key. A validation template header describes the template itself, while the rows in OE_PC_VTMPLT_COLS describe the individual column-based conditions that make up the template. Heuristically, the mined foreign-key structure classifies this object as satellite-leaning: it holds descriptive, context-dependent attributes that qualify a parent entity rather than defining an independent business entity or a many-to-many association. This classification should be treated as a modeling suggestion rather than a documented design contract.

Key Information Stored

The documented physical schema for release 12.2.2 contains 11 columns under the ONT schema. The most significant of these are:

• VALIDATION_TMPLT_COL_ID — the surrogate primary key, enforced by the unique index OE_PC_VTMPLT_COLS_PK. It uniquely identifies each validation pair row.
• VALIDATION_TMPLT_ID — the foreign key to OE_PC_VTMPLTS, identifying the parent validation template to which the rule belongs.
• COLUMN_NAME — the order attribute or column being evaluated by the rule.
• VALIDATION_OP — the comparison operator applied to the column value (for example equality, range, or set membership).
• VALUE_STRING — the literal value or value expression against which the column is compared.
• ZD_EDITION_NAME — the editioning column that supports Oracle EBS 12.2 online patching and edition-based redefinition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns capturing row creation and modification context.

A second unique index, OE_PC_VTMPLT_COLS_U1, is defined over (VALIDATION_TMPLT_COL_ID, ZD_EDITION_NAME), which is the edition-aware business-key candidate. Practically, the meaningful business key for a validation rule is the combination of VALIDATION_TMPLT_ID, COLUMN_NAME, and VALIDATION_OP, although that combination is not documented as an enforced unique constraint.

Common Use Cases and Queries

The principal use case is diagnosing why an order or order line fails validation or defaulting logic. Administrators and developers query this table to enumerate the rules attached to a given template, verify the operator and comparison value, and trace unexpected order behavior back to configuration.

• Listing all rules for a template: SELECT column_name, validation_op, value_string FROM ont.oe_pc_vtmplt_cols WHERE validation_tmplt_id = :p_template_id;
• Searching for rules targeting a specific attribute: SELECT * FROM ont.oe_pc_vtmplt_cols WHERE column_name = 'ORDER_TYPE_ID';
• Edition-aware lookups in 12.2.2 should account for ZD_EDITION_NAME when resolving the active definition; for example WHERE zd_edition_name = 'SET1' or the currently active edition.
• Audit and change reporting across CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY to track who modified validation configuration.
• Reporting joins to OE_PC_VTMPLTS to present template names alongside their constituent column rules.

Related Objects

The most significant related objects, based on the documented foreign keys, are:

• OE_PC_VTMPLTS — the parent validation template header; joined on OE_PC_VTMPLT_COLS.VALIDATION_TMPLT_ID = OE_PC_VTMPLTS.VALIDATION_TMPLT_ID.
• OE_PC_VTMPLT_COLS_PK — the primary key unique index over VALIDATION_TMPLT_COL_ID.
• OE_PC_VTMPLT_COLS_U1 — the edition-aware unique index over (VALIDATION_TMPLT_COL_ID, ZD_EDITION_NAME).
• Order Management processing logic that consumes validation templates, such as order import and order entry validation routines within the ONT module, reads these rows to enforce column-value conditions.

Because the metadata documents only a single FK relationship, the related-object surface is comparatively narrow; other dependencies are driven through the parent template rather than directly through this table.