on 06-21-2007 7:18 PM
Hi All,
I am working on a scenario in which multiple IDOCs are pushed from R/3 to XI. I have created a BPM to merge these IDOCs as per the guide lines given on number of postings/weblogs like Pooja Pandey, Michael and even SAP Basis. But I failed to figure out what the problem is.
XI successfully delivers the IDOCs as XML in a file. But only first IDOC is delivered. The rest of IDOCs are missing. I read a lot about setting '0..unbounded' for IDOC tags but could not set it. While setting the occurences I compared my Message Mapping with BpmPatternCollectMerge in SAP Basis and set as follows.
Source:
Messages 1..1
Message1 1..1
ZUPFIN... 0..unbounded
IDOC 1..1
...and so on
Target:
Messages 1..1
Message1 1..1
ZUPFIN... 1..1
IDOC 1..1
... and so on
Any idea what is going wrong in this ?
Thanks a lot.
- Atul
Atul,
In your source message the ZUPFIN is 0..unbounded , in target the ZUPFIN is 1..1 , so u will get only one occurrence. Which segment u want to multiple times.
Best regards,
raj.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raj,
I tried to change the occurence to 1..unbounded but could not. I copied and pasted the xsd of this message and corrected it to be 1..unbounded. But when I did 'Import XML or xsd', it removed 'Messages and Message1 nodes. I have read somewhere to 'Export xsd' in 'Tools'. On what screen this menu is displayed ?
Thanks.
- Atul
HI,
In Message Mapping -->Go to Messages Tab and make the occurence of the source as 0..unbounded
Hope ur interface mapping also in the similar lines.
Now, make sure that your target structure can hold multiple IDOCS. for that you need to have your parent of IDOC node should occur multiple times in that target structure..This blog may give some idea if you closely observe.
/people/narendra.jain/blog/2005/12/30/various-multi-mappings-and-optimizing-their-implementation-in-integration-processes-bpm-in-xi
Rgds,
moorthy
Experts,
Has any body idea, why it gives following error message when I try to import the target message after adding maxOccurs="unbounded" ?
"<i>Imported messages can only be used when the source and target messages have the frequency value 1 The source message has a frequency value of 0..unbounded. Change the frequency on the "Messages" tab page</i>"
Thanks.
- Atul
Hey
i m not sure if you have some other requirements too coz of which ur using BPM,but if ur using BPM just to bundle IDOC's,then you can easily do that without BPM
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
thanx
ahmad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
You are getting multiple IDOCs into BPM. But output you are getting one message right? IF so, your N:1 Mapping is not done correctly.
i.e your target message type should have occurence of 1..n and also the interface mapping. Closely obsever the N:1 mapping done in the BpmPatternCollectMerge.
Also go to SXMB_MONI->PE and check the Technical Details to make sure that, you are getting multiple IDOCs and you are executing the N:1 Transformation step correctly.
Also in the N:1 Mapping, check out the context you used. Make it root . Then test the mapping independently in the Integration Repository.
Hope it helps,
Regards,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Moorthy,
I checked the mapping in BpmPatternCollectMerge. It is 0..unbounded in source and 1..1 in target.
As you have mentioned, I tested the mapping in IR. I duplicated 'Message1' node by 'duplicate subtree' option and then tested. The target contained only ONE IDOC. I did not populate the IDOC fields, though. Then I duplicated IDOC node on the source, but the result is the same. Before this test, I changed the occurence to 0..unbounded on target message.
- Atul
User | Count |
---|---|
88 | |
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.