Results for “get_service_ticket_string”

16 results




Overview
Explore in AI Chat

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

Overview

EDR_XDOC_UTIL_PKG is a utility package in the Oracle E-Business Suite EDR (Electronic Document Repository / E-Records) module. Its primary business function is to support the creation, management, and transmission of electronic records (e-records) associated with documents such as invoices and other transactional PDFs. The package provides helper routines for managing temporary session parameters required by the AppsContext initialization, generating e-record attachments, constructing notification message bodies, and handling HTTP communication including service ticket generation and validation against Oracle's e-record/HTTP service infrastructure.

The package is classified as OTHER in the ETRM repository, indicating it is not a public API intended for customer extension, but rather an internal support package invoked by other EDR components. Its scope covers both database-side record management (parameter staging, attachment creation, LOB handling) and outbound integration concerns (HTTP requests and service ticket authentication).

Key Procedures and Functions

  • GENERATE_ERECORD — The central routine responsible for producing an electronic record from a source document, orchestrating the persistence of the e-record and its associated metadata.
  • EDR_CREATE_ATTACHMENT — Creates the attachment linking the generated e-record to the underlying document within the FND attachment framework, ensuring the record is retrievable from the standard attachment UI.
  • GET_NTF_MESSAGE_BODY — Builds the body content used in workflow or notification messages related to e-record processing, formatting the message text for delivery.
  • REQUEST_HTTP — Issues HTTP requests (typically via UTL_HTTP) to an external or internal service endpoint, handling the transport of e-record payloads or associated requests.
  • GET_SERVICE_TICKET_STRING — Retrieves or constructs the service ticket string used to authenticate against the HTTP service. This is the routine the user searched for; it supplies the credential token consumed by REQUEST_HTTP and the associated validation logic.
  • VALIDATE_SERVICE_TICKET — Verifies the validity of a service ticket before use, confirming the ticket has not expired and is acceptable for the requested service operation.

Tables Accessed

  • EDR_ERESPARAMETERS_T (and its _S sequence) — Stores temporary e-record parameters, including AppsContext values such as user ID, responsibility ID, NLS settings, and language. This table is central to SET_TEMP_PARAMS and DELETE_TEMP_PARAMS, which stage and clean up session context required during the PDF e-record creation process.
  • EDR_PSIG_DOCUMENTS — Holds document references tied to the e-record generation process.
  • FND_ATTACHED_DOCUMENTS_S — Underlies attachment creation, providing the sequence and attachment records.
  • FND_DOCUMENT_CATEGORIES — Supplies the category information used when registering the attachment.
  • FND_HTTP_SERVICE_TICKETS — Stores issued service tickets, supporting GET_SERVICE_TICKET_STRING and VALIDATE_SERVICE_TICKET.
  • FND_LOBS — Stores the binary large object content of the generated e-record attachment.
  • FND_USER — Provides user context (via FND_GLOBAL and direct lookups) for parameter initialization.
  • DUAL and UTL_HTTP — Used for scalar evaluation and outbound HTTP transport respectively.

Usage Notes

EDR_XDOC_UTIL_PKG is invoked indirectly by the EDR framework rather than directly by end users. It is referenced by two other packages, which call its procedures to generate e-records and to communicate with HTTP services. Typical invocation paths include concurrent programs that batch-generate PDF e-records, and workflow or notification processes that call GET_NTF_MESSAGE_BODY to format messages. GET_SERVICE_TICKET_STRING and VALIDATE_SERVICE_TICKET are exercised during outbound HTTP integration, where a service ticket must be obtained and validated prior to transmitting e-record data.

Because the package uses PRAGMA AUTONOMOUS_TRANSACTION in its parameter management routines, calling code must be aware that parameter inserts and deletes commit independently of the caller's transaction. Deployments on 12.1.1 and 12.2.2 behave equivalently; no environment-specific branching is documented. Customizations should avoid hard-coding calls to this package, as it is an internal utility subject to change between patch levels.