Results for “add_hierarchy_version”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ZPB_BUSAREA_MAINT is an APPS-owned PL/SQL package that provides the maintenance API for Business Areas within the Oracle Enterprise Performance Foundation / Enterprise Resource Planning (FEM) data model used in Oracle E-Business Suite 12.1.1 and 12.2.2. A Business Area represents a logical grouping of dimensions, hierarchies, attributes, ledgers, datasets, and users that together define a query context for profitability, cost management, and analytic reporting. The package encapsulates the discrete operations needed to construct, populate, version, and administer these objects without requiring direct DML against the underlying FEM repository tables. Its header identifies the file as ZPBVBAMS.pls, version 120.9, dated 2007/12/04, and it is classified under the ETRM metadata as an "OTHER" API. The package is referenced by three other packages within the EBS schema, indicating that it acts as a foundational service layer consumed elsewhere in the ZPB/FEM code path.
Key Procedures and Functions
The documented interface exposes 30 procedures and functions that fall into several functional groups. The core creation and structure APIs include:
- CREATE_BUSINESS_AREA — instantiates a new Business Area record.
- CREATE_EMPTY_VERSION — creates a version container with no pre-populated content; this is the entry point most closely tied to the "create_empty" search term, allowing callers to build a version incrementally.
- COPY_VERSION — duplicates an existing version to serve as the basis for a new one.
- ADD_DIMENSION, ADD_ATTRIBUTE, ADD_LEVEL, ADD_HIERARCHY, ADD_HIERARCHY_VERSION, ADD_HIERARCHY_MEMBER, ADD_LEDGER, ADD_DATASET — attach the constituent elements that define a Business Area version.
- ADD_CONDITION — adds an attribute condition (with value, optional value set, and operator) that filters the version.
- ADD_USER, LOGIN, REMOVE_USER — manage user membership and access to the Business Area.
- CHANGE_HIER_VERS_INCL — modifies hierarchy version inclusion behavior.
- REFRESH — rebuilds or synchronizes Business Area content, often after underlying dimension or hierarchy changes.
- REMOVE_ATTRIBUTE — detaches a previously added attribute.
- DELETE_BUSINESS_AREA and DELETE_BUSINESS_AREA_CR — remove a Business Area, the latter associated with change-request handling.
Parameter lists are intentionally not restated here; the package header governs the exact signatures.
Tables Accessed
The package operates against a broad set of APPS-synonym FEM and ZPB tables. Dimension and attribute definitions are drawn from FEM_DIMENSIONS_B, FEM_DIM_ATTRIBUTES_B, FEM_DIM_ATTR_VERSIONS_B, FEM_XDIM_DIMENSIONS, and FEM_FUNC_DIM_SETS_B/FEM_FUNC_DIM_SET_MAPS, which together supply the multidimensional metadata and functional dimension-set mappings. Hierarchy structure is managed through FEM_HIERARCHIES, FEM_LEDGERS_ATTR, and FEM_GLOBAL_VS_COMBO_DEFS (value-set combinations used by ADD_CONDITION). Object catalog and definition tables FEM_OBJECT_CATALOG_B, FEM_OBJECT_DEFINITION_B, and BISM_OBJECTS store Business Area object registrations. FND_USER is read for user membership operations (ADD_USER, LOGIN, REMOVE_USER), and FND_CONCURRENT_REQUESTS is consulted for concurrent processing context, typical of REFRESH-style operations. ZPB_ACCOUNT_STATES holds state information tied to the Business Area lifecycle.
Usage Notes
ZPB_BUSAREA_MAINT is not typically called directly by end users. It is invoked by EBS forms and concurrent programs that present the Business Area maintenance UI, and by the three dependent PL/SQL packages noted in the metadata. Custom extensions that programmatically build or modify Business Areas should call these APIs rather than performing direct inserts, since the package enforces internal consistency among dimensions, hierarchies, attributes, and user privileges, and triggers any dependent refresh logic. The CREATE_EMPTY_VERSION procedure is particularly useful when a caller needs a blank version to populate selectively through successive ADD_* calls, avoiding the overhead of cloning an existing version.