Sap Spool Request Status Completed But No Printout

18.09.2019 admin

BOM To Microsoft ExcelThe BOM to Microsoft Excel plugin is run by DriveWorksduring the model generation process. (DriveWorks Administrator,DriveWorks User, DriveWorks Autopilot). It traverses the SOLIDWORKSassembly of a newly generated clone (regardless of whether thecomponents are captured by DriveWorks or not) to retrieve the BOMinformation (Assembly Structure and Properties) and inserts thedata into a new Excel file (based on a template) and saves the filein the Assemblies folder.This plugin is machine specific and should be installed on eachmachine where models can be generated.

Sap Spool Request Status Completed But No Printout

Sap Spool Request Status Completed But No Print Out Form
Sp01 Sap

Is there way so I could remove the creation of spool request when I execute program in background (the standard one--Execute in Background)? I don't want to create spool.

Thanks in advance!

Hello,Some spool requests are completed with status 'Completed(Problem)'. When we check the output Request Logs find below things:Print request processing logThe host spool is reporting errorsThis request may not have been printed. Status unknownMost im. Jun 14, 2011 - What is the difference between spool request and output request? Completed (The output request printed successfully). Waiting (Spool request is in waiting status and spool system has not yet. ( This minus status means that the spool request is not yet sent to the host system and no output request exists). Hello Friends, I am facing one problem related to Spool Request, which is generated through Scheduled Background Jobs (scheduled by funcional people). The Background Job is having status “completed” when analyzing it. But, its associated Spool Request is showing “waiting” Status, with “Frontend unavailable” as Status Text. Here is the brief status of that Spool.

Suncatcher

4,3042 gold badges29 silver badges61 bronze badges

Czarinaaaaa29Czarinaaaaa29

2 Answers

After clicking on Execute in background, at the options popup, give the printer name NULL OR search similar in the printer list.

For additional information, see note:

181571 - Output device NULL

It states:

Similar to /dev/zero on UNIX, the output to a device named NULL has the effect that no data is created in the spool system when you print ABAP lists.

szakoszako

1,1841 gold badge6 silver badges12 bronze badges

Solution is, when you are displaying report/alv in your program, you have to put condition 'IF sy-batch IS INITIAL'. Inside this condition, put the display report so that when you execute report in Background (SY-BATCH EQ 'X'), it would not generate spool.

Hope this helps to anyone who will experience the same.

Czarinaaaaa29Czarinaaaaa29

Not the answer you're looking for? Browse other questions tagged sapjobsspool or ask your own question.

Symptom

You are using BRF+ (S/4Hana default) output determination logic.
You set up rules in transaction OPD to determined an output record whose dispatch time is 1-immedate in a purchasing document which uses BRF+ technology. This would mean that immediately at the document's saving/approving the output determined and processed too (sending data to vendor).
The status of the output message is 'completed' , but in SP01 at the spool you see error 'frontend unavailable'.

You also notice that for example at a purchase order's case, if you set the dispatch time to 2-scheduled, then you can print manually via ME9ff a similar case.

Environment

Product

SAP S/4HANA all versions

Keywords

BRF+, BRFPlus, BRF Plus, OPD, front end unavailable, SP01, spool, failed, error, printing, nachricht, me21n, me22n, me31l, me32l, me31k, me32k, completed, APOD_D_OR_ITEM, , KBA , MM-PUR-GF-OC , Message determination and printing , How To