Search Results apps_database_id

Overview

FND_SOS_SERVICE is an internal Oracle E-Business Suite authentication service package owned by the APPS schema. It is part of the foundation (FND) layer that underpins session establishment and user credential validation across the EBS technology stack. The package is classified as OTHER in the ETRM metadata, indicating that it is not a general-purpose public API but rather a supporting component consumed by other framework services. Its principal role is to validate user name and password combinations presented by external or internal callers and to return the full set of session attributes required to establish an authenticated EBS session — including the numeric user identifier, the session identifier, and the Oracle Applications database identifier. In practice, FND_SOS_SERVICE functions as a bridge between sign-on requests (for example, those originating from the Oracle Application Server / Single Sign-On integration or from session cookie validation logic) and the underlying security tables that hold user credentials and active session state. Because the package is declared AUTHID CURRENT_USER, it executes with the privileges of the invoker rather than the definer, a design choice consistent with a service that operates on behalf of an already-identified session context.

Key Procedures and Functions

• AUTHENTICATE — The primary procedure in the package. It accepts a user name and password as input and returns, through its OUT parameters, the login status, the numeric user identifier, a description, the user status, the user's language setting, the session identifier, the external session identifier, and the Oracle Applications database identifier (apps_database_id). This last value is the element most directly aligned with the object search term "apps_database_id," and it is returned to the caller so that the authenticated session can be correctly associated with the specific EBS database instance in a multi-database or shared sign-on environment. The procedure effectively produces the complete identity envelope for a session.
• VALIDATE_USER_COOKIE — A function that accepts a user name and password and returns a VARCHAR2 result. It is used to validate the user cookie presented by a client during session resumption or re-authentication, providing a lighter-weight verification path than the full AUTHENTICATE call. Its return value signals whether the supplied credentials remain valid for the associated cookie.

Tables Accessed

The package reads from three tables through APPS synonyms:

• FND_USER — Stores the EBS user account record, including the encrypted password, user status, and account description that AUTHENTICATE returns to the caller. This is the authoritative table for credential verification.
• FND_LANGUAGES — Supplies the language information returned in the languages OUT parameter, so the caller can construct a session with the correct NLS environment.
• ICX_SESSIONS — Holds active session records. The package interacts with this table to create or validate the session identifier (session_id and xsid) returned by AUTHENTICATE and used by the session manager.

Usage Notes

FND_SOS_SERVICE is an infrastructure package and is not intended for direct invocation by end users or by ordinary customizations. It is invoked by the EBS sign-on and session management flow — particularly the components that serve login requests and validate session cookies — as well as potentially by the Oracle Single Sign-On or Applications SSO integration layer where an external identity must be mapped to an EBS user and database. The inclusion of the apps_database_id OUT parameter in AUTHENTICATE reflects the need to disambiguate the target EBS database in environments where multiple application databases share a common authentication path. Custom code should not call this package directly; the supported integration points are the standard login APIs and SSO configuration. Because it is declared AUTHID CURRENT_USER and references only APPS synonyms, it requires the calling session to already hold appropriate privileges on FND_USER, FND_LANGUAGES, and ICX_SESSIONS. The metadata records no other packages as referencing FND_SOS_SERVICE, which is consistent with its role as a low-level service invoked through the framework rather than through published dependency chains.