Results for “qty_remaining”

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

Overview

CSI_T_TXN_LINE_DETAILS is a transaction-staging table within the CSI (Install Base) product family in Oracle E-Business Suite, holding line-level detail records generated during Install Base transaction processing in releases 12.1.1 and 12.2.2. Each row describes a single instance-related line submitted to the Install Base transaction engine, capturing the state of an item instance as it existed before, and as it will exist after, a transaction is applied. The table is populated by the transaction interface programs that accept feeds from Order Management, Inventory, Service, and external sources, and is consumed by the Install Base transaction processor to create, update, or terminate instance records.

From a modeling perspective, the documented foreign-key topology and the presence of a single-column surrogate primary key suggest classifying this object as hub-leaning. It acts as a stable identity anchor for a transaction line detail, with subsidiary attribute structures (extended attributes, party details, and organization assignments) attached through dependent tables. This classification is a heuristic suggestion derived from the foreign-key structure rather than an enforced constraint.

Key Information Stored

The table contains 81 documented columns, of which the following are most significant for functional and integration analysis:

• TXN_LINE_DETAIL_ID — surrogate primary key (CSI_T_TXN_LINE_DETAILS_PK) and also the sole unique index, CSI_T_TXN_LINE_DETAILS_U01. This is the column referenced by all dependent child tables.
• TRANSACTION_LINE_ID — foreign key to CSI_T_TRANSACTION_LINES, identifying the parent transaction line to which the detail belongs.
• INSTANCE_ID and CHANGED_INSTANCE_ID — foreign keys to CSI_ITEM_INSTANCES; the former identifies the instance being processed, the latter the successor instance when a change or replacement occurs.
• CSI_SYSTEM_ID and TRANSACTION_SYSTEM_ID — references to CSI_SYSTEMS_B and CSI_T_TXN_SYSTEMS respectively, defining the system context of the transaction.
• INVENTORY_ITEM_ID, INV_ORGANIZATION_ID, INVENTORY_REVISION — the item and revision being transacted.
• SERIAL_NUMBER and LOT_NUMBER — instance-level identifiers for serialized and lot-controlled items.
• QUANTITY, UNIT_OF_MEASURE, QTY_REMAINING — quantity detail supporting partial and split transactions.
• PROCESSING_STATUS, ERROR_CODE, and ERROR_EXPLANATION — execution state and diagnostics produced by the transaction processor.
• SUB_TYPE_ID and INSTANCE_STATUS_ID — foreign keys to CSI_IB_TXN_TYPES and CSI_INSTANCE_STATUSES, classifying the transaction subtype and target instance status.
• LOCATION_TYPE_CODE, LOCATION_ID, INSTALL_LOCATION_TYPE_CODE, INSTALL_LOCATION_ID — where the instance resides or is being installed.
• INSTALLATION_DATE and IN_SERVICE_DATE — lifecycle dates carried into the resulting instance record.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing row-level access.
• SOURCE_TXN_LINE_DETAIL_ID and CASCADE_OWNER_FLAG — self-referencing lineage and cascade ownership control.

Common Use Cases and Queries

The most frequent operational use is diagnosing failed Install Base transactions by inspecting processing status and error content:

• SELECT txn_line_detail_id, transaction_line_id, processing_status, error_code, error_explanation FROM csi_t_txn_line_details WHERE processing_status = 'ERROR';
• Joining to the parent transaction line to reconcile staged detail against the originating transaction: SELECT d.* FROM csi_t_txn_line_details d, csi_t_transaction_lines l WHERE d.transaction_line_id = l.transaction_line_id;
• Reporting instance-level movement by joining INSTANCE_ID to CSI_ITEM_INSTANCES for current instance attributes.
• Auditing source feeds from Order Management via XDP_ORDER_LINE_ITEMS.IB_SOURCE_ID to confirm that order lines reached the Install Base interface.
• Extracting extended attribute values through CSI_T_EXTEND_ATTRIBS keyed on TXN_LINE_DETAIL_ID for custom reporting.

Related Objects

Key related objects and join columns include:

• CSI_T_TRANSACTION_LINES — parent header/line entity via TRANSACTION_LINE_ID.
• CSI_ITEM_INSTANCES — instance being processed, via INSTANCE_ID and CHANGED_INSTANCE_ID.
• CSI_T_EXTEND_ATTRIBS — descriptive flexfield values via TXN_LINE_DETAIL_ID.
• CSI_T_II_RELATIONSHIPS — instance-to-instance relationships via SUBJECT_ID and OBJECT_ID.
• CSI_T_ORG_ASSIGNMENTS and CSI_T_PARTY_DETAILS — organization and party context via TXN_LINE_DETAIL_ID.
• CSI_T_TXN_SYSTEMS, CSI_SYSTEMS_B, CSI_IB_TXN_TYPES, and CSI_INSTANCE_STATUSES — classification and system references.
• XDP_ORDER_LINE_ITEMS — Order Management source lineage via IB_SOURCE_ID.