Skip to Content
avatar image
Former Member

Setting up UOM's

I need to know if I am doing this process correctly. It seems that it is a duplication of effort and probably more than is required.

We are on SRM 4.0, ECC 5.0, and using classic scenario.

Before we went live last year with SRM, a comparison of UOM's and ISO codes was necessary between SRM and R3. If they were out of sync, an adjustment was done. If a UOM existed without an ISO code, I had to create a new ISO code.

In the setup process of punching out to other vendors, a list of UOM's had to be provided by the vendor. If the UOM was not set up in SRM or R3, we had to create it. Therefore, case could appear multiple times (CA or CS). We tried a mapping table within SRM. But, the items would not come over to SRM after checking out of the vendor if their UOM did not exist. The mapping table would take CA and turn it into CS on the shopping cart.

It would appear that I am doing more than is necessary. Does anyone have any documentation on how UOM's should be set up in SRM and R3 when punching out to other vendors? Is there an easier way?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Aug 22, 2006 at 08:38 AM

    Hi Monique,

    As far as I know UOM/ISO Codes and Currencies we have to transfer from R/3 to SRM System or we have to download in the SRM system and than mapped with the R/3.

    We do at the time of initial downloading i.e DNL_CUST_BASIS.. i.e for UOM/ISO Codes and Currn.

    Once u download it successfully than only u can mapped with the respective backend i.e R/3.

    Is this is the ans ur looking for if its solve ur purpose award the point.


    Vijay Mittal

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Monique,

      I am experiencing the same problem you did. Regardless of the UOM in R/3, in SRM, i dont want to create new UOM for every external vendor. We have created a Z table mapping utilising the Catalog BADI - however, this only seems to work if we maintain the Vendor UOM in CUNI, which as you say, defeats the purpose of this exercise. Can you please offer any suggestion? I appreciate your time!!!

      regards Adam