Oracle and EPSG and Units Of Measure tabel.
I believe there is a wrong value in the Oracle 11g Enterprise database on Windows 64 bit.
We installed this a couple of months ago and found out that the Units Of Measure table is different from a Oracle 10g.
Here is what I think is wrong.
Oracle 10g Express Edition
9101 radian Radian angle 9101 1 1 ISO 1000:1992 EPSG FALSE
9102 degree Decimal Degree angle 9101 3.14159265358979 180 EPSG FALSE
9103 arc-minute angle 9101 3.14159265358979 10800 EPSG FALSE
9104 arc-second angle 9101 3.14159265358979 648000 EPSG FALSE
9105 grad angle 9101 3.14159265358979 200 EPSG FALSE
9106 gon angle 9101 3.14159265358979 200 EPSG FALSE
9107 degree minute second angle 9102 EPSG EPSG FALSE
9108 degree minute second hemisphere angle 9102 EPSG EPSG FALSE
9109 microradian angle 9101 1 1000000 ISO 1000. EPSG FALSE
9110 sexagesimal DMS angle 9102 EPSG EPSG FALSE Oracle 11g Enterprise
9101 radian Radian angle 9101 1 1 ISO 1000:1992 EPSG FALSE
9102 degree Decimal Degree angle 9101 3,14159265358979 180 EPSG FALSE
9103 arc-minute angle 9101 3,14159265358979 10800 EPSG FALSE
9104 arc-second angle 9101 3,14159265358979 648000 EPSG FALSE
9105 grad angle 9101 3,14159265358979 200 EPSG FALSE
9106 gon angle 9101 3,14159265358979 200 EPSG FALSE
9107 degree minute second angle 9101 EPSG EPSG FALSE
9108 degree minute second hemisphere angle 9101 EPSG EPSG FALSE
9109 microradian angle 9101 1 1000000 ISO 1000. EPSG FALSE
9110 sexagesimal DMS angle 9101 EPSG EPSG FALSE It is all about the conversion from 9110 to 9101.
11g tells me do nothing.
While 10g tells me to go via 9102, which in the end does pi/180.0.
I've checked EPSG v6.17 (Access database) which is similar as 10g.
Is it a know bug in Oracle 11g (why change it in the first place? it was correct).
I filed this as a bug (9534127), and it's fixed.
The following is the workaround (as mentioned in the bug description):
begin
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9107; -- degree minute second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9108; -- degree minute second hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9110; -- sexagesimal DMS, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9111; -- sexagesimal DM, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9203; -- coefficient, based on 9201
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9115; -- degree minute, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9116; -- degree hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9117; -- hemisphere degree, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9118; -- degree minute hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9119; -- hemisphere degree minute, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9120; -- hemisphere degree minute second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1 where
uom_id = 9121; -- sexagesimal DMS.s, based on 9102
end;
begin
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9107; -- degree minute second,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9108; -- degree minute second
hemisphere, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9110; -- sexagesimal DMS, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9111; -- sexagesimal DM, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9115; -- degree minute, based on
9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9116; -- degree hemisphere, based
on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9117; -- hemisphere degree, based
on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9118; -- degree minute hemisphere,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9119; -- hemisphere degree minute,
based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9120; -- hemisphere degree minute
second, based on 9102
update mdsys.sdo_units_of_measure set factor_b = 3.14159265358979, factor_c
= 180, target_uom_id = 9101 where uom_id = 9121; -- sexagesimal DMS.s, based
on 9102
end;
begin
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9001 where uom_id = 10031; -- Meter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9001 where uom_id = 10032; -- Meter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
target_uom_id = 9001 where uom_id = 10033; -- Kilometer, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1000, factor_c = 1,
target_uom_id = 9001 where uom_id = 10034; -- Kilometer, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
target_uom_id = 9001 where uom_id = 10035; -- Centimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .01, factor_c = 1,
target_uom_id = 9001 where uom_id = 10036; -- Centimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
target_uom_id = 9001 where uom_id = 10037; -- Millimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .001, factor_c = 1,
target_uom_id = 9001 where uom_id = 10038; -- Millimeter, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1609.344, factor_c = 1,
target_uom_id = 9001 where uom_id = 10039; -- Mile, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1852, factor_c = 1,
target_uom_id = 9001 where uom_id = 10040; -- Nautical Mile, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .3048006096012, factor_c =
1, target_uom_id = 9001 where uom_id = 10041; -- U.S. Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .3048, factor_c = 1,
target_uom_id = 9001 where uom_id = 10042; -- Foot (International), based on
10032
update mdsys.sdo_units_of_measure set factor_b = .0254, factor_c = 1,
target_uom_id = 9001 where uom_id = 10043; -- Inch, based on 10032
update mdsys.sdo_units_of_measure set factor_b = .9144, factor_c = 1,
target_uom_id = 9001 where uom_id = 10044; -- Yard, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 20.1168, factor_c = 1,
target_uom_id = 9001 where uom_id = 10045; -- Chain, based on 10032
update mdsys.sdo_units_of_measure set factor_b = 5.0292, factor_c = 1,
target_uom_id = 9001 where uom_id = 10046; -- Rod, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116619497596571965479068149417, factor_c = 1, target_uom_id = 9001 where
uom_id = 10047; -- Link, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30481225298450596901193802387605, factor_c = 1, target_uom_id = 9001 where
uom_id = 10048; -- Modified American Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30479726511509957523453133559723, factor_c = 1, target_uom_id = 9001 where
uom_id = 10049; -- Clarke's Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.30479951799004225054718498468167, factor_c = 1, target_uom_id = 9001 where
uom_id = 10050; -- Indian Foot, based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
uom_id = 10051; -- Link (Benoit), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.20116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
uom_id = 10052; -- Link (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
20.116782494375873394114972441151, factor_c = 1, target_uom_id = 9001 where
uom_id = 10053; -- Chain (Benoit), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
20.116765121552632252046201402296, factor_c = 1, target_uom_id = 9001 where
uom_id = 10054; -- Chain (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.914398553970126751641554954045, factor_c = 1, target_uom_id = 9001 where
uom_id = 10055; -- Yard (Indian), based on 10032
update mdsys.sdo_units_of_measure set factor_b =
.91439841461602873872937279101345, factor_c = 1, target_uom_id = 9001 where
uom_id = 10056; -- Yard (Sears), based on 10032
update mdsys.sdo_units_of_measure set factor_b = 1.8288, factor_c = 1,
target_uom_id = 9001 where uom_id = 10057; -- Fathom, based on 10032
end;
begin
update mdsys.sdo_units_of_measure set factor_b =
.017453292519943295769236907684886, factor_c = 1, target_uom_id = 9101 where
uom_id = 10001; -- Decimal Degree, based on 10002
update mdsys.sdo_units_of_measure set factor_b = 1, factor_c = 1,
target_uom_id = 9101 where uom_id = 10002; -- Radian, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.0000048481368110953599358991410235795, factor_c = 1, target_uom_id = 9101
where uom_id = 10003; -- Decimal Second, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.00029088820866572159615394846141477, factor_c = 1, target_uom_id = 9101
where uom_id = 10004; -- Decimal Minute, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
uom_id = 10005; -- Gon, based on 10002
update mdsys.sdo_units_of_measure set factor_b =
.015707963267948966192313216916398, factor_c = 1, target_uom_id = 9101 where
uom_id = 10006; -- Grad, based on 10002
end;
/
Similar Messages
-
Partner profile LI and unit of measure
Hi gurus,
I am experiencing a weird situation and probably you have any clue about it.
I have configured an output to send the Purchase order information via EDI. I have used the standard function and programs to create the output. I have created the condition record for that particular vendor and output.
Then i have created the LI partner profile in we20 with the vendor number and the message types ORDERS and ORDCHG and I have also included my output with the ME10 and the ME11 in each of the messages.
When i create the PO and the output is sent I have the PO number but then i have the standard error message " Update was terminated" with the error "There is no conversion factor for material and unit of measure !" I have reviewed the PO and i have used a UoM PC that i have as an ISO code.
the point is if I use a different LI partner profile with exactly the same information then the idoc is sent without any problem. I have deleted the partner LI that I orinally created and i created it again as a copy of the one that is working but without sucess.
I have reviewed the vendor master data...but all is exactly the same.
I think or there is some config missing or that I have created the partner profile incorrectly. But it is rare that the partner profile has any link to the UoM.
Do you have any idea what it can be?
thanks so muchI understand from your mail, you have maintained the ISO equivalence to your UOM. When you change your vendor in WE20, did you change that information in MN04? This is the place where the right output type is triggered.
Other than that make sure you configured all the necessary items in WE20 -> Outbound Parameters -> process code and all otehr necessary settings.
Let me know, how it works?
Regards, -
Supplement Units of Measurement and Units of Measure
Hi All,
The company i work for, the WM system fabrics are stored in the Roll based form and in the QM module i have to create inspection lot for it. I found in the customizing "Supplement Units of Measurement and Units of Measure" which i think will help me in my process. Please explain the procedure for the "Supplement Units of Measurement and Units of Measure" in customizing.
Regards,
DTDhttp://help.sap.com/erp2005_ehp_04/helpdata/EN/c6/f83bb94afa11d182b90000e829fbfe/frameset.htm
-
Change Material Number and unit of measure
Can we change material code and / or its Unit of measure . Please help
http://sap-img.com/materials/change-base-unit-of-measure.htm
Re: change material code
Change of unit of measure -
Material Master IDOC MATMAS05 and unit of measure
Hi
We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
Thanks
NileshThats the way it works. In any interfacie to or from external sys. , it uses the ISO code from CUNI instead of the UOM .
-
Invalid vales of characteristic and units of measure
Hello,
During the data load the system generated the following messages :
1. No SID found for value 'CBM' of characteristic 0VOLUMEUNIT
2. Value "X%X'''" (like that) of characteristic contents invalid letters
What do you reccomend to do?hi,
check table t006a if CBM is there.
if you load from r/3, you may need to transfer from r/3, by rsa1 > source system > right click 'transfer global setting'.
you can maintain the unit use transaction CUNI. -
Unit of Measures missing in Crystal XI
Crystal Reports XI fixpack 3.2.
I'm designing a crystal report that contains a distance field with a measurement and unit of measure. In bex the value displays correctly,eg. 104,000 KM. In crystal I have three options for my key figure: Value, formattted value and Unit.
The value field contains 104,000, the formatted value contains 104,000 KM and the Unit field should contain "KM" but it's empty.
I don't get anything from unit field for any of my data rows (about 100 rows returned).
Do I need to make some setting adjustment or something? Any and all suggestions are welcome.
Thanx,
erUpon further review I noticed that the Unit dimension is being correctly populated when the value is a monetary amount. For example $100 CAD, the CAD is populated in the Unit dimension for this key figure. The distance measurements (all KM) don't have anything.
The UOM is present in both key figures in the bex query when run in Bex Analyzer. -
I have my base unit of measure set as EA and in the additional unit of measure I'm trying to put a conversation to state that 1 EA = 165838 KG
The system wouldn't allow that since the this field in the table only accepts 5 characters and 0 dec. (it also saves the digits in x,xxx format which means I can only give 4 digits).
Is there anything to do to fix this? I can't store in Ton because it won't be accurate.
Thank youIdeally your base unit should be the smallest unit or a small unit. In this case KG should have been the base unit.
However, if you still wish to continue...
try using 500 EA = 82919 TON (This is exact if 1 TON = 1000 KG)
If it is not allowing 5 digits, and you are willing to have a minor approximation, you can use
50 EA = 8292 TON. At 1 TON = 1000 KG, this works out to 1 EA = 165840 KG (A difference of 2 KG from actual figure).
Hope this helps,
Lakshman
P.S. Dear Srao, changing the number of decimals in currencies and Units of measures is not recommended. -
Report on material code, description and all unit of measure conversions
report on material code, description and all unit of measure conversions ?
any ideas?Material Number MATNR
with this key and SPRAS (the desired Language key)
from MAKT you can get the descriptions..
and with MATNR from MARM you can get alternative UOM and the conversion rates.
If you need help on MARM how to get the conversions please notify.
Hope it helped
Please reward if found useful
Best Regards -
Unit of measurement for materials received and withdrawn
Hi Experts,
Base unit of material is KG whereas sales unit is M2 and conversion is maintained between both. Now I am using sale unit (M2) while entering material componenets. Then I am raising PR, PO, GR in project and withdraw the material in sale unit M2. But system updates the report in KG (under purchasing data tab of component). When I get material report, system shows reqmt qty in M2 but received and withdrawn qty in KG. Its confusing and doesn' serve the reporting purpose. Can we do something so that received and withdrawn qty will appear in M2 (sale unit) rather than KG (base unit)?
Thanks and Regards
Dinesh ChauhanHi,
To resolve this issue, you need to maintain the conversion factors. In material master, additional tab, unit of measure tab you need to maintain the conversion factors. Say example I Kg = How much M2. If you maintain this the system will convert automatically all the Kg in to M2, or vice versa you can do. Otherwise you can maintain the conversion factors in the Info Record also for externally procured materials.
Regards,
V. Suresh
Edited by: V.SURESH on Jan 5, 2009 12:19 PM -
Material Master MATMAS IDOC and base unit of measurement
Hi
We are using SAP standard material master IDOC type MATMAS05 to trigger IDOC. Our material master is having base unit of measure as "G". We are not using ISO unit of measurement. But Material master IDOC, segment E1MARM is populating base unit of meaurement (MEINS) as "GRM".
Any idea why IDOC is picking ISO unit of measurement instead of material master base unit of measurement.
Any idea how to send base unit of measurememt as "G" instead of "GRM" in DOC segment.
Thanks
NileshThere are ISO codes for country keys, currency keys, units of measure and shipping instructions. According to SAP design guidelines, you should use ISO codes for an IDoc if they are available. When you set up the IDoc, the SAP codes have to be replaced by ISO codes.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf -
Unit of measure for Stock and Non-stock Item in CJ20N
When I attach Material to an activity (item Category N Non-stock item) in Project Builder (CJ20N), It is peaking its Base unit of Measure as unit. Now when I try to change it, it is showing an error
Item category N: Only base unit of measure M allowed
Message no. CO344
But for the same material if I change the item Category to L Stock item, then it allows me to change the unit.
Please guide me regarding this Behavior. Is there any customization, by doing which it will allow me do the same for Non-stock Item or It is not Possible.firstly I am assuming that the activity is internal processing type - doesn't matter really
now to attach a material select actvity and from the template area click and drag material which will open the material detail screen in the work area
because it is a non stock item I am assuming text description - in the requirements qty you enter the qty and next to it the units - changeable
if you choose a material number maintained as material master then obviously the unit will be from the material master.
If you are using an externally processing activity then in config check OPUU for the network type and see if order unit has been populated - that might be the problem -
Views and Base unit of Measure is not coming in Chines Lang
HI All
Plz Help me.
I log-In Chines Server, during MM01 the views are coming in English language instead of chines.
and during PO creation The Base unit of Measure is not Coming in Chines Language it is displaying Some number??
I have maintained Source and taget lag in CUnI..but still Im getting this problem..
How to solve this plz help..
Thanks and regards
Ramesh reddyHi
Please maintain the translation in the Following Configuration
Logistics - General->Material Master->Configuring the Material Master->Define Structure of Data Screens for Each Screen Sequence
Select the Specific Screen Sequence & Maintain the languages
Similarly please maintain the Translations in the Transaction CUNI for the Base UOM in respective languages
I hope currently in your system only Language EN is maintained
Thanks
Madhav -
How to maintain space between value and base unit of measure in sapscript
Hi Guys,
I am working on an upgradtion project, i have problem like while upgrading from 4.6b to 5.0. i need to main a space between value and base unit of measure. can anyone letme know how to maintain in the form. I mean in sapscript.
Thanks,
YogeshThere are a couple of ways to handle this, if you need a bigger space between, you can use tabs in the paragraph format. Or you can just write the space in between the fields like so.
ZA &MSEG-MENGE& &MSEG-MEINS&
Regards,
RIch Heilman -
Stock and Values in Alternative Unit of Measure
Dear Experts,
Can anybody suggest me any Standard Report for Stock and Value in Alternative Unit of Measure.
Regards,
vgl
Edited by: vglokam on Aug 16, 2010 8:56 AMHi,
you cannot take stock report with alternate UoM. Alternate UoM is for "ORDERING" purpose only and not for SKU.
Arul
Maybe you are looking for
-
Error Message 1316 while uninstalling Java 2 Runtime Env SE v1.4.2_03msi
I recently updated to Java 10 while in the process of clearing some nasty virus/malware off my system. I worked with a tech guide to do the clean up. He told me to uninstall old updates, including Java 2 Runtime Environment, SE v1.4.2_03. In the proc
-
Warning For a Document that Deviates from the Budget:
Good Day! I want to have a warning for accounts that I used that deviates from a monthly budget. What I did is in the General Settings>>Budget Tab, I click budget Initialization and click WARNING", for monthly budget and also tick Purchase Orders,G
-
Hi, Is there anyway to increase the drawing sace size. I am in need of making wraps and fabric prints of up to 90' in length. Is there a better way of going about this? We have been decreasing the file size to 10% lets say and then multiplying the
-
Issues in Executing Database Trigger
Dear All, I wrote two triggers and the second trigger is dependent on the first trigger but the first trigger is not fired and if i inserted the record in the table omni_reportingdatastatus manually then the second trigger gets fired. 1) trigger CREA
-
Embedded Controller update (which is included with the BIOS update) for my T400
I have a T400. That's all I know. I'm supposed to dwonload one of these two updates. ThinkPad Package version BIOS version Embedded Controller version T400 (with IEEE 1394 models)