Results for “obj_type”

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

Overview

BIS_OBJ_HIERARCHY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BIS (Business Intelligence System / Applications BIS) product family. Its role is to expose the hierarchical relationship between the objects that make up a BIS dashboard or portal—such as regions, portlets, and reports—and the concurrent programs, form functions, and lookups that resolve those objects into user-facing names. In effect, the view flattens the object dependency model into a single, denormalized row set that describes each BIS object, its display type, its refresh mode, and, where applicable, the Oracle EBS concurrent program or function that backs it.

The view is especially relevant to administrators and report developers who need to trace which underlying concurrent program or function is associated with a given BIS object. Because one of its projected columns is USER_CONCURRENT_PROGRAM_NAME, the view is frequently reached for when a user searches on that term, indicating a common requirement to reconcile a BIS object with its FND_CONCURRENT_PROGRAMS_VL definition.

Underlying Base Objects

Although the ETRM metadata records no explicitly documented base objects for this view, the view text reveals the objects on which it depends. The driving subquery is a UNION of OBJECT_TYPE/OBJECT_NAME from BIS_OBJ_DEPENDENCY and DEPEND_OBJECT_TYPE/DEPEND_OBJECT_NAME from the same table, producing the complete set of objects participating in the BIS hierarchy. This derived set is then outer-joined to:

• BIS_OBJ_PROG_LINKAGES — supplies the linkage between a BIS object and its concurrent program, plus REFRESH_MODE.
• FND_CONCURRENT_PROGRAMS_VL — provides USER_CONCURRENT_PROGRAM_NAME and APPLICATION_ID for the linked program.
• FND_COMMON_LOOKUPS — filtered on LOOKUP_TYPE = 'BIS_OBJECT_TYPE', yielding the OBJ_DISP_TYPE meaning.
• FND_FORM_FUNCTIONS_VL — supplies USER_FUNCTION_NAME for objects of type PORTLET or REPORT.

All joins to the linkage, program, lookup, and function tables are outer joins (marked with the (+) operator), so every object in the dependency set is retained even when no matching program or function exists.

Key Columns

• OBJ_TYPE — the BIS object type code (for example PORTLET or REPORT), derived from the dependency table.
• OBJ_NAME — the internal name of the BIS object.
• USER_OBJ_NAME — a display name. For PORTLET and REPORT types it resolves to FUNC.USER_FUNCTION_NAME; otherwise it falls back to OBJ_NAME.
• USER_CONCURRENT_PROGRAM_NAME — the user-facing concurrent program name from FND_CONCURRENT_PROGRAMS_VL, correlated through the linkage's CONC_APP_ID and CONC_PROGRAM_NAME.
• REFRESH_MODE — the refresh behavior defined on the object-program linkage.
• OBJ_DISP_TYPE — the lookup meaning corresponding to the object type, providing a human-readable display classification.

Common Use Cases and Queries

Typical use cases include auditing which concurrent program backs a BIS report, validating that objects in the dependency hierarchy resolve to valid programs and functions, and generating listings of BIS objects by display type. The following query lists BIS objects alongside their linked concurrent program and refresh mode:

SELECT obj_type, obj_name, user_obj_name, user_concurrent_program_name, refresh_mode, obj_disp_type FROM apps.bis_obj_hierarchy_v WHERE user_concurrent_program_name IS NOT NULL ORDER BY obj_type, obj_name;

A second common pattern filters for a specific concurrent program name to identify every BIS object that depends on it:

SELECT obj_type, obj_name, user_concurrent_program_name FROM apps.bis_obj_hierarchy_v WHERE user_concurrent_program_name = :program_name;

Because the view is defined entirely on supported APPS synonym objects and uses outer joins, it is safe to query directly without additional joins; consumers should note that rows without a linked program will return NULL for USER_CONCURRENT_PROGRAM_NAME.