Results for “relationship_code”

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

Overview

CE_UPGA_RELATION_REC is an audit table within the Cash Management (CE) module of Oracle E-Business Suite, owned by the CE schema. As documented in the ETRM repository, it functions as the audit counterpart to CE_UPG_RELATIONSHIP_REC, capturing the state of bank-to-entity relationship records as they are processed by the Oracle Payments upgrade utilities. In EBS 12.1.1 and 12.2.2, this object supports the migration and reconciliation of legacy banking relationship data into the current Payments architecture.

The table carries 22 documented columns and is classified heuristically as a standalone object under the Data Vault modeling convention, based on its foreign key structure. Modeling guidance suggests treating it as an auditable satellite-style construct anchored to the upgrade run, rather than a pure business hub or link. Its primary purpose is historical traceability: preserving a snapshot of relationships keyed by upgrade identifier so that upgrade outcomes can be verified and disputes investigated after the fact.

Key Information Stored

The composite primary key, CE_UPGA_RELATION_REC_PK, is defined over CE_UPGRADE_ID, BANK_ENTITY_TYPE, and RELATIONSHIP_TYPE. This combination forms the surrogate identity of each audit row and ties the record to a specific upgrade execution, entity classification, and relationship category.

• CE_UPGRADE_ID — identifier of the upgrade run that produced the audit entry.
• UPGRADE_STATUS — outcome or state of the relationship during the upgrade.
• BANK_ENTITY_TYPE — classification of the bank-side entity participating in the relationship.
• RELATIONSHIP_TYPE / RELATIONSHIP_CODE — categorical and coded descriptors of the relationship.
• RELATIONSHIP_ID — reference to the underlying relationship record being audited.
• PARTY_ID — party associated with the relationship.
• SUBJECT_TYPE / SUBJECT_TABLE_NAME / SUBJECT_ID — polymorphic reference to the subject side of the relationship.
• OBJECT_TYPE / OBJECT_TABLE_NAME / OBJECT_ID — polymorphic reference to the object side of the relationship.
• START_DATE / END_DATE — effective dating for the relationship.
• JOB_TITLE / CREATED_BY_MODULE — supplementary attributes describing the relationship context.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified the row.

The subject-side lookup resolves through the documented foreign key SUBJECT_ID → IGS_UC_COM_EBL_SUBJ, which anchors the polymorphic subject reference for the relevant relationship category.

Common Use Cases and Queries

Typical usage centers on post-upgrade validation and reconciliation. A common pattern retrieves all audit rows for a given upgrade run:

• SELECT ce_upgrade_id, bank_entity_type, relationship_type, upgrade_status FROM ce.ce_upga_relation_rec WHERE ce_upgrade_id = :upgrade_id;
• Comparing the audit population against CE_UPG_RELATIONSHIP_REC to detect records that failed, were skipped, or were transformed unexpectedly.
• Tracing a specific business relationship through RELATIONSHIP_ID or PARTY_ID to confirm the recorded outcome.
• Reporting on upgrade status distributions by BANK_ENTITY_TYPE and RELATIONSHIP_TYPE for sign-off documentation.
• Reviewing effective dating (START_DATE/END_DATE) to confirm temporal accuracy of migrated relationships.

Related Objects

• CE_UPG_RELATIONSHIP_REC — the source table for which this object is the audit complement.
• IGS_UC_COM_EBL_SUBJ — referenced via the SUBJECT_ID foreign key.
• CE_UPGA_RELATION_REC_PK — the primary key constraint enforcing composite uniqueness.
• CE_UPGRADE_ID-linked upgrade control tables — parent records identifying each upgrade execution.
• Relationship and party tables in the CE schema — populated through the corresponding relationship identifiers.