Search Results validate_payload_forms

Overview

EDR_ERES_EVENT_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, first shipped in its current form around the 12.0.x release and still active in 12.1.1 and 12.2.2. It belongs to the Oracle E-Records (EDR) product family and is documented under the ETRM category BUSINESS_ENTITY EDR_EVIDENCE_STORE. The package exposes the public API surface used to raise e-signature events and related events in deferred mode, meaning that evidence records are queued and processed rather than immediately written synchronously during a user transaction.

The package declares AUTHID CURRENT_USER and relies on the standard global constants and type definitions typical of EBS public APIs, including a global package name constant and an indexed-by-binary-integer table of e-record identifiers. Its central data structure is the ERES_EVENT_REC_TYPE record. As reflected in the header comments for Bug 3136403 and Bug 3893101, this record was deliberately denormalized: instead of embedding a workflow parameter table, it exposes up to seven PARAM_NAME_n / PARAM_VALUE_n pairs plus an EVENT_XML CLOB. This design lets callers describe an evidence event and its payload without directly manipulating FND_WF_EVENT structures, while still supporting rich XML content.

The package is referenced by twelve other packages, which confirms its role as a shared service layer for evidence-store event publication rather than an end-user-facing module.

Key Procedures and Functions

• VALIDATE_ERECORD — Validates a supplied e-record identifier, confirming that the referenced evidence record exists and is eligible for the requested event.
• VALIDATE_PAYLOAD — Validates the payload parameters supplied for an e-signature event, ensuring names and values conform to the expectations of the evidence store.
• VALIDATE_PAYLOAD_FORMS — A Forms-oriented variant of payload validation, used when the calling context is an Oracle Forms block rather than a programmatic caller.
• GET_EVENT_DETAILS — Retrieves the details of an already-registered event, allowing callers to inspect event metadata and status.
• RAISE_ERES_EVENT — The primary event publication routine; raises an e-signature or related EDR event in deferred mode using the denormalized ERES_EVENT_REC_TYPE structure.
• RAISE_INTER_EVENT — The routine most directly associated with the search term raise_inter_event; it raises an intervening or intermediate event, typically used to interpose an additional evidence step between other events in a signing or approval flow.
• GET_ERECORD_ID — Returns the e-record identifier associated with a given event, allowing callers to correlate an event with its persisted evidence record.

Tables Accessed

• EDR_PSIG_DOCUMENTS — Stores the signature/evidence documents against which events are raised and validated.
• WF_EVENTS — The Oracle Workflow event registry, read to confirm that the named event exists and is subscribable.
• WF_EVENT_SUBSCRIPTIONS — Defines the subscriptions that determine which deferred agent processes a raised event.
• PLITBLM — The generic PL/SQL index-by table with LOB support used as an intermediate buffer, particularly for payload and XML handling.

Usage Notes

EDR_ERES_EVENT_PUB is invoked by Oracle Forms-based e-signature flows, by concurrent programs that drain deferred event queues, and by custom code integrating with the E-Records evidence store. Callers that need to insert an additional evidence step into an existing signing chain typically call RAISE_INTER_EVENT, while standard evidence publication uses RAISE_ERES_EVENT. Because processing is deferred, callers should not assume the evidence record is immediately visible; GET_ERECORD_ID and GET_EVENT_DETAILS are used to reconcile status afterwards. The authoritative functional reference remains Metalink Note 268669.1, Oracle E-Records API User's Guide.