Results for “transfer_components_flag”

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

Overview

CSI_T_II_RELATIONSHIPS is a transactional staging table within the Oracle E-Business Suite Install Base (CSI) module. Its documented description—Transaction Details: Instance to Instance Relationships—indicates that it captures the relationships asserted between two item instances as part of an Install Base transaction, prior to those relationships being committed to their production counterparts. In Oracle EBS 12.1.1 and 12.2.2, the table functions as the transactional feeder for the runtime relationship model, carrying both the linkage between instances and the descriptive attributes that govern how that linkage behaves.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a link classification: the table contains numerous references to hubs and dimensions (transactions, instances, relationship types, security groups) rather than standing alone as an entity. This is a heuristic suggestion rather than a documented model, and implementers should treat it as a conceptual aid when designing downstream integrations.

Key Information Stored

The table holds 46 documented columns. The most operationally significant are the following:

• TXN_RELATIONSHIP_ID — Surrogate primary key, enforced by CSI_T_II_RELATIONSHIPS_PK and additionally by unique index CSI_T_II_RELATIONSHIPS_U01.
• TRANSACTION_LINE_ID — Foreign key to CSI_T_TRANSACTION_LINES, tying the relationship to a specific line of an Install Base transaction.
• SUBJECT_ID / OBJECT_ID — The two endpoints of the relationship. Both are documented as foreign keys into CSI_T_TXN_LINE_DETAILS and, in the case of OBJECT_ID, into CSI_ITEM_INSTANCES.
• RELATIONSHIP_TYPE_CODE — Foreign key to CSI_II_RELATION_TYPES, defining the semantics of the link (for example, parent/child or component/assembly).
• CSI_INST_RELATIONSHIP_ID — Foreign key into CSI_II_RELATIONSHIPS, which becomes the runtime instance relation after the transaction is processed.
• SUBJECT_TYPE / OBJECT_TYPE — Classifiers describing the nature of each endpoint.
• DISPLAY_ORDER, POSITION_REFERENCE, MANDATORY_FLAG — Presentation and enforcement attributes controlling how the relationship is surfaced and whether it must be satisfied.
• ACTIVE_START_DATE / ACTIVE_END_DATE — Effective dating for the relationship.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org data access.
• TRANSFER_COMPONENTS_FLAG, TARGET_COMMITMENT_DATE, MIGRATED_FLAG — Processing controls governing component transfer, commitment timing, and migration status.
• OBJECT_VERSION_NUMBER and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Concurrency control and audit trail.

The 15 ATTRIBUTE columns and CONTEXT column provide the standard EBS DFF extensibility slot, while SUB_CONFIG_INST_* and OBJ_CONFIG_INST_* columns carry configuration instance header, revision, and item identifiers for each endpoint.

Common Use Cases and Queries

Typical reporting and diagnostics centre on validating what relationships a transaction will assert before or after processing:

SELECT r.txn_relationship_id,
       r.relationship_type_code,
       r.subject_id,
       r.object_id,
       r.active_start_date,
       r.active_end_date
FROM   csi.csi_t_ii_relationships r
WHERE  r.transaction_line_id = :p_transaction_line_id
ORDER  BY r.display_order;

Joining to CSI_II_RELATION_TYPES yields human-readable relationship names, and joining SUBJECT_ID/OBJECT_ID to CSI_T_TXN_LINE_DETAILS resolves each endpoint. Correlation against CSI_II_RELATIONSHIPS via CSI_INST_RELATIONSHIP_ID confirms whether a staged relationship has been materialised. A common reconciliation query compares staged rows against their runtime counterparts to detect relationships that failed to commit.

Related Objects

• CSI_T_TRANSACTION_LINES — Parent transactional line; join on TRANSACTION_LINE_ID.
• CSI_T_TXN_LINE_DETAILS — Supplies subject and object detail records; join on SUBJECT_ID and OBJECT_ID.
• CSI_ITEM_INSTANCES — The instance master; join on OBJECT_ID.
• CSI_II_RELATIONSHIPS — Runtime instance-to-instance relationship table; join on CSI_INST_RELATIONSHIP_ID.
• CSI_II_RELATION_TYPES — Lookup of relationship semantics; join on RELATIONSHIP_TYPE_CODE.
• FND_SECURITY_GROUPS — Security context; join on SECURITY_GROUP_ID.