Results for “csi_txn_errors”

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

Overview

CSI_TXN_ERRORS is the Install Base transaction error repository within the Oracle E-Business Suite CSI (Install Base) product. It captures row-level failures encountered during the processing of installed base transactions — for example, when inventory material movements, serial number changes, lot-controlled adjustments, or instance status updates cannot be applied to the Install Base repository. Each record preserves the diagnostic context required to identify, triage, and reprocess the failed transaction, including the originating source reference, the error message text, and the affected item, serial, lot, and instance identifiers.

The table resides in the CSI schema and is classified as VALID in ETRM. Under the heuristic Data Vault classification derived from its foreign-key structure, CSI_TXN_ERRORS is satellite-leaning: it carries descriptive, non-key attributes (error text, message identifiers, control-code flags, source references) attached to the CSI_TRANSACTIONS hub through TRANSACTION_ID, rather than acting as an independent hub or pure link. This classification should be treated as a modeling suggestion for data-warehouse design rather than an intrinsic property of the OLTP table.

Key Information Stored

• TRANSACTION_ERROR_ID — surrogate primary key (CSI_TRANSACTION_ERRORS_PK) and the sole documented unique-index candidate (CSI_TXN_ERRORS_U01). It uniquely identifies each error row and is the safest join key for downstream extracts.
• TRANSACTION_ID — foreign key to CSI_TRANSACTIONS; ties the error back to the parent installed base transaction.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces multi-org / operating unit data isolation.
• ERROR_TEXT and MESSAGE_STRING — the human-readable diagnostics describing the failure.
• MESSAGE_ID — the Oracle Application Object Library message identifier, enabling lookup of the standard message definition.
• ERROR_STAGE and TRANSACTION_ERROR_DATE — the processing phase at which the failure occurred and its timestamp.
• SOURCE_TYPE, SOURCE_ID, SOURCE_GROUP_REF, SOURCE_HEADER_REF, SOURCE_LINE_REF — the originating document lineage from the source system.
• INV_MATERIAL_TRANSACTION_ID — link to the Inventory material transaction that triggered the Install Base update.
• INVENTORY_ITEM_ID, SERIAL_NUMBER, LOT_NUMBER, INSTANCE_ID — the item, serial, lot, and instance affected by the error.
• PROCESSED_FLAG — status indicator used to control reprocessing or error resolution.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and optimistic-locking columns.
• SRC_/DST_ control-code flags (serial, lot, location, revision-quantity, and COMMS_NL_TRACKABLE_FLAG) — indicate whether the source and destination organizations are serial-, lot-, location-, or revision-controlled, or network-trackable, which frequently explains validation failures.

Common Use Cases and Queries

Install Base administrators use this table to review unresolved transaction failures arising from Inventory-to-Install-Base integration, serialized item moves, and item instance status changes. Typical reporting includes error counts by message, by source document, and by aging since TRANSACTION_ERROR_DATE.

A representative diagnostic query joins the error rows back to their parent transaction and to the message definition:

• Unresolved errors: SELECT e.TRANSACTION_ERROR_ID, e.TRANSACTION_ID, e.MESSAGE_ID, e.ERROR_TEXT, e.TRANSACTION_ERROR_DATE FROM CSI.CSI_TXN_ERRORS e WHERE e.PROCESSED_FLAG = 'N' ORDER BY e.TRANSACTION_ERROR_DATE;
• Errors grouped by message: SELECT MESSAGE_ID, COUNT(*) FROM CSI.CSI_TXN_ERRORS GROUP BY MESSAGE_ID ORDER BY 2 DESC;
• Item/serial impact: restrict by INVENTORY_ITEM_ID, SERIAL_NUMBER, or LOT_NUMBER to trace a specific asset's failure history.
• Source tracing: filter on SOURCE_TYPE and SOURCE_HEADER_REF to correlate errors with a specific receiving or shipping document.

Related Objects

• CSI_TRANSACTIONS — joined via CSI_TXN_ERRORS.TRANSACTION_ID = CSI_TRANSACTIONS.TRANSACTION_ID; the parent hub record.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for row-level security context.
• FND_MESSAGES / FND_NEW_MESSAGES — resolved through MESSAGE_ID to obtain the standardized message name and text.
• MTL_MATERIAL_TRANSACTIONS — reached via INV_MATERIAL_TRANSACTION_ID to identify the triggering inventory movement.
• MTL_SYSTEM_ITEMS_B — via INVENTORY_ITEM_ID, to obtain item description and control attributes.
• CSI_ITEM_INSTANCES — via INSTANCE_ID, to examine the affected instance record and its status.
• CSI_TXN_ERRORS_PK / CSI_TXN_ERRORS_U01 — the primary key constraint and unique index that enforce identity.