Results for “csi_txn_types_u01”

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

Overview

CSI.CSI_TXN_TYPES is an Oracle E-Business Suite seed data table that stores the catalog of Installed Base Source transaction types. Each row defines a transaction type that a source application can raise against Oracle Installed Base, providing the metadata required by Installed Base to interpret, validate, and process inbound transactions originating from external or internal source systems. The table resides in the CSI (Installed Base) schema, is owned by CSI, and maps to FND Design Data object CSI.CSI_TXN_TYPES. In the documented 12.2.2 physical schema it contains 32 columns and is stored in the APPS_TS_SEED tablespace with a PCTFREE of 10, reflecting its role as a reference and setup table rather than a high-volatility transactional table.

Under the heuristic Data Vault classification derived from foreign key structure, this object is satellite-leaning. It is best modeled as a descriptive satellite attached to the source application context, since its columns carry descriptive attributes about each transaction type (names, descriptions, object codes, directional flags) rather than functioning as a pure hub or link. The unique index documented as CSI_TXN_TYPES_U01 over TRANSACTION_TYPE_ID (and ZD_EDITION_NAME in the 12.2.2 schema) reinforces this interpretation by supplying the business-key discriminator for the satellite.

Key Information Stored

The columns below represent the most functionally significant attributes of the table.

• TRANSACTION_TYPE_ID — Surrogate primary key (CSI_TXN_TYPES_PK). Uniquely identifies each Installed Base source transaction type and is the column carried by CSI_TXN_TYPES_U01.
• SOURCE_APPLICATION_ID — Foreign key to FND_APPLICATION. Identifies the application that originates the transaction.
• SOURCE_TRANSACTION_TYPE — The transaction type code as known to the source application.
• SOURCE_TXN_TYPE_NAME — The user-facing name of the source transaction type.
• DESCRIPTION — Free-text description of the transaction type.
• SOURCE_OBJECT_CODE — Holds the value of JTF_OBJECT_CODE.SOURCE_OBJECT_CODE, used to validate a source_transaction_id from the source application before Installed Base processes the transaction.
• IN_OUT_FLAG — Indicates the direction of the material movement (inbound or outbound) associated with the transaction type.
• SEEDED_FLAG — Indicates whether the transaction type is seeded by Oracle or created by the customer.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Standard descriptive flexfield columns, each VARCHAR2(150), allowing customer-defined extension of the transaction type definition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and last update context.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org security partitioning.

Common Use Cases and Queries

A frequent reporting requirement is to enumerate all transaction types registered for a given source application, joining to FND_APPLICATION for the application name.

• Listing seeded versus customer-defined types: SELECT transaction_type_id, source_txn_type_name, seeded_flag FROM csi.csi_txn_types WHERE seeded_flag = 'Y';
• Identifying inbound versus outbound material movements using IN_OUT_FLAG for inventory-impact analysis.
• Joining to CSI_TRANSACTIONS on TRANSACTION_TYPE_ID to attribute each Installed Base transaction to its originating type, which is the primary operational join path.
• Validating source object codes against JTF_OBJECT_CODE.SOURCE_OBJECT_CODE when diagnosing transaction rejection or interface errors.
• Reviewing DESCRIPTIVE flexfield values (CONTEXT and ATTRIBUTE1–15) for customer-specific categorization and downstream reporting.

Related Objects

The following objects are the most significant dependencies and reference points for CSI.CSI_TXN_TYPES.

• CSI.CSI_TRANSACTIONS — References this table via TRANSACTION_TYPE_ID, linking each Installed Base transaction to its defined type.
• FND_APPLICATION — Referenced by SOURCE_APPLICATION_ID, supplying the source application identity.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security grouping.
• JTF_OBJECT_CODE — Source of the SOURCE_OBJECT_CODE value used for validation.
• CSI.CSI_TXN_TYPES_PK — Primary key constraint on TRANSACTION_TYPE_ID.
• CSI_TXN_TYPES_U01 — Unique index on TRANSACTION_TYPE_ID (with ZD_EDITION_NAME in 12.2.2).