Search Results display_aolj_rup




Overview
Explore in AI Chat

Overview

FND_AOLJ_UTIL is a utility package in the Oracle E-Business Suite Applications Foundation (FND) layer, owned by APPS and classified as a UTIL object within the ETRM repository. Its source header (AFAJUTLB.pls, version 120.4, last modified 2006) indicates it has been a stable part of the EBS codebase across releases, including 12.1.1 and 12.2.2. The package provides low-level helper routines that support the Application Object Library Java (AOLJ) infrastructure, covering areas such as profile option retrieval, NLS session configuration, session creation and conversion, guest session handling, and validation of ICX (Oracle iProcurement / Self-Service Framework) sessions. Because it exposes eight documented functions and procedures rather than a business API, it is intended for internal consumption by other FND components rather than direct end-user invocation. The ETRM metadata lists zero other packages as referencing it, which suggests it is called primarily from Java-based AOL/J servlets, JSPs, and thin-client components that delegate session and localization work down to PL/SQL.

Key Procedures and Functions

  • MULTI_PROFILE_VALUE_SPECIFIC — Retrieves one or more profile option values for a specific user, responsibility, and application combination. It accepts a delimited list of profile names and returns the corresponding values concatenated in a result string. Defaults fall back to the current login context when identifiers are omitted.
  • SET_NLS_CONTEXT — Executes an ALTER SESSION to establish NLS settings for the database session, including NLS_LANGUAGE, NLS_DATE_FORMAT, NLS_DATE_LANGUAGE, NLS_SORT, NLS_TERRITORY, and NLS_NUMERIC_CHARACTERS. This ensures date, number, and sort behavior match the application user's locale.
  • GETCLASSVERSIONFROMDB — Returns the version of a Java class as recorded in the database, typically by inspecting USER_OBJECTS or a related repository, so the AOLJ layer can confirm that deployed Java code matches the expected release.
  • CREATESESSION — Establishes an EBS session record, binding the authenticated user context needed for subsequent AOL/J operations.
  • IS_VALID_ICX — Validates an ICX session, confirming that a given session identifier corresponds to a live, authenticated Self-Service / iProcurement session before privileged operations are allowed. This is the routine surfaced by the user's search term.
  • CONVERTGUESTSESSION — Promotes or converts a guest (anonymous) session into an authenticated session, a common pattern during login flows where a user browses anonymously before signing in.
  • DISPLAY_AOLJ_RUP — Renders or reports AOLJ Release Update Pack information, used for diagnostics and patch-level verification.
  • GENERIC_ERROR (internal) — Not a public API. It sets the FND message SQL_PLSQL_ERROR with routine, error number, and reason tokens and raises APP_EXCEPTION.RAISE_EXCEPTION, providing consistent error handling across the package.

Tables Accessed

  • FND_USER — Read to resolve and validate user identities during session creation, guest-session conversion, and profile lookups.
  • USER_OBJECTS — Queried by GETCLASSVERSIONFROMDB to determine Java class versions loaded into the database.
  • DUAL — Used for single-row evaluations, such as NLS context setting and simple validation checks.
  • DBMS_JAVA — Invoked to bridge PL/SQL and Java session context, supporting the AOLJ session and class-version routines.

All access is performed through APPS synonyms, consistent with standard EBS coding practice.

Usage Notes

FND_AOLJ_UTIL is an internal infrastructure package rather than a business-facing API. It is typically invoked from Java servlets, JSP pages, and AOL/J session-management code that need to validate ICX sessions (IS_VALID_ICX), convert guest sessions after authentication (CONVERTGUESTSESSION), or establish locale-aware database sessions (SET_NLS_CONTEXT). Custom code should avoid calling these routines directly unless replicating AOL/J behavior, because their contracts are tied to the Java layer and are not documented for external use. In 12.1.1 and 12.2.2, the package remains compatible with the OAF and Self-Service Framework stacks. The absence of dependent packages in ETRM indicates that changes here ripple primarily into the Java tier, so any modification should be treated as high-impact and regression-tested against login, iProcurement, and Self-Service flows.