Results for “cs_bus_process_txns”

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

Overview

CS_BUS_PROCESS_TXNS is a Service (CS) module intersection table that defines the association between business processes and the transaction types they operate upon. In Oracle EBS 12.1.1 and 12.2.2, business processes such as return, repair, or exchange flows are configured to accept a defined set of transaction types; this table records which transaction types are valid for each business process. It therefore functions as setup or reference data that drives service transaction processing and validation logic within the Service module.

From a Data Vault modeling perspective, the mined metadata suggests classifying CS_BUS_PROCESS_TXNS as a link table. It carries no descriptive business attributes of its own beyond control columns; instead it resolves a many-to-many relationship between two independent entities, CS_BUSINESS_PROCESSES and CS_TRANSACTION_TYPES_B. The composite nature of its primary key reinforces this interpretation.

Key Information Stored

The table is physically owned by the CS schema and, in the documented 12.2.2 schema, contains 26 columns. The most significant of these are:

• BUSINESS_PROCESS_ID — Foreign key to CS_BUSINESS_PROCESSES; identifies the parent business process.
• TRANSACTION_TYPE_ID — Foreign key to CS_TRANSACTION_TYPES_B; identifies the transaction type associated with the process.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating columns that delimit when the association is active, enabling date-effective setup.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, supporting multi-organization / security-group data partitioning.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO audit columns tracking record provenance.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — The standard DFF (Descriptive Flexfield) column set for customer-defined extensions.

The surrogate/primary key is defined by CS_BUS_PROCESS_TXNS_PK, spanning (BUSINESS_PROCESS_ID, TRANSACTION_TYPE_ID). A unique index, CS_BUS_PROCESS_TXNS_U1, exists on the same column pair, confirming that this combination is the documented business-key candidate ensuring one association per process/transaction-type pair.

Common Use Cases and Queries

Typical usage centers on service setup validation and reporting. Consultants and developers query this table to determine which transaction types are permitted for a given business process, and to reconcile configuration during migrations from 12.1.1 to 12.2.2.

• Listing active transaction types for a business process:

  SELECT bpt.transaction_type_id, tt.name
  FROM   cs_bus_process_txns bpt,
         cs_transaction_types_b tt
  WHERE  bpt.transaction_type_id = tt.transaction_type_id
  AND    bpt.business_process_id = :process_id
  AND    TRUNC(SYSDATE) BETWEEN NVL(bpt.start_date_active, TRUNC(SYSDATE))
       AND NVL(bpt.end_date_active, TRUNC(SYSDATE));

• Auditing configuration changes via the WHO columns (created_by, last_update_date).
• Validating that no orphaned transaction types exist by outer-joining to CS_TRANSACTION_TYPES_B.
• Cross-checking security-group partitioning of setup data.

Related Objects

• CS_BUSINESS_PROCESSES — joined on BUSINESS_PROCESS_ID; the parent business process definition.
• CS_TRANSACTION_TYPES_B — joined on TRANSACTION_TYPE_ID; the base transaction type definition.
• CS_TRANSACTION_TYPES_TL — provides translated names for transaction types referenced here.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for security partitioning.
• CS_INCIDENTS_ALL and related service request tables that consume the process/transaction-type associations during transaction creation and validation.

The FK relationships to CS_TRANSACTION_TYPES_B and CS_BUSINESS_PROCESSES, together with the unique index on the composite key, make this table a reliable join point for any query that must correlate business process configuration with transaction type definitions.