20.03.2013 Views

SAP Printing Customer documentation Volume 2 : [ZA0x] The ... - ELP

SAP Printing Customer documentation Volume 2 : [ZA0x] The ... - ELP

SAP Printing Customer documentation Volume 2 : [ZA0x] The ... - ELP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>SAP</strong> <strong>Printing</strong>: <strong>Customer</strong> <strong>documentation</strong>: <strong>Volume</strong> 2: [<strong>ZA0x</strong>] page 37 / 59<br />

However, before you contact our support, please try to isolate the problem source further, using the following approaches:<br />

• Try reproducing the problem using our device and a reference device type (if that makes sense).<br />

If it still occurs, it is only device-related.<br />

In all other cases, the problem may come from our device type.<br />

• Try using a standard document (transaction SO10 -> <strong>SAP</strong>SCRIPT-xxxxTEST).<br />

• If applicable, try to print to your device from a different environment.<br />

If possible, print from Windows using our Windows driver, and specify the same settings.<br />

• Check the command sequence in the "Printer initialization" action of the Format used in the Device type used for misspellings.<br />

• Check the Spool requests (transaction SP01).<br />

• Check the Output requests (transaction SP01).<br />

• Check the <strong>SAP</strong> system Process Overview (transaction SM50 -> in the "Type" column, click on "SPO").<br />

• Check the Spool Error Log.<br />

• Check the Spool server Trace (transaction SPAD -> Output devices -> -> [main menu] -> Goto -> Spool server trace -><br />

Display).<br />

• Check the <strong>SAP</strong> server System Log (transaction SM21).<br />

Steps 3, 4, 5 : See the following sections.<br />

4.4 How to contact our support<br />

If you couldn't fix the problem by yourself, and you found the problem is not purely <strong>SAP</strong> related, you need to contact our technical support.<br />

Please contact your local representative.<br />

4.5 What information to prepare<br />

If you do contact our support, please be prepared to have the following information ready:<br />

Basic information<br />

Category Details<br />

• Personal • Your personal data (company, contact person, address, ...)<br />

• Problem • Clear and detailed description of symptoms, reproducibility, all your above findings, ...<br />

• Physical device • Model name, serial number, controller firmware version, Total RAM, installed printer<br />

options/accessories (Mailbox, Finisher, ...), ...<br />

• Output device (logical printer) • Verbal description of Access method (how is the printer connected ?) and device type<br />

used<br />

• Device type • Name of base device type (the one you originally derived your device type from)<br />

• Brief description of your modifications (in the "Printer initialization" actions or Print<br />

controls), if any<br />

• Description of intended effect/setting<br />

• Document • What kind (<strong>SAP</strong>script/SmartForms, ABAP)?<br />

(if <strong>SAP</strong>script/SmartForms): Which Form ? Which Style ? Which Page format ?<br />

• Which Format was used when printing?<br />

• <strong>SAP</strong> system frontend environment • Operating system<br />

• <strong>SAP</strong>GUI version<br />

Note: This information is displayed in the title of the <strong>SAP</strong>logon screen.<br />

• <strong>SAP</strong> system server environment • "Host data" (Operating system, Codepage)<br />

• "Database data" (System, Release)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!