BPM Multi Line Container in Integration Process Applies to: SAP XI 3.0. For more information, visit the SOA Management homepage. Summary The requirement is that individual employee details are to for a particular week be sent to the receiver system. Author: SrinivasaPhani Potharaju Company: Gems Techno Solutions India Pvt Ltd, an EDS Company Created on: 20 March 2008 Author Bio: SrinivasaPhani is an SAP XI consultant working in Gems Techno Solutions as a Senior Software Engineer. 2008 SAP AG 1
Table of Contents Business Requirement, Data types, Message types...3 Source Structure...3 Target Structure...3 Message Mapping...4 Interface Mapping...4 Integration Process...5 Sample of 2 Input Output Files...5 File1...5 File2...6 Related Content...6 Disclaimer and Liability Notice...7 2008 SAP AG 2
Business Requirement, Data types, Message types The Business requirement is to send the new joinees (employees) of an organization to the receiver system. All The Sent Files will be in the multi line container for the time specified in the BPM and then and sent individually to the receiver Source Structure Target Structure 2008 SAP AG 3
Message Mapping We used XSLT mapping: <?xml version='1.0'?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/xsl/transform" xmlns:ns1="http://ehro.eds,com/pspc/bpm/scenarios"> <xsl:template match="/"> <ns1:newjoineed> <xsl:value-of select="ns1:newjoinees"/> <xsl:for-each select="ns1:newjoinees/join"> <Join> <FirstName> <xsl:value-of select="firstname"/> </FirstName> <LastName> <xsl:value-of select="lastname"/> </LastName> <middlename> <xsl:value-of select="middlename"/> </middlename> <dateofj> <xsl:value-of select="dateofj"/> </dateofj> <desg> <xsl:value-of select="desg"/> </desg> </Join> </xsl:for-each> </ns1:newjoineed> </xsl:template> </xsl:stylesheet> You zip the code and import in to Imported Archives Interface Mapping Here my outbound message interface is Newjoinees and inbound interface is Newjoined. Use the mapping program imported in to imported archives here 2008 SAP AG 4
Integration Process The design of integration process and the container variables used By this way you can put 500 files and get 500 output files. Sample of 2 Input Output Files File1 <?xml version="1.0" encoding="utf-8"?> <Join> <FirstName>sriya</FirstName> <LastName>Sinha</LastName> <middlename>sree</middlename> <dateofj/> <desg>swe</desg> </Join> </ns0:newjoineed> 2008 SAP AG 5
File2 <?xml version="1.0" encoding="utf-8"?> <Join> <FirstName>Srinivasa</FirstName> <LastName>Phani</LastName> <middlename>chandra</middlename> <dateofj/> <desg>swe</desg> </Join> </ns0:newjoineed> Outputs generated 1)<?xml version="1.0" encoding="utf-8"?> <Join><FirstName> sriya </FirstName> <LastName>Sinha</LastName><middlename>Sree</middlename><dateofj></dateofj><desg>Swe</ desg></join></ns0:newjoineed> 2)<?xml version="1.0" encoding="utf-8"?> <Join><FirstName>Srinivasa</FirstName> <LastName>Phani</LastName><middlename>Chandra</middlename><dateofj></dateofj><desg>Sw e</desg></join></ns0:newjoineed> Related Content http://help.sap.com/search/highlightcontent.jsp http://help.sap.com/saphelp_nw04/helpdata/en/41/e3d13f7fb44c21e10000000a1550b0/frameset.htm For more information, visit the SOA Management homepage. 2008 SAP AG 6
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. k 2008 SAP AG 7