Search Results fnd_table_of_varchar2_255




Overview
Explore in AI Chat

Overview

EDR_ADHOC_USER_PVT is a private PL/SQL package in the APPS schema of Oracle E-Business Suite, belonging to the EDR (E-Records / Electronic Records and Signatures) product family used by Oracle's regulatory compliance framework. Its classification as a "PVT" package indicates it is an internal helper package, not a public API intended for direct customer invocation. It supports the ad hoc user and signer-list maintenance behavior associated with electronic signature configuration, providing the low-level logic that public EDR packages and Oracle Forms call during signature setup and maintenance. The package is documented as VALID in ETRM for both 12.1.1 and 12.2.2, confirming availability across the two release lines.

Key Procedures and Functions

The ETRM metadata documents a single public subprogram for this package:

  • UPDATE_SIGNERLIST — The procedure responsible for maintaining the signer list associated with electronic signature definitions. It encapsulates the insert, update, or removal logic needed to keep the list of authorized signers consistent with the signature definition being configured or modified. Parameter lists are not documented in the ETRM excerpt and should not be assumed; callers must reference the package specification for exact signatures.

Because the package is classified as PVT, UPDATE_SIGNERLIST is intended for use by other EDR packages and forms within the product, not as a supported external API.

Tables Accessed

The documented table references for this package are:

  • EDR_ESIGNATURES — The base electronic signature definition table. The package reads the signature definition context to determine the correct signer list to operate against.
  • EDR_ESIGNATURES_S — The corresponding translated (TL) table holding language-specific signature definition text. Access here ensures the signer list update is applied within the appropriate language context.
  • DUAL — Used for singleton SELECT statements, typically for sequence value retrieval, date/sysdate checks, or conditional validation logic within the procedure.
  • PLITBLM — A PL/SQL index-by table of VARCHAR2 used as an in-memory collection to pass or stage multi-row signer data between the package and its caller before committing to the EDR tables.

The dependency listing also shows the package references the APPS synonym for FND_TABLE_OF_VARCHAR2_255 and the SYS.STANDARD package, consistent with standard collection-based PL/SQL constructs.

Usage Notes

EDR_ADHOC_USER_PVT is not exposed as a customer-facing public API. Typical invocation paths are:

  • Internal EDR package calls — Public EDR packages that manage electronic signature setup delegate signer-list maintenance to UPDATE_SIGNERLIST rather than performing the DML directly, keeping the logic centralized.
  • Oracle Forms — The EDR signature configuration forms (responsibility-specific) call this procedure when a user adds or modifies signers on a signature definition and saves the record.
  • Custom extension code — Because the package is documented and marked VALID, technically it can be called from custom code, but doing so is unsupported. Sites with strong governance requirements generally restrict direct calls to PVT packages.

Because ETRM lists no dependencies on other packages beyond the tables above, EDR_ADHOC_USER_PVT is a leaf-level utility with no downstream packages depending on it. Customizations should avoid binding to it directly; instead, use the supported public EDR signature APIs. Runtime errors from this package during signer-list changes will typically surface through the calling form or concurrent program, and diagnosis should focus on EDR_ESIGNATURES and EDR_ESIGNATURES_S data integrity, language-row consistency, and concurrency on the signature definition being modified.