ZHANWIN device type does not print Korean characters

Hi All,
We are trying to print smart forms containing Chinese,Taiwanese and Korean characters from our ECC 6.0
As per SAP Note 1038413 - Unicode SAPWIN device type for CJK fon, we used the device type ZHANWIN to print smart forms for these characters.
But with this device type we are unable to print smart forms with Korean characters. But as per the note, it has to support Korean characters too.
Please help with this issue.
Thanks and Regards,
Subashree

Hi Subashree,
it is likely that the problem with ZHANWIN is related to the font used in the form. if you want to print Korean characters via ZHANWIN, you need to specify a Korean font like KPBATANG for the Korean characters in the form. Then this will be mapped to a suitable windows font in windows. If you chosse e.g font COURIER , it is mapped to windosw font Courier New which does nto contain the Korean characters.
For SWINCF or SWINCFCK the font in SAP is not so impertant. The mapping of the characters in windows is based on the Unicode character range. So as Nils said, SWINCFCK should work regardless of the font in the SAP form.
Regards,
Aidan

Similar Messages

Device type does not support page format

Hi All,
There is one issue when I print a sapscript. I get an error message as follows:
Device type EPESCP9 does not support page format ZSG02
Could someone advise?
Thanks
Alice

Hi,
The page format ZSG02 is not present in Device type EPESCP9.
in SPAD t.code add the page format in that device type.
Better inform to BASIS people they will add page format in that device type.
Refer the link Device type does not support page format
Regards,
Dhina..

PDF created in MS Word does not print special characters correctly

I am having a problem with converting an MS Word document to a PDF. This document contains the Ohm symbol and the greater than or equal to symbol. I am using Word 2007 and Acrobat X Pro.
I am simply using the insert symbol feature in Word to insert the symbols. They appear fine in Word. When I print to PDF the Ohm symbol turns into an '&' and the greater than or equal to symbol turns into an 'e'.
A fellow I work with who has the exact same computer and program setup as me does not have this issue.
What can I do to correct this?
Thanks!
Chris

I tried all of the print/press options and they all do the same thing.
I have always used the pdf maker button from the MS Word ribbon.
I just tried using the print dialog and selected Adobe PDF with the 'high quality print' option that I need to use and this time it worked! But it is not really fixed as I make a lot of PDFs every day and need the one-click functionality.
In the PDFs that work and PDFs where the character fails I tried editing the text and it says that the font is substituted. In MS Word i am using Arial, Acrobat is using some "ArialMT" font that I never heard of.
The embeded fonts are also listed as ArialMT.

PO Document (View Document) does not display Korean Characters

Hi,
We have a situation here. In Production, the asian characters are not being displayed in PO Document
Navigation: Purchase Orders - > Inquire -> View Document
Surprisingly, a cloned environment of PROD displays the asian characters fine. Has anyone come across a similar issue?
This uses the XML Publisher template stylesheets. Both PROD and QA have the same style sheets. The template is setup with language as Korean.
It would be great if anyone can please guide me troubleshoot this issue and identify the cause.

Thanks for your response.
I did check the fonts under $OA_JRE_TOP/jre/lib/fonts and $AF_JRE_TOP/jre/lib/fonts folders in both QA and PROD environments.They are identical and albany fonts do not exist under them. But Korean characters are visible in PDFs generated under QA but not in PROD.
Is there a profile option set to guide XMLP to a folder for fonts? Please let me know.
Also, the JDK upgrade happened a couple of weeks before and PROD is pointing to JDK 1.5 but QA is still pointing to JDK 1.4 (cloned from a copy week earlier from PROD upgrade).

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

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

Update was terminated - Class PO - Number 366 - Device ARCH does not exist

Dear Gurus,
We are using Automatic PO generation through ME59, we also applied one SAP note to pick the custom document type through ME59 (normally the system pick NB as standard document)
In MN05 - if i set as default output type 1 - print ( then the document is generating with the correct document with correct number range)
But if i set in MN05 - default output as 2 - fax ( then i am getting this Update was terminated - Class PO - Number 366 - Device ARCH does not exist).
Please advice
Regards
RS

Dear Friend,
Output determination for fax is not done properly. check the device connnectivity.
SPRo>>Maintain Message type of PO
For the particular document type - i have removed the default PO Print out settings - now its working fine. Is this the right way?
Please advice
RS

My hp deskjet 1510 series does not print when connected to my hplap top (windows Vista),

