Results for “user_function_name”

6 results




Overview
Explore in AI Chat

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

Overview

BIS_DISPLAY_FORM_FUNC_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the Applications BIS (Business Intelligence System) product family. It presents a curated, normalized list of Oracle Forms-based functions registered in the EBS function security framework, together with classification metadata that identifies whether each function is a form, a subfunction, or another object type. Because the underlying FND_FORM_FUNCTIONS_VL view (the object referenced in typical user searches such as "fnd_form_functions_vl") stores raw registration data, BIS_DISPLAY_FORM_FUNC_V adds derived attributes — most notably the OBJECT_TYPE and OBSOLETE flags — that make the function inventory more directly consumable by BIS dashboards, reporting extracts, and diagnostic queries.

Underlying Base Objects

The view is defined primarily over FND_FORM_FUNCTIONS_VL, the translatable (VL) form of the FND_FORM_FUNCTIONS table, which is the authoritative registry of form functions, their parameter strings, and their associated web HTML calls. The view enriches each row with data supplied by helper objects. It references BIS_FUNCTIONAL_AREAS to resolve the FUNCTIONAL_AREA_ID and BIS_FUNCTIONAL_AREAS_VL to resolve the FUNCTIONAL_AREA_NAME for the short name 'BIS_UNN'. The scalar function BIS_UTIL.GET_OBJECT_TYPE is invoked to derive OBJECT_TYPE from the function's TYPE, PARAMETERS, and WEB_HTML_CALL values. A NOT EXISTS subquery against BIS_FORM_FUNCTION_EXTENSION_VL excludes functions already captured by the extension table, and the result set is combined with a UNION ALL branch over the same source family. Although the ETRM metadata documents no explicitly registered base objects, the view text unambiguously builds on these FND and BIS tables.

Key Columns

  • FUNCTION_ID — Primary identifier of the function in FND_FORM_FUNCTIONS.
  • FUNCTION_NAME — The internal function name used in menu and security assignments.
  • OBJECT_TYPE — Derived classification via BIS_UTIL.GET_OBJECT_TYPE, distinguishing forms from other function types.
  • USER_FUNCTION_NAME — The user-facing name displayed in responsibility and menu configuration.
  • WEB_HTML_CALL and PARAMETERS — The invocation string and parameter list for the function.
  • ISSEED — Flag (Y/N) indicating whether the function is seeded by Oracle, evaluated from CREATED_BY values 1, 2, or 120.
  • FUNCTIONAL_AREA_ID / NAME / SHORT_NAME — Classification into the BIS functional area, defaulting to 'BIS_UNN'.
  • APPLICATION_ID — The owning application, defaulted to -1 where NULL.
  • OBSOLETE — Derived flag ('T'/'F') based on the presence of '&POBSOLETEFLAG=Y' in the PARAMETERS string.
  • LAST_UPDATE_DATE and CREATED_BY — Audit columns inherited from the source view.

Common Use Cases and Queries

Typical usage includes auditing form functions across applications, identifying seeded versus custom functions, and excluding obsolete registrations from menu or security analysis. A representative query is:

SELECT FUNCTION_NAME, USER_FUNCTION_NAME, OBJECT_TYPE, ISSEED, OBSOLETE
FROM   BIS_DISPLAY_FORM_FUNC_V
WHERE  OBSOLETE = 'F'
AND    ISSEED = 'N'
ORDER  BY FUNCTION_NAME;

Because the view filters on non-null TYPE, WEB_HTML_CALL, and FUNCTION_NAME, it is well suited to feeds that populate BIS compliance and configuration reports without additional cleansing.