Customization › SAP Interface › SAPSPEX Error Codes and SAP Log

SAPSPEX Error Codes and SAP Log

Processing errors cause printing to be abnormally terminated, so an entry is made in the SAP log. This exit logs the following errors:

Oxxx

ESFOPEN call has failed with a STATUS=PE. xxxx indicates which field in the ESFOPEN parameter list is in error.

OPxx

ESFOPEN call has failed. xx is the status code returned.

WRxx

ESFWRIT call has failed. xx is the status code returned.

CLxx

ESFCLOS call has failed. xx is the status code returned.

NOEP

SAPSPEX exit is unable to locate the entry point for ESFOPEN. This is probably caused by not including the CA Spool call interface routines (AESFPRIV) during link-edit.

NOFI

SAPSPEX exit is called with the W request type, but no file has yet been opened.

NOPA

SAPSPEX exit is called, but the parameter lists created by the SAPSPEI exit could not be found.

NOST

Pointer passed from exit SAPSEI to exit SAPSPEX points to invalid storage. This means that printing of the file is abnormally terminated.