Results for “replace_user_data_token”

8 results




Overview
Explore in AI Chat

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

Overview

EDR_UTILITIES is a shared PL/SQL utility package in the Oracle E-Business Suite E-Records and E-Signatures (ETRM) module. It consolidates the low-level infrastructure routines used by the rest of the EDR schema: XML generation and manipulation, electronic record assembly, approver resolution through Oracle Approvals Management (AME), user profile lookups, transaction history management, and general data-cleanup tasks. The package is classified as an internal API (API classification: OTHER in ETRM 12.2.2) rather than a public or user-callable interface, and its procedures are invoked by higher-level EDR programs, workflow subscription rule functions, and forms-based transactions. The header revision embedded in the source (120.19.12010000.2, dated 2009) indicates the package descended from the original 11i E-Records codebase and was carried forward into 12.1.1 and 12.2.2 without structural redesign. It is a foundational, load-bearing utility rather than a business-process package, and it is referenced by at least twelve other packages across the EDR family.

Key Procedures and Functions

  • PRINTCLOB — A stub routine for printing CLOB content, retained for compatibility. The body performs no operation (NULL).
  • VERIFY_SETUP — Validates that a given event and event key are correctly configured, resolving event subscription details, application context, AME transaction type, and XML mapping prior to e-record processing. Raises a dedicated exception when multiple enabled e-signature subscriptions are detected for the same event.
  • GENERATE_ERECORD — Produces the electronic record artifact for a completed transaction.
  • GENERATE_XML — Builds the XML payload that underlies the generated e-record.
  • TEMP_DATA_CLEANUP — Purges transient staging data left behind after processing.
  • GET_DELIMITED_STRING — Formats a list of values into a delimited string suitable for XML or display output.
  • EDR_RAISE3 — Standardized error-raising helper used across EDR packages.
  • EDR_NTF_HISTORY — Retrieves notification history associated with an e-record transaction.
  • GETWHOCOLUMNS — Returns the WHO-column audit values (created by, updated by, and related context) for a record.
  • GETUSERDISPLAYNAME — Resolves a user ID to a display name.
  • GETOVERRIDINGDETAILS — Fetches approver-override detail information for a transaction.
  • GETACTUALRECIPIENT — Determines the effective recipient of a notification or e-signature request after AME routing.
  • GETUSERIDFROMAME — Maps an AME approver entry back to an FND user ID.
  • GETPROFILEVALUE / GETPROFILEVALUESPECIFIC — Wrappers over FND profile option retrieval, at user and site/application levels respectively.
  • GET_USER_DATA — Assembles user-specific merge data for document and notification generation.
  • REPLACE_USER_DATA_TOKEN — Substitutes user-data tokens within templates or documents.
  • CLOB_REPLACE — Performs string replacement inside CLOB values.
  • GETUSERROLEINFO — Returns the role assignments applicable to a user for routing or approval resolution.
  • GET_EVENT_DESCRIPTION — Returns the descriptive text for a workflow or e-record event.

Tables Accessed

The package reads and writes the EDR transactional and staging tables. EDR_ERECORDS and EDR_ESIGNATURES hold the generated electronic records and signature entries; EDR_ERESPARAMETERS_T and EDR_PSIG_DETAILS store e-signature parameter and detail data. XML artifacts pass through EDR_RAW_XML_T and EDR_FINAL_XML_GT, while EDR_COLLATE_PRINT_TEMP, EDR_PREPARE_DOCUMENT_TEMP, EDR_TRANS_QUERY_TEMP, and EDR_PROCESS_ERECORDS_T serve as transient working tables for document preparation, collation, and processing. EDR_EVENT_RELATIONSHIP and EDR_INTER_EVENT_TEST_SCENARIOS supply event linkage and test-scenario data. EDR_REDLINE_TRANS_DATA supports redline change tracking. AME_CALLING_APPS is consulted to determine whether AME should be invoked for the calling application, and FND_APPLICATION resolves application ID, code, and name for the transaction context. Consistent use of APPS synonyms means all access is through the shared applications schema.

Usage Notes

EDR_UTILITIES is not intended for direct customer invocation. It is called from EDR forms, concurrent programs, and workflow subscription rule functions such as EDR_PSIG_RULE.PSIG_RULE, which invokes VERIFY_SETUP to validate event setup before an e-signature or e-record can proceed. The package depends on Oracle Workflow (WF_EVENTS, WF_EVENT_SUBSCRIPTIONS, WF_CORE) and Oracle Approvals Management (AME_UTIL, AME_CALLING_APPS) at runtime, so AME and Workflow must be configured for the relevant application before E-record functions will operate. Because twelve other packages reference it, changes to its signatures carry broad regression risk; the practice of embedding revision headers and bug references in the source (for example Bug 3164491 for the override-details exception, Bug 2674799 for AME approver tables, Bug 4912782 for subscription filtering) reflects Oracle's incremental patching history. When troubleshooting E-records issues, DBAs commonly trace VERIFY_SETUP and GENERATE_XML activity, since failures in subscription matching or XML assembly surface as errors in those routines rather than in the calling forms.