Results for “common_flow_status_code”

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

Overview

CSD_REPAIR_TYPE_RULES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the Depot Repair (CSD) product family. It exposes the repair type transition rules that govern how an item moves from one repair type to another, together with the common flow status associated with each rule. In effect, the view presents the configuration that determines the valid transitions of a repair through the Depot Repair workflow.

Because the view denormalizes the underlying transactional and translation tables into a single row per rule, it is well suited to reporting, concurrent program data sources, Oracle Reports, BI Publisher datasets, and interface/API lookups. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and references the FND_GLOBAL package (via USERENV) and the FND_LOOKUPS view to obtain the language-specific and lookup-code descriptions for each row.

The column searched by the user, ALLOW_ALL_RESP_FLAG, is a rule-level indicator that controls whether all responsibilities may effect the transition, as opposed to a restricted set. This makes the view central to security and responsibility scoping of repair type transitions.

Underlying Base Objects

The view is defined over the following documented base objects:

• CSD_RT_TRANS_B (synonym) — the repair type transition base table, holding FROM_REPAIR_TYPE_ID, TO_REPAIR_TYPE_ID, COMMON_FLOW_STATUS_ID, REASON_REQUIRED_FLAG, CAPTURE_ACTIVITY_FLAG, ALLOW_ALL_RESP_FLAG and OBJECT_VERSION_NUMBER.
• CSD_RT_TRANS_TL (synonym) — the transition translation table, supplying the DESCRIPTION in the user's session language.
• CSD_REPAIR_TYPES_TL (synonym) — the repair type translation table, providing the TO_REPAIR_TYPE name.
• CSD_FLOW_STATUSES_B (synonym) — the flow status base table, joined to obtain the status code.
• FND_LOOKUPS (view) — supplies the MEANING (COMMON_FLOW_STATUS) for the lookup code under lookup type CSD_REPAIR_FLOW_STATUS.
• FND_GLOBAL (package) — used indirectly through USERENV('LANG') to filter translation rows to the session language.

All joins are inner joins on the translation IDs and language, so a row appears only when a matching translation exists for the current session language.

Key Columns

• RT_TRAN_ID — primary key of the transition rule.
• FROM_REPAIR_TYPE_ID / TO_REPAIR_TYPE_ID — the source and destination repair type identifiers.
• TO_REPAIR_TYPE — the language-specific name of the destination repair type.
• COMMON_FLOW_STATUS_ID / COMMON_FLOW_STATUS_CODE / COMMON_FLOW_STATUS — the flow status identifier, its lookup code, and its translated meaning.
• REASON_REQUIRED_FLAG — indicates whether a reason must be captured for the transition.
• CAPTURE_ACTIVITY_FLAG — indicates whether activity is captured for the transition.
• ALLOW_ALL_RESP_FLAG — indicates whether all responsibilities are permitted to perform the transition; when not set, responsibility-level restrictions apply.
• DESCRIPTION — the translated description of the transition rule.
• OBJECT_VERSION_NUMBER — optimistic locking column carried from the base table.

Common Use Cases and Queries

Typical uses include validating repair flow configuration, driving setup reports, and building responsibility-aware transition lists in extensions or integrations.

• List all transition rules with their status and flags.
• Return only rules open to every responsibility, by testing ALLOW_ALL_RESP_FLAG.
• Find the valid next repair types from a given source type.

Sample SQL:

SELECT rt_tran_id,
       from_repair_type_id,
       to_repair_type,
       common_flow_status,
       reason_required_flag,
       capture_activity_flag,
       allow_all_resp_flag
  FROM apps.csd_repair_type_rules_v
 WHERE allow_all_resp_flag = 'Y'
 ORDER BY to_repair_type;

SELECT to_repair_type, common_flow_status
  FROM apps.csd_repair_type_rules_v
 WHERE from_repair_type_id = :p_from_type_id;

Because the view depends on translation joins and USERENV('LANG'), queries should be run in a session where the language is set appropriately; otherwise rows with missing translations may not appear.