Device Type unsuitable for ADS Documents

Hi ,
Whenever we are using transaction PC00_M40_F16 for taking the print of
the form16. We are unable to get the print preview/print out . The
following error we are getting :-
Device Type unsuitable for ADS Documents
Kindly suggest the resolution ASAP
Regards
Vinay Patel
RCL SAP SUPPORT

Jeroen,
please go through SAP Note 685571. Not all the usual device types are supported when you use Interactive Forms for printing.
Regards,
Markus Meisl

Similar Messages

Printer setting - Device type unsuitable for ADS documents - reg

Hai Expert
I am trying to generate print preview, From 16, I am getting error "Device type unsuitable for ADS documents"
guide me to where have to do corrections
Regards
Vincent

May be you should try the right forum:
pk

Error - Device type unsuitable for ADS documents

Hi,
I have created a print form using transaction SFP and i am doing test from transaction SFP
(Test function module )
/1BCDWB/DOCPARAMS
YCTC 0000000000
YCTCUSAGE 0000000000
Once i press f8 system asking for printer, then i have given printer name as LOCL and select print preview. then system giving error as
Cannot find PDL type for output device locl and Device type unsuitable for ADS documents
Can i anybody give info what i am doing wrong.
I have tested with FP_TEST_03 that also giving the same error
a®

Hi,
I have tried with LP01 and with some other printers in the network its giving error that "Call contained error (02)"
I tried with all FP_TEST*
but no results
a®

When Printing Form16, Error "Device types are unsuitable for ADS Documents"

When Priniting Form16 it displays a message in the taskbar "Device types are unsuitable for ADS Documents"
Regards,
Ranga

You need a special device/printer for ADS. Try doing some research on that error.

Device types are not suitable for ADS documents when printing Form16

In Form 16 , while printing the Form16 of the employee it occurs an error "Device types are not suitable for ADS documents" in the task bar.
Regards,
Ranga

Can you check
Note 1116245 - ADS Check List before sending message to SAP
and see which of the steps are not working for you?
Markus

Document type change for excise document

Dear Experts,
I would like to change the document type for excise invoice generated at the time of J1IIN. At present system is generating document type SA. I want to maintain different number range for these documents instead of SA document number. So I would like maintain different document type for these document.
I have maintained different document ED in Tax on goods movement - Basic settings - maintain Company code settings, but still system picking document type SA.
Please advice.
Thanks & Regards,
Krishna Kumar

Dear Santosh,
Yes you are correct, I need to change the document type of accounting document posted to FI for Excise invoice. We are creating excise invoice with reference to billing document in J1IIN. Document type RV is assigned to billing document type in VOFA. But how I can check the document type for Excise invoice?
Thanks,
Krishna Kumar

Document type definitions for xml documents exported from SBO?

I am looking for DTD or XSD specifications for the documents that are exported from SBO via the DI API. It seems that this information is not available with the standard DI API documentation. Does anyone have a clue about where to look for these specifications ?
Best regards,
Henry Nordströ

The DI Company object has a GetBusinessObjectXmlSchema method which allows you to retreive the schema details.
Below is the sample from the DI help file.
Dim XMLStr As String
Dim domDoc As DOMDocument
Set domDoc = New DOMDocument
XMLStr = vCmp.GetBusinessObjectXmlSchema(oInvoices)
domDoc.loadXML (XMLStr)
domDoc.save ("C:\ XMLFiles \MyXML2.xml")
Regards,
John.

Find Material Document with Movement type 103 for material document 105

Hi experts,
In PO History, I have three line items with movement type 103 (Blocked Stock) and one with movement type 105 (From blocked stock to unrestricted stock). I would like to know the material document with movement type 105 document that has the movement type 103.
Regards,
Abdullah

Hi,
you can get the material documents (mblnr) for the movement type(bwart) in table AUFK.
But i think you need to pass some other data along with bwart like matnr or aufnr for getting the correct mblnr.
Regards,
Chaitanya

Order type field for PO/Document type field for PR

Hi Everybody
a) In Purchase Order creation screen (ME21)-for order type field -NB(standard order) is coming as default-How to make it blank(since we are using plantwise PO NOs)
b)In purchase requisition screation screen(ME51)also Document type-NB(standard order) is coming as default-How to make it blank(since we are using plantwise Purchase requisitions)
Thanks in advance
Joseph David

