Results for “edr_utilities”

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

Overview

EDR_UTILITIES is a shared PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, with source header revisions dating to the 12.1.x code line and carried forward into 12.2.2. It is declared AUTHID CURRENT_USER, meaning its unqualified references to EDR and FND objects resolve through the invoking session's schema and synonym chain. The package anchors the EDR (E-Records / Electronic Document Delivery) product family, the technology that generates XML payloads, applies XSL formatting, and dispatches documents and notifications for e-signature and transactional record-keeping within Oracle Approvals Management and related business flows. It also supplies a broad set of AME and user-resolution helpers used across the EDR suite. The API classification is OTHER, reflecting that it is an internal supporting library rather than a public, supported integration interface. It references fifteen documented tables and is invoked by at least twelve other packages, confirming its role as a foundational dependency rather than an end-user entry point.

Key Procedures and Functions

The 39 documented units divide into several functional groups:

• Document generation: GENERATE_XML produces the XML payload for a given map code and document identifier, returning the output CLOB together with error code, error message, and log file name. GENERATE_ERECORD combines the raw XML with an XSL definition to produce the rendered record. PRINTCLOB and CLOB_REPLACE support CLOB manipulation and diagnostics.
• Setup validation: VERIFY_SETUP checks configuration for a given event and event key, returning ERRBUF and RETCODE in the standard concurrent-program convention. The package constant validate_setup_ui_ctx ('VALIDATE_SETUP') distinguishes the user-interface invocation context for setup validation.
• Notification and e-signature processing: EDR_RAISE3 raises an EDR business event with event name, key, optional data and send date, and parameter lists. EDR_NTF_HISTORY retrieves notification history for a document. GET_EVENT_DESCRIPTION returns descriptive text for an event.
• User and approver resolution: GETWHOCOLUMNS, GETUSERDISPLAYNAME, GETUSERIDFROMAME, GET_USER_DATA, GETUSERROLEINFO, GETOVERRIDINGDETAILS, GETACTUALRECIPIENT, and GETPROFILEVALUE / GETPROFILEVALUESPECIFIC resolve users, roles, approvers, profile options, and overriding recipient data, drawing on subtypes imported from AME_UTIL.
• Text substitution: REPLACE_USER_DATA_TOKEN and GET_DELIMITED_STRING parse and substitute tokens embedded in document text.
• Housekeeping: TEMP_DATA_CLEANUP purges temporary working data, and EDR_NTF_HISTORY supports historical review of dispatched notifications.

The user query term get_rules_and_variables does not correspond to any documented procedure in this package. Rule and variable retrieval in the EDR/AME context is generally exposed elsewhere; EDR_UTILITIES supplies the underlying profile, user, and event resolution primitives that such calls depend on.

Tables Accessed

• EDR_RAW_XML_T and EDR_FINAL_XML_GT: staging for pre-transform and post-transform XML used by GENERATE_XML and GENERATE_ERECORD.
• EDR_ERECORDS, EDR_ERESPARAMETERS_T, EDR_PROCESS_ERECORDS_T: the e-record repository and the parameter/processing staging used during document assembly.
• EDR_ESIGNATURES and EDR_PSIG_DETAILS: e-signature and signature detail records applied to generated documents.
• EDR_EVENT_RELATIONSHIP and EDR_INTER_EVENT_TEST_SCENARIOS: event linkage definitions and test scenarios consulted during event raising and validation.
• EDR_TRANS_QUERY_TEMP, EDR_PREPARE_DOCUMENT_TEMP, EDR_COLLATE_PRINT_TEMP, EDR_REDLINE_TRANS_DATA: temporary and redline working tables populated by the generation and cleanup routines.
• AME_CALLING_APPS and FND_APPLICATION: resolve the calling application context used when determining AME behavior and application short names.

Usage Notes

EDR_UTILITIES is not intended for direct end-user invocation. It is called by EDR forms (notably setup validation via VERIFY_SETUP), by concurrent programs that generate and dispatch e-records, and by workflow/business-event processing that calls EDR_RAISE3 to launch notifications. Because it is a private supporting package with an OTHER classification, customizations should invoke documented EDR entry points rather than calling these procedures directly; signatures may change between patch levels. In 12.1.1 and 12.2.2 the package resides in APPS and depends on AME_UTIL types and FND synonyms, so execution must occur in a session with the standard APPS initialization (FND_GLOBAL / MO) and appropriate EDR and AME grants.