Results for “csi_t_org_assignments”

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

Overview

CSI_T_ORG_ASSIGNMENTS is a transactional staging table within the CSI (Install Base) product of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. Its stated purpose is to hold "Transaction Details : Instance-Organization Associations" — that is, the intermediate representation of the relationship between an instance (a tracked item or asset) and the operating unit(s) to which it is assigned, as captured on an Install Base transaction line. The table sits in the CSI schema and is consumed by the Install Base transaction processing engine that ultimately materializes or maintains the corresponding interface record in CSI_I_ORG_ASSIGNMENTS.

The ETRM metadata classifies the object heuristically — using its foreign key topology as the signal — as a link table in a Data Vault style model. That classification is a modeling suggestion rather than a documented assertion: the table resolves many-to-many style associations between transaction line detail and instance/operating unit entities, which is the characteristic shape of a link. Practitioners designing downstream analytics or historization should treat it as a transactional association carrier and not as a standalone business entity hub.

Key Information Stored

The documented physical schema defines 32 columns. The most consequential are summarized below.

• TXN_OPERATING_UNIT_ID — the single-column surrogate primary key (CSI_T_ORG_ASSIGNMENTS_PK) and also the column behind the unique index CSI_T_ORG_ASSIGNMENTS_U01. This makes it the primary business-key candidate for the row.
• TXN_LINE_DETAIL_ID — foreign key to CSI_T_TXN_LINE_DETAILS; the transaction line detail that spawned this organization association.
• INSTANCE_OU_ID — foreign key to CSI_I_ORG_ASSIGNMENTS; the target instance–operating unit association record that this transaction row will affect.
• OPERATING_UNIT_ID — the operating unit being associated with the instance.
• RELATIONSHIP_TYPE_CODE — classifies the nature of the instance-to-organization relationship.
• ACTIVE_START_DATE / ACTIVE_END_DATE — effective dating for the association.
• PRESERVE_DETAIL_FLAG — controls whether fine-grained detail is retained during processing.
• MIGRATED_FLAG — indicates whether the row originated from a migration or legacy load.
• Standard EBS audit and concurrency columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and SECURITY_GROUP_ID (foreign key to FND_SECURITY_GROUPS).
• CONTEXT plus ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF/extension block.

Common Use Cases and Queries

Typical reporting isolates in-flight Install Base transactions and their organization associations:

• Trace which transaction line detail generated an organization assignment.
• Reconcile staged rows against the applied interface record in CSI_I_ORG_ASSIGNMENTS.
• Audit migrated associations using MIGRATED_FLAG.
• Filter by effective dates to report active assignments.

A representative join pattern:

SELECT t.TXN_OPERATING_UNIT_ID, t.TXN_LINE_DETAIL_ID, t.OPERATING_UNIT_ID, t.RELATIONSHIP_TYPE_CODE, t.ACTIVE_START_DATE, t.ACTIVE_END_DATE
FROM CSI_T_ORG_ASSIGNMENTS t, CSI_T_TXN_LINE_DETAILS d, CSI_I_ORG_ASSIGNMENTS i
WHERE t.TXN_LINE_DETAIL_ID = d.TXN_LINE_DETAIL_ID
AND t.INSTANCE_OU_ID = i.INSTANCE_OU_ID;

Related Objects

• CSI_T_TXN_LINE_DETAILS — via TXN_LINE_DETAIL_ID; the parent transaction line detail.
• CSI_I_ORG_ASSIGNMENTS — via INSTANCE_OU_ID; the instance–operating unit interface record.
• FND_SECURITY_GROUPS — via SECURITY_GROUP_ID; security group control.
• CSI_T_ORG_ASSIGNMENTS_PK / CSI_T_ORG_ASSIGNMENTS_U01 — the primary and unique indexes over TXN_OPERATING_UNIT_ID.
• Install Base transaction processing APIs and concurrent programs that consume CSI_T_* staging rows when applying associations into the CSI interface tables.