Vous êtes sur la page 1sur 3

In your SAP system run program RSPO0075 to add the access method G.

Do the below configuration in SPAD and check the result...

1. Device Type : <Your printer model> Or "SWIN"
2. Device Class : Standard Printer
3. Host Spool Access Method: "G: Front End Printing with Control Tech."
4. Host Printer : _DEFAULT

In SM21 if the errors like for following occured:

Printer #### Temporarily Locked Due to Connection Problem
You need to mark the flag "Do not query Host Spooler for Output Status" in trans
action SPAD -> Tab Access Method.
Frontend Printing on Local Printers
In addition to the general print authorizations, every user requires the followi
ng authorizations for frontend printing:
Authorization object S_SPO_DEV, authorization field SPODEVICE, authorization %LO
Authorization object S_RFC:
Field Value
"Run Installation Check for R/3 Spool" from SPAD. Resolve if there is any error
or warning.
I suspect that because SAPLPD uses a front-end printing process, the spool proce
ss will continue to be engaged until the printout is successfully completed. Tha
t means that if a user is printing to their desktop and it's a 40 page report, n
othing else can use that spool process until it completes.
Review OSS note 15355
In accordance with discussion with Mr.Ashutosh on SAP BASIS issue in GRPL I here
by submit my understanding of the problem defination and the scope of work to be
System Scenario
Thin/Thick client Server environment with SAP R3 4.7
First Task
Problem Defination
1. Print information from first thin client routes to correct print machine but
SAPLPD open for the first thin client, print information executed from the secon
d thin client does not route to the respective printer instead triggered into th
e queue of the print machine of the first thin client.
2. SAPLPD remains open after the print, variable LP_CMD is set incorrectly or is
not set at all.
1. Import specified Basis Support Packages, depending on the release or implemen
t the correction instructions as of SAP Note 821519.
2. Import specified kernel patch depending on the release.
3. Install the latest SAP GUI
Advantage of New SAP GUI
- SAPLPD is no longer required. However, it is still delivered to
provide for older systems. As of SAPGUI 7.10, the shortcut to SAPLPD
in the Windows Start menu (created when you installed SAPGUI)
is deleted.
- There is no longer a printer selection box in the SAP system.
Instead, a Windows printer selection box is called directly
from the Control.
- The environment variable LP_CMD is no longer needed in the
terminal server environment.
Email attachment is the SAP Note 821519.

Second Task
Database Refresh from Production Server to Quality Server
Scope of Work
1. Backup of Production Data
2. Backup of Quality Data
3. Restore Production Data on Quailty Server
4. Examine the new Production Data on Quality Server
5. Check Transport System in the Landscape
6. Take Approval of users working on Quality Server

If the difficulty persists further troubleshooting is required.

Pleae kindly revert if more information is needed.
SAP BASIS Consultant
Check if you are using the latest version of SAPLP ( at least).
If it exists, delete the entry LPRINT_DEST in table TSPOPTIONS.
On the terminal server, set the system-wide environment variable LP_CMD to the v
alue \saplpd\saplpd -f&F -c&C -p&P (-P&P as of SAPLPD 4.24).
CAUTION: The word "saplpd" must not appear in uppercase letters in the above-men
tioned command.
If the GUI path contains blanks, set the entire expression - excluding the argum
ents in double quotation marks - for example: "c:\program files\sappc\sapgui\sal
pd\saplpd" -f&F -c&C -P&P.
Also It is better to register saplpd as a service, if you haven't done so. (See
below SAP note)
#42268 Operate SAPLPD as a service on Windows NT/2000/XP
If issue persists, try get the latest saplpd. (See SAP note 328252)
#328252 SAPLPD patches in SAPnet
If issue persists, try increase the debug level of saplpd to the highest level.
(See SAP Note 12552)
#12552 Request for debugging information for SAPLPD