Secondary Data Determination Convert UoM from Alternate to Default

[Former Member]

Hello! The problem I am having is that data can be entered in Units of Measure that are not the default, but when moved to another characteristics, the values are converted to the default values of the new characteristic. Note - when the data is being moved to a different characteristic, the new characteristic is a copy of the existing characteristic, so configuration on both characteristics is the same.

Example for Melting Point (Phase Transition Solid/Liquid): the value can be entered in °F, even though the default for the Value characteristic is °C. When the data is saved to the properties tree, the temperature remains unconverted (still in °F). We then execute EH&S Expert Rules though Secondary Data Determination to move the information to a copy of the Melting Point characteristic, which still has the default UoM of °C. When the data is saved to this copy of the Melting Point characteristic the data is converted from °F to °C (and the numeric conversion is mathematically correct). However, we want the value and unit of measure to remain unconverted.

This same situation is happening with other units of measure, it s not unique to just temperature. Also, it occurs in the ABAP processing but it seems to be a background conversion because in debug mode, you cannot see the actual change in the internal tables.

Has anyone else experienced this? Have you found a solution?

Points rewarded for helpful answers!!!

Thanks,

Amy

[Former Member · Accepted solution]

Hello Amy,

I assume that the rule which copies the data is a custom rule?

If I remeber it correctly there is a setting in the mapping MDBs of expert where you can specify, that you want to keep the UoM and not use the system default.

EH&S Expert uses this to write the explanatory comment of the rule set (So that it states you entered the value in °F and not in °C).

I would think that should work for you as well....

Hope this helps

Mark

[Former Member]

Hi Mark,

Thank you for the information! The database option I used was /STRING. This left the unit of measure (UoM) unchanged. I found a list of database (.mdb) options at the Fact Level and am including for any future readers of this thread.

[http://help.sap.com/saphelp_470/helpdata/en/32/b292c6f3de11d2b518006094b92d29/content.htm]

Thank you again!!!

Amy