Problem importing printer device type using RSTXSCRP

Hello,
Referring to sapnote 8928 I have extracted 6 printer device types that I wish to import into our dev box.
(note: I am trying this on our sandbox first).
However, the readme instructions for performing the import using RSTXSCRP are out of date or not complete for all SAP versions. For one they refer to a radio button that does not exist in our version of . (note: RSTXSCRP is also the ABAP called when doing the import from SPAD).
In addition, when attempting the import, I receive a popup box requesting a package. Since I have never used packages I am at a loss. There is no option to create a new one, as when I created transports back when I did ABAP.
I can save these as local objects, but they are then not transportable. I wish to be able to transport these through the landscape as they go to production. I really do not want to do a bunch of individual imports in every system, since I would need to do so for R3, BW, APO, etc.
So long into short: How do I import printer device types using either RSTXSCRP or SPAD and have them transportable?

Prabhu, Thank you, but this does not answer the question. It only repeats the information I already have.
How do I enter the package information when I do not have it, do not know how to get it or how to create a new one.
I have been out of directly working with SAP for a couple years and have only recently returned.
This is apparently such a basic thing it is not even in any of the documentation I can find.

Similar Messages

Problem Exporting / Importing print forms with program RSTXSCRP

Hi!
there is problem Exporting / Importing print forms with program RSTXSCRP.
when I transfer print form from one SAP system to other, logo image and some text is missing... what could be the reason?
Maybe there is other way to transfer print forms between SAP systems without using program RSTXSCRP?
Will reward,
Mindaugas

Hi,
when you transfer print forms from one sap system to another, logos are not transfered automatically. these are actually .bmp files which need to be existing in every client. then only when you run your print program logo can be seen in your print output. hence logos need to be created explicitly in every client where you want to run your print program.
thanks,
sksingh

Updating printer device attributes using RFC

Hello all,
I'm a new entrant to the SAP world and still finding my feet. I think the term newbie can be applied freely.
My pilot involves using the NW RFC libraries to update printer attributes. So far I think RSPO_ functions seem to be the appropriate choice for dealing with printing. I can get the list of printers by using either ADS_GET_PRINTER_LIST or RSPO_ADM_DEVICES_GET. They both seem to return the same data, though the ADS version has far more detail. I've discovered these APIs mainly by trial/error and searching the forums/google/...
However I cannot seem to find the functions for updating the attributes.
RSPO_DEVICE_UPDATE and RSPO_ADM_DEVICE_UPDATE looked promising, but they cannot be called remotely.
My questions/doubts:
1. Is what I'm trying to do possible and supported?
2. Are RSPO_ family the correct functions for dealing with device updates, or is there another set of functions?
3. If the DEVICE_UPDATE is indeed the correct function, what are the workarounds for accessing it remotely; so far I can think of using a think ABAP wrapper which is exposed remotely, using the web services SOAP call.
I've been trying to find the canonical reference documentation for dealing with printers at an API level, but with no success. Any pointers to docs/references would be much appreciated!
I understand these are very entry level questions, and do beg everyones' pardon.
regards

Thank you Anzy and Priti, we're much further ahead now due to your help.
Priti, we do want to update the output device attributes. Specifically device type and driver. I cannot find RSPO_SXOMS_I_UPDATE_PRINTER function defined in the customer SAP test instance. I'll post the exact version numbers and configuration tomorrow, once I again have access to the server.
Anzy, I've started writing a Z_ wrapper over RSPO_ADM_DEVICE_UPDATE for the time being. Thanks for the pointer.
It seems that all the RSPO_ RFCs are view and read only. The update/create APIs are non-remote. I wanted to find the design/security documentation for understanding these decisions. Does SAP documentation have a technical/security architecture overview? Or perhaps a specific forum?
Once again, thank you both from me and the Idea Device engineers.

ONeil Printer Device Type not in SPAD

Dear all,
I am trying to add a printing device in SPAD, but unable to find the same in the list of entries in SPAD.
My device is ONEIL MF4Te Bluetooth device. Once it is added , we need to use this printer to print from our PDA to Bluetooth printer.
Thanks
Adnan

Hi,
You just use SWIN device in that list.
Regards
Kemparaju

Adding new printer Device Type

Hi Friends,
we have a new printer. now we don't have the exact device type matching the printer(Xerox Workcentre 7232). i visited xerox website and their i found a exact device type. Now my question is
1) If i install this new Device Type at saplevel does it overwrite any existing devicetypes at sap level.
2) Do we have any device type which matches this printer.
Thanks,
Vijay

