Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from TerryB on Jun 11 at 12:37 PM Robert,
When we first implmented SAP we had a similar situation. Since we had already developed (and tested) the LSMW process, we decided to just use that same LSMW for periodic data synch jobs. The only extra development was on the legacy system side, to detect when customer creation or change occurred, and write to a flat file that would then periodically be processed by LSMW. It was not as real-time or as automated as a "real" interface, but it required only a small amount of extra development effort, and worked well during the interim period until the legacy system was retired.
Cheers,
TerryB
| | | ---------------Original Message---------------
From: robert phelan
Sent: Friday, June 08, 2012 9:41 AM
Subject: Master Data Management (Customer / ShipTo)
I have a non-SAP friend whose company is implementing SAP currently. He asked my advice on this:
They are not currently going to use SAP as the master data source for their SoldTo / ShipTo information. They have an established 3rd party system for this.
However, they need this info for billing etc? So they need to migrate and keep this info current. And eventually down the line, they will use SAP as the master data source.
Their lead developer consultant said there was no way SAP could handle this. He's obviously wrong.
The only thing I could come up with is, after all the data is migrated via LSMW, to have an inbound iDoc process the changes.
Can you think of any other viable options?
Thanks,
Robert. |
| Reply to this email to post your response. __.____._ |   _.____.__ |
