Setting up UOM's

[former_member114630]

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?

[Former Member]

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.

BR,

Vijay Mittal

[former_member114630]

I am able to set up the UOM/ISO codes in both systems. However, my issue is with the punchout vendors. If I select an item from a vendor using an UOM that is not in our systems, do I have to create it in our system? We created a Z table in the SRM backend system that would map those UOM's to one of our own. But, that did not appear to work unless I actually set up the vendor's UOM in our system as well. That sort of defeats the purpose of mapping to our existing UOM's.

I just need to find out what is the best approach to UOM's and making it work with our vendors.

[yann_bouillut]

Hi Monique,

That's correct : you have to maintain ISO and UOM in SRM as well as in ECC/R/3 before you can wrok with a punchout catalogue.

Step 1 : identify the supplier catalog punchout ISO codes

Step 2 : maintain ISO and UOM in SRM and ECC/R/3

Kind regards,

Yann

[Former Member]

Yann/Monique,

I dont think so we need to maintain UOM in SRM and R/3. We need to maintain it right only in R/3.The key is that we need to maintain synchronized data between R/3 and SRM and this is achieved by maintaining everything right in R/3 and replicating the customizing object DNL_CUST_BASIS3. This will bring in all UOM in SRM.

This will achieve your synchronization for punch outs and in-house catalogs.

Thanks,

Sundeeo

[yann_bouillut]

Hi Sundeep,

"Maintaining in both SRM and R/3" does not mean that you have to do it twice

Kind regards,

Yann

[Former Member]

Yann,

Thanks for the clarification. It was a little misleading.

Sundeep

[former_member114630]

I actually do it twice - first in SRM and then again in R3. I never did the copy from R3 to SRM.

Then, I guess the mapping table we created is useless if I still have to create the vendor's UOM's. This will make the UOM table messy with multiple codes for the same thing (ie CA and CS for case).

If there is an easier way to do all this, please let me know.

[Former Member]

Monique,

The easiest way is to identify all the UOM and iSO codes and maintain them right in R/3 and pull them with R3AS in SRM. There is also a way of mapping...i dont remember out of my head...i.e. mapping commercially used to ISO code and things like that.

We had the same situation and the problem was resolved by identifying and maintaing everything right in R/3 and pulling them into SRM. If any further clarifications needed let me know.

Thanks,

Sundeep

[former_member114630]

The process I used to replicate the UOM's is probably the same as using R3AS. I would go through the IMG, pull up the UOM/ISO Codes, and click Adjustment. That would compare the two system and update as necessary. I only used R3AS when we went live with SRM and haven't done it since. Our consultants did not tell me that this would replicate the UOM's for me.

I just don't like the idea of having multiple codes for the same thing.

Thanks to you and Yann for helping me with this topic.

[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