Categories
- ABAP Development
- BASIS Security
- BASIS Administration
- BASIS Database
- BI - Business Intelligence
- CRM Customer Relationship
- EP Enterprise Portals
- FICO Financials
- HCM HR Human Capital
- JAVA Development
- Management Accounting
- Master Data Management
- MM Material Management
- PLM Customer Service
- PLM Data Management
- PLM Plant Management
- PLM Project Management
- PLM Quality Management
- PP Production Planning
- SAP Analytics
- SAP ERP Fundamentals
- SCM Discreet Mfg
- SCM Inventory Warehouse
- SCM Logistics Execution
- SCM Process Mfg
- SCM TM Transportation
- SD Sales and Distribution
- SMI Solution Manager
- SOA Service Architecture
- SRM Supplier Relationship
- XI PI Process Integration
Most Rated Articles
»
BASIS Administration
Rate Author : Current :
2.87 /5
Rate this Article : Current :
2.06 /5
Managing Spool and Output Requests
To maintain spool and output devices, call the Output Controller (transaction SP01 or choose System -> Services -> Output Control). If you only want to check the status of your own spool requests, choose System -> Own Spool Requests (transaction SP02).
Transaction SP01 provides many selection criteria for selecting particular spool or output requests. Every user can individually and easily define the selection criteria that he or she requires using the Further Selection Criteria... function.
It is even possible to monitor spool and output requests on other SAP systems. To do this, enter a valid RFC connection in the System Name field. If this field remains empty, all systems that were selected for remote monitoring using transaction RZ20 (table ALCONSEG) are addressed.
The displayed list shows all spool or output requests that match your selection criteria. The list is created using the SAP List Viewer (ALV). This allows you to change the appearance of the list as you desire. This means that you can show and hide columns, sort columns, or create variants.
The following indicators specify the status of a spool request:
-
Not yet sent to the operating system (no output request exists).
+
Spool request is still being created (stored in spool system).
Waiting
The output request has not yet been processed by the spool system. Proc.
A spool work process is formatting the output request for printing.
Print.
The output request is being printed by the operating system spooler. If the query at the host spooler is not activated, this status is shown for around a minute.
Compl.
The output request has been printed. If the query at the host spooler is not activated, the status changes to Compl. as soon as the output request is transferred to the host spooler.
There are output requests with various statuses.
Problem
Indicates an error not of a serious nature (such as incomplete character set). This request was still printed.
Error
Indicates a serious error (such as a network error).
Time
A particular time was specified for the output of the request by the request creator.
If you select the status of a spool request, the system displays the associated output requests. For the output requests of multiple spool requests, select these and choose Output Requests (or choose F5).
For every unsuccessful output request, a log is written that you can use for error analysis.
Regular deletion of old spool requests and monitoring the consistency of the spool database are system administration tasks.
To delete old spool requests, schedule the ABAP program RSPO1041 with an appropriate variant as a periodically running background job. For more information about RSPO1041, see SAP Note 130978.
To check the consistency of the spool database, schedule the ABAP program RSPO1043 with an appropriate variant as a daily running background job. For more information about RSPO1043, see SAP Note 98065.
For information about the reorganization of TemSe and spool, see also SAP Note 48400.
Overview: Other Print Scenarios
Here is an overview of other print scenarios:
External Output Management Systems (OMS) can be addressed from the SAP system using a defined interface (BC-XOM) (access method E). This method is of particular interest if you have a very large volume, or the output of multiple systems (SAP systems and others) is to be centrally controlled and monitored. For a list of all certified products, see http://www.sap.com/softwarepartnerdir (Software Partner and Product Directory).
Since SAP Basis 4.0B (as of a particular kernel and Support Package status), you can send print output by e-mail to a user (access method M). The e-mail is sent using SAPconnect. For more information, see SAP Notes 311037 and 513352.
A user can also be connected to an SAP system from a Web browser through the SAP GUI for HTML. A connection of this type can be made directly using the SAP system (with the integrated ITS, as of SAP Web AS 6.40), through the middleware (Web server and SAP ITS) of the SAP system, or as part of an enterprise portal (such as the SAP Enterprise Portal). What options does this user have for print output? One option is the previously described output by e-mail. On the other hand, Web printing does not require an e-mail client. You can use Web printing as of SAP Basis 4.6B. To do this, the system administrator must provide a printer with device type PDF1 and access method F. If the user selects this printer, a PDF document appears in a new window. The user can then print this PDF document. SAP Note 351230 describes the exact prerequisites and contains additional information about Web printing.
To maintain spool and output devices, call the Output Controller (transaction SP01 or choose System -> Services -> Output Control). If you only want to check the status of your own spool requests, choose System -> Own Spool Requests (transaction SP02).
Transaction SP01 provides many selection criteria for selecting particular spool or output requests. Every user can individually and easily define the selection criteria that he or she requires using the Further Selection Criteria... function.
It is even possible to monitor spool and output requests on other SAP systems. To do this, enter a valid RFC connection in the System Name field. If this field remains empty, all systems that were selected for remote monitoring using transaction RZ20 (table ALCONSEG) are addressed.
The displayed list shows all spool or output requests that match your selection criteria. The list is created using the SAP List Viewer (ALV). This allows you to change the appearance of the list as you desire. This means that you can show and hide columns, sort columns, or create variants.
The following indicators specify the status of a spool request:
-
Not yet sent to the operating system (no output request exists).
+
Spool request is still being created (stored in spool system).
Waiting
The output request has not yet been processed by the spool system. Proc.
A spool work process is formatting the output request for printing.
Print.
The output request is being printed by the operating system spooler. If the query at the host spooler is not activated, this status is shown for around a minute.
Compl.
The output request has been printed. If the query at the host spooler is not activated, the status changes to Compl. as soon as the output request is transferred to the host spooler.
There are output requests with various statuses.
Problem
Indicates an error not of a serious nature (such as incomplete character set). This request was still printed.
Error
Indicates a serious error (such as a network error).
Time
A particular time was specified for the output of the request by the request creator.
If you select the status of a spool request, the system displays the associated output requests. For the output requests of multiple spool requests, select these and choose Output Requests (or choose F5).
For every unsuccessful output request, a log is written that you can use for error analysis.
Regular deletion of old spool requests and monitoring the consistency of the spool database are system administration tasks.
To delete old spool requests, schedule the ABAP program RSPO1041 with an appropriate variant as a periodically running background job. For more information about RSPO1041, see SAP Note 130978.
To check the consistency of the spool database, schedule the ABAP program RSPO1043 with an appropriate variant as a daily running background job. For more information about RSPO1043, see SAP Note 98065.
For information about the reorganization of TemSe and spool, see also SAP Note 48400.
Overview: Other Print Scenarios
Here is an overview of other print scenarios:
External Output Management Systems (OMS) can be addressed from the SAP system using a defined interface (BC-XOM) (access method E). This method is of particular interest if you have a very large volume, or the output of multiple systems (SAP systems and others) is to be centrally controlled and monitored. For a list of all certified products, see http://www.sap.com/softwarepartnerdir (Software Partner and Product Directory).
Since SAP Basis 4.0B (as of a particular kernel and Support Package status), you can send print output by e-mail to a user (access method M). The e-mail is sent using SAPconnect. For more information, see SAP Notes 311037 and 513352.
A user can also be connected to an SAP system from a Web browser through the SAP GUI for HTML. A connection of this type can be made directly using the SAP system (with the integrated ITS, as of SAP Web AS 6.40), through the middleware (Web server and SAP ITS) of the SAP system, or as part of an enterprise portal (such as the SAP Enterprise Portal). What options does this user have for print output? One option is the previously described output by e-mail. On the other hand, Web printing does not require an e-mail client. You can use Web printing as of SAP Basis 4.6B. To do this, the system administrator must provide a printer with device type PDF1 and access method F. If the user selects this printer, a PDF document appears in a new window. The user can then print this PDF document. SAP Note 351230 describes the exact prerequisites and contains additional information about Web printing.