Search Results g_business_area_does_not_exist
Overview
APPS.POA_EUL_UTILS is a utility package body in the Oracle E-Business Suite procurement intelligence / Oracle Procurement Analysis (POA) product family. Its principal role is to manage interaction with the Oracle E-Business Suite Executive Understanding Layer (EUL), the metadata repository that underlies the Oracle Discoverer reporting environment historically bundled with EBS. In EBS 12.1.1 and 12.2.2, this package provides the runtime plumbing that allows POA reporting components to locate and initialize an EUL business area before analytical queries are executed.
The package operates by resolving an EUL owner schema (for example, an APPS or dedicated EUL schema) and then resolving a specific business area by name within that schema. It exposes package-level state — the EUL owner, the business area identifier, the business area name, and Discoverer version — that calling routines use to build dynamic SQL against EUL metadata tables. The metadata classifies this object as API classification OTHER, indicating it is an internal supporting utility rather than a public or supported API.
Key Procedures and Functions
The documented interface lists a single procedure, EULMAIN. This procedure serves as the primary entry point into the package and is responsible for orchestrating the EUL initialization sequence. Based on the package body excerpt, EULMAIN drives the initialization of business area context through internal helper procedures such as InitBusArea3i (Discoverer 3i) and InitBusArea4i (Discoverer 4i), each of which targets a different EUL version's metadata layout. EULMAIN therefore acts as a version-aware dispatcher: it detects or receives the applicable Discoverer version and routes control to the appropriate business-area lookup routine.
The internal helpers resolve a business area name into a numeric business area identifier by querying the EUL business areas table dynamically. Error handling is explicit: a missing business area raises G_BUSINESS_AREA_DOES_NOT_EXIST (Oracle error 100), while a missing EUL owner or EUL table raises G_EUL_OWNER_DOES_NOT_EXIST (Oracle error -942). No parameter lists are documented for EULMAIN in the available metadata, and none should be assumed.
Tables Accessed
The metadata records one referenced table accessed through an APPS synonym: PLITBLM. In EBS this is the PL/SQL intermediate/translation-style table used in certain Oracle Applications internal utilities for staging and message or lookup storage. Within POA_EUL_UTILS, PLITBLM is referenced in support of the package's dynamic SQL and lookup logic. In addition to this documented reference, the package body excerpt shows dynamic queries against the EUL_BUSINESS_AREAS table in the resolved EUL owner schema, which supplies the business area ID and name used to seed package state.
Usage Notes
POA_EUL_UTILS is not documented as being referenced by any other package, which indicates it is invoked at the boundary of the product — typically from a concurrent program, a wrapper package, or a form-based reporting action that must prepare Discoverer EUL context before running a workbook. The presence of g_errbuf and g_retcode globals follows the standard Oracle Applications concurrent program convention, suggesting EULMAIN may be callable in a concurrent or submission context where error buffer and return code must be surfaced.
The user search term "user_measure" is consistent with Discoverer EUL metadata concepts, where measures are defined within business areas; this reinforces the package's role as an EUL business-area resolver rather than a measure-definition engine. Because the package targets multiple Discoverer versions, deployments on 12.1.1 versus 12.2.2 should not assume identical EUL layouts. Customizations should treat this package as internal, avoid direct dependency on its globals, and prefer supported reporting APIs.