How To Fix SPRX123 - Document not found (path &2&3&4, error code &1)

SPRX123 - Overview

• Message type: E = Error

• Message class: SPRX - Proxy Generation

• Message number: 123

• Message text: Document not found (path &2&3&4, error code &1)

What causes this issue?

The error occurred while calling cl_gui_frontend_services=>gui_upload;
the file with the specified path could not be loaded. Error code 1
generally means that the file does not exist.
The following are possible error codes:
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer ,, = 4
invalid_type,,,,,, = 5
no_authority,,,,,, = 6
unknown_error ,,,, = 7
bad_data_format ,,,, = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
not_supported_by_gui = 17
error_no_gui = 18
OTHERS = 19

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

SPRX123 - Details

• The SAP error message SPRX123, which states "Document not found (path &2&3&4, error code &1)," typically indicates that the system is unable to locate a specific document or file that is expected to be present in the specified path. This error can occur in various contexts, such as when dealing with document management systems, archiving, or file retrieval processes.
  Causes:
  
  Incorrect Path: The specified path in the error message may be incorrect or may have been changed.
  Document Deletion: The document may have been deleted or moved to a different location.
  Authorization Issues: The user may not have the necessary permissions to access the document.
  System Configuration: There may be issues with the configuration of the document management system or archiving settings.
  Network Issues: If the document is stored on a network drive, there may be connectivity issues preventing access.
  
  Solutions:
  
  Verify the Path: Check the path specified in the error message to ensure it is correct. Make