Search Results load_functional_area




Overview
Explore in AI Chat

Overview

BIS_FUNCTIONAL_AREA_PUB is a public PL/SQL API package in the APPS schema that serves as the maintenance wrapper for the BIS_FUNCTIONAL_AREAS table and its associated translation and application-dependency tables. The package header comment identifies its purpose explicitly: it is a "wrapper for populating the table BIS_FUNCTIONAL_AREAS_TL and relationship with FND_APPLICATIONS table." In Oracle EBS 12.1.1 and 12.2.2, this package is part of the BIS (Business Intelligence System, historically associated with Daily Business Intelligence and related EBS analytics) product family. It governs the master and translated definitions of functional areas—the categorization construct used to organize EBS application functionality for reporting and intelligence purposes—and the mapping that links each functional area to one or more Oracle Applications registered in FND_APPLICATION. The package was created 24-NOV-2004 by Aditya Rao and carries a 2005 header revision, indicating long-term stability.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, organized around two record-keeping domains: functional areas and functional-area-to-application dependencies. The package declares standard action constants—C_CREATE, C_UPDATE, C_RETRIEVE, C_DELETE—used to signal the operation being performed, which is the source of the c_retrieve token associated with this object.

  • CREATE_FUNCTIONAL_AREA — creates a new functional area definition, inserting the base row in BIS_FUNCTIONAL_AREAS and the translatable attributes in BIS_FUNCTIONAL_AREAS_TL.
  • UPDATE_FUNCTIONAL_AREA — modifies an existing functional area's name and description, including translated values.
  • RETRIEVE_FUNCTIONAL_AREA — returns the details of one or more functional areas to the caller, using the Functional_Area_Rec_Type record defined in the package header. This is the procedure exercised when a caller passes the C_RETRIEVE constant.
  • TRANSLATE_FUNCTIONAL_AREA — maintains language-specific rows for a functional area in BIS_FUNCTIONAL_AREAS_TL.
  • LOAD_FUNCTIONAL_AREA — bulk-loads functional area definitions, typically from a seed or interface source.
  • DELETE_FUNCTIONAL_AREA — removes a functional area and its dependent rows.
  • CREATE_FUNC_AREA_APPS_DEP — establishes a new dependency row linking a functional area to an application.
  • UPDATE_FUNC_AREA_APPS_DEP — changes an existing functional-area / application mapping.
  • LOAD_FUNC_AREA_APPS_DEP — bulk-loads application dependency rows.
  • REMOVE_FUNC_AREA_APPS_DEP — deletes a specific functional-area / application mapping.
  • ADD_LANGUAGE — registers an additional language, enabling translation rows for the appropriate MLS languages.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • BIS_FUNCTIONAL_AREAS — the base table holding the functional area identifier, short name, and WHO audit columns.
  • BIS_FUNCTIONAL_AREAS_TL — the multilingual (translation) table holding NAME and DESCRIPTION by language; this is the table the package header names as its primary target.
  • BIS_FUNC_AREA_APP_DEPENDENCY — the intersection table recording which applications depend on or are associated with each functional area.
  • FND_APPLICATION — read to validate and resolve application short names for the dependency records.
  • BIS_FUNC_AREA_ID_S — the sequence supplying primary keys for BIS_FUNCTIONAL_AREAS.
  • DUAL — used for single-row expressions and sequence retrieval.

Usage Notes

BIS_FUNCTIONAL_AREA_PUB is the supported public entry point for maintaining functional areas; callers should not write directly to the underlying tables, because the package enforces the combination of base row, translation rows, and dependency rows. It is invoked from EBS forms, from concurrent programs that seed or migrate functional-area metadata, and from custom PL/SQL that needs to create, update, query, or delete functional areas and their application mappings. The RETRIEVE_FUNCTIONAL_AREA procedure, selected via C_RETRIEVE, is the read path and populates the Functional_Area_Rec_Type record structure declared at lines 27–38 of the package header. The related record type Func_Area_Apps_Depend_Rec_Type carries the application dependency data. Because the package is classified as PUB, it is documented and supported for customer and partner use, but the standard precautions of EBS API invocation apply: commit after successful calls, preserve the package-generated WHO audit values, and expect exceptions raised through standard EBS error-handling mechanisms. The ETRM metadata notes that this package is referenced by one other package, so adopters should treat it as a stable dependency anchor within the BIS schema rather than a leaf utility.