Simple,In order of ME21/ME51,Press F4,Select Required order/requistion type,Add it to Favourite list
or else
Create a transaction variant for ME21 & ME51 using t.code SDH0.
Transaction Variant - A Step by Step Guide for Creation,Check below link,
http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation
Edited by: Jeyakanthan A on Apr 2, 2010 5:42 PM

Output Type Default for Sales Document Header

Hello,
I have defined the Output Type ZTER and have assigned it to a print program and a form. Now when I go to transaction VA03, in the Menu Bar select Sales Document -> Issue Output to, I don't see my new Output Type ZTER present. I have to manually add it using VA02 and Extras -> Output -> Header -> Edit in order to add this Output Type.
My question is, how can I make it default to show when I select the Menu Bar (Sales Document -> Issue Output To) and then a prompt box comes up to allow the user to select.
A bit of addition information, I have already maintained the Output Condition
Thanks.
Edited by: jamison2004 jordan2004 on Aug 26, 2008 10:57 AM

Hi jamison,
please check output determination and you need to maintain condition records(like with sales organization and condtion type etc)of output type via tcode NACR. while saving the sales order it will condition records and populate output types automatically.
Tks... Venkat

Output Type for Invoice document

Hi,
The Output Message for Invoice Document was not created during MIRO in 2004. So no output generated & user cant able to take invoice printout via MR90.
Now user needs to output the message & take the printout. How to create the output type (tcode) for invoice document.
Regards,
Baskar

Hi
Follow this
Goto Tcode NACE ...select application MR ...click output types .... here create a copy of ERS and name it as say INVS
Now again in NACE slect MR and click on condition records and maintain condition record for INVS wrt co code
Now in Tcode M808 maintain INVS in the schema MR0002
Now when u create a MIRO doc then at header level do check if print is getting activated or not
Then take print out in MR90 tcode

Sap Device Type for Canon IR3035N

Hi there,
I am printing remittance advice notes on a canon ir3035n printer. The output looks fine in the spool file but when you print the output some of the text is printing with a large amount of spacing between the words. The sap device type that is being used is SAPGOF. I am guessing that this maybe the cause of this and was wondering has anyone else used the Canon IR3035n and experienced similar problems? I was going to attempt to use a different device type but am unsure of which device type to use.
Is there a specific device type available for use with this printer? Failing that, does anybody know of a generic Canon device type which I can select from the list of devices types available from transaction SPAD?
Any help would be appreciated.

Hi
Pls refer to OSS note
Note 1069132 - CANON: List of supported printers/device types
It may give some idea.
I hope IR3035N - IR stands for Image Runner.
In the Note search for 3035, you may get some idea
Pls take opinion from SAP / Basis before implementing the note
Regards
Madhan D

Need proper device type for Xerox printer "WorkCentre 5755. 5775, 5790"

Hi ,
Could anybodies suggest the proper device type for *"Xerox printer "WorkCentre 5755. 5775, 5790".
Thanks
Regards
Priyabrata Mishra

Hi Sujit,
I need he information about the device types for these printer models
Work Centre 5755/5775/5790
Please suggest if there is any compatible device types available in the given link by you. I have already downloded all the device types from this link but there is no device type information for these mentioned printer models above. Please suggest
Thank you so much for giving your valuable time
Regards
Priyabrata

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

WCS 7.0.164.0 Report by vendor (device type)

WCS 7.0.164.0
I have been asked to produce a client’s report that shows all different vendors (devices type). We have about 10000 users in our system on about 3000 APs (light version) I created a client summary report but encountered some limitations:
If I select any time period over 6 hours, I get the message “The report you are trying to generate contains more than the supported number of records (10000). Change the report criteria to generate a report with fewer records”
If I select a time period of 6 hours or less, I get the report including vendor statistics. Is there any way to differentiate within the vendors by device type? For example instead of the vendor apple, get apple-iPhone, apple-iTouch, apple-laptop, etc.
I would like the ability to create my own reports, by I don’t think it is possible on the Version I’m running. All reports can be customized up to a point, but you still get information you might not care for.
Thanks for any information to overcome these issues.
Jorge Jiles.

Hi Jorge,
It looks like such a level of granularity may not be achievable yet.
Should you need such a feature to be evaluated for potentially being included in future software releases, I would recommend to contact your local Cisco account team.
They should be able to follow up and submit a product enhancement request (PER).
Business units will evaluate PERs and, if feasible for the market, they may consider implementing such an enhancement in future versions of the SW/HW.
Regards,
Fede

Device Type unsuitable for ADS Documents

Similar Messages

Maybe you are looking for