Search Results pv_date_format




Overview

FND_SESSION_MANAGEMENT is a core Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a foundational infrastructure API. Its purpose is to manage the lifecycle of user sessions established through the Oracle EBS sign-on and self-service frameworks. The package creates, validates, and terminates web sessions, generates unique identifiers for sessions and transactions, maintains session-scoped attribute values used to carry context across form and framework calls, and raises workflow events associated with session activity.

Because the Oracle EBS middle tier maintains state for authenticated users, this package is the authoritative mechanism for issuing session identifiers (newsessionid), transaction identifiers (newtransactionid), and externally exposed identifiers (newxsid). It also supports session validation against the ICX session tables and participates in sign-on, guest conversion, and logout flows. In both release 12.1.1 and 12.2.2, the package status is VALID and its ETRM classification is OTHER, reflecting its role as internal infrastructure rather than a public business API. Its dependency footprint — exposing 31 documented procedures and functions and being referenced by 15 other packages — confirms that much of the Oracle EBS application stack implicitly relies on it for session integrity.

Key Procedures and Functions

  • NEWSESSIONID, NEWTRANSACTIONID, NEWXSID — generate globally unique identifiers for a session, an individual transaction within a session, and the externally referenced session identifier respectively.
  • CREATESESSION, CREATETRANSACTION — persist new session and transaction records used by the web-based runtime.
  • CONVERTGUESTSESSION — promotes a guest (unauthenticated) session to an authenticated session following sign-on.
  • REMOVETRANSACTION — retires a completed or abandoned transaction record.
  • VALIDATESESSION_PRAGMA, VALIDATESESSIONPRIVATE — perform validation of the active session; the pragma variant supports compile-time use of the validation function inside SQL.
  • NEWSESSIONRAISEEVENT, DONEWSESSIONEVENT — raise workflow events at session start and session completion, typically consumed by business event subscribers.
  • SETSESSIONPRIVATE, GETSESSIONCOOKIENAME — set session state flags and return the cookie name used to identify the session at the browser tier.
  • GETID, GETNLS_PARAMETER — return the current session identifier and resolve NLS (language/territory) parameters relevant to the session.
  • PUTSESSIONATTRIBUTEVALUE, GETSESSIONATTRIBUTEVALUE, CLEARSESSIONATTRIBUTEVALUE — maintain a session-scoped name/value attribute store shared between forms, frameworks, and custom code.
  • UPDATESESSIONCONTEXT — refresh contextual data attached to the active session.
  • INITIALIZESSWAGLOBALS — initialize the session-facing globals used by the self-service web applications layer.

Tables Accessed

Usage Notes

FND_SESSION_MANAGEMENT is not intended for direct invocation by end users or typical customizations. It is called transparently by the sign-on framework (FND_SIGNON), the self-service application session layer (APP_SESSION), function execution (FND_RUN_FUNCTION), and the Oracle Application Framework utility layer (FND_AOLJ_UTIL, FND_SESSION_MANAGEMENT internal dependencies), as well as by vertical and module packages such as BSC_SECURITY, BSC_MO_UI_PKG, BSC_BIS_LOCKS_PUB, CZ_CF_API, FEM_DIS_UTL_PKG, MO_GLOBAL, WF_MONITOR, and WFA_SEC.

From a Forms or OA Framework perspective, the package is invoked during application startup, after authentication, and during normal navigation and logout. Concurrent programs and workflow subscribers that need to identify the originating session or raise a session-scoped event may reference the event routines. Custom code should interact with this package cautiously: identifiers returned by NEWSESSIONID, NEWTRANSACTIONID, and GETID are used as keys in ICX_SESSIONS and ICX_TRANSACTIONS, and session attributes written via PUTSESSIONATTRIBUTEVALUE are visible to all components sharing the same session. Because the package is owned by APPS and repeatedly referenced across the application stack, any modifications or direct calls in a production environment should be confined to supported extension points rather than patched implementation logic.