Search Results installed_status_code




Overview
Explore in AI Chat

Overview

The CS_TRANSACTION_TYPES_VL view in the APPS schema is a single-language (VL) presentation view belonging to the Oracle E-Business Suite Service (CS) product family. It exists to provide a translated, user-facing representation of service transaction type definitions while keeping language-independent attributes stored in the underlying base table. The view is defined as a join between the base table CS_TRANSACTION_TYPES_B and the translation table CS_TRANSACTION_TYPES_TL, exposing all business columns from the base table alongside the translated NAME and DESCRIPTION columns from the translation table. The join is filtered by T.LANGUAGE = USERENV('LANG'), so only the rows matching the session language are returned.

In Oracle EBS 12.1.1 and 12.2.2 this view functions as the canonical read interface for service transaction type metadata used by forms, concurrent programs, and reporting. The status of the object is VALID in the documented metadata, confirming it is a supported and compiled APPS object.

Underlying Base Objects

The documented referenced base objects are CS_TRANSACTION_TYPES_B (SYNONYM) and CS_TRANSACTION_TYPES_TL (SYNONYM). The _B table stores the language-independent attributes of each transaction type, keyed by TRANSACTION_TYPE_ID, and includes audit columns, flags such as SEEDED_FLAG, REVISION_FLAG, MOVE_COUNTERS_FLAG, NO_CHARGE_FLAG, and DEPOT_REPAIR_FLAG, plus the descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT. The _TL table stores the translated NAME and DESCRIPTION text by language. The view joins these two tables on TRANSACTION_TYPE_ID and restricts the translation side by the current session language, producing one row per transaction type per session language.

Key Columns

Common Use Cases and Queries

Typical usage includes identifying the status applied to installed counters, driving order-entry interfaces, and populating service transaction LOVs. A representative query filtering on the searched column:

  • SELECT transaction_type_id, name, installed_cp_status_id, installed_status_code FROM cs_transaction_types_vl WHERE installed_cp_status_id IS NOT NULL;
  • Joining to CS_CP_STATUSES via INSTALLED_CP_STATUS_ID to resolve a human-readable status name.
  • Driving LOV validation in service forms by selecting name and transaction_type_id for the current language.

Because the view enforces USERENV('LANG'), queries always return translated text appropriate to the runtime session, which is essential for multilingual reporting and integration.