Results for “oke_fldmx_termcond_rtree_v”

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

Overview

The OKE_FLDMX_TERMCOND_RTREE_V view is an Oracle Application Object Library (APPS) database object in the Oracle E-Business Suite (EBS) OKE – Project Contracts module. According to the documented metadata (ETRM 12.2.2), the view returns the term types that have been assigned to a business area within the flowdown matrix. It serves as a reporting and integration layer over the flowdown configuration maintained in Project Contracts, exposing the hierarchical relationship between business areas and the standard term types that apply to them.

Because the view is owned by APPS and reports a status of VALID in both the 12.1.1 and 12.2.2 contexts, it is safe for use in custom SQL reports, concurrent programs, and integration queries that need to inspect flowdown assignments. Its principal value lies in presenting flowdown data in a flattened, display-ready format rather than requiring custom joins across the underlying business area, term type, and flowdown objects.

Underlying Base Objects

The documented view text defines OKE_FLDMX_TERMCOND_RTREE_V as a UNION over two sets of rows. The first branch sources business-area header information, while the second sources the term-type detail records. The documented referenced base objects are:

• OKE_BUSINESS_AREAS_V (VIEW) – Supplies the BUSINESS_AREA_NAME and BUSINESS_AREA_CODE values used in both the header and detail branches.
• OKE_FLOWDOWNS (SYNONYM) – Provides the flowdown assignment records linking a TERM_TYPE_CODE to a BUSINESS_AREA_CODE (aliased as TF in the view text; the detail branch references OKE_TERMCOND_FLOWDOWNS).
• OKE_TERM_TYPES_V (VIEW) – Provides the TERM_TYPE_NAME corresponding to each TERM_TYPE_CODE (aliased as TT).

The union structure produces two logical record types: header rows flagged as BIZAREA and detail rows flagged as TERMCOND. This shape supports tree-style (RTREE) rendering of the flowdown matrix, where each business area acts as a parent node and the assigned term types appear as child nodes.

Key Columns

The view exposes the following documented columns:

• CTX – Record context/type identifier. Contains the literal 'BIZAREA' for business-area rows and 'TERMCOND' for term-type rows.
• INIT_STAT – Initial expansion or status indicator for the tree node (-1 for business-area rows, 0 for term-condition rows).
• DEPTH – Node depth within the tree hierarchy (1 for business areas, 2 for term types).
• LABEL – Display label for the node. For business areas this is BUSINESS_AREA_NAME; for term types it is TERM_TYPE_NAME.
• DATA – The underlying key value. For business areas this is BUSINESS_AREA_CODE; for term types it is a concatenation of the padded business area code and term type code.
• SORT_KEY – Sort value used to order the tree. For term-type rows it is a padded concatenation of BUSINESS_AREA_NAME and TERM_TYPE_NAME.

The residual columns in the view text (the numeric literals such as 1, 2, -1, and 0) map to these positional attributes and are used to control tree rendering and ordering. The reported BUSINESS_AREA_NAME column is available directly from OKE_BUSINESS_AREAS_V, which is why the user search term business_area_name resolves against this view.

Common Use Cases and Queries

Typical uses include auditing which term types have been flowed down to a specific business area, building the flowdown matrix tree in a custom UI or report, and validating configuration completeness during implementation or upgrade testing.

Sample query to list term types assigned to every business area:

• SELECT CTX, DEPTH, LABEL, DATA, SORT_KEY FROM APPS.OKE_FLDMX_TERMCOND_RTREE_V ORDER BY SORT_KEY;

To restrict output to a particular business area, filter on the DATA value or on the LABEL column:

• SELECT LABEL, DATA FROM APPS.OKE_FLDMX_TERMCOND_RTREE_V WHERE CTX = 'TERMCOND' AND DATA LIKE '<BUSINESS_AREA_CODE>%' ORDER BY LABEL;
• SELECT LABEL FROM APPS.OKE_FLDMX_TERMCOND_RTREE_V WHERE CTX = 'BIZAREA';

Because the view joins OKE_TERMCOND_FLOWDOWNS, OKE_TERM_TYPES_V, and OKE_BUSINESS_AREAS_V internally, ad-hoc queries can retrieve flowdown assignments without reconstructing those joins manually. When using the view in custom code, restrict access by the appropriate business-area or responsibility context to avoid leaking configuration across operating units.

Note that the documentation references OKE_FLOWDOWNS as a synonym alongside OKE_TERMCOND_FLOWDOWNS in the view text; both refer to the same underlying flowdown data in the OKE schema. For 12.1.1 and 12.2.2, the view is valid and can be relied upon for read-only reporting, but it should not be updated directly, as it is a non-updatable union view.