Search Results icx_admin_sig




Overview
Explore in AI Chat

Overview

The APPS.ICX_ADMIN_SIG package body is a server-side PL/SQL utility that renders the administrative sign-on and session-management HTML interface for Oracle E-Business Suite. The module belongs to the ICX (Interaction Cartridge/Communications) product family, which underpins the Oracle Applications self-service framework and the single sign-on (SSO) integration layer. In Oracle EBS 12.1.1 and 12.2.2, the package is a critical component of the administrative authentication flow: it generates the dynamic HTML that users see during the administrative login, session validation, and error-handling pages, and it mediates interactions between the mid-tier Apache/mod_plsql runtime and the back-end session tables.

The body is recorded in ETRM as VALID in the APPS schema, carries an API classification of OTHER, and exposes thirteen documented program units. It depends on core Oracle technology stack packages (OWA_UTIL, HTP, HTF, STANDARD) as well as several EBS foundation APIs (FND_MESSAGE, FND_MSG_PUB, FND_SSO_MANAGER, FND_HELP, FND_APPLICATION, FND_FORM_FUNCTIONS_VL, ICX_SEC, ICX_SESSIONS, ICX_CALL, ICX_PLUG_UTILITIES, ICX_UTIL). Because it is referenced by thirty-eight other database objects but does not itself reference any user-defined object outside the APPS schema, it acts as a presentation-layer leaf in the dependency graph.

Key Procedures and Functions

The thirteen documented program units divide into HTML rendering helpers, help-window helpers, and session-control routines:

  • OPENHEADER / CLOSEHEADER / CLOSEHEADER2 — Emit the opening and closing HTML document fragments (typically the <html>, <head>, and <body> tags plus associated style and script references) used to frame every administrative page produced by the package.
  • BACKGROUND — Writes out the page background and related cosmetic markup shared by the administrative screens.
  • TOOLBAR — Renders the toolbar region that presents navigation and action links to the administrator during a session.
  • FOOTER — Produces the closing content appended to each generated page, including copyright and navigation anchors.
  • STARTOVER — Provides the restart entry point that reinitializes the administrative sign-on flow, typically after an authentication failure or timeout.
  • ERROR_SCREEN — Formats the standard diagnostic page shown when validation against the session tables fails or when a fatal condition is encountered.
  • SHOWTABLE / DISPLAYTABLE — Generate tabular HTML output from query results, used to present administrative listings without requiring a Forms-based UI.
  • HELP_WIN_SCRIPT / HELP_WIN_SYNTAX / ICX_FND_HELP — Manage the JavaScript and markup for the pop-up Help window, dynamically retrieving topic text through the FND_HELP and FND_MESSAGE APIs.

No argument lists are reproduced here; parameter signatures should be obtained from the live package specification, as they are not documented in the ETRM extract.

Tables Accessed

Through APPS synonyms the package reads FND_APPLICATION, ICX_SESSIONS, and the Oracle Web Toolkit views HTF, HTP, and OWA_UTIL. ICX_SESSIONS is the principal business table: it stores active session state and is queried by the administrative sign-on and validation paths to confirm that a caller holds a live, authenticated session before any administrative markup is emitted. FND_APPLICATION supplies application identity metadata used when resolving application context for the rendered pages. HTF and HTP are the Oracle-supplied PL/SQL HTML generation packages, while OWA_UTIL supplies CGI-style utilities (URL escaping, MIME header emission) required by the mod_plsql environment.

Usage Notes

ICX_ADMIN_SIG is invoked indirectly rather than through a Forms module. In a standard EBS deployment the package is called by the mod_plsql cartridge servlet when the administrative sign-on URL is requested, and its procedures are commonly called from other ICX packages and from custom PL/SQL that builds session-aware HTML pages. Because the body is referenced by thirty-eight database objects but references none in return, it is effectively a leaf utility: extending it affects only the pages it generates. Customizations should be applied through supported personalization or by cloning the package into a custom schema rather than modifying the seeded APPS body, and all changes should be recompiled and validated against both 12.1.1 and 12.2.2 runtimes to preserve supportability.