Results for “scope_op”

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

Overview

OE_UPGRADE_PC_SCOPE is a transient staging table owned by the ONT (Order Management) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to support the upgrade of processing constraints data. Processing constraints in Order Management govern which order attributes can be modified, by whom, and under what conditions; the rules are assembled from record sets, scopes, and validation assignments. During an upgrade or data migration, the legacy scope identifier for a processing constraint must be remapped to the new processing constraint scope values used by the current release. OE_UPGRADE_PC_SCOPE holds that mapping so the conversion program can translate old scope references without manual intervention.

The table is documented with five columns and a small set of constraints. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the table does not behave as a conventional hub, link, or satellite. In practice it is best modeled as a temporary persistence or mapping entity whose rows are meaningful only within the context of a single upgrade run. The standalone classification is a modeling suggestion rather than a hard architectural rule, and it reflects the fact that the table has a narrow, single-purpose lifecycle outside normal transactional processing.

Key Information Stored

The documented physical schema contains five columns, all of which participate in either the primary key or the foreign-key relationship. The primary key is OE_UPGRADE_PC_SCOPE_PK, defined over (SCOPE_CODE, OLD_OBJECT_ID). A unique index, OE_UPGRADE_PC_SCOPE_U1, is also defined over (SCOPE_CODE, OLD_OBJECT_ID), making this composite the business-key candidate that enforces one mapping row per legacy scope object.

• SCOPE_CODE — the processing constraint scope code being upgraded. It is the first element of both the primary key and the unique business key.
• OLD_OBJECT_ID — the identifier of the legacy scope object as it existed prior to conversion. It is the second element of the primary key and unique index, and it distinguishes the multiple legacy objects that may share a scope code.
• NEW_ENTITY_ID — the identifier of the converted or newly created entity in the target model. This is the principal payload of the mapping, supplying the value the upgrade program writes into the live processing constraint tables.
• RECORD_SET_ID — a foreign-key reference to OE_PC_RSETS, associating the upgraded scope with its processing constraint record set.
• SCOPE_OP — the scope operator associated with the scope entry, qualifying how the scope is applied during constraint evaluation.

There is no single surrogate column in this table; the composite primary key is itself the identifier, and the unique index duplicates that surface as a business-key candidate. Because the table is populated only during upgrade activity, its row count is typically modest and tied to the number of legacy scopes being converted.

Common Use Cases and Queries

The primary use case is post-upgrade reconciliation: confirming that every legacy processing constraint scope now resolves to a valid new entity. Administrators and upgrade teams query the table to count unmapped or duplicated scopes, to identify legacy objects that share a scope code, and to validate the join between the mapping and the record set table.

• Listing all scope conversions performed for a given scope code: SELECT scope_code, old_object_id, new_entity_id FROM ont.oe_upgrade_pc_scope WHERE scope_code = :scope_code ORDER BY old_object_id;
• Detecting duplicate or ambiguous mappings using the unique key definition: SELECT scope_code, old_object_id, COUNT(*) FROM ont.oe_upgrade_pc_scope GROUP BY scope_code, old_object_id HAVING COUNT(*) > 1;
• Joining to the record set table to verify scope-to-record-set integrity: SELECT s.scope_code, s.old_object_id, s.new_entity_id, r.record_set_id FROM ont.oe_upgrade_pc_scope s, ont.oe_pc_rsets r WHERE s.record_set_id = r.record_set_id;

Reporting generally focuses on upgrade completeness and exception handling rather than day-to-day order processing.

Related Objects

The documented foreign-key relationship ties the table directly to the processing constraint record set definition. Other related objects belong to the surrounding processing constraint framework and typically participate through the scope codes and entity identifiers carried here.

• OE_PC_RSETS — processing constraint record sets; joined on RECORD_SET_ID via the documented foreign key.
• OE_PC_SCOPES — the live processing constraint scope definitions that the upgrade populates or into which NEW_ENTITY_ID resolves.
• OE_PC_RSET_SCOPES — the association between record sets and scopes, validated when the upgraded scope is attached to its record set.
• OE_PC_CONSTRAINTS — processing constraints whose behavior depends on the scope and record set remodeled by this upgrade.
• OE_PC_ASSIGNMENTS — assignment rules that reference processing constraint scopes and may be affected by the conversion.
• OE_UPGRADE_PC_* — companion upgrade staging tables used by the same conversion program to migrate other processing constraint components.

Because the table is proprietary Oracle upgrade infrastructure, it is not intended for direct maintenance; queries against it are read-only and primarily diagnostic.