Integrating MDM Server with Enterprise Information Systems using SAP as an example, Part 2, Enriching customer records with SAP specific information

From the developerWorks archives

Hans Schoen, Sebastian Nelke, and Mike Grasselt

Date archived: January 11, 2017 | First published: July 25, 2013

This article is a sequel to the "Integrating MDM Server with Enterprise Information Systems using SAP as an example, Part 1" tutorial. In Part 1, the focus was on propagating customer master data from an MDM Server to an SAP® system. Part 2 focuses on how additional information added to the records in the SAP system can be sent to a MDM Server. In the demonstrated scenario, the customer record previously propagated to the SAP system is enriched with an SAP-generated tax identifier. The SAP Intermediate Document (IDoc) mechanism is used to send the modified customer record from the SAP system to the Enterprise Service Bus (ESB). On the ESB side, the WebSphere Adapter for SAP Applications is used to pick up the IDoc and feed its data into a mediation flow. Based upon the provided data, the mediation flow creates the MDM Server web service requests updating the customer record with the tax ID.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=938234
ArticleTitle=Integrating MDM Server with Enterprise Information Systems using SAP as an example, Part 2: Enriching customer records with SAP specific information
publish-date=07252013