Results for “trasaction_date”

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

Overview

APPS.CSI_SYSTEMS_TRANSACTIONS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that joins transaction-level records from CSI_TRANSACTIONS with the system-instance (instance/asset) definition tables CSI_SYSTEMS_B, CSI_SYSTEMS_H, and CSI_SYSTEMS_TL. It is part of the Enterprise Asset Management / Complex Maintenance, Repair, and Overhaul (CSI) schema, which tracks the lifecycle, configuration, and transactional history of systems and their components. The view exposes a single flattened record per system-transaction relationship, combining core transaction attributes with descriptive system metadata and the name of the last user who updated the row. Because it is deployed as an APPS synonym-backed view, it is accessible to custom reports, concurrent programs, and downstream integrations without requiring direct grants on the underlying base tables.

Underlying Base Objects

The view is defined over five documented base objects (all referenced through APPS synonyms): CSI_TRANSACTIONS, CSI_SYSTEMS_B, CSI_SYSTEMS_H, CSI_SYSTEMS_TL, and FND_USER. CSI_TRANSACTIONS is the driving transactional table, supplying transaction identifiers, dates, quantity, status, and descriptive flexfield (DFF) attributes. CSI_SYSTEMS_B holds the base system definitions, while CSI_SYSTEMS_TL holds translated system names and descriptions keyed by language, and CSI_SYSTEMS_H holds the historical/system-association rows linking a system to a transaction. FND_USER provides the application user name for audit purposes. The join conditions are: T.TRANSACTION_ID = H.TRANSACTION_ID, H.SYSTEM_ID = TL.SYSTEM_ID, TL.SYSTEM_ID = B.SYSTEM_ID, FND.USER_ID = T.LAST_UPDATED_BY, and TL.LANGUAGE = USERENV('LANG') for language-restricted retrieval.

Key Columns

• TRANSACTION_ID / TRASACTION_DATE — The primary transaction identifier and the transaction date. Note the documented view aliases the date column as TRASACTION_DATE (a spelling variance in the view definition); users searching for "transaction_date" should query this alias.
• SOURCE_TRANSACTION_DATE — The date the source transaction originated in the originating system.
• TRANSACTION_TYPE_ID / TXN_SUB_TYPE_ID — Classify the transaction and its subtype.
• SOURCE_GROUP_REF / SOURCE_HEADER_REF / SOURCE_LINE_REF / SOURCE_DIST_REF_ID1 / SOURCE_DIST_REF_ID2 — Source-system reference keys tracing back to the originating document, line, and distribution.
• INV_MATERIAL_TRANSACTION_ID — Links to the Inventory material transaction when applicable.
• TRANSACTION_QUANTITY / TRANSACTION_UOM_CODE — Quantity transacted and its unit of measure.
• TRANSACTION_STATUS_CODE / TRANSACTION_ACTION_CODE / TRANSACTED_BY — Status, action, and the originating actor of the transaction.
• SYSTEM_ID / NAME / SYSTEM_NUMBER / SYSTEM_DESCRIPTION — System-instance identity and localized description.
• TXN_USER_NAME — The FND_USER user name of the last updater.
• ATTRIBUTE1–15 / CONTEXT — Descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard audit and optimistic-locking columns.

Common Use Cases and Queries

Typical uses include system transaction history reports, asset movement audits, and integration extracts that must surface both transaction detail and human-readable system names. A frequent query pattern filters on the transaction date alias:

SELECT transaction_id, trasaction_date, system_number, name, transaction_quantity, transaction_uom_code, transaction_status_code FROM apps.csi_systems_transactions_v WHERE trasaction_date BETWEEN :p_from AND :p_to;

Another common requirement joins to additional CSI detail tables or filters by system to produce a per-instance activity ledger, or uses TXN_USER_NAME for audit trails. Because the view enforces TL.LANGUAGE = USERENV('LANG'), returned NAME and SYSTEM_DESCRIPTION values are language-specific to the session's environment, which should be considered when exporting data across locales.