Skip to Content

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

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)


- 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


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


Add comment
10|10000 characters needed characters exceeded

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 17, 2016 at 12:39 PM


    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!



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Christoph Ostrop

      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.



  • Posted on Aug 17, 2016 at 05:00 PM

    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?



    Add comment
    10|10000 characters needed characters exceeded

    • 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.