follow note 8928      List of supported printers/device types
note 635230      Xerox SAP PCL and PostScript Device Types
note 6427      Information about device type upload/download
cheers,
-Sunil

Problem importing two service interfaces using the same data types

Hi,
I've been playing around with BPM for a while. Now I wanted to add a custom service interface to my starting event. I created the interface in ESR of CE 7.11. After importing I get this error message and I can't use the interface:
Cannot change XsdSimpleTypeDefinition AcademicTitleCodeContent by importing the document http://sap.com/xi/APPL/SE/Global::src/wsdl/TestInterface.wsdl, because it is already defined in the document http://sap.com/xi/APPL/SE/Global::src/wsdl/rootwsdl_CustomerERPByIDQueryResponse_InService.wsdl in this project. Importing into another project might be possible.
Of course the problem is clear, but how can I achieve importing two service interfaces that use the same data type without changing the xsd source?
Thanks in advance,
Mane

Sorry for the late answer, but I am really busy at the moment.
Unfortunately I can't the Interface and data types are already changed.
But this happened various times. Each time I already had imported a SAP Enterprise Service into NW BPM that contains a bunch of inline data types. While creating my own interface I referenced one of those data types that are stored in a SAP namespace. After import the error message appeared.
In the wsdl of the created interface there is a import statement for the namespace where the referenced data types origin from. Additionally there is a namespace definition xmlns:p1="SAPnamespace". In the element the type is "p1:ReferencedType". Could this maybe cause the error, because one time it is with this leading p1 in my created wsdl and once without in the SAP Service wsdl?
Thanks and I am looking forward to next EhP of NW BPM,
Mane

Problems with USB device when using WindowsNT

Hi,
my problem is that I want to use a simulator which can only be connected with USB to the computer.
I used the VISA Driver Development Wizard as discribed in this link (http://zone.ni.com/devzone/conceptd.nsf/webmain/6792BAB18242082786256DD7006B6416) and it didn't work.
I'm using Windows NT and VISA 3.1 and I read that it isn't possible to create a USB connection with VISA when using Windows NT. So my questions
1) is this right
2) Has someone a idea what I can do? I tried to use VISA USB Control and this also didn't work.
I hope I discribed my problem detailed enough. It's my first post.
Thanks for your responses
Joerg

As you can see in this table, USB is not supported by VISA under NT:
http://digital.ni.com/public.nsf/websearch/EE34F21ECC2BE01286256C52005D1A1F?OpenDocument
I would recommend to use Win2000 or XP. Using one of these OSes you could use this turorial to create your VISA-driver:
http://zone.ni.com/devzone/devzoneweb.nsf/Opendoc?openagent&1D0DD81FF1448CAE86256D90006EE2B4
If it is not posssible to change the OS, you have to look for other ways of programming your usb-device. Check the web or the Microsoft site for help concerning Windows SDK and USB.
Hope this helps a little!

Problem with printing perfomance when using a fixed width font

