Search Results fnd_http_ticket




Overview
Explore in AI Chat

Overview

FND_HTTP_TICKET is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that implements a lightweight, server-side ticketing mechanism for HTTP operations. Its core purpose is to issue short-lived, one-time-use or limited-lifespan tokens (tickets) that a caller can present back to the application to authorize or correlate a subsequent HTTP-driven action. Because the payload carried by a ticket includes both an operation identifier and an argument string, the package guards against ticket misuse: a ticket issued for one operation or target object cannot be repurposed for another. Tickets are generated from a 128-bit cryptographically secure random number, providing tamper resistance without requiring the caller to manage session state.

The package is classified as OTHER in the ETRM 12.2.2 metadata and exposes eighteen documented procedures and functions. It is referenced by nine other packages within the EBS codebase, indicating that it serves as shared security infrastructure rather than a user-facing API. The design notes in the source header indicate that tickets are stored in an index-organized table to minimize storage overhead, since access is either by primary key (ticket value) or by full scan.

Key Procedures and Functions

Tables Accessed

  • FND_HTTP_TICKETS — The primary index-organized table storing each ticket's RAW(16) key, START_DATE, END_DATE, OPERATION, and ARGUMENT columns. It backs all creation, validation, update, and destruction logic.
  • FND_HTTP_SERVICE_TICKETS — Stores service-scoped tickets supporting the SET/GET/COMPARE service ticket routines.
  • UTL_RAW — The Oracle-supplied RAW manipulation utility, used to generate, compare, and convert the 16-byte ticket values and their string equivalents.

Usage Notes

FND_HTTP_TICKET is invoked programmatically rather than through a standard form. Typical callers include EBS framework components that construct outbound HTTP links—such as notification, workflow, or single-sign-on flows—where a token must be issued on one request and validated on another. Custom code follows the same pattern: create a ticket, transmit it to the client as a URL parameter, then call a CHECK or CHECK_ONETIME routine upon its return. P_ LIFESPAN defaults to sixty seconds in the documented CREATE_TICKET signature, reflecting the short-lived nature of these tokens. Administrators may schedule PURGE_TICKETS as a concurrent program to clear expired rows. Because the package is referenced by nine other packages, changes should be treated as framework-level and tested against all dependent components.