Search Results bis_customization

Overview

APPS.BIS_CUSTOMIZATION is a PL/SQL package that belongs to the Oracle E-Business Suite Business Intelligence System (BIS) product family, which underpins the Oracle EBS Daily Business Intelligence (DBI) and related analytics infrastructure. In EBS 12.1.1 and 12.2.2 the package carries a documented API classification of OTHER, meaning it is not exposed as a formally published public API but is used internally to manage customization metadata for the BIS/DBI regions and region items that make up the analytics user interface framework. Its role is administrative: it registers, and removes, the customization records that describe how region items have been personalized or extended within the BIS architecture.

The package owns one package specification and one package body and reports a status of VALID in the ETRM repository. It does not reference any external database object directly according to the dependency listing; instead, all table access is performed through APPS synonyms. The package is referenced by no other packages, which indicates that it sits at the edge of the dependency graph and is invoked directly by runtime or upgrade code rather than being reused as a shared library.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions for this package. No parameter lists are published, so only their purpose is described below.

• INSERT_CUSTOM_REGISTRY — Inserts a record into the customization registry. This procedure is responsible for registering a customization entry so that the BIS/DBI framework recognizes a user-defined or extended region item. It writes the identifying and descriptive information needed to associate the customization with its parent region item, enabling the analytics layer to render or suppress the item appropriately.
• DELETE_REGION_ITEM — Removes a region item record. This procedure deletes the region item and its associated registry entry, cleaning up customization metadata when an item is withdrawn, reset, or otherwise no longer required. It is the counterpart to the registration logic and is used to keep the AK region item tables consistent with the active customization set.

Tables Accessed

Three tables are accessed through APPS synonyms, all belonging to the Application Object Library (AK) region framework:

• AK_CUSTOM_REGISTRY — The customization registry table. It stores the entries written by INSERT_CUSTOM_REGISTRY, capturing which region items have been customized and the metadata that identifies them.
• AK_REGION_ITEMS — The base table of region items. It holds the individual items (fields, buttons, regions) that make up an AK region definition; DELETE_REGION_ITEM removes rows here as part of its cleanup logic.
• AK_REGION_ITEMS_TL — The translation table for AK_REGION_ITEMS. It stores the language-specific (translatable) attribute values for each region item, so deletions and registrations must maintain consistent rows across both the base and translation tables.

Usage Notes

Because BIS_CUSTOMIZATION is classified as OTHER and is referenced by no other packages, it is not intended for general developer consumption. It is typically invoked by the BIS/DBI application code or by administrative utilities that manage the customization registry behind the DBI dashboards. In practice, entries are created indirectly through the personalization and customization features surfaced in the EBS analytics UI, and the package's procedures execute to synchronize the AK region item tables with those changes.

Custom code should treat these procedures as internal: their absence from the published API list, the unavailability of documented signatures, and the lack of downstream dependents all argue against direct invocation. Any reliance on BIS_CUSTOMIZATION in a 12.1.1 or 12.2.2 environment should be validated against the actual package specification in the APPS schema, since the ETRM excerpt does not expose parameter details. Where the analytics framework itself drives the registration and deletion of customization records, no manual call is required.