Results for “csi_i_asset_txn_temp”

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

Overview

CSI_I_ASSET_TXN_TEMP is a temporary staging table owned by the CSI schema within the Oracle E-Business Suite Install Base module. As its name and description indicate, it holds Asset transactions on a transient basis: records are written to this table during processing and subsequently consumed, validated, or purged. In the ETRM 12.2.2 physical schema, the object contains 29 documented columns and carries a status of VALID.

The table functions as the intermediate persistence layer for asset-related transaction intake. Downstream processes read from the staged rows to create or update Install Base instances and supporting entity records. Because the data is retained only temporarily, the table should be treated as a processing artifact rather than a system of record.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. From a modeling perspective, this suggests the object is best understood as neither a hub nor a link in a dimensional sense, but rather a transient landing structure. Any historical retention or analytical use should be preceded by explicit staging into a durable target.

Key Information Stored

The primary key is CSI_I_ASSET_TXN_TEMP_PK, defined on TRANSACTION_ID. A separate unique index, CSI_I_ASSET_TXN_TEMP_U01, is defined on the combination of TRANSACTION_ID and INSTANCE_ID, making this pair the documented business-key candidate. Because the table stages both new-asset creation and updates to existing assets, INSTANCE_ID distinguishes which Install Base instance the transaction affects.

The most operationally significant columns include:

• TRANSACTION_ID — surrogate primary key and transaction identifier.
• INSTANCE_ID — the Install Base instance against which the transaction is applied.
• TRANSACTION_STATUS — processing state used to drive downstream consumption.
• TRANSACTION_QUANTITY — quantity affected by the transaction.
• SERIAL_NUMBER and TAG_NUMBER — identifying attributes of the asset.
• ASSET_DESCRIPTION, MANUFACTURER_NAME, and MODEL_NUMBER — descriptive asset attributes.
• ASSET_CATEGORY_ID and BOOK_TYPE_CODE — categorization and depreciation book context.
• ASSET_KEY_CCID, PAYABLES_CCID, and DEPRN_EXPENSE_CCID — accounting flexfield references.
• ASSET_LOCATION_ID, EMPLOYEE_ID, and SECURITY_GROUP_ID — location, personnel, and security context.
• PROJECT_ID and TASK_ID — project and task associations.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Typical activity centers on monitoring staging backlog and verifying transaction completion. Counting rows by status is a frequent operational check:

SELECT TRANSACTION_STATUS, COUNT(*) 
FROM   CSI.CSI_I_ASSET_TXN_TEMP 
GROUP BY TRANSACTION_STATUS;

Joining the staging rows to the instance and location context supports reconciliation of inbound asset transactions:

SELECT t.TRANSACTION_ID, t.INSTANCE_ID, t.SERIAL_NUMBER, 
       t.ASSET_LOCATION_ID, t.TRANSACTION_STATUS
FROM   CSI.CSI_I_ASSET_TXN_TEMP t
WHERE  t.TRANSACTION_STATUS = 'PENDING';

Reporting use cases include reconciling asset cost and categorization fields against the Install Base, validating accounting flexfield references prior to posting, and auditing security group assignment across transactional batches.

Related Objects

The documented foreign keys establish the principal relationships:

• CSI_A_LOCATIONS via ASSET_LOCATION_ID — resolves the asset location.
• PSB_EMPLOYEES via EMPLOYEE_ID — resolves the assigned employee.
• FND_SECURITY_GROUPS via SECURITY_GROUP_ID — enforces row-level security.

Beyond these, the INSTANCE_ID column logically relates to the Install Base instance tables, and downstream Install Base processing APIs consume the staged rows to create or update asset instances. Analytics against this table should always be treated as point-in-time, given its temporary nature.