Symptoms
· If you load data that has an external format and is to be converted into an internal format using a language-dependent conversion exit, the system uses the system language of the current user, usually the background user of BW, for the conversion. If the system language is different from the data language, errors may occur during the conversion, for example in the CUNIT exit.
· If DataSources have several segments, the system postprocesses the application structure only for the last segment.
· During the currency translation, the system tries to convert the amount using the non-converted currency value. This results in an error.
Possible Solutions
1. SPRO-> SAP Netweaver -> General Setting-> Check units of measurement->
Units of measurement
There you need to create new entry for your custom unit.
It could be your data is in incorrect format. Check ur
data sequence, make sure it match exactly as in
datasource/trans structure. Example that column
suppose to be stored UOM but it does captured data
other than uom.
data sequence, make sure it match exactly as in
datasource/trans structure. Example that column
suppose to be stored UOM but it does captured data
other than uom.
2. Step 1 > Type the transaction Code, CUNI
Step 2 > Click on "Units of Measurement" -- You get a Table displayed
Look for CS,EA,DZ,LB under Units field
If you have only one or two of the above 4 fields, you need to add the remaining ( In my case, DZ and CS were missing)
Step 3 > Type the transaction Code , CUNI again
Step 4 > Click on ISO codes and look for the missing values
see if you can find any thing you were not able to find previously in this table
( In my case i found DZN -- DOZEN and CS -- Case listed here )
Step 5> Go back to " Units of Measurement" and hit F7 to create a new record
Int.Meas.Unit --> CS
Commercial ----> CS
Technical --------> CS
Measurement Unit text --> Case
ISO Code ---> CS
Hit save button
Step 6 > Repeat step 5 for DZN -- Dozen
Step 2 > Click on "Units of Measurement" -- You get a Table displayed
Look for CS,EA,DZ,LB under Units field
If you have only one or two of the above 4 fields, you need to add the remaining ( In my case, DZ and CS were missing)
Step 3 > Type the transaction Code , CUNI again
Step 4 > Click on ISO codes and look for the missing values
see if you can find any thing you were not able to find previously in this table
( In my case i found DZN -- DOZEN and CS -- Case listed here )
Step 5> Go back to " Units of Measurement" and hit F7 to create a new record
Int.Meas.Unit --> CS
Commercial ----> CS
Technical --------> CS
Measurement Unit text --> Case
ISO Code ---> CS
Hit save button
Step 6 > Repeat step 5 for DZN -- Dozen
3. Check in T006 table. Table t006* contains 'master' data for all unit of measurement, characteristic 0unit.
to populate data of any characteristic infoobject that reference to 0unit, the value must exist in the table.
to populate data of any characteristic infoobject that reference to 0unit, the value must exist in the table.
To display the table you can use transaction se16.
for entry/maintain you can use transaction CUNI
or first transfer from r/3 use rsa1->source system->right click r/3 source system->'transfer global setting', mark 'unit of measurements' and choose option 'update table'->execute, after that se16 check if EA and DZ exist or not (also the other 2 values).
we cannot maintain unit for 'Case, Each, Dozen, U.S. pound'. for unit just have 3 digit. So first correct your .csv file for these values, 'each' with EA and 'dozen' with DZ.
if no standard code for case and us pound, you may define them with transaction CUNI, e.g us pound with USP, remember to change the .csv value with the same.
No comments:
Post a Comment