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
Nilesh

Thats the way it works.  In any interfacie to or from  external sys. , it uses the ISO code from CUNI instead of the UOM .

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 much

    I 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,

  • Error while creatting the Material Master IDOC in ERP 2005

    Hello All,
    I am trying to create scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0).
    I am using Auto ID 4.0 on a NW04s system. The backend is a ERP2005 system.
    The scenario requires that I need to create a material in the backend and send it to the NW04s system using IDOCs.
    After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID from the transaction AIDMM. I get a message that IDOC is just being created. But I could not find it in the transaction WE02.
    On debugging I found that the function MARD_GENERIC_READ_MATNR_PLANT resulted in error.
    Thanks for any kind of input.
    Regards,
    Rahul
    Message was edited by:
            Rahul Gavande

    Dear,
    Check ABAPer for file settings.
    - CANNOT_SKIP_ATTRIBUTE_RECORD : The attributes could not be read in the EPS parcel. The file cannot be opened for reading, because it may have been deleted in the meantime.
    - CANNOT_DETERMINE_EPS_PARCEL : The EPS parcel is not in the EPS Inbox, because it may have been deleted. You must download the relevant patch again (for example, Hot Package).
    - CANNOT_DETERMINE_DATA_FILES : The name of a data file could not be determined, because a profile parameter was not correctly configured. Check the settings using the report RSPARAM.
    - CANNOT_DISASSEMBLE_R_DATA_FILE : An R3trans data file could not be unpacked. A possible error source is that the relevant EPS parcel was not found. The data file could not be opened for writing. An error occurred when transmitting a 20K block from the EPS Inbox to the directory /usr/sap/trans/data (UNIX).
    - CANNOT_DISASSEMBLE_D_DATA_FILE : An ADO data file could not be unpacked. The reasons are the same as with the message CANNOT_DISASSEMBLE_R_DATA_FILE .
    - CANNOT_CREATE_COFILE : The cofile could not be created from the relevant data file. One possible error source is that <sys>adm does not have write authorization for the directory /usr/sap/trans/cofiles (UNIX).
    Check Note: 70752.
    Regards,
    Syed Hussain.

  • Creting material master idocs

    Hi,
       i want to create a MAterial master idoc, whenever a material is created ( it should happen automatically).
    1. is it calling BD10 transaction in user exit for building IDOC
    2. Can it be done through Change pointers even in the case of Creatin gthe material.
    Cheers

    Hi Kumar,
    i have done change pointers method for a ztable,not used for standard table,but i can share the configurations which i did in my case.
    1>we81
    2>we31
    3>we30
    4>we82
    5>bd61
    6>scdo
    7>bd52
    8>bd51
    9>bd60
    10>we20
    11>bd64
    basically in ur case u have to create an object in SCDO,check the field matnr,go to dataelement and in further characteristics tabb u will find one chek box ,as its standard it will be check for zdataelement u need to check it.
    i have created one function module and wrote the logic for generating an idoc.
    chek all the tcodes .
    regards,
    Nagaraj

  • Error while sending Material Master IDOC to Auto ID

    Hello All,
    I am using Auto ID 4.0 on NW04s.
    The backend is ERP2005.
    I am trying scenario from RFID-Enabled Outbound Processing - Conf Guide (SAP AII 4.0)
    After completing the configuration on the backend, I tried sending the Material Master IDOC to Auto ID.
    I get a message that IDOC is just being created. I could not find it in the transaction WE02.
    Also, they are not appearing in the AII system.
    Thanks for any kind of input.
    Regards,
    Message was edited by:
            Rahul Gavande

    Hi Rahul,
    I have not worked on these version of products. And I don't know what changes have been done in the new versions.
    But still, can you let me know, what is the exact configuration that you have done and also
    which partner are you trying to send the IDOC. And if you are trying to send the IDOC then I will suggest to debug the transaction and see till what level it proceeds.
    Best of luck,
    Arundeep

  • Error while sending Material Master IDOC to Auto ID 2.1

    Hello All,
    I am using Auto ID 2.1 with SP1 on NW04.
    Integration server is XI 3.0 with corresponding XI Content for Auto ID.
    The backend is ERP2004.
    I am using the config guide for Auto ID 2.1.
    After completing the configuration, I tried sending the Material Master IDOC to Auto ID.
    IDOC gets created successfully. XI says the message transfer is successfully.
    In the log of Auto ID. I am getting the following error while importing the Material Master product:
    Product ID AUTOIDAII_MAT has an invalid format
    Internal error in /AIN/DM_PROD_COMMIT
    Message no. COM_PRODUCT897
    The description says that it may be a program error.
    Or the program expects some variable to be filled which has not occured.
    Any idea what could be the error. Or where should I try looking for to get more detail info.
    Do some one knows what should be the patch levels for the different components in all three servers for Auto ID 2.1 SP1.
    Thanks for any kind of input.
    Regards,
    Arundeep Singh

    HI Arundeep,
    use the following
    1) XI 3.0 SP level 12
    2) AII 2.1 SP2
    3) check in rfid outbound configuration guide for any customising for product to be done in AII
    regards,
    ashit singh

  • MATERIAL ON IDOC,ALE AND EDI

    hi,
        IF U HAVE ANY  MATERIAL ON IDOC,ALE AND EDI PLZ  SEND TO MY MAIL ID([email protected])  OR  GIVE ANY SITE ADDRESS?

    hi,
    for ALE/IDOC
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    For ALE -- IDoc's
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    ALE/ IDOC/EDI
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    ALE/ IDOC/ XML
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
    http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
    IDOC Convertion
    /people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    http://www.sapgenie.com/ale/why_ale.htm
    http://www.sapdevelopment.co.uk/training
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    for EDI
    check these links.....
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.onestopsap.com/interview-Question/ale/
    http://www.onestopsap.com/interview-Question/edi/
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sap-img.com/abap/ale-bapi.htm
    http://www.sap-img.com/basis/difference-between-edi-and-idoc.htm
    http://www.sappro.com/downloads/OneClientDistribution.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    Please check this link for EDI/ALE/IDoc online documentation.
    http://www.easymarketplace.de/online-pdfs.php
    good link
    http://myweb.dal.ca/hchinni/sap/idocs/IDoc%20Cookbook%20for%20EDI%20and%20Interfaces.doc
    If you need further info shoot me a test mail to [email protected]
    Regards,
    GNK

  • 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,
    DTD

    http://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

  • Post material master idoc  with class and characteristic values

    Hi,
    I need to post the class and characterstic values of material while posting the material using idoc of basic type matmas05 . Can anyone suggest me the fields and segment details to fill the class, class type and characteristic values in matmas05.
    Note : the class and characteristic values are already created in the system, my purpose is to assign them to material while creating. so please give me the field and segment details in idoc basic type matmas05.
    thanks
    Kiran

    I  try to do the samething. I see the fields E1CUVAL : CU: Characteristic valuation in the structure of MATMAS05 but when I run the IDOC, these fields never appear even they exist for the material.
    Did you find an answer to your question that can help me?

  • Material master for Rods and Plates.

    Hi all!
       I need to know the answer for two critical questions in SAP-MM. I have asked this question some time before but have'nt got any replies. Here again i throw the same.
    1. How to maintain material master for Rods of various diameter and length. One thing is sure that ordering unit is 'Kgs' and Basic unit of measure is 'mm'. I have a typical example for this. Say 1kgs=30mm. I am purchasing 1000 kgs (i.e.30000mm). In GRN i can receive the material as a whole stock say 30000mm.
           But eventhough the total length of the stock is 30000mm where can i maintain the breakage.i.e. for example say,
       1000mm - 10 Nos. 2000mm - 5 Nos. 2500mm - 4 Nos.
    some of our friends are saying that we can map this via batch. But even batch is not possible. There is a reason. Say if length is the batch number and basic unit of measure is Nos, then how can you give the conversion between Nos & Kgs in additional data. For example how can i say 1000 kgs = 1 nos or 2 nos. This will be ridiculous then. I can give every dia available into different material codes. Thats not a problem. But how to receive rods in different length. I need the length & numbers combination. Also while issuing the materal after cutting numbers should reduce accordingly.
    2. How to maintain the material master for Plates of various thickness. I think we can use Kgs as ordering unit and Sq.mm as basic unit of measure. How can we map the material issues to production for these kind of materials. We are issuing the material after cutting in 2-D only of various sizes in same material. No 3 domentional cutting is done. I need  the lenght & width to be changed accordingly after issuing. 
    Thanks in advance,
    Regards,
    Raj.

    Hi all!
    I need to know the answer for two critical questions in SAP-MM. I have asked this question some time before but havenu2019t got any replies. Here again I throw the same.
    1. How to maintain material master for Rods of various diameter and length. One thing is sure that ordering unit is 'Kgs' and Basic unit of measure is 'mm'. I have a typical example for this. Say 1kgs=30mm. I am purchasing 1000 kgs (i.e.30000mm). In GRN i can receive the material as a whole stock say 30000mm.
    But even though the total length of the stock is 30000mm where can i maintain the breakage.i.e. for example say,
    1000mm - 10 Nos. 2000mm - 5 Nos. 2500mm - 4 Nos.
    Dear
    ANS:
    First create different material code specific to length so identity of material at store will be their.(with specification at purchasing text tab)
    Now as ur sure with ordering unit keep as kg. (this is at info record level)
    Base UOM will be as MM (material master)
    So now about issue part keep conversion factor as u require and make some standard according ur client .
    some of our friends are saying that we can map this via batch. But even batch is not possible. There is a reason. Say if length is the batch number and basic unit of measure is Nos, then how can you give the conversion between Nos & Kgs in additional data. For example how can i say 1000 kgs = 1 nos or 2 nos. This will be ridiculous then. I can give every dia available into different material codes. Thats not a problem. But how to receive rods in different length. I need the length & numbers combination. Also while issuing the materal after cutting numbers should reduce accordingly.
    2. How to maintain the material master for Plates of various thickness. I think we can use Kgs as ordering unit and Sq.mm as basic unit of measure. How can we map the material issues to production for these kind of materials. We are issuing the material after cutting in 2-D only of various sizes in same material. No 3 domentional cutting is done. I need the lenght & width to be changed accordingly after issuing.
    ANS:
    Dear for this make material master as name with ur spacification and UOM as kg after cutting or processing according to Wight  u can make issue note in the system.
    Name as plate x*y sqr mm
    So ordering as kg
    Issue as kg

  • PO outbound IDOC - Issue with Unit of measure

    Hi,
    I am facing issue with unit of measure.
    1) In the PO outbound idoc in segment E1EDP01, the unit is always converted into ISO code and sent. Is there any way to avoid it.
    2) Now while changing unit to ISO code, it checks if it is preset in T006 table. Now in some of the cases like Unit FT3, there are no entries in T006 table, hence IDOC is going into error. Let me know how can this be resolved. Do I need to update T006 table if yes then how can I do it.
    Thanks.
    Regards,
    Shahu

    Sorry.. Posting it in ABAP Development forum.

  • Creating Material Master IDoc when creating a Material

    Hi Guys,
        My requirement is to trigger an IDOC at the time when I am creating a material using MM01 transaction. The Changepointer is active and when i am tring to send materials using BD10 it's showing that the IDOC is created which certifies that the config is OK. but when I am creating a material and saving it ..the same process is not triggering an Idoc.
    Can anyone help me out ...where I am missing out.
    Thanks
    Debasis Roy Chowdhury

    Hi Debasis,
    Activating pointers for the message type do not  trigger Idoc, we need to manually or scheduled the program to create the idoc against  pointers.You need to run BD21 transaction or  schedule RBDMIDOC .
    Go through this [Idoc Triggers|Automatic Trigger of Idoc Sending to PI on Material Master Create/Change;.There is a good discussions.
    Regards,
    Madhu.
    Edited by: madhurao123 on Feb 2, 2012 9:40 PM
    Edited by: madhurao123 on Feb 2, 2012 9:43 PM

  • Material master iDOC for inbound process

    Hi,
    I am trying to post the Data to the inbound iDOC for material master and i want to set the KZKUP(coproduct Flag) in MARA table but there is no field in the E1MARAM segment of the MATMAS03 iDOC to set this flag. There is one field in the E1MARCM segment but setting that is not reflecting in the MARA table it is setting in the MARC table only.
    So can anybody help me out in this.
    Thanks.

    Hi Dirk ,
    Thanks for your reply . Can we use matmas03 for loading. What will be the differences between these two IDOCS.

  • 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;
    /

Maybe you are looking for