Search Results create_functional_area




Overview
Explore in AI Chat

Overview

APPS.BIS_FUNCTIONAL_AREA_PVT is a private PL/SQL package in Oracle E-Business Suite that provides the core implementation logic for maintaining functional area definitions within the Business Intelligence System (BIS) schema. A functional area represents a logical grouping of business activities used across Oracle EBS applications to categorize and organize information for reporting, personalization, and application-level configuration.

The package is classified as PVT (private), meaning it is not intended to be called directly by external consumers. Instead, it operates behind the public API package BIS_FUNCTIONAL_AREA_PUB, which exposes the same record type (Functional_Area_Rec_Type) and serves as the sanctioned entry point. The private package encapsulates the procedural business logic that populates and maintains the BIS_FUNCTIONAL_AREAS and BIS_FUNCTIONAL_AREAS_TL tables, along with their relationship to the FND_APPLICATIONS table. The header comment identifies the package as "Private for populating the table BIS_FUNCTIONAL_AREAS_TL and relationship with FND_APPLICATIONS table," confirming its role as the data-maintenance engine for functional area metadata.

The package was created on 24-NOV-2004 by Aditya Rao and carries the source file designation BISVFASS.pls. Its design follows Oracle's standard API architecture, including an API version parameter, a commit flag defaulting to FND_API.G_FALSE, and standardized OUT parameters for return status, message count, and message data.

Key Procedures and Functions

The ETRM metadata documents nine procedures within this package, several of which correspond directly to the extract provided:

  • CREATE_FUNCTIONAL_AREA — Inserts a new functional area definition into the base and translation tables, using the Functional_Area_Rec_Type record passed from the public API layer.
  • UPDATE_FUNCTIONAL_AREA — Modifies an existing functional area definition, applying changes to the base table and any affected translation rows.
  • TRANSLATE_FUNCTIONAL_AREA — Manages translated (language-specific) content for functional areas, writing to the _TL table for the appropriate language.
  • DELETE_FUNCTIONAL_AREA — Removes a functional area and its associated translation and application-dependency records.
  • CREATE_FUNC_AREA_APPS_DEP — Establishes an association between a functional area and one or more Oracle applications, recording the dependency relationship.
  • UPDATE_FUNC_AREA_APPS_DEP — Modifies an existing functional-area-to-application dependency association.
  • REMOVE_FUNC_AREA_APPS_DEP — Deletes a functional-area-to-application dependency association.
  • RETRIEVE_FUNCTIONAL_AREA — Queries and returns functional area data, supporting validation and display requirements.
  • ADD_LANGUAGE — Inserts language-specific rows into the translation table, supporting the multilingual requirements of the _TL architecture.

All procedures share the common API signature pattern: p_Api_Version, p_Commit, an IN record of type BIS_FUNCTIONAL_AREA_PUB.Functional_Area_Rec_Type, and the standard OUT parameters x_Return_Status, x_Msg_Count, and x_Msg_Data for error handling and diagnostics.

Tables Accessed

The package reads from and writes to four documented tables via APPS synonyms:

  • BIS_FUNCTIONAL_AREAS — The base table storing functional area definitions, including the functional area identifier, name, and associated attributes.
  • BIS_FUNCTIONAL_AREAS_TL — The translation table holding language-specific descriptions and names, populated by TRANSLATE_FUNCTIONAL_AREA and ADD_LANGUAGE.
  • BIS_FUNC_AREA_APP_DEPENDENCY — The intersection table capturing which Oracle applications depend on or are associated with each functional area; maintained by the CREATE, UPDATE, and REMOVE _FUNC_AREA_APPS_DEP procedures.
  • FND_LANGUAGES — The Oracle Applications language repository, referenced to validate and resolve installed languages when inserting translation rows.

Usage Notes

Because BIS_FUNCTIONAL_AREA_PVT is a private package, direct invocation is discouraged and unsupported. It is designed to be called exclusively by its public counterpart, BIS_FUNCTIONAL_AREA_PUB, which performs validation and then delegates to the private procedures for actual data manipulation. This layering ensures that all functional area maintenance flows through a single, controlled interface.

Typical invocation scenarios include Oracle Forms-based setup screens for functional area definition, concurrent programs that seed or migrate functional area data, and custom extensions that require functional area setup as part of an implementation or configuration script. The p_Commit flag allows callers to defer or force a database commit, enabling multi-step transactions to be assembled within a single logical unit of work.

The ETRM metadata records that this package is referenced by one other package, consistent with its role as an internal implementation detail used by the public API layer. Developers using the searched term "create_functional_area" should route their calls through BIS_FUNCTIONAL_AREA_PUB rather than this private package to ensure forward compatibility across EBS 12.1.1 and 12.2.2 releases.