on 05-03-2007 10:17 AM
Hi,
I have a File (1) to File (*) scenario.
Both my input and output structures are the same
A typical input XML example would be
<?xml version="1.0" encoding="utf-8"?>
<n0:FileInterfaceFCC xmlns:n0="http://kpr.com/sample">
<Item> ( occurence 0....Unbound)
<Name>TestFCC</Name> ( occurence 1 )
<Age>10</Age> ( occurence 1 )
</Item>
</n0:FileInterfaceFCC>
The output structure is the same. My requirement now is that, i would like to have separate files for each difference in <name> </name>.
How can i achieve the same. What mapping principles should I use.
Thanks,
Abhishek
Hi,
In the mapping you map your name --> splitbyvalue(ValueChanged) --> to the root of the target message. Then do the mapping.
Then in the sender communicaiton channel put no. of records per message is 1.
So on each change in name your file sender communicaiton channel will take 1 message at a time. In the file reciever communication channel you put the mode as timestamp. So for each and every change in the name you will one file. This may increase your traffic in XI.
---Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhishek,
Please use multimapping for this.
Set Recordset per message = 1 in your sender file adapter.
And Map one to one with the item(occ 0 to unb) to the header node of the receiver adapter.
This will solve your purpose.
Thanks
Amitanshu
Please Reward Points if you find the answer helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi-
Try multimapping
http://help.sap.com/saphelp_nw04/helpdata/en/21/6faf35c2d74295a3cb97f6f3ccf43c/content.htm
Some more helpful links
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.