Search Results oe_upgrade_pc_condns

Overview

The OE_UPGRADE_PC_CONDNS table is a technical repository within the Oracle E-Business Suite (EBS) Order Management (ONT) module. As indicated by its name and description, its primary historical role was to store condition data during the upgrade process to the 11i release. In the context of EBS 12.1.1 and 12.2.2, this table is a legacy artifact from that migration. It does not support active transactional processes but remains as a reference data store for conditions that were transitioned from a pre-11i environment. Understanding its structure is crucial for historical data analysis, auditing, and troubleshooting legacy upgrade-related data issues.

Key Information Stored

The table's structure is defined by a composite primary key, which uniquely identifies each condition record slated for upgrade. The key columns are:

• CONDITION_CODE: The core identifier for the specific business rule or condition being upgraded.
• OLD_OBJECT_ID: References the original identifier of the object (e.g., a pricing or modifier entity) from the pre-upgrade system.
• ACTION_ID: Likely denotes a specific upgrade action or step applied to the condition.
• RESULT_ID: Potentially stores a reference to the outcome or the new object ID generated in the 11i system post-upgrade.

Together, these columns form the OE_UPGRADE_PC_CONDNS_PK primary key, ensuring the uniqueness of the upgrade mapping for each condition from its old context through the applied action and result.

Common Use Cases and Queries

Current use cases are predominantly analytical and historical. A common requirement is to trace the lineage of a pricing condition or modifier from its legacy source. For instance, to find all upgrade records for a specific condition code, one would query:

SELECT * FROM ont.oe_upgrade_pc_condns WHERE condition_code = '<CODE_VALUE>';

Another typical query involves joining this table with the current pricing condition tables (like QP_LIST_LINES) on derived IDs to audit the completeness of the historical upgrade. Reporting use cases focus on generating summaries of upgraded conditions by action or result for compliance and migration validation reports. It is important to note that direct manipulation of this table is not standard practice for ongoing operations.

Related Objects

Based on the provided metadata, the primary documented relationship is its own primary key constraint. While explicit foreign key constraints to other tables are not listed in the excerpt, the column semantics strongly suggest logical relationships. The OLD_OBJECT_ID and RESULT_ID columns would logically relate to identifiers in legacy pre-11i condition tables and the corresponding post-upgrade tables in the QP (Advanced Pricing) or ONT schemas, such as QP_LIST_HEADERS_B or OE_PRICE_ADJUSTMENTS. The table is central to the OE_UPGRADE_PC_CONDNS_PK index. Any dependencies would be from historical upgrade scripts or data fix programs that populated this mapping table during the system migration to 11i.