SAP ERP ==> SAP Basis

The output device is change by one inexistent when the output is executed.   When the user creates the outbound delivery the output is determinate, but not prints yet (status not processed). Here the output device is correct and is the one set in the condition record. Then, when the user executes the post good issue the output device is change by one inexistent call SIS0, and the field Spool request: Name is complete with the name of the message. 

Please first check the entry in table NAST, field LDEST. Is it correct after saving the delivery ?

I think the best is then to set a breakpoint during the creation of the goods issue in function module MESSAGING in order to find out if the printer is changed here. If this does not help please goto TA V/34, find out the used print program and set a breakpoint there (normally at the beginning of form ENTRY).

Spool Consistency Check 

RSPO1041 is the report to delete the old spool request,

RSPO1043 is the report to check the consistency of spool DB

Try to schedule these report in SA38 with variants, schedule once or as periodically.

You can use the spool consistency check to check whether tables that contain spool requests, output requests, and output data are inconsistent. If necessary, you can delete inconsistencies.

Along with deleting old spool requests, the spool consistency check is one of the most important functions for maintaining the SAP spool database. You should perform the spool consistency check regularly in the background. 

As the spool consistency check affects performance, you should schedule it either during the night or at the weekend. 

You require an administrator authorization.

The spool consistency check checks the following table entries for spool requests:

- Header entry in table TST01 (TemSe objects)

- Object associated with the header entry; it can be stored in the file system or in the database table TST03 (TemSe data of the object)

- Entry in table TSP01 (spool requests)

- Entry in table TSP02, if output requests exist

You can identify and delete inconsistencies both in the background and in dialog:

- You can use report RSPO1043 to identify and delete inconsistencies in the background. This has the following advantages:

- Inconsistencies are only deleted if they appear during repeated runs. There is therefore no danger of accidentally deleting temporary inconsistencies.

 - Temporary inconsistencies are not actual inconsistencies and must not be deleted. Temporary inconsistencies may occur, for example, if a user is writing data to the TemSe during the consistency check.

- No timeouts

- You can use transaction SPAD or report RSPO0043 to display and delete inconsistencies in dialog. However, we do not recommend these methods for your production systems due to the following disadvantages:

- Accidental deletion of temporary inconsistencies
Only after a minimum of a second check can you determine whether an inconsistency was only temporary, because, for example, another user was writing to the TemSe during the check, or whether the check has found an actual inconsistency.

- Timeouts

For more information about spool consistency checks, see SAP Notes 48400 and 98065 in the SAP Service Marketplace.

Only delete inconsistent spool requests with the spool consistency check and not with the TemSe consistency check due to the following disadvantages of the TemSe consistency check: 

-  The TemSe consistency check does check the header entries in table TST01 and associated objects only for spool requests, but rather for all TemSe objects. 

-  Deleting TemSe inconsistencies includes only the header entry in TST 01 and the actual TemSe object. However, to delete a spool request, you must also remove the entry in TSP01 (spool requests) and, if an output request exists, in table TSP02 (output requests).

Relevance Contents:

• List Of Output Device Type Table
• Auto Convert Spool Output To PDF File
• Change Output Device Settings At Runtime

SAP Basis Admin Books
SAP System Administration, Security, Authorization, ALE, Performance Tuning Reference Books

SAP Basis Tips

• SAP BC Tips and Basis Components Discussion Forum
• Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES