Basis Errors and Solutions

Symptom

You use an external storage system (content server) to store documents. You can no longer print using access method ‘M’ (generating e-mails using the SAP spool in accordance with note 513352).
The output request has the status incorrect (error in the ABAP processing), and the following entries appear in the trace of the spool work process:
M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 11613]
A ABAP/4 Program SAPLSHTTP .
A Source LSHTTPU16 Line 79.
A Error Code RPERF_ILLEGAL_STATEMENT.
A Module $Id: //bas/620/src/krn/runt/abfunc.c#20 $ SAP.
A Function ab_jrfc Line 5195.
M *** ERROR => caught error RPERF_ILLEGAL_STATEMENT: Statement
RFC-SYSTEM RFC_ID id RFC_VALUE value not permitted in current status
S *** ERROR => internal mode aborted [rsporperf.c 72]
S *** ERROR => FRONTEND_MAIL(RSPOLPRF) aborted [rsporperf.c 148]
S *** ERROR => calling mail form failed (rc=99) [rspomail.c 109]

Other terms

RSPO_FILE_TO_OFFICE, SO_ATTACHMENT_INSERT_API1, SO_ATTACHMENT_INSERT
SO_CONTENT_TO_KPRO_PUT, SDOK_PHIO_STORE_CONTENT

Reason and Prerequisites

If you use an external storage system, data is transferred using HTTP protocol. The roll-out of the user context must be guaranteed. However, this is not possible in the spool work process. A roll-out may occur for various reasons (for example, with memory bottlenecks). However, it is not useful to change the memory settings in this case.

Solution

Use other options as access method ‘M’ to send data by e-mail (see Note 513352).
If this is not possible, implement the attached correction instructions or import the relevant Support Package. Then use the report RSPO0021 to activate the optionMAIL_FROM_DIALOG. When you do this, a dialog work process takes over the sending of the requests. We recommend that you define at least two spool work processes on an application server that operates an output device with access method ‘M’; this avoids possible blocks of other print methods.