Results for “oke_fldmx_document_rtree_v”

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

Overview

OKE_FLDMX_DOCUMENT_RTREE_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts product family. Its functional purpose is to present the attachment (document) categories that have been assigned to a business area within a flowdown matrix. In other words, it exposes, in a hierarchical or tree-like layout, the relationship between business areas and the document categories configured against them through the flowdown setup.

The view is a reporting and integration object rather than a transactional entity. It does not store data itself; instead it consolidates rows from the flowdown configuration and the associated business area and document category definitions, allowing inquiry screens, reports, and downstream interfaces to resolve which document categories apply to a given business area. The "RTREE" designation, combined with the CTX, DEPTH, and INIT_STAT columns, indicates that the view is structured to feed a hierarchical tree control or record-tree display, where each row represents a node at a defined depth.

Underlying Base Objects

Per the documented metadata, OKE_FLDMX_DOCUMENT_RTREE_V is defined over the following referenced objects:

• FND_DOCUMENT_CATEGORIES_VL (VIEW) – the base document category view, supplying the category identifier and user-facing category name.
• OKE_BUSINESS_AREAS_V (VIEW) – the business area view, supplying business area code and name.
• OKE_FLOWDOWNS (SYNONYM) – the flowdown configuration synonym, supplying the association between business areas and document categories.

Because FND_DOCUMENT_CATEGORIES_VL is the same object users frequently search for by name, this view is effectively a specialized consumer of the standard document category definition. The join path is: OKE_FLOWDOWNS.DOCUMENT_CATEGORY_ID = FND_DOCUMENT_CATEGORIES_VL.CATEGORY_ID, and OKE_FLOWDOWNS.BUSINESS_AREA_CODE = OKE_BUSINESS_AREAS_V.BUSINESS_AREA_CODE. The view text itself is a UNION of two branches: one producing the top-level business area nodes and one producing the child document category nodes.

Key Columns

• CTX – a context/type discriminator. The view emits the literal 'BIZAREA' for business area rows and 'DOCUMENT' for document category rows, identifying the node type.
• INIT_STAT – an initial-state flag, populated with -1 for business area nodes and 0 for document nodes, typically used to control expansion state in a tree.
• DEPTH – the hierarchy level, assigned 1 for business areas and 2 for document categories.
• LABEL – the display label. For business areas this is BUSINESS_AREA_NAME; for document nodes it is DC.USER_NAME from FND_DOCUMENT_CATEGORIES_VL.
• DATA – the node payload. Business areas return BUSINESS_AREA_CODE; document nodes return the padded business area code concatenated with the document category ID.
• SORT_KEY – the ordering key. Business areas return BUSINESS_AREA_NAME; document nodes return the padded business area name concatenated with the user name, driving tree ordering.

Common Use Cases and Queries

Typical uses include reviewing flowdown setup, validating which document categories are attached to each business area, and powering hierarchical inquiry forms. A simple listing of all nodes follows:

• SELECT ctx, depth, label, data, sort_key FROM apps.oke_fldmx_document_rtree_v ORDER BY sort_key;
• SELECT * FROM apps.oke_fldmx_document_rtree_v WHERE ctx = 'DOCUMENT'; — isolates document category nodes only.
• SELECT * FROM apps.oke_fldmx_document_rtree_v WHERE depth = 1; — lists business areas.
• Joining back to FND_DOCUMENT_CATEGORIES_VL by category identifier allows reconciliation with the category master, confirming that each flowdown-assigned category still exists and is active in the category view.

Because the view is read-only and derived purely from configuration, it is safe for ad hoc reporting and interface extraction, though queries should filter by business area to avoid returning the full tree where only a single area is of interest.