NW-7.40, configure new printer in SPAD, transport through landscape into prod. system, collateral damage possible

[christoph_ostrop]

in NW-7.40 SP13

===============

when we have to create a new printer definition / output device within our SAP-ECC-landscape,

we do (in developm.system)

- SPAD,

- create new printer / output device

- configure needed information

- save

- save into STMS transport (workbench) request

- run transport request in test-/qa-system

- run transport request in prod.system

question:

during executing transport request (run) in prod. system,

- is there any thereby-affect to current print output-workprocess possible ?

   maybe lost of cache-content of available printer ? or something else ?

- is there any collateral damage on output processing - e.g. suddenly printer unknown or not possible to use

Christoph

[Former Member · Accepted solution]

Hi

If I have understood you question correctly then, there would be no problem in importing a new printer that would affect the existing prints, printers, spool process, etc

Once import is completed, just verify the printer is present in SPAD with correct spool server assigned to it. And test it with a print. Done!

Regards

Prithviraj

[christoph_ostrop · Accepted solution]

yes,

some people of our serivedesk tried to see a cause of some print-errors with running transports of new added printer / output devices.

as i understood your answer, this STMS transport of new printer should not affect any output-workprocess in any way.

Thanks,

Christoph

[Former Member · Accepted solution]

Hi Christoph,

Import of new printer in a system has no effect on other prints, printers, work process this is what I have observed for many years.

Regards

Prithviraj

[Sriram2009]

Hi Christoph

In transaction SPAD, New printer and short name are different from the privies printer devices?

Is this any error message while releasing the printouts?

BR

SS

[christoph_ostrop]

Hi,

to prevent different short names, we already did an export of all printers / output-devices

from production-system and import that into development-system,

and after that, we every time do add new printer / output devices first in dev,

then transport to q/s and to prod.

So the printer-shortname is the same in all systems.

thanks.