Search Results next_b

Overview

APPS.CSD_FLOW_STATUS_RULES_V is a reporting view within the Oracle E-Business Suite Depot Repair and Field Service foundation, exposing the configuration of flow status transitions defined for repair types. Flow status transitions govern how a repair or service order moves from one lifecycle state (for example, from "Awaiting Diagnosis" to "In Repair") and which Oracle Workflow process, if any, is invoked when that transition occurs. In the context of Oracle EBS 12.1.1 and 12.2.2, the view is a denormalized read-only presentation layer over the transactional flow-status-transition tables, resolving internal foreign keys into human-readable lookup codes and Workflow process display names.

The object surfaced by the query term "wf_proc" is the join to WF_RUNNABLE_PROCESSES_V, aliased WF_PROC. This join is what allows the view to expose the Workflow item type, process name, and the descriptive display name of the associated process, enabling report consumers to identify the workflow-driven behavior attached to each status transition without querying Workflow tables directly.

Underlying Base Objects

The view is constructed from the following documented base objects:

• CSD_FLWSTS_TRANS_B (SYNONYM) — the base table holding the transition definitions, aliased FLWSTS_B. It supplies the primary key FLWSTS_TRAN_ID, the from/to status identifiers, repair type, workflow attributes, and the descriptive flags described below.
• CSD_FLWSTS_TRANS_TL (SYNONYM) — the translation table, aliased FLWSTS_TL, joined on FLWSTS_TRAN_ID and restricted to the session language via USERENV('LANG'). It supplies DESCRIPTION.
• CSD_FLOW_STATUSES_B (SYNONYM) — referenced twice as CURR_B and NEXT_B to resolve the from and to flow status rows from their identifiers.
• FND_LOOKUPS (VIEW) — referenced twice as CURR_STS_LKUP and NEXT_STS_LKUP, restricted to LOOKUP_TYPE = 'CSD_REPAIR_FLOW_STATUS', to translate status codes into MEANING values.
• WF_RUNNABLE_PROCESSES_V (VIEW) — aliased WF_PROC, joined with outer-join syntax on item_type and process_name, providing the Workflow process DISPLAY_NAME.
• FND_GLOBAL (PACKAGE) — invoked implicitly through USERENV('LANG') to determine the current language.

Key Columns

• FLWSTS_TRAN_ID — primary identifier of the transition rule.
• REPAIR_TYPE_ID — the repair type to which the transition applies.
• CURRENT_FLOW_STATUS_ID / CURRENT_FLOW_STATUS_CODE / CURRENT_FLOW_STATUS — the originating status, exposing both the internal code and the lookup meaning.
• NEXT_FLOW_STATUS_ID / NEXT_FLOW_STATUS_CODE / NEXT_FLOW_STATUS — the destination status and its descriptive meaning.
• WF_ITEM_TYPE / WF_PROCESS_NAME / WF_DISPLAY_NAME — the Oracle Workflow item type, process name, and human-readable display name invoked on transition. WF_DISPLAY_NAME is null when no workflow is attached.
• REASON_REQUIRED_FLAG — indicates whether a reason code must be captured when the transition executes.
• CAPTURE_ACTIVITY_FLAG — indicates whether activity/resource capture is enforced on transition.
• DESCRIPTION — translated descriptive text from the TL table.
• ALLOW_ALL_RESP_FLAG — indicates whether all responsibilities are permitted to perform the transition.
• OBJECT_VERSION_NUMBER — optimistic locking column inherited from the base table.

Common Use Cases and Queries

The view is typically used to document, audit, or report on repair flow configuration, and to confirm which Workflow processes are bound to specific transitions. A representative query listing all transitions for a repair type follows:

• SELECT CURRENT_FLOW_STATUS, NEXT_FLOW_STATUS, WF_ITEM_TYPE, WF_PROCESS_NAME, WF_DISPLAY_NAME, REASON_REQUIRED_FLAG FROM APPS.CSD_FLOW_STATUS_RULES_V WHERE REPAIR_TYPE_ID = :p_repair_type_id ORDER BY CURRENT_FLOW_STATUS, NEXT_FLOW_STATUS;

To identify transitions that invoke a Workflow process, filter on a populated display name: SELECT * FROM APPS.CSD_FLOW_STATUS_RULES_V WHERE WF_DISPLAY_NAME IS NOT NULL;. To verify rules requiring a reason code, restrict by REASON_REQUIRED_FLAG = 'Y'. Because the view relies on FND_LOOKUPS and the translation table, results reflect the language of the session and current lookup meanings, making it suitable for both ad-hoc diagnostics and embedded reporting across 12.1.1 and 12.2.2 instances.