Knowledge Management

Question:
We have a situation where one of our widely used vendors has been absorbed by another of our larger vendors and we wish to consolidate the former vendor under the new group.
This leaves us with many thousands of Purchase Info Records which 'belong' to the old vendor and need to be transferred to the new vendor. I'm thinking about LSMW, but perhaps MEMASSIN could do it better?
I'd like to, preferably, change the vendor number against all Info records for the old vendor to the new vendor number (but as the Vendor number is part of the key to EINA I suspect this isn't possible??)
So second best would be to use MEMASSIN to create new info records with reference to the old ones. But I can only get this to work by Info Record Number (not vendor number) which doesn't really help.
Any help gratefully received
Answer:
Hi,
Have you ever thought of changing the name of the vendor master record instead of creating the new vendor master record and then updating the purchasing master data?.
Cheers,
HT
Answer:
Hi,
Forgot to log into the system using my own name.
Cheers,
HT
_________________
Moderator:

Answer:
We do still have this option, but from both a future analysis perspective and an 'ease of use' perspective, we believe the best solution is to combine all future purchases under the same account (if we can do it easily).
Unfortunately, this vendor supplies over 5000 materials to 120 plants, so manual exercise will take ages
Answer:
Hi,
We do still have this option, but from both a future analysis perspective and an 'ease of use' perspective, we believe the best solution is to combine all future purchases under the same account (if we can do it easily).
As I have said that if you are purely changing the description of the vendor name (instead of the vendor number), then you don't have to worry about historical data at all since the same vendor number is seen.
Cheers,
HT
_________________
Moderator: