Results for “pos_init_session_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

POS_INIT_SESSION_PKG is a small utility package owned by the APPS schema in Oracle E-Business Suite. It is classified as an API of type OTHER within the ETRM metadata, indicating that it is not a standard business-object API but rather an internal support routine invoked by the framework. The package carries the AUTHID CURRENT_USER declaration, meaning its database objects are resolved in the schema of the invoking user at runtime rather than as the definer, and its header identifies it as a member of the POS family of packages. The package was first shipped in 2001 (header revision 115.0), and it remains present through the 12.1.1 and 12.2.2 releases as a component of the shared session-management layer used by Oracle EBS web-based components.

The single documented procedure, InitSession, provides a programmatic mechanism for initializing an application session record on behalf of a caller. In practice this package supports the requirement that a valid session row exist in the ICX_SESSIONS table before EBS functions, menus, and responsibilities can be resolved for a logged-in user. It therefore sits at the boundary between the login/connection pool infrastructure and the EBS security model.

Key Procedures and Functions

The ETRM documentation for this package lists one procedure:

• InitSession — Initializes the session record for the supplied responsibility identifier. The procedure accepts a responsibility identifier parameter (documented as p_resp_id VARCHAR2) and is responsible for establishing the session context associated with that responsibility. Because the ETRM metadata classifies this package as OTHER, the procedure should be treated as an internal framework entry point rather than a published extension API; it is not accompanied by the standard API error-handling and validation conventions expected of documented business APIs.

No other procedures or functions are documented for this package in ETRM. Customizations that depend on this entry point should be prepared for behavior changes between maintenance releases, since the package has no formal API compatibility guarantee.

Tables Accessed

According to the documented metadata, POS_INIT_SESSION_PKG references a single table through APPS synonyms:

• ICX_SESSIONS — The EBS session table. This table records active user sessions, including session identifiers, user and responsibility context, and related connection information. The InitSession procedure writes to (and potentially reads from) this table to create the session row that the EBS framework subsequently uses to resolve menus, functions, and security for the user's responsibility. ICX_SESSIONS is central to Oracle EBS session management and is referenced by many components across the technology stack.

Because the package operates under AUTHID CURRENT_USER, the ICX_SESSIONS synonym resolves to the table in the invoking user's context, and appropriate privileges on the APPS synonym are required for the procedure to execute successfully.

Usage Notes

POS_INIT_SESSION_PKG is an internal framework package rather than a general-purpose toolkit. ETRM records that it is referenced by three other packages, confirming that its primary consumers are other PL/SQL components in the POS and session-management layers rather than direct calls from end users. Its typical invocation occurs during session establishment, when the framework needs to seed a session row in ICX_SESSIONS for a given responsibility.

Because the package is not documented as a public API, developers should avoid calling InitSession directly from custom forms, concurrent programs, or client extensions. Custom code that manipulates ICX_SESSIONS or attempts to bypass the standard EBS security layer can corrupt session state and is unsupported. When troubleshooting session or login anomalies in 12.1.1 or 12.2.2, the package is worth noting as one of the internal components that participates in session creation; diagnostics should nevertheless focus on the ICX_SESSIONS contents and the callers that invoke this package rather than on the procedure itself.