Results for “edr_erecord”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The concurrent program EDR_TEMP_DATA_CLEANUP_P is an administrative utility belonging to the EDR – E-Records product within Oracle E-Business Suite. Its user-facing name is E-records Temporary Data Cleanup, and it is shipped in an enabled state. The program performs housekeeping against transient staging structures used by the E-Records feature set, removing residual rows that accumulate as electronic records, signatures, and associated workflow artifacts are created and processed.

According to the ETRM metadata, the program's stated purpose is to "Clean up temporary tables like EDR_ERECORD, EDR_ESIGNATURE and so on." The EDR_ERECORD table referenced in that description is directly relevant to the search term edr_erecord: it functions as a working or interim store for e-record transactions before they are promoted to their final persisted state. Left unmanaged, these staging tables can grow substantially, degrading query performance and inflating storage. This concurrent program provides the supported, Oracle-delivered mechanism for purging that data rather than relying on manual DML.

Execution Details

The documented execution attributes for the program are as follows:

• Product: EDR – E-Records
• User Name: E-records Temporary Data Cleanup
• Enabled: Yes
• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: EDR_TEMP_DATA_CLEANUP
• Execution Filename: EDR_UTILITIES.TEMP_DATA_CLEANUP

Because the execution method is a PL/SQL stored procedure, the runnable logic resides in the package EDR_UTILITIES, specifically the procedure TEMP_DATA_CLEANUP. The Standard argument method indicates that parameters, where defined, are passed positionally rather than through a token-substitution or descriptive-flexfield scheme.

How to Run

The program is submitted through the standard Oracle EBS concurrent request flow. A user with the appropriate EDR responsibility navigates to Requests > Run, selects E-records Temporary Data Cleanup from the list of values, optionally adjusts any parameters presented, and submits the request. Because the definition is enabled and the executable already exists, no additional setup is required in a standard installation.

General guidance applies as with most cleanup utilities:

• Schedule the program during a low-activity window, since purging large staging tables can hold locks and generate significant undo.
• Review any parameters before submission; leaving defaults typically targets the standard retention window, while narrower criteria reduce transaction volume.
• Confirm there are no in-flight e-record or e-signature transactions that depend on the temporary rows being removed.
• Monitor the concurrent request log for row counts processed and for any errors raised by the underlying procedure.

Related Objects

The program operates primarily against the temporary structures named in its description, notably EDR_ERECORD and EDR_ESIGNATURE, along with other transient E-Records tables covered by the "and so on" clause of the metadata. These tables are populated by the E-Records capture and e-signature flows during routine user activity. Administrative equivalents in adjacent modules include generic temporary-table cleanup programs, but this specific utility is scoped to the EDR schema. When investigating records that appear to have disappeared, administrators should verify whether this cleanup program has recently run, as it removes data that the E-Records application treats as non-permanent.