Search Results is_erec_required

Overview

EDR_STANDARD_PUB is the public utility package within the Oracle E-Records (EDR) module of Oracle E-Business Suite, delivered under the APPS schema with AUTHID CURRENT_USER semantics. Oracle E-Records provides the electronic evidence store and electronic signature infrastructure used by regulated industries to capture, retain, and audit business transaction records in compliance with frameworks such as 21 CFR Part 11. The package header comment describes its scope as containing "all general Oracle E-Records utilities," and the package is registered in ETRM as a public API (API classification PUB) with the display name "Oracle E-Records Utility," mapped to the EDR_EVIDENCE_STORE business entity.

The package exposes shared helper routines used across the EDR module rather than a single business transaction. Its responsibility set includes evaluating whether an electronic signature or electronic record is required for a given action, resolving signature status for evidence documents, assembling descriptive flexfield prompts and column names for display, resolving lookup meanings, and generating XML payloads that represent user-entered data for storage in the evidence store. It is referenced by seven other packages, confirming its role as a foundational utility layer.

Key Procedures and Functions

The eighteen documented routines cover several functional groups:

• Signature and record requirement checks: GET_PSIGSTATUS returns the signature status associated with an evidence document, which is the routine most frequently targeted by callers auditing workflow approval outcomes. IS_ESIG_REQUIRED determines whether an electronic signature is mandated for the current operation, and IS_EREC_REQUIRED determines whether an electronic record must be created.
• Evidence and query resolution: GET_ERECORD_ID returns the identifier of the electronic record generated for a transaction. GET_QUERYID_ONEVENTS and GET_QUERYID_ONPARAMS resolve query identifiers against events and parameters respectively, supporting the rule engine that decides which EDR rules apply.
• Rule variable retrieval: GET_AMERULE_VARVALUES and GET_AMERULE_VARIABLEVALUES return the input variable values bound to an AME (Approvals Management Engine) rule, allowing EDR rule evaluation to reuse AME configuration.
• Flexfield display helpers: GET_DESCFLEX_ONEPROMPT and GET_DESCFLEX_ALLPROMPTS return descriptive flexfield prompt labels, either individually or in full, for rendering evidence content in forms and reports.
• Formatting and lookup helpers: DISPLAY_DATE, DISPLAY_DATE_ONLY, and DISPLAY_TIME_ONLY provide consistent date and time formatting for evidence display. GET_LOOKUP_MEANING resolves a lookup code to its translated meaning.
• Audit and notification utilities: IS_AUDITVALUE_OLD compares an audit value against its prior state. GET_NOTIF_ROUTING_INFO returns workflow notification routing information. USER_DATA_XML constructs the XML representation of user-supplied data captured with an electronic record.

Tables Accessed

The package accesses two objects through APPS synonyms. EDR_PSIG_DOCUMENTS stores electronic signature evidence documents; GET_PSIGSTATUS and related routines read this table to determine the approval or rejection state of a signed document. PLITBLM is the standard Oracle date and time formatting specification table used by the DISPLAY_DATE family of routines to derive locale-appropriate display formats. The package header also declares collection types based on edr_standard.eventDetails and edr_standard.RuleInputValues, and a G_SIGNATURE_STATUS global holding workflow status values such as APPROVED or REJECTED, plus flexfield column-name and prompt record types covering thirty columns.

Usage Notes

EDR_STANDARD_PUB is intended for invocation from Oracle Forms-based EDR-enabled transactions, from concurrent programs that process or report on evidence records, and from custom PL/SQL that integrates with the E-Records evidence store. Because the package is declared AUTHID CURRENT_USER, callers must hold the necessary privileges on the underlying EDR objects granted through the APPS schema. Signature status should be read through GET_PSIGSTATUS rather than by direct SQL against EDR_PSIG_DOCUMENTS, since the API encapsulates the status derivation logic used by the EDR workflow. The package is documented in MetaLink Note 268669.1, Oracle E-Records API User's Guide, which remains the authoritative reference for parameter signatures and return types on both EBS 12.1.1 and 12.2.2.