Results for “cs_bus_process_txns_v”

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

Overview

The APPS.CS_BUS_PROCESS_TXNS_V view belongs to the Oracle Service (CS) product family and is documented in the ETRM repository as a "View to show transaction groups." It presents the association between business processes and the transaction types that those processes operate upon, exposing the relationship as a single denormalized result set suitable for reporting, concurrent program lookups, and integration extracts. Because the view resolves the numeric TRANSACTION_TYPE_ID into the human-readable transaction type name, it removes the need for downstream consumers to perform their own join against the transaction type setup table. The object is owned by the APPS schema and is marked VALID in both the 12.1.1 and 12.2.2 releases. In 12.1.1 the underlying business process transaction data is stored in a user-named synonym, while in 12.2.2 the documented base objects are exposed as synonyms CS_BUS_PROCESS_TXNS and CS_TRANSACTION_TYPES. This naming difference reflects the standard EBS convention in which runtime objects are frequently referenced through private or public synonyms rather than by an explicit customer or product schema qualifier.

Underlying Base Objects

The view text is defined over two base objects joined on the transaction type identifier:

• CS_BUS_PROCESS_TXNS — the driving table, aliased BPT in the view definition. It stores one row per business process / transaction type combination and carries the descriptive flexfield columns (ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT) together with the standard WHO audit columns and the effective dating columns START_DATE_ACTIVE and END_DATE_ACTIVE.
• CS_TRANSACTION_TYPES — the transaction type setup table, aliased TT. Its NAME column supplies the TRANSACTION_TYPE value that is surfaced by the view.

The join predicate is BPT.TRANSACTION_TYPE_ID = TT.TRANSACTION_TYPE_ID. The ROWID of CS_BUS_PROCESS_TXNS is projected as ROW_ID, which allows callers to identify the underlying row for updates or diagnostics. The view is read-only in practice; inserts and updates must be directed at the base table.

Key Columns

• ROW_ID — ROWID of the CS_BUS_PROCESS_TXNS row, useful for row-level identification.
• BUSINESS_PROCESS_ID — identifier of the business process that the transaction type is linked to.
• TRANSACTION_TYPE_ID — the numeric foreign key to the transaction type definition.
• TRANSACTION_TYPE — the transaction type name resolved from CS_TRANSACTION_TYPES.NAME; this is the column most commonly used in user-facing queries and is the target of searches for "transaction_type."
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating bounds that determine whether the association is currently active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the descriptive flexfield segments for the business process transaction assignment.

Common Use Cases and Queries

Typical usage includes validating which transaction types are attached to a given business process, feeding service request or depot repair configuration reports, and driving concurrent program parameters that accept a transaction type. A representative query listing active associations is:

SELECT business_process_id,
       transaction_type_id,
       transaction_type
FROM   apps.cs_bus_process_txns_v
WHERE  SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                   AND NVL(end_date_active, SYSDATE);

To locate the business processes linked to a specific transaction type name:

SELECT business_process_id, transaction_type
FROM   apps.cs_bus_process_txns_v
WHERE  transaction_type = :p_transaction_type;

Because the view performs the name resolution internally, it is preferable to querying CS_BUS_PROCESS_TXNS and CS_TRANSACTION_TYPES separately when the transaction type name is the only descriptive attribute required. Callers should account for the possibility that a business process transaction row exists without a matching transaction type definition, in which case the inner join will suppress the row.