on 01-28-2010 5:29 AM
Hello Guruz,
WHile creationd of purchase order, there is a check kept which compares the vendor communication language which gets updated in the Po header - Communucation tab with Db table T006A which holds the Unit of measurements with Language Key and pops up an error message.
It cheks the order unit in the PO, and the T006A whether the unit is maintained in the Language key as in the PO header - Communiction tab.
But while creating a unit of measurement in CUNI, we dont have the option to maintain the language key for the UOM.
In CUNI, it defaults the language key as EN in table T006A.
I need a prompt support from you guys on this issue. Please suggest how to go about with this?
Best Regards
Greg.
Hello Gregory,
For me the vendor communication language is the language to use in the forms you will sent to him.
For example, if you work with a Chinese vendor, but do not maintain any form in Chinese, then the default communication language should be english for example.
What i mean is yes, if you have 75 vendor languages, then you have to maintain the unit description 75 times; but i am not sure that you really use 75 different languages.
Isabelle
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Isabelle,
The check is not kept in forms but in the purchase order.
If you are having your base is spread in some 50+ countries, you will have vendors from 75 or more countries. It is always possible that at least half of them are using different languages or might be the local language.
Now how to find a solution for this? It is not possible to update all language packs in the server and then maintain the units of measurements in the language keys.
Please suggest.
Regards
Greg
is this the first error you have with languages?
What are you doing with all the other things like payment terms and shipping conditions?
They need to be translated too to the communication language entered in the vendor master.
If you use 50 different language, then you have to translate all customizing you did yourself into these languages. Otherwise you have to ask yourself why are you maintaining e.g. IT for italian in the vendor master while you then use english terms.
Hello Jurgen,
We started facing this from past 2-3 weeks only. The issue comes up while trying to delete a line item in a PO or trying to create a PO for some vendors whose communication language is not EN.
But strange part is that these PO's were successfully created without any error messages, but while deletion it is giving problem now. The reason is that there is a check which checks the table T006A for the unit of measurement in the PO line item whether maintained in the vendor communication language. Couldn't find any OSS also released by SAP for this issue.
Regards
Greg
sure it is feasible, all other companies that use SAP globally with many languages do this.
But this is usually a decision made in the very beginning of a project and rollout.
We maintain several languages including simple and traditional chinese. Our design says: local language to local vendor and customers, English language to common used and all foreign customer and vendors.
Hi
In CUNI in tope menu in GOTO option you can see translation for Dimensions, ISO codes (Press F6 in cuni) and Unit of measures(press F7 in cuni). You need to do all. Then it will work.
Regards
Antony
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
When i am trying to go for the language key in CUNI, it says that the said language is 'not available in server'. I guess it is checking whether the language patch is updated in the server.
But it doesn't sound logical to maintain all the unit of measurements in all the vendor languages. Suppose if we are having vendors with 75 communication languages and we are having 50 units os measurements, so does that mean that we have to maintain units of measurements 75 X 50 times ?
Kindly provide your inputs on the issue. We are facing lots of issues with this control kept in PO header checking for the T006A with the vendor communication language.
Regards
Greg
User | Count |
---|---|
100 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.