Results for “create_region_items”

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

Overview

BIS_PMV_REGION_ITEMS_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the Oracle Business Intelligence System (BIS) / Daily Business Intelligence infrastructure, specifically the region-based personalization and page layout framework used by the EBS home page and dashboard regions. The package encapsulates the server-side logic required to manage the association between configurable regions and the items (links, functions, or content elements) they contain. Operationally it functions as the internal implementation layer that supports the public region extension APIs, most notably BIS_REGION_ITEM_EXTENSION_PVT and BIS_AK_REGION_PUB, which in turn expose region and item management to the Oracle Applications Framework (OAF) region administration screens.

The package is classified as a PVT (private) API, meaning it is not intended to be called directly by external or customer-developed code. Its status is VALID, and the ETRM documentation records it as referenced by two other database objects, confirming it is embedded within a broader call chain rather than acting as an entry point.

Key Procedures and Functions

The documented package exposes three procedural entry points, all of which conform to the standard EBS API design pattern built on FND_API:

• CREATE_REGION_ITEMS — Inserts new region-item associations, creating the records that link a personalized region to the individual items it should display. This routine is the mechanism by which administrators add content to a region during page setup or personalization.
• UPDATE_REGION_ITEMS — Modifies existing region-item records, supporting changes to item sequencing, visibility, or attributes after initial creation.
• DELETE_REGION_ITEMS — Removes region-item associations, allowing items to be detached from a region without deleting the underlying content definition.

Each procedure follows the FND_API convention of accepting a standard parameter set (p_init_msg_list, p_commit, x_return_status, x_msg_count, x_msg_data) and routes errors through FND_MSG_PUB. The ETRM extract documents only the procedure names and purposes; no parameter lists are published and none should be assumed.

Tables Accessed

The only table documented as referenced through APPS synonyms is PLITBLM. This is the EBS temporary/interface table used in BIS region processing. In practice, the package also writes to the underlying region and region-item base tables (such as BIS_REGIONS and BIS_REGION_ITEMS) indirectly via its dependencies on BIS_AK_REGION_PUB and BIS_REGION_ITEM_EXTENSION_PVT. All data manipulation is performed under the APPS schema using the STANDARD package for PL/SQL types and the FND_API and FND_MSG_PUB packages for error handling and message stack management.

Usage Notes

Because this is a private package, it is not invoked directly by forms, concurrent programs, or customer extensions. It is called exclusively by the two documented referencing objects, which expose the functionality through the Oracle Applications Framework region administration and personalization UI. Developers debugging home-page region behavior or extending region content should work through the public APIs (BIS_AK_REGION_PUB, BIS_REGION_ITEM_EXTENSION_PVT) rather than BIS_PMV_REGION_ITEMS_PVT. Any customization that calls the private body directly risks breakage on patching or upgrade, since Oracle does not guarantee its signature across releases.