Search Results region_validation_exception

Overview

APPS.ICX_API_REGION is a PL/SQL package body within the Oracle E-Business Suite Internet Computing Architecture (ICX) product family. It provides the programmatic interface through which Oracle EBS applications create, modify, copy, and remove regions and the page plugs assigned to them. Regions in the ICX framework are the reusable content containers that make up self-service pages, and page plugs are the individual functional components mapped into those containers. The package therefore sits at the center of page-layout maintenance for the Oracle iStore, Oracle iProcurement, and related self-service web applications, giving both Forms-based administration screens and batch processes a controlled, validated means of manipulating the underlying region and plug metadata tables.

The object is documented as VALID and is classified under API classification OTHER. It carries no dependency on any external database object that references it in turn, but it depends on the ICX region and plug tables, the ICX security package ICX_SEC, the PL/SQL Web Toolkit package HTP, and DUAL.

Key Procedures and Functions

Eleven documented procedures and functions comprise the public surface of this package:

• CREATE_MAIN_REGION — establishes a top-level region record, forming the root of a region hierarchy.
• SPLIT_REGION — divides an existing region into constituent parts, supporting layout reorganization without loss of assigned content.
• DELETE_REGION — removes a single region definition.
• GET_REGION — retrieves a region definition for display or validation purposes.
• ADD_REGION — inserts a region into an existing structure, typically as a subordinate node.
• EDIT_REGION — updates the attributes of an existing region.
• GET_CHILD_REGION_LIST — returns the set of regions subordinate to a given parent, supporting tree traversal.
• DELETE_REGIONS — removes multiple regions in a single operation, handling the associated hierarchy cleanup.
• COPY_REGION_PLUGS — duplicates the page plug assignments from one region to another, enabling rapid replication of a configured layout.
• COPY_CHILD_REGIONS — replicates the child region structure beneath a target region, used when cloning a page template.
• GET_MAIN_REGION_RECORD — returns the top-level region record associated with a given context.

Together these routines cover the full lifecycle of region administration: creation of roots, insertion and editing of nodes, hierarchical retrieval, duplication of content and structure, and controlled deletion.

Tables Accessed

The package operates against the base and translated tables of the ICX region and page-plug model. ICX_REGIONS stores the region definitions themselves and is the primary target of the create, add, edit, and delete operations. ICX_REGIONS_S is the corresponding translated (secure) table, read to resolve language-specific region names and descriptions. ICX_PAGE_PLUGS holds the assignments of functional plugs to regions and is the source and destination for COPY_REGION_PLUGS; ICX_PAGE_PLUGS_S provides the translated plug labels. The presence of ICX_PAGE_PLUGS_S in the dependency list is directly relevant to the user's search term "icx_page_plugs_s", which identifies the translated page-plug table referenced by this package. DUAL is used for single-row selection and sequence or constant evaluation, while HTP indicates that portions of the package emit HTML output, consistent with its role in rendering self-service pages. ICX_SEC is invoked for security validation of region access.

Usage Notes

ICX_API_REGION is not referenced by any other database object, which confirms that it functions as a top-level entry point rather than an internal helper. It is most commonly invoked from the Oracle EBS administrative Forms that maintain self-service page layouts, where the region tree is displayed and edited interactively. Concurrent programs that seed or migrate region configurations, and custom PL/SQL extensions that programmatically build page structures, call the same procedures. Because the package writes to core ICX metadata tables, it should be invoked only through supported administration paths or carefully controlled custom code, and changes should be validated against the translated _S tables to ensure multilingual consistency. The same behavior applies across EBS 12.1.1 and 12.2.2, as the ICX region model is unchanged between these releases.