Search Results edr_eresmanager_t_s

Overview

EDR_ERES_EVENT_PVT is a private (PVT-classified) PL/SQL package body in the APPS schema that belongs to the Oracle E-Business Suite EDR (Electronic Data Records / E-Records) module supporting the ERES (Electronic Records and Electronic Signatures) framework. Its principal business responsibility is to raise and manage workflow business events associated with electronic records, whether those records are captured through e-signature transactions or processed as part of a batch. The package acts as the event-handling engine behind the ERES Manager: it builds the payload that describes an e-record event, resolves the subscribers that should be notified, determines the approvers, creates the appropriate workflow process, and dispatches the event through the Oracle Workflow event system. Because it is a private package body, it is intended to be called from within the EDR module — primarily from the public package EDR_ERES_EVENT_PUB — rather than directly by external applications. In EBS 12.1.1 and 12.2.2 the object is documented as VALID and is not referenced by any other database object, reinforcing its role as an internal implementation unit behind a published API surface.

Key Procedures and Functions

The package body exposes eight documented program units, each handling a distinct stage of the e-record event lifecycle:

• RAISE_EVENT — The central entry point that assembles event attributes and raises the ERES workflow event.
• RAISE_TABLE — A variant used when multiple e-records are supplied, allowing events to be raised in a table-driven manner.
• GET_SUBSCRIPTION_GUID — Resolves the unique identifier of the workflow event subscription that governs notification for the event in question.
• CREATE_PAYLOAD — Constructs the XML or parameter payload that carries the e-record context to event subscribers and downstream processes.
• GET_EVENT_APPROVERS — Determines which approvers are associated with the event, supporting the approval-routing requirements of the ERES framework.
• CREATE_MANAGER_PROCESS — Creates the ERES Manager workflow process instance used to track and manage the e-record event.
• DELETE_ERECORDS — Removes processed e-records from the working tables once the event has been handled.
• GET_EVENT_DETAILS — Retrieves the descriptive details of an event, used when building payloads or reporting event context.

Tables Accessed

The package operates on the core ERES and Workflow tables, all accessed through APPS synonyms:

• EDR_ERESMANAGER_T and EDR_ERESMANAGER_T_S — The ERES Manager header and its translated/status companion table; these hold the manager process records created and updated by the package. The user query term "edr_eresmanager_t_s" corresponds directly to this object.
• EDR_ERESPARAMETERS_T — Stores the configuration parameters that drive e-record event processing.
• EDR_PROCESS_ERECORDS_T — Holds the e-records being processed, and is the table from which records are removed by DELETE_ERECORDS.
• EDR_PSIG_DOCUMENTS — Contains the electronic signature documents linked to the e-records.
• EDR_RAW_XML_T — Stores the raw XML content used when building event payloads.
• FND_APPLICATION and FND_USER — Provide application and user context for the event.
• WF_EVENTS, WF_EVENT_SUBSCRIPTIONS, and WF_PARAMETER_LIST_T — Oracle Workflow tables used to identify subscriptions, format parameter lists, and raise the event.
• DUAL and PLITBLM — Standard PL/SQL utility references.

Usage Notes

EDR_ERES_EVENT_PVT is invoked indirectly through the public API EDR_ERES_EVENT_PUB and is also referenced by three other packages within the EDR module. Typical invocation scenarios include raising an event when an e-record requires signature or approval, creating the associated ERES Manager workflow process, and cleaning up processed e-records after completion. Customizations should call the public APPS package rather than this private body, since the procedures here are internal and their signatures are not a supported extension point. Sites extending ERES behavior should subscribe custom workflow processes to the raised events using the Oracle Workflow subscription model surfaced by GET_SUBSCRIPTION_GUID, and should treat CREATE_PAYLOAD and GET_EVENT_DETAILS as the authoritative sources of event context. Because the body depends on EDR_UTILITIES, FND_MSG_PUB, FND_API, and the Workflow event APIs, validations and messaging follow standard EBS API conventions, with errors surfaced through the FND message stack.