Search Results fs_lkup




Overview
Explore in AI Chat

Overview

APPS.CSD_REPAIR_TYPES_VL is a multilingual (VL, "view with language") reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents repair type definitions used by the Depot Repair and Oracle Service modules, combining the base table CSD_REPAIR_TYPES_B with its translation table CSD_REPAIR_TYPES_TL so that descriptive text (name, description) is returned in the session's current language (userenv('LANG')). The view also enriches each repair type with workflow item type display names, flow status lookup values, and a wide set of billing-related foreign key columns.

The view is primarily consumed by forms, concurrent programs, and custom reports that need a single, translated row per repair type, including the workflow and flow status context required to drive repair order processing. Because it is a VL view, developers should treat it as a read-only interface over the underlying base and translation tables.

Underlying Base Objects

The view is defined over the following documented objects:

  • CSD_REPAIR_TYPES_B – the base (non-translated) repair type definition, providing all technical attributes, flags, and the start_flow_status_id.
  • CSD_REPAIR_TYPES_TL – the translation table supplying NAME and DESCRIPTION filtered by session language.
  • WF_ITEM_TYPES_VL – outer-joined to resolve workflow_item_type into a display_name.
  • CSD_FLOW_STATUSES_B – outer-joined on flow_status_id to obtain the flow_status_code.
  • FND_LOOKUPS – outer-joined on lookup_type = 'CSD_REPAIR_FLOW_STATUS' to translate the flow status code into a meaning.
  • FND_GLOBAL – package supplying userenv('LANG') for the language join.

The joins are outer joins (+) on the workflow item type, flow statuses, and lookups, so a repair type is still returned even when those ancillary definitions are missing.

Key Columns

In the context of the search term start_flow_status_code, the most relevant projected columns are:

  • start_flow_status_id – the flow status identifier stored on the base repair type.
  • start_flow_status_code – the lookup code resolved via CSD_FLOW_STATUSES_B and FND_LOOKUPS.
  • start_flow_status_meaning – the descriptive meaning of that lookup code.

Other notable columns include repair_type_id (primary key), name and description (from the translation table), workflow_item_type and display_name, start_date_active and end_date_active, the DFF columns attribute_category and attribute1–attribute15, business_process_id, price_list_header_id, and the numerous billing type identifiers (cps_txn_billing_type_id, cpr_txn_billing_type_id, ls_txn_billing_type_id, lr_txn_billing_type_id, mtl_txn_billing_type_id, lbr_txn_billing_type_id, exp_txn_billing_type_id). Several operational flags are exposed: auto_process_rma, interface_to_om_flag, book_sales_order_flag, release_sales_order_flag, ship_sales_order_flag, internal_order_flag, third_party_flag, and seeded_flag.

Common Use Cases and Queries

Typical uses include listing active repair types with their initial flow status, validating workflow configuration, and joining repair type metadata to billing setup. Example query to retrieve start flow status information:

  • SELECT repair_type_id, name, start_flow_status_code, start_flow_status_meaning FROM apps.csd_repair_types_vl WHERE start_date_active <= SYSDATE AND (end_date_active IS NULL OR end_date_active >= SYSDATE);

To inspect billing and workflow configuration for a specific repair type:

  • SELECT name, workflow_item_type, display_name, business_process_id, price_list_header_id, cps_txn_billing_type_id FROM apps.csd_repair_types_vl WHERE repair_type_id = :p_repair_type_id;

Reports requiring all translated descriptions should always query the VL view rather than the _B table to guarantee language-appropriate text.