Search Results irc_login




Overview
Explore in AI Chat

Overview

IRC_LOGIN is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM "OTHER" API category. Its header, dated 2007, aligns with the early R12 codebase and remains present in both 12.1.1 and 12.2.2. The package addresses the boundary between EBS and externally launched web entry points: it constructs execution links that carry a user into an authenticated session, validates login credentials supplied at that boundary, and converts a session token into the EBS application session. This places IRC_LOGIN in the family of "iRecruitment"/iRecruitment-adjacent login utilities (the IRC prefix) used for single sign-on and direct-URL integration scenarios, where an external portal, partner site, or the "bwremote" style remote-access account handshake passes a user into EBS without a normal Forms login. Because the package is not a public, published interface and has no dependents, it is best understood as an internal helper consumed by feature-specific code rather than a general-purpose authentication API.

Key Procedures and Functions

The documented interface contains three entry points, all of which touch identity and session establishment.

  • CREATEEXECLINK2 (function) — Builds a URL or execution link that launches an EBS function within an identified application, responsibility, and security group context on a named server. Its parameters cover the target function name, application short name, responsibility key, security group key, server name, and an optional parameters string; the function returns the constructed link. It is the package's outbound direction: assembling a trusted entry point rather than consuming credentials.
  • VALIDATE_LOGIN (function) — Evaluates a supplied user name, password, and a disable flag, returning a validation result. This is the credential-checking routine, and the disable argument indicates the caller may request that authentication be suppressed or short-circuited for a controlled scenario.
  • CONVERTSESSION (procedure) — Takes a session token together with a user name and password and converts that token into an authenticated EBS session. It is the central operation for token-based session handoff.

Parameter signatures above reflect only what the header shows; internal logic is not exposed in the documented metadata.

Tables Accessed

IRC_LOGIN resolves the following objects through APPS synonyms: FND_APPLICATION and FND_FORM_FUNCTIONS, used to look up the application short name and the target function when building an execution link; FND_RESPONSIBILITY and FND_SECURITY_GROUPS, used to validate the responsibility and security group context named by the caller; FND_NODES, used to confirm the target server; and FND_USER, used for credential and account validation during login and session conversion. Together these reads ensure that any generated link or converted token points at a legitimately configured EBS navigation context and a real, enabled user account.

Usage Notes

IRC_LOGIN is not invoked directly by end users. It is called from Forms-based customizations, from feature code that renders external or remote login entry points, and potentially from concurrent programs or custom PL/SQL that implement token-based session handoff. In practice the pattern is: VALIDATE_LOGIN verifies credentials, CONVERTSESSION establishes the session from a token, and CREATEEXECLINK2 produces the navigable link into the target responsibility. The package is referenced by zero other packages, so it has no shared-library role and should be treated as internal; direct calls from custom code carry upgrade risk. The "bwremote account" query likely reflects a remote-access account configured against this login path. Administrators should verify the account is active in FND_USER and correctly mapped to a responsibility and security group before troubleshooting the handoff.