Hello.
I'm using the java.awt.print.Printable interface for printing text.
Everything works fine when I choose a font like Serif.
When I choose a fixed width font, like Courier, the printing becomes too slow!!!
Any Idea?
My code looks like that :
private int sizeFont = 10;
private font myFont = new Font ("Courier", Font.PLAIN, sizeFont);
public int print(Graphics g, PageFormat pf, int indice)
Graphics2D g2=(Graphics2D)g;
while(myCondition){
g2.drawString(myString,0,0);
g2.translate(0,this.sizeFont);
return Printable.PAGE_EXISTS;

If it interests someone, I have found a solution :
do not use "Courier", but "Courier New" .

Rendering Problem when printing to PDF using PDFCreator.

When I print my report to PDF using PDF Creator it overlays the text over itself vs when i export to pdf and then print it prints it fine, can anyone enlighten me as to why it does this?

Hi Raudel,
According to your description, you can export the report to PDF and print it well. However, when you print the report directly to PDF with PDF Creator, fields are overlapping.
Since you mentioned the report can display correctly after you export the report to PDF then print it, we can make sure the PDF rendering can work fine with reporting services. So it should not be the issue in Reporting Services. As we tested in our environment,
when print the report directly to PDF with PDF Creator, report also display well. In your scenario, it supposed to be issue with PDF Creator. I suggest you contact the PDF Creator vendor to get some more effective advices.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu

Problem in printing Address Type 3

Hi Experts,
This post is in context of Address type 3 (Contact Person).
Please see the below mentioned code which has been coded in the script :
/:           IF &VBDKA-ZZADRND& EQ &SPACE&
/:           IF &VBDKA-ADRNP_2& EQ &SPACE&
/:           ADDRESS *TYPE 3* PARAGRAPH AS
/:             FROMCOUNTRY &VBDKA-SLAND&
/:             PERSONNUMBER &VBDKA-ZZPRSNR&
/:             ADDRESSNUMBER &VBDKA-ADRNR&
/:            ENDADDRESS
/:           ELSE
/:           ADDRESS *TYPE 2* PARAGRAPH AS
/:             FROMCOUNTRY &VBDKA-SLAND&
/:             PERSONNUMBER &VBDKA-ZZPRSNR&
/:            ADDRESSNUMBER &VBDKA-ADRNP_2&
/:            ENDADDRESS
/:           ENDIF
Now as per the above code, Address of Type 2 is coming fine but when it comes to Address TYPE 3 i.e. Contact Person address is not getting displayed on the form. I have checked in ADRC table, record exists.
Can I have some valuable inputs on the same and please let me know if you need any other relevant info.
THanks in Advance!!!
Cheers
VJ

Check the standa saphelp for priority and number of lines toprint it correctly.
Thanks
Nabheet

Print Adobe PDF problem: Device type related?

Hi,
we have developed a number of adobe print forms and we face a problem. The problem is that not all types of printers can directly print (without first preview the pdf) the form.
We are using an output device with device type post2 (pdf1 works for some printers too) and access method F (Printing on Frontend computer) , but some printers work perfectly and others instead of the form, print out some postscript (or print) commands.
We can as well change our printers and get some postscipt printers but the problem is that we want to give access and print the forms some of our partners who logon to our system via VPN and we cannot "force" them to buy new printers.
Do you have any suggestion for this problem?
Thanx in advance
Kostas

the ABAP Backend is sending a ADS-document in an XML format to the ADS Server (JAVA), the ADS returns a "Parts" for the forms. A "parts" consist of an PDF file and a print file (PostScript, PCL or ZPL), which are placed in the Global Directory. All the conversion should take place within the ADS Server.
This "Parts" are then send as a PDF to the SAP Spooler.
For the printing of this PDF document in the SAP Spool System one of the Device types (POST2, HPLJ4, HP9500, PDF1, AZPL203, AZPL300) is taken into account which send the actual PDF to a physical printer.
What you see in SP01 are the "parts" of an ADS-document.
Report RSPO0020 (for troubleshooting ADS printing issues) is displaying the "Parts", send back from ADS to the backend System
The XDC file is the printer description in XML format, which the Adobe Document Services requires in order to create the "Parts" file. PDF documents can only be printed on printers of SAP device types for which there is an XDC file on the Adobe Document Server. Report RSPO0022 can be used to manage the mapping between the printer device type and the XDC file
Nesimi

Which device type support Unicode printing ?

Hi all,
Do you know which cascading font device types support Customer-defined true type fonts ?
I use HP LaserJet printer. I've imported ZSWINCF device type in to SAP system and installed some true type fonts required for my report. It's able to print <b>Unicode </b>text in ABAP List but unable in SAPScript/Smartform printing.
I also try to use ZHPUTF8 or HPUTF8, and install these fonts. But i've problem in printing out.
Do you know how to resolve this problem ?
Thanks,
Best regards,

Hi
see this OSS notes may be useful
OSSNote:960341
Symptom
In some device types (e.g HPLJ4, HPLJ5) you experience non-uniform character spacing in the PDF document after the PDF conversion of SAPscript or Smart Forms documents, using HELVE or TIMES fonts. You want to know the reason.
Other terms
CONVERT_OTF, SAPscript, Smart Forms
Reason and Prerequisites
The problem is not due to an error in the PDF converter but due to the fact, that the printer font, underlying the device type (e.g. Univers or CG Times in PCL-5 device types), is not available for the PDF converter and is either not available in Adobe Reader. The PDF converter has to try to simulate the layout of the printer font by means of a font which is predefined in Adobe Reader. This is done by assigning the letter widths of the printer font to the font used in Adobe Reader.
The PDF file contains a table with letter widths, used by Adobe Reader in the output of text, for each used printer font (except PostScript fonts).
Example:
%Charwidth values from HP4300 HELVE 060 normal
/Widths
[ 278 333 500 633 633 1000 758 333 333 333 633...
Adobe reader converts this width table, by modifying the space between each character, so that the specified letter width (= space between the current and the next letter) is kept.
This 'Simulation' of printer fonts results in the sometimes visible irregular spaces in PDF.
The PDF converter always uses the Helvetica Adobe PostScript font for the display of HELVE and the Times Roman Adobe PostScript font for the display of TIMES. However, for these Adobe PostScript fonts, Adobe Reader often uses a Windows TrueType font, which differs slightly from the original PostScript font.
Solution
Workaround: Use the POST2 PostScript device type or the PDF1 PDF device type for the PDF conversion of documents in the Latin-1 character set. They both use the Adobe PostScript fonts Helvetica or Times Roman for the HELVE/TIMES printer fonts.
Header Data
Release Status: Released for Customer
Released on: 30.06.2006 12:44:06
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Header Data
Release Status: Released for Customer
Released on: 22.08.2005 09:57:20
Priority: Recommendations/additional info
Category: Customizing
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
BC-SRV-SSF Smart Forms
<b>Reward points for useful Answers</b>
Regards
Anji

URGENT: Smartform - Attaching Font to Device Type and Printing

Hello Smarform Gurus,
I have uploaded CORPOS font to SAP and using in SMARTFORMS. Whenever the PDF is called for invoice, it should print immediately.
When I open the smartform and then print, the printout is coming fine with CORPOS font.
Problem: When Invoice is created and PDF is called immediately, the prinout is not coming properly. It's because the printer device type KYOFS150 we are using does not support CORPOS. Pls let me know the options we have. We have also referred to SAP note 12462.
Thanks in advance,
Abhishek

Hi
U need to update the printer device type KYOFS150 or use another one supports that font
Max

Printing a new format page in Matrix Printer with the SAPWIN Device Type...

Hi,
The requierements is to print Identification Material Labels with an Epson DFX-8500 printer. The label font is TIMES 34, therefore the Printer Device Type is SAPWIN. The real throuble is that label size (Format Page) doesn't exist.
I created a New Format Page but when a print the Materlal Label (SAPSCRIPT), the SPAD configuration isn't recognized. I need an Height of 432 PT (Like INCH6 because the paper is continuous form) isn't recognized.
Could somebody help me???
Alexis Sánchez N.
SAP ABAP Development Consultant
<< removed >>
Valencia, Venezuela
Edited by: Rob Burbank on May 25, 2010 3:56 PM

Hi all,
I solved myself... This is the way...
I have an Epson Matrix Printer (Epson DFX-8500)
In SAP, I created the Epson DFX-8500 Printer with the device type SAPWIN. This printer have some attributes in windows operational system (Windows XP). One of this attributes is the default paper size (Letter).
To change this, you have to do what the SAP Note 163136 (Creating new paper size for Windows NT-2000-XP-2003) says:
Solution
Note: This note is based on Note Q157172 from the Microsoft Knowledge Base.
You create a new paper size this way in Windows NT:
1. Choose 'Control Panel' and double-click 'Printer'.
2. Select 'Server Properties' in the 'File' menu.
3. Select the 'Create A New Form' check box on the 'Forms' tab page.
4. Enter the settings for the new paper size.
NOTE : If you set up your own customized paper size, the margins
cannot exceed the settings of the installed printer. The print area
must correspond to the margin settings of the printer driver used.
5. Save the paper size.
Proceed as follows to use the new paper size as the default format:
1. Select 'Printer' in the 'Control Panel'.
2. Click the right mouse button to select the required printer and select
'Document defaults'.
3. Select the new paper size in the 'Paper Size' selection box (on the
'Advanced' tab page).
4. Click OK.
5. Again with the right mouse button click the required printer and
select 'Attributes'.
6. Open the 'Device Settings' tab page and select the paper tray from
which you should print. Then select the new paper size.
NOTE: New paper sizes are stored on the computer on which they were
created. If you create a new paper size for a shared printer, you must
create the new paper size on the printer's print server.
NOTE : In Windows XP, there is an error in this procedure that can be
corrected with Note Q838298 from the Microsoft Knowledge Base.
I hope it helps you...
Alexis Sánchez N.
SAP ABAP Development Consultant
Valencia, Venezuela

Printing problem with printer EPSON 1070+

Hi ,
I am printing Document using SAP smartforms on EPSON 1070+ Printer. The device type used for task is EPESCP.
Page foramt I am using is DIN3.
When print is taken on specified printer it is printing all content of document in one font and not in the font which has been attached part of text.Document is display properly(text in different fonts) in print preview,but output on actual printer comes differently.
What should be done to correct problem ?
Thanks in advance,
Amit R

Hi Amit,
Have you checked by printing Word document on same printer??...
If the right part of the paper still left blank, then margin setting of the printer in windows has problem,
Otherwise check it in SPAD only.
Also check your Margin settings at printer.
Regards,
Audy

Problem importing printer device type using RSTXSCRP

Similar Messages

Maybe you are looking for