Results for “user_message”

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

Overview

The OE_UPGRADE_PC_CONDNS table is an Order Management (ONT) schema object that stores the pricing and processing conditions to be upgraded to Oracle E-Business Suite Release 11i. It functions as a staging and control structure used during the upgrade path from earlier releases of Oracle Order Entry, preserving rule conditions, validation logic, and result mappings so they can be migrated into the 11i pricing and order capture model. The object resides in the ONT schema with a status of VALID and contains nine documented columns in the 12.2.2 physical schema.

From a Data Vault modeling perspective, the metadata classifies this table heuristically as standalone. This suggests there are no mined foreign-key dependencies outward to other hubs or links; the table is best modeled as a self-contained reference or staging object rather than a conformed hub or link. The standalone classification reflects its transitional nature: it is not a long-lived transactional entity but a working set consumed during the upgrade process.

Key Information Stored

The table's identity is anchored by its primary key, OE_UPGRADE_PC_CONDNS_PK, defined over the composite of CONDITION_CODE, OLD_OBJECT_ID, ACTION_ID, and RESULT_ID. A unique index, OE_UPGRADE_PC_CONDNS_U1, covers the same four columns in the order CONDITION_CODE, ACTION_ID, RESULT_ID, and OLD_OBJECT_ID, confirming this combination as the effective business key.

• CONDITION_CODE — Identifies the type or category of condition being upgraded; the leading element of both the primary key and the unique business key.
• OLD_OBJECT_ID — References the identifier of the legacy object (rule, qualifier, or condition) from the pre-upgrade environment.
• ACTION_ID — Identifies the action associated with the condition being migrated.
• RESULT_ID — Identifies the result produced when the condition is satisfied.
• VTMPLT_ID — Links the condition to its associated value template used in the pricing engine.
• NEW_ENTITY_ID — Holds the identifier of the target entity created in the upgraded (11i/12.x) data model.
• GROUP_NUMBER — A sequencing or grouping value used to organize related conditions during processing.
• VALIDATION_ENTITY_ID — References the entity used to validate the condition before it is applied.
• USER_MESSAGE — Stores the message text returned to the user when a validation or condition rule fails.

Common Use Cases and Queries

This table is primarily relevant to upgrade and data migration activities rather than day-to-day order entry. Typical uses include verifying that all legacy conditions have a corresponding target entity, auditing the mapping between old and new identifiers, and reporting on validation messages carried forward into the upgraded environment.

A representative audit query counts un-migrated conditions — that is, rows whose legacy object does not yet have a resolved target:

SELECT CONDITION_CODE, COUNT(*)
FROM   ONT.OE_UPGRADE_PC_CONDNS
WHERE  NEW_ENTITY_ID IS NULL
GROUP  BY CONDITION_CODE;

To trace a specific legacy object through the upgrade, join on the business key:

SELECT OLD_OBJECT_ID, NEW_ENTITY_ID, VALIDATION_ENTITY_ID, USER_MESSAGE
FROM   ONT.OE_UPGRADE_PC_CONDNS
WHERE  OLD_OBJECT_ID = :legacy_id
AND    CONDITION_CODE = :condition;

Reporting scenarios commonly group by OLD_OBJECT_ID and GROUP_NUMBER to confirm completeness of the condition set, and filter on USER_MESSAGE to surface conditions that failed validation during the upgrade.

Related Objects

Because the heuristic classification is standalone, the metadata documents no outbound foreign keys to other ONT tables. The most significant related objects are therefore those implied by the column semantics and the surrounding upgrade infrastructure:

• OE_UPGRADE_PC_ACTIONS — Parallel staging table for the actions referenced by ACTION_ID.
• OE_UPGRADE_PC_RESULTS — Parallel staging table for results referenced by RESULT_ID.
• QP_VTMPL_DEFINITIONS — Value template definitions referenced by VTMPLT_ID in the pricing schema.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — Order capture entities influenced by migrated conditions.
• QP_PRICING_ATTRIBUTES — Pricing attributes consumed by condition and validation logic.

Joins between this table and these objects rely on CONDITION_CODE, ACTION_ID, RESULT_ID, VTMPLT_ID, VALIDATION_ENTITY_ID, and NEW_ENTITY_ID rather than declared referential constraints.