Search Results lock_user




Overview
Explore in AI Chat

Overview

The APPS.ZPB_BUSAREA_VAL package body is a validation engine within the Oracle EBS Enterprise Planning and Budgeting (EPB) / Financial Services Accounting Hub family of modules. It belongs to the ZPB (business area) namespace, which controls security, scope, and definitional integrity for Business Areas. Business Areas represent logical groupings of financial data (ledgers, dimensions, hierarchies, and functional dimension sets) that govern how data is read, written, and owned across the application.

The package's central responsibility is to validate that the queries and definitions underpinning a Business Area still evaluate correctly after changes to the underlying metadata — for example, dimension removal, hierarchy revision, or dataset reconfiguration. Where validation fails, the package "locks out" the affected user by setting scope and ownership flags so that stale or invalid definitions cannot be used until they are corrected. The header comment dates the source to release 120.49, and the package carries the standard "noship" designation, indicating it is an internal, unsupported API rather than a published interface.

Key Procedures and Functions

  • LOCK_OUT_USER — The procedure most closely associated with the search term lock_user. It updates the ZPB_ACCOUNT_STATES table, setting the READ_SCOPE, WRITE_SCOPE, and OWNERSHIP columns to the "locked" value (documented as constant G_LOCK_OUT = 2) as required by the validation outcome. It also inserts the invalid query's name and path details into ZPB_VALIDATION_TEMP_DATA for later retrieval by the Java middle-tier layer. The documented parameter concepts include a business area identifier, a user id, query name/path/type, an error-type flag (fix-and-mark-invalid "F" versus refresh-only "R"), and an initialization-fix flag that suppresses automatic metadata fixing for real-time UI validation.
  • VAL_AGAINST_EPF — Validates a Business Area definition against the EPF (Enterprise Planning and Forecasting) metadata model, confirming that referenced dimensions, hierarchies, and datasets resolve consistently.
  • VAL_AGAINST_EPB — Performs the equivalent validation against the EPB Business Area model, ensuring the definition remains internally consistent and usable.
  • VAL_DEFINITION — A top-level validation entry point that evaluates a Business Area definition and drives scope locking through the mechanisms described above.

The G_MAX_NAME_LENGTH, G_READ_RULE, G_WRITE_RULE, and G_OWNER_RULE constants show that validation is applied independently per rule type, and the G_BUS_AREA_PATH_PREFIX and G_SECURITY_ADMIN_FOLDER constants indicate the ADF/BC4J folder paths used to resolve and secure the associated query definitions.

Tables Accessed

The documented table references span four functional groups. User identity is resolved through FND_USER. Validation state and results are persisted in ZPB_STATUS_SQL and, as described for LOCK_OUT_USER, in the temporary validation data table and ZPB_ACCOUNT_STATES. Business Area object metadata is held in BISM_OBJECTS and BISM_OBJECT_TYPES. Definitional structures are validated against the FEM tables: FEM_DATASETS_ATTR and FEM_DATASETS_B; FEM_DIMENSION_GRPS_B, FEM_DIM_ATTRIBUTES_B, and FEM_DIM_ATTR_VERSIONS_B; FEM_FUNC_DIM_SETS_B and FEM_GLOBAL_VS_COMBO_DEFS; FEM_HIERARCHIES and FEM_HIER_DIMENSION_GRPS; and FEM_LEDGERS_ATTR and FEM_LEDGERS_B. These reads establish whether the dimensions, hierarchies, ledgers, and functional dimension sets referenced by a Business Area still exist and remain consistent.

Usage Notes

ZPB_BUSAREA_VAL is an internal validation package invoked by the EPB/EPF middle-tier Java services rather than directly by end users. It is typically triggered when a user saves or executes a Business Area definition, when the metadata fixer runs as a batch or concurrent process, and during real-time validation from the UI. Because it is documented as unsupported ("noship") and is referenced by one other package, custom code should not call these procedures directly; instead, invoke the supported Business Area maintenance flows, which delegate to this package. Administrators investigating a locked-out user should treat the ZPB_ACCOUNT_STATES scope columns and ZPB_VALIDATION_TEMP_DATA as the authoritative record of the lock and its cause.