Search Results zpb_busarea_val




Overview
Explore in AI Chat

Overview

ZPB_BUSAREA_VAL is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM "OTHER" API category. It belongs to the Enterprise Performance Foundation / Profitability and Cost Management (formerly ETRM) product family, and its name reflects its role as a business area validation utility. The package enforces the integrity of business area definitions and versions by validating them against Enterprise Performance Foundation (EPF) and Enterprise Planning and Budgeting (EPB) metadata, and by locking out users whose queries no longer conform to the underlying dimensional model. It therefore sits at the boundary between user-authored query objects and the shared metadata repository, protecting both from inconsistent state. The package header carries a source control identifier dated 2007, indicating it is a mature component that has remained stable across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The package exposes four documented procedures.

  • LOCK_OUT_USER — Updates ZPB_ACCOUNT_STATES, setting the READ_SCOPE, WRITE_SCOPE, and OWNERSHIP columns to the locked value (2) as required. It also inserts the invalid query's name and path details into ZPB_VALIDATION_TEMP_DATA for later retrieval by the Java layer. Its parameters include the business area identifier, the user identifier drawn from FND_USER, the invalid query object name and path, the query type, the query error type, an initialization/fix flag, and the status SQL identifier. The query type distinguishes read, write, and ownership rules; the header comments explicitly enumerate G_READ_RULE, G_WRITE_RULE, and G_OWNER_RULE as the accepted values.
  • VAL_AGAINST_EPF — Validates a business area version against EPF to ensure that all required metadata exists and is enabled. It accepts a version identifier and an initialization flag for the message list, and returns a standard return status together with message count and message data outputs.
  • VAL_DEFINITION — Validates a business area definition, applying the same validation conventions used elsewhere in the package.
  • VAL_AGAINST_EPB — Validates business area content against EPB metadata, complementing the EPF-oriented validation performed by VAL_AGAINST_EPF.

Tables Accessed

The package references a broad set of APPS synonyms. FND_USER supplies the user identifier passed into LOCK_OUT_USER, while ZPB_STATUS_SQL provides the query path and status SQL identifier types used in that procedure's signature. The BISM_OBJECTS and BISM_OBJECT_TYPES tables hold the business intelligence object definitions against which query validity is judged. The remaining FEM tables constitute the EPF metadata substrate: FEM_DATASETS_B and FEM_DATASETS_ATTR, FEM_DIMENSION_GRPS_B, FEM_DIM_ATTRIBUTES_B and FEM_DIM_ATTR_VERSIONS_B, FEM_FUNC_DIM_SETS_B, FEM_GLOBAL_VS_COMBO_DEFS, FEM_HIERARCHIES and FEM_HIER_DIMENSION_GRPS, and FEM_LEDGERS_B with FEM_LEDGERS_ATTR. These are read during validation routines such as VAL_AGAINST_EPF and VAL_AGAINST_EPB to confirm that dimensions, hierarchies, datasets, and ledger attributes referenced by a business area remain present and enabled.

Usage Notes

ZPB_BUSAREA_VAL is invoked primarily from the Java middle tier during real-time validation of user queries, and from concurrent or batch processes that perform metadata fix-up. The p_init_fix parameter in LOCK_OUT_USER indicates whether metadata fixing should be attempted; the header comments state that fixing is not performed for real-time validation originating from the user interface, in which case the query is simply marked invalid or refreshed. The error type parameter distinguishes queries requiring a fix and invalidation ("F") from those that are merely refreshed ("R"), the latter applying when a dimension has been removed and repair is not feasible. The package is referenced by one other package, confirming it is a supporting utility rather than an entry-point API. Customizations should avoid calling LOCK_OUT_USER directly, since it writes to ZPB_ACCOUNT_STATES and ZPB_VALIDATION_TEMP_DATA in coordination with the Java layer.