Automatic UOM conversion

Hi All,
When i create a SO, i have to enter Gross Weight and Net Weight by hand, however i set up Units of Measure. My Sale unit is EA, Weight unit is KG and 1 EA = 10KG.
So, how to do the Gross weight and Net weight is automatic?
Thanks & best rgds!

Hi Friend,
I am sure that you must have filled weight in gross weight and net weight field and its not coming in the sales document so you are filling it there.
<b>Please go to VOV7, and make a tick mark on the weight and volume releventy</b>. This way your issue will be resolved.
If your problem is caused by lacking conversion rule of unit of measurement then go to additional data of the specific material change view and define it ther.
If not solved please come back.

Similar Messages

Utilizing Aggregates with Automatic UOM Conversion

We are using SAPs suggested UOM conversion techniques for 3.5 as described in this document: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b7b2aa90-0201-0010-a480-a755eeb82b6f">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b7b2aa90-0201-0010-a480-a755eeb82b6f</a>
I am realizing that any aggregates that are built and need to use this UOM conversion must contain the 0MATERIAL InfoObject. Has anyone found an alternative to this?
If I want to run a yearly sales volume by customer report with implicit UOM conversion the query will not use any of my customer specific aggregates because they don't contain 0MATERIAL. Adding 0MATERIAL to these aggregates would increase the size of the aggregate by a factor of approximately 500. I'm trying to avoid this for obvious reasons.
Thanks.

HI Jonathan,
UOM conversions work explicetly at the material level.Therefore if you want your aggregate to use UOM conversion use must include the material in your aggreagtes.
Aggregates contains data at the level depending upon the characterstis included into the aggregates.
Now if you want something to act upon at a particular level the data at that level has to be maintained.and agrregate are nothing but the cubes.
This leads to the performance issue but there is no other way as UOM conversions have to happen at the material level.
Hopes it clarifies.
Thanks

UOM Conversion to be used in transformation

Hi Experts,
I am trying to make use of the BI 7.0 UOM conversion feature in one of our InfoCubes where the source quantity which is in Base UOM needs to be converted to cases.
I went through all the steps which are as follows:
1. I have 0BASE_UOM as the base unit of measure for 0MATERIAL
2. A DSO was automatically generated with the name Z_OUOM I gave in 0MATERIAL configuration
3. I created a transformation for this DSO with source as 0MAT_UNIT
4. Created a DTP and loaded the DSO
5. Created a Conversion type with settings 'Dynamic Determination of conversion factor as Using Reference InfoObject = 0MATERIAL
Source Unit of Measure: Unit of Measure from Data Records
6. Target Unit of Measure: Fixed Unit of Measure = 'CS'.
In InfoCube transformation I have the following mapping:
Rule type: Direct Assignment
Target Unit: 0UNIT
Unit: From Conversion
Conversion Type: ZCASES
Source Unit: 0BASE_UOM
Source Fields of Rule:
0MATERIAL
0REQ_QTY
0BASE_UOM
Target Fields of Rule:
ZREQ_QTY
0UNIT
When I load the InfoCube, the quantities are indeed getting converted to cases provided there are conversion factors available for that material in the UOM generated DSO
Here is my question: How can I handle records where the material does not have conversion factors in the UOM generated DSO?
I get an error when loading using a DTP as 'No quantity conversion possible'. There is one record in the source DSO that has a material number with no unit conversions in UOM generated DSO
I am aware there is an option of using routine, but I do not want to use it unless I am sure this method won't work

Hi Aditi,
There is no way you can check if UOM is present or not in UOM DSO and then do the conversion via using conversion type.
What you can do is write the routine rather than conversion type, to fetch the data from the UOM DSO.
If conversion factor exist then you can convert it simple by multiplying with the value, if not then you can easily skip the record by putting IF condition.
IF factor <> 0.
ENDIF.
Hope this helps.Let me know if you need more info.
Regards,
Viren

Costing Data: UOM Conversion for Activities

