Results for “transaction_system_id”

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

Overview

CSI_T_TXN_SYSTEMS is a transaction-staging table in the CSI (Install Base) product of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Its documented description is "Transaction Details : System Details," indicating that it holds the system-level attributes captured during an Install Base transaction — for example, an instance creation, update, or move operation — before or as those attributes are applied to the live install base records. Where CSI_T_TXN_LINE_DETAILS records the transactional line context, CSI_T_TXN_SYSTEMS holds the customer-facing and site-specific detail for the system being transacted, including contact assignments and ship-to, bill-to, and install site references. The table has 46 documented columns and is owned by the CSI schema.

Heuristically, the mined foreign-key structure classifies this object as satellite-leaning. This suggests modeling CSI_T_TXN_SYSTEMS as a satellite attached to a transaction-level hub or link, since it carries descriptive and contextual attributes (names, contacts, site references, active dates) rather than acting as a standalone business key registry. That classification is a modeling suggestion inferred from the FK topology, not a declarative property documented by Oracle.

Key Information Stored

The surrogate primary key is TRANSACTION_SYSTEM_ID, enforced through CSI_T_TXN_SYSTEMS_PK. A unique index, CSI_T_TXN_SYSTEMS_U01, also exists on TRANSACTION_SYSTEM_ID, making it the documented business-key candidate.

• TRANSACTION_SYSTEM_ID — surrogate primary key and unique-index candidate identifying each transaction system row.
• SYSTEM_NAME, DESCRIPTION, SYSTEM_TYPE_CODE, SYSTEM_NUMBER — descriptive identity of the system being transacted.
• BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, TECHNICAL_CONTACT_ID, SERVICE_ADMIN_CONTACT_ID — foreign keys to HZ_PARTIES identifying the contacts associated with the system.
• SHIP_TO_SITE_USE_ID, BILL_TO_SITE_USE_ID — foreign keys to HZ_CUST_SITE_USES_ALL referencing the ship-to and bill-to site uses.
• INSTALL_SITE_USE_ID — foreign key to HZ_PARTY_SITES denoting the install site.
• CUSTOMER_ID — foreign key to HZ_CUST_ACCOUNTS identifying the owning customer account.
• TRANSACTION_LINE_ID — associates the system detail with its parent transaction line.
• CONFIG_SYSTEM_TYPE, COTERMINATE_DAY_MONTH — configuration and cotermination attributes.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating for the system record.
• MIGRATED_FLAG, OBJECT_VERSION_NUMBER, SECURITY_GROUP_ID — migration indicator, optimistic locking, and multi-org security references.

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ATTRIBUTE1–ATTRIBUTE15 flexfield columns are also present.

Common Use Cases and Queries

Typical reporting scenarios include reconciling staged transaction systems against the customer model, auditing contact and site assignments captured during a transaction, and diagnosing failed or pending Install Base transactions. A representative join retrieves the system with its customer and sites:

• SELECT ts.TRANSACTION_SYSTEM_ID, ts.SYSTEM_NAME, ts.SYSTEM_NUMBER, ts.CUSTOMER_ID, ts.SHIP_TO_SITE_USE_ID, ts.BILL_TO_SITE_USE_ID FROM CSI_T_TXN_SYSTEMS ts WHERE ts.START_DATE_ACTIVE <= SYSDATE;
• Join to CSI_T_TXN_LINE_DETAILS on TRANSACTION_SYSTEM_ID to correlate system detail with line detail: SELECT ld.TRANSACTION_LINE_ID, ts.SYSTEM_NAME FROM CSI_T_TXN_SYSTEMS ts, CSI_T_TXN_LINE_DETAILS ld WHERE ts.TRANSACTION_SYSTEM_ID = ld.TRANSACTION_SYSTEM_ID;
• Join to HZ_CUST_ACCOUNTS on CUSTOMER_ID and to HZ_PARTIES on the contact columns to resolve customer and contact names.

These queries support transaction audit reports, migration validation (filtering on MIGRATED_FLAG), and customer-site assignment analysis.

Related Objects

• CSI_T_TXN_LINE_DETAILS — references CSI_T_TXN_SYSTEMS via TRANSACTION_SYSTEM_ID; the principal child of this table.
• HZ_CUST_ACCOUNTS — joined through CUSTOMER_ID.
• HZ_PARTIES — joined through BILL_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, TECHNICAL_CONTACT_ID, and SERVICE_ADMIN_CONTACT_ID.
• HZ_CUST_SITE_USES_ALL — joined through SHIP_TO_SITE_USE_ID and BILL_TO_SITE_USE_ID.
• HZ_PARTY_SITES — joined through INSTALL_SITE_USE_ID.
• FND_SECURITY_GROUPS — joined through SECURITY_GROUP_ID for multi-org security.