Search Results get_event_approvers

Overview

The APPS.EDR_ERES_EVENT_PVT package is the private implementation layer of the Oracle E-Business Suite Electronic Records and Electronic Signatures (ERES) event framework. It resides in the APPS schema and carries the PVT API classification, indicating that its procedures are intended for internal consumption by the paired public package EDR_ERES_EVENT_PUB and by other ERES processing components rather than by external customizations. Its primary business function is to manage the lifecycle of ERES events: constructing event payloads, resolving workflow subscriptions and approvers, raising workflow events, and maintaining the e-record manager process records that drive electronic signature and approval routing. It is a dependency of the public API EDR_ERES_EVENT_PUB, and it in turn depends on EDR_CONSTANTS_GRP, FND_API, FND_WF_EVENT, and the collection type FND_TABLE_OF_VARCHAR2_255. The package is referenced by EDR_ERES_EVENT_PUB, EDR_PSIG_RULE, and EDR_UTILITIES, confirming its role as a shared internal engine for ERES event handling.

Key Procedures and Functions

• RAISE_EVENT — Publishes an ERES event to the Oracle Workflow event system, serving as the core mechanism by which ERES activity is broadcast.
• RAISE_TABLE — Provides a table- or collection-oriented variant for raising ERES events, supporting bulk or multi-row event scenarios.
• GET_SUBSCRIPTION_GUID — Resolves the globally unique identifier for a workflow event subscription, used to target the correct subscriber configuration.
• CREATE_PAYLOAD — Builds the event payload passed to Workflow, assembling the parameter data required by subscribers.
• GET_EVENT_APPROVERS — Determines the approvers associated with an ERES event, typically by interrogating manager and subscription configuration.
• GET_EVENT_DETAILS — Retrieves the descriptive and parameter detail of a defined ERES event.
• CREATE_MANAGER_PROCESS — Creates the e-record manager process record used to track approval and signature processing.
• DELETE_ERECORDS — Removes stale or completed e-record entries from the ERES tracking tables.

Tables Accessed

• EDR_ERESMANAGER_T / EDR_ERESMANAGER_T_S — The base and secondary e-record manager tables, written by CREATE_MANAGER_PROCESS and cleared by DELETE_ERECORDS.
• EDR_ERESPARAMETERS_T — Stores event parameter definitions consumed during payload construction.
• EDR_PROCESS_ERECORDS_T — Holds the e-record processing records managed across the event lifecycle.
• EDR_PSIG_DOCUMENTS — Maintains signature document associations evaluated during approval routing.
• EDR_RAW_XML_T — Holds raw XML content used when assembling or parsing event payloads.
• WF_EVENTS / WF_EVENT_SUBSCRIPTIONS — Oracle Workflow event and subscription definitions that drive subscription GUID resolution and event raising.
• WF_PARAMETER_LIST_T — Workflow parameter collection used to supply event payload arguments.
• FND_USER / FND_APPLICATION — Identify users and owning applications for approver and event context resolution.
• DUAL / PLITBLM — Utility references used for PL/SQL constructs and low-level helpers.

Usage Notes

Because EDR_ERES_EVENT_PVT is a private package, it should not be invoked directly from customer extensions. Application logic and supported customizations call the public counterpart EDR_ERES_EVENT_PUB, which in turn delegates to this package. The package is typically executed in the context of ERES processing flows — electronic signature capture, approval routing, and e-record lifecycle management — and may be reached from EDR_PSIG_RULE and EDR_UTILITIES during the same runtime. Raise events are delivered through Oracle Workflow, so subscribers must be configured via WF_EVENT_SUBSCRIPTIONS for meaningful notification to occur. Because the procedures manipulate the EDR_* tracking tables and raise Workflow events, any diagnostic or repair activity should be performed with awareness of the Workflow agent and ERES audit trail. The package is marked VALID in both 12.1.1 and 12.2.2 environments, and no public parameter contract should be assumed from its signatures; integrators are directed to the public API layer.