Results for “src_reference_reqd”

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

Overview

The CSI_IB_TXN_TYPES table is a reference and configuration table within the Oracle Install Base (CSI) module of Oracle E-Business Suite, holding the definition of Installed Base transaction types. Each row describes how a specific category of Installed Base transaction behaves — for example, whether a source reference is mandatory, whether ownership changes are permitted, or whether status, revision, or return information must be supplied. Because the CSI module governs the lifecycle of customer assets and their relationships after shipment, this table functions as the controlling metadata layer that drives transaction validation and processing logic across the Install Base application.

The table is classified heuristically as a standalone Data Vault entity. In modeling terms, it is best treated as a reference hub or lookup table rather than a satellite or link, since most of its relationships are encoded through attribute values (flags and codes) rather than through foreign key dependencies to other transactional entities. The documented physical schema for 12.2.2 contains 28 columns, owned by the CSI schema and marked VALID.

Key Information Stored

The surrogate primary key of the table is SUB_TYPE_ID, enforced by the constraint CSI_IB_TXN_TYPES_PK. A second unique index, CSI_IB_TXN_TYPES_U02, spans SUB_TYPE_ID and ZD_EDITION_NAME, indicating that the table participates in Oracle's edition-based redefinition (EBR) model and that ZD_EDITION_NAME is part of the business key scope.

• IB_TXN_TYPE_CODE — the functional code identifying the Installed Base transaction type.
• CS_TRANSACTION_TYPE_ID — links the row to the associated transaction type identifier.
• SRC_REFERENCE_REQD, NON_SRC_REFERENCE_REQD, PARENT_REFERENCE_REQD — flags indicating whether a source, non-source, or parent reference must be provided for the transaction.
• SRC_CHANGE_OWNER, NON_SRC_CHANGE_OWNER — control whether ownership change is permitted for source and non-source transactions.
• SRC_CHANGE_OWNER_TO_CODE, NON_SRC_CHANGE_OWNER_TO_CODE — target ownership codes applied when an ownership change is allowed.
• SRC_STATUS_ID, NON_SRC_STATUS_ID, PARENT_STATUS_ID — the status values assigned to the instance for each transaction context.
• SRC_RETURN_REQD and SRC_REVISION_REQD, PARENT_REVISION_REQD — flags governing return and revision requirements.
• SEEDED_FLAG — distinguishes Oracle-delivered seed data from customer-defined entries.
• FREEZE_FLAG — indicates whether the transaction type is locked against modification.
• SECURITY_GROUP_ID — the multi-tenant security grouping, referencing FND_SECURITY_GROUPS.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and MIGRATED_FLAG.

Common Use Cases and Queries

Developers and functional consultants query this table to determine which validation rules apply to a given Installed Base transaction before processing it. A typical diagnostic query retrieves all active, non-frozen transaction types and their reference and ownership rules:

• SELECT SUB_TYPE_ID, IB_TXN_TYPE_CODE, SRC_REFERENCE_REQD, NON_SRC_REFERENCE_REQD, SRC_CHANGE_OWNER FROM CSI.CSI_IB_TXN_TYPES WHERE FREEZE_FLAG = 'N';
• Join to CSI_T_TXN_LINE_DETAILS on SUB_TYPE_ID to report which transaction subtype each actual transaction line used.
• Filter by SEEDED_FLAG = 'Y' to isolate Oracle-delivered types prior to customization review.
• Audit queries joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID to validate multi-org security partitioning, particularly in EBR-enabled environments where ZD_EDITION_NAME must also be considered.

Related Objects

The documented foreign key relationships anchor this table to two significant objects:

• FND_SECURITY_GROUPS — referenced by CSI_IB_TXN_TYPES.SECURITY_GROUP_ID, controlling row-level security assignment.
• CSI_T_TXN_LINE_DETAILS — the primary dependent table, referencing CSI_IB_TXN_TYPES through SUB_TYPE_ID; this is the interface table where transaction lines are staged and validated against the type definitions.

Because the classification is standalone with minimal outbound dependencies, administrators should treat CSI_IB_TXN_TYPES as a controlled setup entity. Direct DML should be avoided; changes are normally effected through the Install Base setup UI or concurrent programs, ensuring that edition and audit columns remain consistent across the EBR-enabled 12.2.2 environment.