Hi Experts,
I would like to know what transaction (or if there's a transaction/table) to check the UOM conversion of activities in the costing data (tcode CK11N). Let say the activity HEAT, conversion from KWH <-> GJ? Thanks so much!
Best Regards,
Kurtt

Hi,
The UOM conversion is maintained in the SPRO.
But for costing the unit is maintain in Activity say POWER as unit H
But in the production they maintain the receipe activity unit for POWER as unit MIN.
So when you upload the KP06 & KP26 with activity qty,the activity qty should maintain in H.
So when you have the cost run in CK11 then the system will capture automatically for the per ton production the consumption of power activity in MIN.
So if you want to know the what is conversion factor then it is standard UOM definition in SPRO.
SAP NetWeaver--General Settings---Check Units of Measurement
Regards,
Raj

Automatic time conversion is not possible

Hi Friends,
I have a problem in Transformation Level when i am mapping "automatic time conversion is not possible for source field FISCPER to 0FISCYEAR,FISCPER3".can any one help me in this issue.
Thanks
Narasimha

Yes if it was date filed then it would have been possible.If you are trying to derive the fiscal year between datasource and cube then you can get it with the help of simple filed level routine.
Map your fiscper field from source to fiscal year--Rule type Routine.
RESULT = SOURCE_FIELDS-(Technical name of source field)+0(4).
For Posting period
Map your fiscper field from source to fiscper3 year--Rule type Routine.
RESULT = SOURCE_FIELDS-(Technical name of source field)+4(3).
This will give you the required output.
Regards,
AL

How to suppress automatic keyfigure conversion in WD ALV?

Dear experts,
I am having a problem with automatic input conversion in WD ALV.
I have a key-figures (type P length 9, decimals 2)in my ALV which has reference field of type if_salv_wd_c_field_settings=>reffieldtype_curr.
I process the changes by event ON_DATA_CHANGE which passes this change object:
r_param->t_modified_cells
r_param->t_inserted_rows
r_param->t_deleted_rows
r_param->t_error_cells
The thing is that the changes in table r_param->t_modified_cells are already converted into internal format. When user enters "1", I get here in this table value "1.00". But this internal value is not always correct because corresponding reference field with currency key may not be known yet (it is calculated later on background from other fields).
Therefore, for example for currency JPY which has no decimal places external value "1" is converted into wrong internal value "1.00" (the correct internal value is "0.01").
Therefore, I need to suppress the conversion by the ALV and do it myself once the currency key is known.
How can I suppress the automatic input conversion which is done by ALV?
There is no such problem in SAP GUI ALV! There is event DATA_CHANGE with similar change object:
io_data_change->mt_good_cells
io_data_change->mt_mod_cells
io_data_change->mt_inserted_rows
io_data_change->mt_deleted_rows
But all the changes in table io_data_change->mt_mod_cells are in an external format (exactly the way user entered them on the screen)!
Any idea?
Thank you in advance for your help.
Tomas
Edited by: Tomas Havlik on Oct 5, 2010 10:24 AM

I have contacted the Web Dynpro ALV support directly to find out the answer.
There is no solution!
The WD ALV always convert the key figure into internal format. It is not possible to get the raw user input in WD as it is in SAP GUI.
Therefore, I use a workaround in my application - I remeber the number of decimal places of the old currency key and if the new currency key has different number of decimal places, then I shift the decimal point to the right or left correspondingly.

Mass deletion of alternative UOM conversion

Hi Colleagues,
Does anybody knows is there an easy way for mass-deletion of alternative unit of measure conversion rules in material master?
Thanks,
Artashes

I did the following way:
1. created a recording which always deletes the second line in Additional data-> uom conversions.
2. by multiply running this recording via lsmw will delete all uoms.
3. I was not able to do it at once as different materials has different numbers of alternative uom entered.
Thanks,
question closed.

Question about UoM conversion

I'm trying to implement the UoM conversion that is now standard in BI 7.0. I think I have all the backend work done, but I'm having trouble converting the UoM on the front end when running a query.
Here's what I did on the backend to set it up.
1- I went to 0MATERIAL (BEx Explorer tab) and entered 0BASE_UOM as the Unit field.
2 - I then generated the conversion ODS.
3 - I created transformation to the ODS using 0MAT_UNIT_ATTR. I did have to use a master data lookup for the BASE_UOM field (using the values in 0MATERIAL) since the 0MAT_UNIT_ATTR didn't have the Base Unit of Measure, just the conversion one.
4 - Loaded the ODS for 1 material (test material 1 EA = 1 EA and 1 KIT = 20 EA)
5 - Defined a Converstion type (trans RSUOM). I used Dynamic Option 3 (InfoObject, then T006 tables). I set the Source UoM = DataRecord, and Target is set to "Selection during Conversion"
Here's what I did on the query:
1. For my key figure, I went to the conversions tab. I selected my Conversion type.
2. I created a user entry variable with a default value of "EA".
When I run my report, I enter KITS on the selection screen, but the report still shows eaches. I can navigate to the Currency conversion on the report via the menus, but I can't find anywhere for Units.
Any ideas?
Thanks,
Rudy

First, is there any particular reason why you used:
Integer a = Integer.valueOf(1);while I used
Integer a = 1; //boxing
Just to get rid of boxing conversion as a possible issue--which it shouldn't be, but might as well keep it simple.
Integer a = Integer.valueOf(1);
Comparable<String> cs1 = a; // errorbecause we are assigning to a Comparable<String> an
Integer value, and that's illegal, since String and
Integer are not in a subtype relation (?)Something like that, yes. I'm not sure of the exact clause of the JLS that forbids it.
>
Comparable<Integer> ci = a; // ok
Comparable<String> cs2 = ci; // errorbecause we are assigning to a Comparable<String> a
Comparable<Integer>, and again, String and Integer
are not in a subtype relation (?)Yep.
Comparable<String> cs3 = c1; // warning
Comparable<String> cs4 = c2; // warningit's what I believe is called 'heap pollution' I forget what that term means, and am too lazy to look it up, so I'll take your word for it.
and I
believe that on first use a ClassCastException will
be thrown Sounds right. Run it and see for yourself.
(although the compiler behaves correctly by
flagging an unchecked warning, for compatibility with
legacy systems, etc)Right.

How can i determine if a UOM conversion is being used in a query?

I need to find all the queries that are using a QTY UOM conversion. i tried to do a where used and it didn't return anything.

Hi,
Check function module RSZ_I_BASIC_CHA_WHERE_USED
also check this (try the program)
Where-used list of an attribute (either display or navigational)
From AHP
Hope it would help.
Regards,
Satya

How to use own UOM conversion for PO creation...

Hello Experts,
We have a requirement wherein we need to use our OWN UOM conversion(UMREN and UMREZ)
instead of getting it in the inforecord or the material master. Currently we are using BAPI
BAPI_PO_CREATE1 to create PO.
Is there anything that I can do to make the PO creation bypass the inforecord and
the material master UOM conversion. For example in ECC we have 1 CV = 10 EA. We want it to be 1 CV = 15 EA.

Hi Guys,
Any help? Any exits/BADIs/enhancement spots that I can use?

Incorrect UoM Conversion on Transfer Requirement from Production Order

I have a Question on a Production Order that created a Transfer Requirement. Looking at the Components of the BOM within the Production Order, I have a Material where the Issue Unit of Measure is QT and the Base Unit of Measure is EA, with a Quantity of 1. In the Material Master Alternate Unit of Mesaures, the Conversion is setup so that 1 QT = 1 EA. The question of why the 1 for 1 conversion is not relevant, as this is just how the material was setup and I know it does not make any sense. When the Transfer Requirement is created it is showing that 1 Qt = .25 EA. I am unable to locate where this conversion is coming from. We do not want to lose visibility of this part number, as creating a new part number with a Base Unit of Measure of QT would fix the problem.
Is there anywhere in configuration where there could possibily be a Conversion? I have looked at Control Cycles and the Reference Operation Set and do not see anything.

Closing Thread as there has been no responses but I am still looking for a solution. The only possibility that exists at this time is the material was copied from another material and the UoM Conversion was 1 QT = 4 EA on the Copy From Material. I can not see where any changes were made to the unit measure conversion for the new material. The only other possibility is the Production Order was manually converted to the new material incorrectly.

Problem of automatic widening conversion

Hello,
base one link below:
http://docstore.mik.ua/orelly/java-ent/jnut/ch02_04.htm
Finally, the notation Y* means that the conversion is an automatic widening conversion, but that some of the least significant digits of the value may be lost by the conversion. This can happen when converting an int or long to a float or double. The floating-point types have a larger range than the integer types, so any int or long can be represented by a float or double. However, the floating-point types are approximations of numbers and cannot always hold as many significant digits as the integer types.
int = 32 bits
float = 32 bits
why from int to float, will have problem? can show example or diagram of bits of problems?
long = 64 bits
double = 64 bits
why from long to float, will have problem? can show example or diagram of bits of problems?
Thanks.

812322 wrote:
... the notation Y* means that the conversion is an automatic widening conversion, but that some of the least significant digits of the value may be lost by the conversion. This can happen when converting an int or long to a float or double. The floating-point types have a larger range than the integer types, so any int or long can be represented by a float or double. However, the floating-point types are approximations of numbers and cannot always hold as many significant digits as the integer types.
int = 32 bits
float = 32 bits
why from int to float, will have problem? can show example or diagram of bits of problems?
long = 64 bits
double = 64 bits
why from long to float, will have problem? can show example or diagram of bits of problems?Considering just positive double (ignoring 32-bit float).
In a Java double (IEEE754 floating point)
one bit is used for the sign,
11 bits are used for the magnitude and
52 bits are used for the mantissa (the digits)
A Java double can store an int because an int only has 32 bits.
A Java double can store a long that uses only 52 bits.
When converting long values in the range [ 0x0010000000000000 ; 0x7FFFFFFFFFFFFFFF ]
because 11 bits are used for the magnitude
there are not enough bits in the mantissa to represent every long value.
Exercise:
Write a Java application that converts randomly selected long values
in the range [ 0x0010000000000000L ; 0x7FFFFFFFFFFFFFFFL ] to double and
then back to long - compute the divergence (if any) - print (in hexadecimal)
the long value and the divergence.

Article UoM conversion differs from Inforecord UoM conversion

Hi experts,
While creating article through MM41(ALE), in basic data, we have maintained base UoM as KG and another UoM 1 CAR = 12 KG. The article is gettting created properly.
But the issue is the conversion for CAR is not reflecting correctly in the info record, it is 1 CAR = 1 KG in inforecord. In Purchasing view, We have maintained CAR as order unit. and variable order unit as 2 (active with own price).
The conversion in inforecord should be as same as the article UoM conversion. Can you please throw some light on why is this happening?
Many thanks,
Maniraj

Hi,
I have checked inforecord log, there is no change log.
If the UoM measure has not been transferred to inforecord, the ideal conversion should be 1 KG = 1 KG, but in my case its 1 CAR = 1 KG, the order unit is getting transferred, why not the conversion value (1 CAR = 12 KG).
When i create directly throught MM41, all the details in the Note applies, and everything is fine.
Thanks,
Maniraj

UOM conversion problem when issuing material against BOM

Hi All
I have a material which is part of a production BOM.
The base UOM is EA.
The issuing UOM is KG.
I have a UOM conversion of 20 KG = 1 EA.
In the BOM I need to issue 0.034 KG.
When backflushing happens, it issues 1 EA.
Why is it not issuing in KG?
This is a problem because in effect i have now issued 20 KG instead of 0.034 KG!
Any help would be much appreciated.
Thanks
Deidre

Dear All
Thank you for your input. I have double checked and everything in the BOM header and component level is KG, and the plant/storage location data is also KG. The only place the EA appears is in the base uom.
I suppose the biggest mistake is that the material should have been created with base UOM of KG, but it's too late to change it now, which is why I hoped the UOM conversion would have taken care of that.
@Mario, i was actually trying to post 0.034 KG, which then got posted as 1 EA.
Thanks
Deidre

How to calculate UOM conversion rate

Hi All,
Whether there is any Standard API available to calculate the UOM Conversion rate.
There can be interclass intraclass or standard conversion.
Please help.
Thanks,
Arun

Hi,
If the Business no longer uses the 500 pcs conversion, one could Inactivate the conversion and define a new one.
If Business wants to have a choice of using 500 or 450 pcs, then a new Case UOM needs to be defined.
I hope this helps.
Regards
Adarsh Krishna

Automatic UOM conversion

Similar Messages

Maybe you are looking for