Search Results check_timeout




Overview

EDR_PSIG_PAGE_FLOW is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, documented under the Oracle EDR (E-Records and E-Signatures) product family, which underpins the Oracle Process Manufacturing (OPM) quality and electronic signature framework. The package functions as the page-flow orchestration layer for electronic signature (e-signature) processing. Its central responsibility is to manage the lifecycle of an e-signature request from the point it is routed for approval through to its terminal outcome, driving the underlying Oracle Workflow notification and activity model that carries the approval to the designated responder.

The package is classified as OTHER in the ETRM metadata, meaning it is an internal framework component rather than a public, customer-facing API. It is consumed by a cluster of higher-level EDR and GMD/GMI utility packages, confirming its position as shared infrastructure underneath the e-records signature and post-operation logic.

Key Procedures and Functions

The documented interface exposes 17 procedures and functions:

Tables Accessed

Through APPS synonyms the package reads and writes the EDR signature tables EDR_ERECORDS, EDR_ESIGNATURES, EDR_PSIG_DETAILS, EDR_PSIG_DOCUMENTS and EDR_TRANS_ACKN, which store the e-record, signature, signature detail, document, and transaction acknowledgement data. It references FND_USER for signer identity. Oracle Workflow tables WF_EVENT_T, WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, WF_NOTIFICATIONS, WF_NOTIFICATION_ATTRIBUTES and WF_PARAMETER_LIST_T supply the notification and activity state, while PLITBLM provides the standard PL/SQL index-by-table utility for parameter handling.

Usage Notes

EDR_PSIG_PAGE_FLOW is not intended for direct customer invocation. It is referenced by eight APPS packages, including EDR_ATTACHMENTS_GRP, EDR_FWK_TEST_POST_OP, GMD_ERES_POST_OPERATION, GMD_QC_ERES_CHANGE_STATUS_PVT, GMD_QC_ERES_UTILS, GMI_ERES_UTILS, QA_ERES_DEFER and itself. These callers invoke it during e-signature approval flows triggered from OPM quality and e-records transactions, with the workflow notification engine acting as the runtime transport. Customizations should not modify this package; extensions should call the higher-level EDR packages instead.