My hp deskjet 1510 series does not print when connected to my hp lap top (windows Vista), it says the printer is not active, although it is default printer, connected and on. However, it does work when connected to the (also HP) lap top (windows 8) of my husband. I did everything the hp print and scan doctor advised and also what I could find at HP support (like switch of fire walls, reinstall everything, check printpooler ec etc)... it still does nothing except that I managed to print a diagnostic print which should give information about the condition, but it only gives numbers and letters like : 11. SN = [Edited for Personal Information] Yr 12 PER = 05YR etc, that does not really help me :-). It won't print any testpages. H E L P!!!

Hello Elisabeeth,
Welcome to the HP Forums!
I understand you're unable to print using the Deskjet 1510. I will do my best to assist you! When you reinstall the HP software, did the installation state it was complete?
I would start off by following this HP document on 'Printer is offline' Message Displays on the Computer and the Printer Will Not Print. From this document, please make sure you check the connection type and the ports.
Please post your results, as I will be looking forward to hearing from you.
I worked on behalf of HP.

Hp officejet pro 8100 and it does not print bar codes from UPS or USPS

have an hp officejet pro 8100 and it does not print bar codes from UPS or USPS. Can you please please help? i have used my ipad, by HP G62-355DX Notebook and neither will give me printed bar codes. The balance of the mailing label do print, just not the bar code. It may be my imagination, by I believe it used to print thebar codes.

