Search Results attach_checklist




Overview

EDR_ISIGN_CHECKLIST_PVT is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Oracle iSign and Evidence Store functionality. Its principal business function is to determine whether an electronic signature event requires an associated checklist, to verify the presence of a checklist for a given iSign file, and to manage the attachment and removal of checklist content against evidence store entities. Within the Oracle EBS 12.1.1 and 12.2.2 file systems, the package resides in the EDR product family and is declared with AUTHID CURRENT_USER, meaning that its database objects are resolved using the privileges of the invoking user rather than the package owner.

The package is classified as PVT (private), indicating that it is an internal implementation utility not intended for direct invocation by external application code. It is referenced by one other package in the documented metadata, confirming its role as a supporting routine consumed by higher-level iSign processing logic.

Key Procedures and Functions

The documented package exposes four procedures:

  • IS_CHECKLIST_REQUIRED — Evaluates checklist setup for a supplied event name and event key, and returns a status flag indicating whether a checklist is required. When a checklist is required, it also returns the checklist name and checklist version as output values.
  • IS_CHECKLIST_PRESENT — Accepts an iSign file identifier and reports whether a checklist is available for that file. The output status uses a simple Y/N convention, where Y indicates the checklist is present and N indicates it is not available.
  • ATTACH_CHECKLIST — Attaches a checklist to the evidence store entity when one is available for the supplied iSign file. It returns a status value of S (successful) or E (error) to indicate the outcome of the attachment attempt.
  • DELETE_CHECKLIST — Removes an attached checklist from the evidence store entity, complementing the attachment routine for lifecycle management of checklist documentation.

Tables Accessed

The package accesses several tables through APPS synonyms, reflecting its integration with Oracle Workflow, Oracle Application Object Library, and Oracle Approvals Management:

  • WF_EVENTS, WF_EVENT_SUBSCRIPTIONS, and WF_EVENT_T — Used to resolve the Oracle Workflow event context that drives checklist requirement determination, since checklist rules are keyed on event name and event key.
  • FND_APPLICATION — Provides application context information, typically to validate or identify the owning application for the event or checklist configuration.
  • FND_ATTACHED_DOCUMENTS — Stores the document attachments that constitute the checklist linkage to the evidence store entity; the ATTACH_CHECKLIST and DELETE_CHECKLIST procedures operate against this table.
  • AME_CALLING_APPS — Supports integration with Oracle Approvals Management, relevant where checklist requirements intersect with approval routing.
  • PLITBLM — The standard PL/SQL internal table used for parsing and string manipulation during event key processing.

Usage Notes

Because EDR_ISIGN_CHECKLIST_PVT is a private package, it is not intended to be called directly from forms, concurrent programs, or custom extensions. It is invoked internally by the enclosing iSign checklist logic that reacts to Oracle Workflow business events. The typical invocation path is event-driven: a business event such as an item creation is raised, the higher-level package calls IS_CHECKLIST_REQUIRED to evaluate setup, and depending on the result, IS_CHECKLIST_PRESENT, ATTACH_CHECKLIST, or DELETE_CHECKLIST are executed to maintain the checklist state against the evidence store file. Custom developers should target the public wrapper package rather than calling this private utility directly, and any extension work should preserve the AUTHID CURRENT_USER resolution semantics and the standard S/E and Y/N return conventions documented above.