Query regarding Printing multiple documents

[Former Member]

Hi,

We would like to know how we can print multiple documents at once not one by one in SAP.

Presently we are using FB03 to print the GL document one by one.

Thanks

Pooja Gupta

SAP FICO Consultant

[Former Member]

Hi SAP Experts,

I would like to know the Standard SAP functionality from where we can give the number range of documents & take multiple print at once. The format of print document should be same as we can have from FB03 T code.

Thanks

Pooja

Edited by: Pavan Kumar.P on Sep 9, 2008 2:06 PM

[dianamarcela_cardonalopez]

Hello Pavan,

I have the same problem, if you find the answer, please let me know.

Thanks,

Diana

[Former Member]

HI,

We also encountered with the same problem and now we are using HP solution for it.

There are four major problems with the SAP print spool process:

1. Limited bidirectional communication between the SAP environment and the underlying operating

system (UNIX, Linux, and related systems). After the file transfer to the host, the only information

that passes between the two environments is whether the file still remains in the print queue (if the

SAP environment is configured to enable polling).

If the file is no longer present in the host’s print queue, the SAP environment assumes that the file

has printed. If the file disappeared for any other reason, such as a reboot of the operating system

or if the printer is turned off, the assumption is not correct. SAP proceeds to process the next

output request and the file simply disappears, leaving no trace of the failure.

Most often, SAP sets the status flag to ‘complete’ after transferring the request to the host spool

system. This action is a false positive because it actually indicates the handoff is complete, but not

that the job is printed. It aggravates users and increases calls to the helpdesk.

2. The lpr command passes only very specific instructions to the host spooler. The host only attempts

to deliver the file to the specified printer; it does not wait for the printer to confirm that the last

pages printed. It does not perform transformations, repackage the data, or redirect the file to

another printer. Nor does the host track the file and keep a record of what happens. The lpr

command (in some of the UNIX-related distributions) does allow an option to send an e-mail at

completion of a print job, but this option can quickly clog up the e-mail system and is rarely used.

3. Users have to make all adjustments to data within SAP before initiating the print request using the

capabilities already programmed into the SAP environment. This limitation includes advanced

print features such as staple, duplex, and resize, although administrators can enable the SAP

spool work process to handle these types of functionality by creating a new print driver. Further

extensions require additional programming within the environment.

4. A relatively inflexible and unfriendly input process can cost money and slow business processes.

For example, reports often need to go to people in different offices or at different sites. Users must

create multiple output requests in order to send the documents to multiple destinations, or users

must send the report to a print center where someone (extra headcount) collects the multiple

copies and mails them to the recipients (extra mailing costs and extra time). Sending reports by

fax or e-mail require a different set of steps, which further burdens the user.

Regards,

Satish Muvva.