on 08-08-2008 10:42 AM
I have an incoming XML that contains a list of payments and I need to generate a file for each entry (payee) that that is going to be FTP'd. Not all the account numbers will be unique but I still want to generate a unique file for each entry. For example the following inbound XML
Incoming XML
<Payee>
<Acccount>00194763</Acccount>
<Amount>MESSAGE AA</Amount>
<Text>Payment to customer XXXXXXXXX</MoreText>
</Payee>
<Payee>
<Acccount>00192873</Acccount>
<Amount>MESSAGE BB</Amount>
<MoreText>Payment to customer YYYYYYYY</MoreText>
</Payee>
Would be transformed into two outbound XML files as follows
Message ONE
<Payment>
<Acccount>00194763</Acccount>
<Amount>MESSAGE AA</Amount>
<Text>Payment to customer XXXXXXXXX</MoreText>
<Text>Additional Text I've added</MoreText>
</Payment>
Message TWO
<Payment>
<Acccount>00192873</Acccount>
<Amount>MESSAGE BB</Amount>
<MoreText>Payment to customer YYYYYYYY</MoreText>
<Text>Additional Text I've added</MoreText>
</Payment>
Would I use a transformation step? How would BPM know where to split the incoming file as I'm not checking for particular values.
Your help is appreciated
If only purpose if using BPM is to make use of Multimapping, then don't use BPM. See this
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've had a look at the following blog....
When testing the output appears as a single document although it does contain separate messages. According to the blog Messages that result from the split in a mapping-based message split are sent using one AE. So only adapters running on the AE are supported. In particular, this means that target IDOC message splits are not supported since the IDOC adapter is not part of the AE.
I'm using the file adapter, is this what is causing the problem? Is there anyway around this?
Sorry Farooq, the message is appearing in MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>Split mapping created no messages</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Split mapping created no messages</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
My input message is as follows....
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ns1:MT_INPUT xmlns:ns1="urn:xxxxxx.com/TRAINING:MESSAGE:SPLIT">
<INPUT>
<NAME>brad</NAME>
<TEST>aaaaa</TEST>
</INPUT>
</ns1:MT_INPUT>
<ns1:MT_INPUT xmlns:ns1="urn:xxxxx.com/TRAINING:MESSAGE:SPLIT">
<INPUT>
<NAME>matt</NAME>
<TEST>bbbbbb</TEST>
</INPUT>
</ns1:MT_INPUT>
</ns0:Message1>
</ns0:Messages>
Take out you source message and delete the tags that I mentioned in the bold.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ns1:ASH_MULTI_Message1 xmlns:ns1="http://ASH_MULTI">
<age>21</age>
<name>Ashish</name>
<location>Melbourne</location>
</ns1:ASH_MULTI_Message1>
</ns0:Message1>
</ns0:Messages>
Thanks
Farooq.
Hi,
First of all just to split message you need not required BPM.
Just map your payee node to payment node in target.
I hope I have understood your reqts correctly.
Thanks,
Tuhin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure how I would split a message using standard mapping. When I say I want to split a message I mean take ONE XML document and create SEVERAL flat files (depending on the number of entries in the XML.
In mny example I have two payments in the XML document and I need to create TWO seperate XML documents that I will use to create TWO seperate flat files.
I
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.