Search Results icx_ext_supplier




Overview
Explore in AI Chat

Overview

APPS.ICX_EXT_SUPPLIER is a lightweight PL/SQL package belonging to the Oracle iProcurement (ICX) schema in Oracle E-Business Suite. Its declared purpose, reflected in its single public procedure and the small set of objects it touches, is to establish and validate the identity of an external supplier-side user who connects to the procurement application through an externally exposed entry point. The package header is declared AUTHID CURRENT_USER, meaning that the procedures execute with the privileges of the invoking schema rather than the definer, a characteristic consistent with a thin entry-point layer that is called from servlet-based or self-service code paths rather than from trusted batch code. The header line $Header: ICXEXSPS.pls 115.0 99/07/17 03:17:17 porting $ indicates the package has existed since the very early Internet Computing Architecture (ICA) releases of the product and has been carried forward essentially unchanged into the 12.1.1 and 12.2.2 code lines. Within the ETRM catalog it is classified under API classification OTHER, and no other package in the documented set is shown as referencing it, confirming that it is a leaf-level component invoked directly from an application tier entry point rather than from other PL/SQL units.

Key Procedures and Functions

The package exposes exactly one documented program unit:

  • AUTHENTICATE_USER — a procedure whose purpose is to validate an externally presented session ticket and, on success, associate that ticket with a valid authenticated user session. The procedure accepts a single inbound ticket value, expressed in the package specification as a number, which represents the externally issued session identifier. The parameter list is deliberately not reproduced here beyond the documented specification, and no additional parameters should be assumed. Because the package contains only this one procedure, it functions as a single-purpose gate rather than a general-purpose supplier API.

Tables Accessed

The documented table references below are reached through APPS synonyms, which allows the package to be compiled and executed without a hard schema dependency on the underlying owning schemas:

  • FND_USER — the Oracle Applications user registry; used to confirm that the identity being asserted corresponds to a known, active application user.
  • ICX_SESSIONS — the iProcurement/ICX session store; the natural target for ticket validation, since an external ticket must be matched against an existing session record.
  • ICX_REQUISITIONER_INFO — requisitioner profile data, consulted to resolve the requesting party associated with the authenticated session.
  • ICX_POR_ITEM_SOURCES — item source definitions used by the purchasing/ordering engine; referenced so the authenticated context can be tied to a valid sourcing configuration.
  • ICX_PROCUREMENT_SERVER_SETUP — procurement server configuration, providing the environment context in which the external connection is being accepted.
  • HTP — the PL/SQL web toolkit package, indicating that the authentication path is capable of emitting HTML output, typically a redirection or error page, when authentication fails.

Usage Notes

ICX_EXT_SUPPLIER is not intended for direct invocation from Oracle Forms or from concurrent programs. It is a server-side entry point reached from the iProcurement/web tier when an external supplier or partner presents a ticket. The presence of HTP in the referenced objects and of ICX_PROCUREMENT_SERVER_SETUP confirms an HTTP-facing call path, and the AUTHID CURRENT_USER clause indicates the caller supplies its own privileges. In 12.1.1 and 12.2.2 the package remains a legacy Internet Computing Architecture artifact; it is rarely extended by customizations. The retrieval context "Quick Suppliers partners" corresponds to external trading-partner access to iProcurement, which is precisely the scenario this package was written to serve. Custom code requiring supplier authentication should treat the package as a documented but minimal contract: one procedure, one ticket parameter, and no outbound dependencies on other packages.