Search Results cs_transaction_types_v




Overview
Explore in AI Chat

Overview

CS_TRANSACTION_TYPES_V is a public, APPS-owned reporting view within the Oracle E-Business Suite Service (CS) module. It presents Service transaction type definitions, which are the configurable templates that govern how service transactions behave — repair, exchange, loaner, return, and similar depot or field service activity. In Release 12.1.1 and 12.2.2 the view is marked VALID and is exposed through the APPS schema for use in reporting, integration, and extension development, allowing external systems and concurrent programs to read transaction type configuration without joining the underlying base and translation tables directly.

Because the view performs the language join internally — TTL.LANGUAGE = USERENV('LANG') — it returns translated Name and Description values for the active session language. This makes it suitable for reports and interfaces that must present user-facing rather than coded values.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

  • CS_TRANSACTION_TYPES_B — the base table holding the transactional definition of each transaction type, including seeded and installed status, counter behavior, charge behavior, and descriptive flexfield attributes.
  • CS_TRANSACTION_TYPES_TL — the translation table supplying language-dependent NAME and DESCRIPTION columns.

The join is an inner equijoin on TRANSACTION_TYPE_ID between the two, filtered by the session language. The view also synthesizes the ROW_ID column from TT.ROWID and projects a set of placeholder (NULL) columns — NEW_CP_STATUS_NAME, NEW_CP_STATUS_DESC, CUSTOMER_PRODUCT_STATUS_NAME, CUSTOMER_PRODUCT_STATUS_DESC, INSTALLED_BASE — that are not populated in the base definition.

Key Columns

The columns most frequently referenced in queries and integrations include:

  • TRANSACTION_TYPE_ID — primary identifier of the transaction type; used in foreign-key joins to service transaction, order, and counter tables.
  • NAME / DESCRIPTION — translated display values sourced from CS_TRANSACTION_TYPES_TL.
  • MOVE_COUNTERS_FLAG — controls whether counters (for example, usage or meter counters) are moved when the transaction is processed; this is the flag referenced in the user's search and is a key behavioral switch for counter-driven service transactions.
  • NO_CHARGE_FLAG — indicates whether the transaction type is processed without charge.
  • DEPOT_REPAIR_FLAG — identifies transaction types used in depot repair flows.
  • REVISION_FLAG — indicates whether a revision is applied to the item during the transaction.
  • INSTALLED_STATUS_CODE and NEW_CP_STATUS_ID / NEW_CP_STATUS_CODE — define the status transition applied to the installed base and new customer product records.
  • NEW_CP_RETURN_REQUIRED / INSTALLED_CP_RETURN_REQUIRED — govern whether return of the new or installed customer product is mandatory.
  • SEEDED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE — identify Oracle-seeded rows and the effective date window.
  • LINE_ORDER_CATEGORY_CODE and INTERFACE_TO_OE_FLAG — support line-level ordering and Order Management interfacing.
  • ATTRIBUTE1–15 / CONTEXT — the descriptive flexfield segment values for the transaction type.
  • OBJECT_VERSION_NUMBER — used by the framework for optimistic locking during updates.

Common Use Cases and Queries

Typical scenarios include validating the counter-movement behavior of a transaction type, confirming which types interface to Order Management, and listing active transaction types for a picklist or concurrent report.

List active transaction types with counter movement enabled:

  • SELECT transaction_type_id, name, move_counters_flag, depot_repair_flag, no_charge_flag FROM apps.cs_transaction_types_v WHERE move_counters_flag = 'Y' AND NVL(end_date_active, SYSDATE + 1) > SYSDATE AND installed_status_code = 'I' ORDER BY name;

Identify transaction types that interface to Order Management:

  • SELECT transaction_type_id, name, line_order_category_code, interface_to_oe_flag FROM apps.cs_transaction_types_v WHERE interface_to_oe_flag = 'Y';

Because the view performs the translation join automatically, the CUSTOMER_PRODUCT_STATUS_NAME, INSTALLED_BASE, and related status description columns are not populated and should not be relied upon; the corresponding status identifiers (NEW_CP_STATUS_ID, NEW_CP_STATUS_CODE, INSTALLED_CP_STATUS_ID) should be joined to the appropriate status lookup or customer product status table instead.