Search Results aw_space_name
Overview
FPA_GLOBAL_PVT is a private ("PVT" classification) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. Its name associates it with the FPA product family, which in EBS relates to Financial Planning and Analysis / Enterprise Planning and Budgeting functionality. The package provides a small utility surface for interrogating the Oracle OLAP Analytic Workspace (AW) layer: it resolves the correct analytic workspace space name for the EBS instance and determines whether that workspace is currently attached to the database session's OLAP environment.
Because the package is classified as PVT, it is not a public or supported integration API. It is an internal helper used by other FPA components rather than a documented extension point. The ETRM metadata records only two program units and a single inbound reference from another package, which is consistent with a narrowly scoped, single-purpose utility module whose job is to shield callers from the mechanics of constructing the AW space name and issuing OLAP queries against it.
Key Procedures and Functions
- AW_SPACE_NAME — A function that returns VARCHAR2. It constructs and returns the fully qualified analytic workspace space name used by EBS. The implementation selects from FND_APPLICATION using a fixed application identifier (application_id = 440) and concatenates the application short name with a constant suffix (
.fpapjp) to produce the return value. Any caller needing to target the standard FPA analytic workspace delegates naming to this function rather than hard-coding the value. - IS_AW_ATTACHED — A function that returns BOOLEAN. It determines whether the FPA analytic workspace is currently attached. It first calls AW_SPACE_NAME to obtain the target space name, then invokes
dbms_aw.interpwith a dynamically builtshow aw(attached ...)command. The resulting CLOB is partially read usingdbms_lob.read, and the returned text buffer is scanned withinstrfor the literal tokenyes. A non-zero position indicates attachment, and the function returns TRUE; otherwise it returns FALSE. FND_LOG instrumentation at the PROCEDURE and STATEMENT levels brackets entry, intermediate state, and (in principle) exit.
Tables Accessed
- FND_APPLICATION — Read only. Used by AW_SPACE_NAME to resolve the EBS application short name for application_id 440, which is combined with the
.fpapjpsuffix to form the analytic workspace space name. This lookup decouples the hard-coded identifier from the instance-specific short name and allows the package to work across installations where the FPA application carries the same internal ID. - DBMS_AW — Invoked by IS_AW_ATTACHED via
dbms_aw.interpto evaluate theshow aw(attached)command. This is accessible through an APPS synonym and returns a CLOB describing attachment status. - DBMS_LOB — Used by IS_AW_ATTACHED through
dbms_lob.readto extract a small prefix of the CLOB returned by DBMS_AW for string matching.
Usage Notes
FPA_GLOBAL_PVT is invoked from within other FPA packages rather than directly from forms or concurrent programs, as reflected by the single documented referencing package. Callers typically use IS_AW_ATTACHED as a guard, checking prerequisite AW state before attempting operations that depend on the analytic workspace. Because the package is private, customizations should avoid calling it directly; instead, they should prefer supported FPA APIs that already encapsulate AW attachment logic. The $Header line indicates maintenance through an FPA library build, and the presence of FND_LOG calls means diagnostic output can be observed by raising the relevant FND logging levels. Note also that the documented source places an exit log block after unconditional RETURN statements; that code path is unreachable in the shipped version, so exit tracing from this procedure should not be relied upon. Finally, the hard-coded application_id 440 and the .fpapjp suffix bind this package to the standard FPA analytic workspace naming convention, which should be validated during any upgrade between 12.1.1 and 12.2.2 if AW naming conventions change.
-
PACKAGE BODY: APPS.FPA_GLOBAL_PVT
12.2.2
-
PACKAGE BODY: APPS.FPA_GLOBAL_PVT
12.1.1
-
PACKAGE: APPS.FPA_GLOBAL_PVT
12.2.2
-
PACKAGE: APPS.FPA_GLOBAL_PVT
12.1.1
-
PACKAGE: APPS.FPA_UTILITIES_PVT
12.1.1
-
PACKAGE: APPS.FPA_UTILITIES_PVT
12.2.2
-
PACKAGE BODY: APPS.FPA_UTILITIES_PVT
12.2.2
-
PACKAGE BODY: APPS.FPA_UTILITIES_PVT
12.1.1
-
APPS.FPA_GLOBAL_PVT dependencies on FPA_GLOBAL_PVT
12.2.2
-
APPS.FPA_GLOBAL_PVT dependencies on DBMS_AW
12.2.2
-
APPS.FPA_GLOBAL_PVT dependencies on FPA_GLOBAL_PVT
12.1.1
-
APPS.FPA_GLOBAL_PVT dependencies on DBMS_LOB
12.2.2
-
APPS.FPA_GLOBAL_PVT dependencies on DBMS_AW
12.1.1
-
APPS.FPA_GLOBAL_PVT dependencies on DBMS_LOB
12.1.1