Results for “csi_t_transaction_lines”

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

Overview

CSI_T_TRANSACTION_LINES is a transactional staging and processing table within the Oracle E-Business Suite Install Base (CSI) module. It stores individual transaction lines that represent discrete units of change applied against installed base instances, whether originating from order management, service contracts, purchasing, or internal CSI processes. Each row corresponds to one source transaction line fed into the Install Base transaction processor, capturing the source reference, processing outcome, and configuration context required to reconcile changes to customer assets.

Under a Data Vault modeling perspective, the mined foreign key structure suggests this table behaves as a hub-leaning entity. TRANSACTION_LINE_ID functions as the durable surrogate business key around which descriptive satellites such as CSI_T_TXN_LINE_DETAILS are arranged. This classification is heuristic and intended as a modeling suggestion rather than a documented Oracle construct.

Key Information Stored

The table contains 37 documented columns. The most operationally significant are:

• TRANSACTION_LINE_ID — surrogate primary key defined by CSI_T_TRANSACTION_LINES_PK; also enshrined in unique index CSI_T_TRANSACTION_LINES_U01.
• SOURCE_TRANSACTION_ID and SOURCE_TRANSACTION_TABLE — business-key pair forming unique index CSI_T_TRANSACTION_LINES_U02, identifying the originating record and its source table.
• SOURCE_TRANSACTION_TYPE_ID and SOURCE_TRANSACTION_STATUS — classify and track the originating transaction's type and lifecycle state.
• PROCESSING_STATUS, ERROR_CODE, and ERROR_EXPLANATION — capture the outcome of Install Base processing and any rejection diagnostics.
• SOURCE_TXN_HEADER_ID — links the line to its transaction header grouping.
• CONFIG_SESSION_HDR_ID, CONFIG_SESSION_REV_NUM, CONFIG_SESSION_ITEM_ID, CONFIG_VALID_STATUS — record configuration validation context for configured items.
• MIGRATED_FLAG — indicates whether the line was loaded through a migration path.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enforcing multi-tenant data segregation.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS auditing and optimistic locking columns.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — DFF-enabled flexfield columns for extensions.

Common Use Cases and Queries

Typical uses include monitoring pending or errored Install Base transactions, tracing lines back to their source systems, and auditing configuration validation outcomes. A common diagnostic query retrieves failed lines with their reasons:

• SELECT TRANSACTION_LINE_ID, SOURCE_TRANSACTION_TABLE, SOURCE_TRANSACTION_ID, PROCESSING_STATUS, ERROR_CODE, ERROR_EXPLANATION FROM CSI_T_TRANSACTION_LINES WHERE PROCESSING_STATUS = 'ERROR';
• Source-system reconciliation joining on the business key: filter by SOURCE_TRANSACTION_TABLE and SOURCE_TRANSACTION_ID.
• Configuration audit: query CONFIG_VALID_STATUS and associated CONFIG_SESSION_* columns for configured-item validation history.
• Migration verification: filter on MIGRATED_FLAG to separate migrated from native transactions.

Because the table feeds Install Base processing, reports typically join it to detail and relationship tables to reconstruct complete transaction context.

Related Objects

• CSI_T_TXN_LINE_DETAILS — references CSI_T_TRANSACTION_LINES.TRANSACTION_LINE_ID; stores line-level detail attributes.
• CSI_T_II_RELATIONSHIPS — references TRANSACTION_LINE_ID; records instance-to-instance relationships created by transaction lines.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data security.
• Install Base concurrent programs and the CSI transaction processing APIs that populate and consume these rows.
• Related source modules (Order Management, Service, Purchasing) whose transaction tables supply SOURCE_TRANSACTION_TABLE and SOURCE_TRANSACTION_ID values.