Hi,
Try adding an alternate driver and try to print.
To use an alternate print driver for HP printers in Windows 7:
1. Click on the Start menu.
2. Click on Devices and Printers.
3. Click Add a Printer
4. Add a local Printer
5. Select Create a New Port
6. Select Standard TCP\IP port
7. Enter Printer IP address (Printer IP address can be found by printing network config page from printer
8. Under Manufacturer select HP and under printer select HP Officejet 8000 pirinter or Officejet 7410
9. Click apply and try printing
Although I am an HP employee, I am speaking for myself and not for HP.
--Say "Thanks" by clicking the Kudos Star in the post that helped you.
--Please mark the post that solves your problem as "Accepted Solution"

SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
1/ The major number for IDE based drives is 3.
2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
- The major number is 8.
- The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
Armed with this knowledge, I su'd to root and entered:
# mknod /dev/sdc4 b 8 36
and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
# ls -ald /dev/sd*
Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
brw-rw---- 1 root disk 8, 32 date time /dev/sdc
Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

Solved!
See the lengthy response in this post:
http://bbs.archlinux.org/viewtopic.php?id=36468
I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

Hp laserjet 100 color mfp m175 does not print from network nor via usb cable

My hp laserjet 100 color mfp m175 just stopped printing last week. I have tried everything recommended but nothing works. I have re-install it both on wireless network and usb connection = nothing works. It prints all internal reports but nothing from any computer. I have 3 computers which I have tried to print from. It even does not print the test page. Please dont recommend to update drivers etc. as I have spend 2 whole days on this and nothing works!

Hi @einar1854,
I see by your post that you are unable to print by a USB or Wireless connection on 3 different computers, but the printer will print the hardware self tests. I can help you with this.
Download and run the Print and Scan Doctor. It will diagnose the issue and might automatically resolve it. Find and fix common printer problems using HP diagnostic tools for Windows?
For the USB connection, follow these steps if the there are no errors from the Print and Scan Doctor.
(once we get the printer printing this way, we can setup the wireless)
Here are steps to remove the jobs from the spool folder and restart the print spooler.
How to Clear Current Print Queue In Windows Vista & Windows 7.
Follow the steps in this document to get to the device manager to check for the printer entries.
How do I get into Windows Device Manager?
Then click on Identifying problems in Windows Device Manager.
In the list click on Universal Serial Bus controllers and look for USB mass storage device and USB printing support, (make sure any other printers are turned off or disconnected)
Let me know what it showed in the device manager.
Check to make sure the proper port is selected.
Go to start, Devices and Printers, right click the printer and left click Printer Properties, select the Ports tab.
Make sure the USB has a check mark beside it, if not put the check mark there and apply the changes.
Check the print Queue.
In the Devices and Printers folder.
Right-click the name of the product and then click See what's printing .
Click the Printer button, then click Cancel All Documents if there are any documents in the queue.
Click Yes to confirm the action.
If documents remain in the print queue, restart the computer.
Try printing again.
What operating system are you using on the 3 computers? How to Find the Windows Edition and Version on Your Computer.
What were the results when you ran the Print and Scan Doctor? (did it print or scan, any error messages)
Print a configuration page to see also if the printer has a valid IPV4 address, so we have that information for when we setup the wireless. Printing a Configuration Report.
Provide the first 3 sets of numbers in the IPV4 address.
Please provide in detail the results if you are still having issues.
Have a nice day!
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

When text is low on the page, it does not print on the page!

Office Jet J6480, Windows 7 32 bit.
Sometimes pages with a content line near the bottom of the page, does not print or the characters are only partially
printed on the output page.

Hello, you may be able to fix this problem on your HP Officejet J6480 All-in-One Printer by following the steps in the following document: "The Product Does Not Print the Bottom Page Border in Microsoft Office":
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01671543&tmp_task=solveCategory&cc=us&dlc=en&la...
There are two more links inside that web page with some other solutions if you are experiencing this problem with other Operative System:
-Printed Text is Cut Off on the Last Line of the Page in Windows XP
-Printed Text is Cut Off on the Last Line of the Page in Windows Vista
I am an HP employee, Printer/All-in-One Expert.
Give Kudos to say "thanks" by clicking on the "thumps Up icon"
Please mark the post that solves your problem as an Accepted Solution so other forum users can utilize the solution.

Transaction type does not exist. Check entries

Hello all,
EBP 5.0, CCM 1.0, unicode
When I try to log on different language than English and try to shop system is displaying two messages
Internal number range is missing for transaction type. Inform syst. admin
Transaction type does not exist. Check entries
And I cannot see link for Procurement Catalog.
All my customizing up to now was in English, due to the fact that SAP did not provide translation to Croatian (Latin-2 language).
Also catalog call-up has locale "en" for the calling of catalog from EBP.
Please give hint where I can start with debugging.
Gordan

Hello Yann,
main problem, language files for CCM and EBP are not suppied from SAP yet. MY BC told me that they installed Croatian language in WAS, so system should behave as language is intalled fully and represent text in English when there is no translation.
I cannot test other things because EBP will not go into the catalog due to the missing internal numbering for the transaction type. I checked BUS2121 in transaction types but nothing to be found.
I was thinking that those two problems are related but this is not true. First I have to solve number range that check the catalog. Only common between those two problems is logon language.
I even forced our special characters by entering them as UNICODE code and I can see them via catalog manager in english, but only for catalog items. Characteristics and product category names do not follow UNICODE specification.
Confused
Gordan

Dymo Discpainter does not print

Hello, I am starting a new topic because I have tried all the answers posted in the thread:
http://discussions.apple.com/thread.jspa?threadID=1717959&tstart=0
I just got a Dymo discpainter and after some struggle at first I finally got the Discus software program that comes with it to open. Then it wouldn't let my print at all. I am getting the message "Rendering Disc Image" but it does not print. I tried doing the localhost update found in the above thread. I tried unplugging and plugging it back in. I tried updating all software. I reinstalled the software. I wonder if I got a bad device? Just got it yesterday and was so excited to try it and then it didn't work!!
Message was edited by: etcetera25

I am still tearing my hair out. Have not been able to use the discpainter since changing to the latest MacBook Pro.15".I have downloaded the latest driver. even re-downloaded from Magic Mouse the software again. Tried all the usual tips. tried wiping the plist. zapping all the driver software and reloading. Plugging the printer into the computer usb plug direct. Pulling the leads out of the printer, waiting and re-fitting.
Been into Local host printers, modify to find that there is no "unknown usb" even when it is plugged in.
I know that the printer work, with my intel macbook pro. So I might get that back from my daughter and see if it still works with that one. So as to check that the printer is not at fault.
Hope that there is not to many typos, as I usually spot them after posting
Dave

The device type is not recognizable (USIM 9989)

Does anyone know how to resolve this problem? "The device type is not recognizable (USIM9989)"
This problem arises when I am trying to buy an AT&T plan when I was in the US recently, Thanks

Hey All, Just like to share my experience as above with my recent trip to the USA. Like the above comment I too have an iPad with Retina purchased from the Apple Store in HK last year. After arriving and making my way to the ATT store in LA to activate my prepaid the same error occured. An hr later and a lot of head scratching we placed the sim card into another iPad (We'll call it the third version iPad) and went throught the steps of creating an account, choosing a plan and activating the SIM. For what ever the reason my iPad would not activate the card, however activating in another device and replacing it back in mine it worked a treat until the day i left. No settings/apn needed to be altered. A simple restart of the device had it up and running in no time. I could never get to use the inbuilt account side but the web version worked fine.. I cannot comment if its just the HK version of the iPad that gives this error. I would be intrested to know if other users from other countries have had a similer problem.

ZHANWIN device type does not print Korean characters

Similar Messages

Maybe you are looking for