Results for “jtf_dpf_logical_flows_vl”

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

Overview

JTF_DPF_LOGICAL_FLOWS_VL is a translated (VL) view owned by the APPS schema within the JTF – CRM Foundation product family. It presents logical flow definitions used by the Oracle E-Business Suite, particularly within CRM and self-service configuration areas that rely on the DPF (Dynamic Page Flow) framework. Logical flows describe the ordered set of pages or steps that a user navigates through during a guided business process, and this view exposes both the operational attributes of each flow (stored in the _B base table) and the language-specific descriptive text (stored in the _TL translation table).

The view is marked VALID in the ETRM documentation for both 12.1.1 and 12.2.2, and its structure is consistent across those releases. Because it joins language-specific data with operational data and filters by the session language, it is the preferred source for user-facing reporting and integration queries that require readable flow descriptions rather than opaque identifiers. In reporting contexts it functions as a convenient single source for flow metadata, eliminating the need for report authors to manually join the base and translation tables.

Underlying Base Objects

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

• JTF_DPF_LOGICAL_FLOWS_B — the base table holding non-translatable attributes of each logical flow, including identifiers, flags, and audit columns.
• JTF_DPF_LOGICAL_FLOWS_TL — the translation table holding language-specific descriptive text.

The join condition is B.LOGICAL_FLOW_ID = T.LOGICAL_FLOW_ID AND T.LANGUAGE = USERENV('LANG'). The B alias supplies the operational columns plus ROWID as ROW_ID; the T alias supplies LOGICAL_FLOW_DESCRIPTION. Because the join is constrained by USERENV('LANG'), the view returns only one translation row per logical flow — the one matching the current session language. Environments that have not defined a translation for that language will not return a description for the affected flow.

Key Columns

• ROW_ID — the ROWID of the underlying base-table row.
• LOGICAL_FLOW_ID — the primary identifier of the logical flow.
• LOGICAL_FLOW_HEAD_ID — references the parent/header flow grouping.
• LOGICAL_FLOW_NAME — the internal name of the flow.
• SECURE_FLOW_FLAG — indicates whether the flow is treated as secured.
• VALIDATE_FLAG — the flag referenced by the user's search; controls whether validation logic is applied to the flow. It is a commonly queried control attribute for auditing and configuration reporting.
• APPLICATION_ID — the owning application, joinable to FND_APPLICATION.
• FLOW_FINALIZER_CLASS — the Java class invoked to finalize the flow.
• RETURN_TO_PAGE_ID — the page to which control returns on completion.
• BASE_FLOW_FLAG / ENABLED_CLONE_FLAG — indicators for base and clone-enabled flows.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• LOGICAL_FLOW_DESCRIPTION — the language-specific description from the _TL table.

Common Use Cases and Queries

Typical uses include validating flow configuration, auditing validation and security flags, and producing language-aware lists of flows for administrators or integration interface definitions. A representative query for flows where validation is enabled:

• SELECT logical_flow_name, logical_flow_description, application_id, validate_flag FROM jtf_dpf_logical_flows_vl WHERE validate_flag = 'Y' ORDER BY logical_flow_name;
• SELECT l.logical_flow_name, a.application_name, l.validate_flag FROM jtf_dpf_logical_flows_vl l, fnd_application_vl a WHERE l.application_id = a.application_id;
• SELECT logical_flow_id, logical_flow_name, secure_flow_flag, enabled_clone_flag FROM jtf_dpf_logical_flows_vl WHERE base_flow_flag = 'Y';

Because the view is read-only and language-filtered, it is safe for concurrent reporting use but should not be used for DML. Reports intended for multilingual audiences should account for the session-language filter.