Results for “delete_temp_params”

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

Overview

EDR_XDOC_UTIL_PKG is an Oracle E-Business Suite PL/SQL utility package owned by the APPS schema and classified as a general-purpose API object. It belongs to the EDR (Electronic Document/Record) product family, historically associated with Oracle's Approvals Management and transactional eRecord generation functionality. The package provides the core plumbing that allows an EDR rule function to produce a formatted electronic record (eRecord) by invoking an external document-generation service, attaching the resulting output to the originating transaction, and managing supporting infrastructure such as HTTP requests and service tickets.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the invoking user rather than the defining user. This is significant because it interacts with FND attachments, FND LOBs, HTTP service tickets, and UTL_HTTP, all of which are security-sensitive operations typically governed by invoker rights. The header comment ($Header: EDRXDUS.pls 120.4.12000000.1 2007/01/18) indicates the source has been relatively stable since the Release 12.0 timeframe and is carried forward into the 12.1.1 and 12.2.2 code lines with only minor patches (Bug 3170251, Bug 3761813).

Key Procedures and Functions

• GENERATE_ERECORD — The primary entry point. It is invoked from the STORE_ERECORD procedure of a Rule Function and is responsible for calling an external JSP with the required parameters appended to the URL, returning either the generated eRecord content or an error code and message. Its documented parameter set covers the EDR event identifier, the eRecord identifier, the stylesheet repository, stylesheet name and version, the application code, a redline mode flag, and, on output, the generated output format (for example PDF, DOC, HTML, or TEXT) together with error code and error message return values.
• EDR_CREATE_ATTACHMENT — Called from EDRRuleXMLPublisher, this procedure creates an FND attachment for the generated eRecord PDF and returns the file identifier created in FND_LOBS. It accepts parameters identifying the eRecord, the file name, and the stylesheet description/definition.
• GET_NTF_MESSAGE_BODY — Retrieves the body text of a notification message, presumably for embedding or referencing within the eRecord output.
• REQUEST_HTTP — Performs the outbound HTTP call to the document-generation service. This is the mechanism behind the "call the JSP" behavior described in the GENERATE_ERECORD comments.
• GET_SERVICE_TICKET_STRING — Obtains or computes a service ticket credential for authenticating the outbound HTTP request.
• VALIDATE_SERVICE_TICKET — Validates a previously issued service ticket, ensuring the request originates from a trusted source and has not expired.

Tables Accessed

The package accesses several documented APPS synonyms. EDR_ERESPARAMETERS_T and EDR_ERESPARAMETERS_T_S store the parameter definitions and setup for eRecord generation. EDR_PSIG_DOCUMENTS holds document definitions related to the output generated. FND_ATTACHED_DOCUMENTS_S and FND_DOCUMENT_CATEGORIES are used when creating and categorising attachments against transactions. FND_LOBS stores the binary content of the generated attachment file. FND_USER resolves the effective user context. FND_HTTP_SERVICE_TICKETS provides the ticket records consumed and validated by GET_SERVICE_TICKET_STRING and VALIDATE_SERVICE_TICKET. DUAL serves as the standard single-row source for computed values, and UTL_HTTP is the PL/SQL-supplied package used for the outbound web request.

Usage Notes

EDR_XDOC_UTIL_PKG is not intended to be called directly by end users. It is invoked programmatically by the EDR rule engine — specifically through STORE_ERECORD — and by the EDRRuleXMLPublisher integration object. Because GENERATE_ERECORD drives an external HTTP call, execution depends on the configured stylesheet repository and the availability of the target document-generation service; failures surface through the X_ERROR_CODE and X_ERROR_MESSAGE out parameters rather than through unhandled exceptions. The package is referenced by two other packages in the documented metadata, confirming its role as a shared utility rather than a standalone entry point. The presence of GET_SERVICE_TICKET_STRING and VALIDATE_SERVICE_TICKET indicates the design expects an authenticated web service round trip, so administrators must ensure service ticket configuration and UTL_HTTP network access are properly established before eRecord generation will succeed.