Search Results edr_standard




Overview
Explore in AI Chat

Overview

EDR_STANDARD is the core PL/SQL package within the Oracle E-Business Suite EDR (E-Records / Electronic Signature) module, operating under the APPS schema with AUTHID CURRENT_USER. It provides the shared runtime infrastructure that governs electronic signature capture, e-record enforcement, and approval routing across Oracle EBS transactions. The package sits at the intersection of Oracle Workflow, Oracle Approvals Management (AME), and the Oracle Forms-based transaction screens, supplying the logic that determines whether a given business event requires a signature, what the current signature status is, and how workflow notification recipients and descriptive flexfield prompts are resolved. In release 12.1.1 and 12.2.2, EDR_STANDARD exposes 17 documented procedures and functions and is referenced by 18 other packages, making it a foundational dependency for any EBS module that participates in electronic signature compliance, including Purchasing, Payables, Order Management, and Human Resources. Its API classification is OTHER, reflecting that it is an internal utility package rather than a formally published public API, though many of its routines are invoked directly from Oracle Forms libraries.

Key Procedures and Functions

The package groups its documented routines into several functional areas:

  • Signature and e-record status: PSIG_STATUS returns the status of the most recent signature event for a given event and event key, yielding values such as PENDING, COMPLETE, or ERROR. PSIG_REQUIRED returns a boolean indicating whether a signature is required for a specified event. EREC_REQUIRED performs the equivalent check for e-record requirements. PSIG_QUERY and PSIG_QUERY_ONE are invoked from Forms prior to opening the Transaction Query form, allowing the signature state of one or many transactions to be evaluated in bulk.
  • AME rule input resolution: GET_AMERULE_INPUT_VALUES (deprecated in favor of the newer routine) and GET_AMERULE_INPUT_VARIABLES retrieve the input variable values that Oracle Approvals Management requires for a given transaction, rule ID, and rule name. These support the dynamic construction of approval routing rules.
  • Date and time display: DISPLAY_DATE, DISPLAY_DATE_ONLY, and DISPLAY_TIME_ONLY provide formatted presentation of date and time values for the EDR user interface. DISPLAY_DATE_ONLY is the routine most commonly associated with searches such as "display_date_only" and is used to render the date portion of a timestamp without the time component.
  • Audit and workflow helpers: COMPARE_AUDITVALUES compares audit trail values to detect changes. FIND_WF_NTF_RECIPIENT resolves the workflow notification recipient for a given context. GET_USER_RESPONSE returns user-provided response data captured during a signature or approval interaction.
  • Descriptive flexfield utilities: GET_DESC_FLEX_SINGLE_PROMPT, GET_DESC_FLEX_ALL_PROMPTS, and GET_DESC_FLEX_ALL_VALUES retrieve prompt labels and valid values for descriptive flexfields, and GET_MEANING translates a lookup code into its display meaning.

Tables Accessed

EDR_STANDARD reads and writes several tables through APPS synonyms. AME_CALLING_APPS identifies the application context for AME rule evaluation. EDR_AMERULE_INPUT_VAR and EDR_AMETRAN_INPUT_VAR store AME rule and transaction input variables. EDR_PSIG_DOCUMENTS holds the e-record and signature document definitions and states. EDR_TRANS_QUERY_TEMP and its sequence EDR_TRANS_QUERY_TEMP_S support the temporary staging used by PSIG_QUERY for bulk transaction evaluation. FND_APPLICATION provides application metadata, while FND_DESCR_FLEX_CONTEXTS supplies descriptive flexfield context information. WF_EVENTS, WF_EVENT_SUBSCRIPTIONS, WF_EVENT_T, and WF_ROUTING_RULES are consulted to resolve event definitions and notification routing. DUAL and DBMS_SQL support dynamic SQL and scalar evaluation, and PLITBLM is used for PL/SQL index-by table handling.

Usage Notes

EDR_STANDARD is typically invoked from Oracle Forms event handlers and menu actions when a user initiates a transaction that falls under e-record or signature control, and from Oracle Workflow function activities that evaluate signature requirements during approval processing. Custom code should treat the package as an internal EDR utility rather than a public API; calls to GET_AMERULE_INPUT_VALUES should be migrated to GET_AMERULE_INPUT_VARIABLES because the former is explicitly documented as deprecated. The presence of DBMS_SQL and the temporary query table indicates that PSIG_QUERY performs dynamic, set-based evaluation and should be called with care in high-concurrency environments. Because the package is AUTHID CURRENT_USER, grants and synonyms must be verified during upgrades from 12.1.1 to 12.2.2, and dependent customizations should be revalidated after patching since 18 other packages reference it.