on 05-13-2008 10:12 AM
Hi All,
I am getting my output from XSLT mapping like below:
<?xml version="1.0" encoding="UTF-8" ?>
<ZORDERS5>
+ <IDOC BEGIN="1">
.......
......
+ <IDOC BEGIN="1">
......
......
</ZORDERS5>
But in the SAP R/3 it is able to post only the last IDOC (which is second IDOC in this case). I want to post all the IDOCS. What could be the problem?
Edited by: sreinivas prak on May 13, 2008 11:12 AM
Hey,
I had the same problem.
But I made a mistake by changing the occurences.
I used minOccurs="0" maxOccurs="Unbound" instead of only maxOccurs="Unbound"
After deleting the minOccurs it worked.
Maybe you made the same mistake.
Steven
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Steven Dierick. I changed the occurences but didn't activated the IR object. After activating it is working perfectly fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for answers. I will check by changing the occurences.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As the picture of IDOCS (bottom of page in step 7) shown in the blog "/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change with multiple IDOCS, I also have the same structure for multiple IDOCS from XSLT Mapping. There he didn't use any BPM scenario to post the IDOCS. SO do I really need BPM scenario for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you dont have any problem in Mapping and you are able to see the different IDocs in your target structure. Am i correct?
I am assuming you are facing problem while posting differnent Idocs into SAP system via Inbound functiom module which is asssigned to process code.
Can you check, the function module can process different Idocs, Is it looping Control records over Data records, Control and Data records filled properly or not.
Thanks,
Bala
Do I really need to use BPM for this scenario?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can achieve this problem with the usage of BPM.
After receving multiple IDocs into your Multi IDoc Structure, You can use BPM to split Multi IDocs into Single IDocs Strucute. For this use Mode of the Block step as ParForEach so that it will send each IDoc to your Target Structure and will post all the IDocs.
Please let me know if have any questions.
Thanks,
Bala
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am getting my output from XSLT mapping like below
You are implementing the mapping with XSLT technique.....then there is no use to change the occurence of IDOC and imported the XSD again...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My Target message interface is imported external definition of IDOC with occurences changed to unbounded.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have changed the occurences in IDOC as unbounded and imported as XSD. I am able to collect multiple IDOCS. But I am not able to post as IDOCS in SAP R/3.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you tell me what you have mentioned in the target message interface in the interface mapping.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
1)export your IDOC definition from your R/3
2)change the occurance of the IDOC segment so it will allow many
IDOC segments (set the occurance to unbounded )
3) import the IDOC definition again as the "External definition"
4)create a mapping from you source message type to the created external IDOC definition
5)test the scenario you should be able to see that the occurance of the IDOC segment is not 1..1 anymore.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srinivas,
Post multiple IDOCS
There are two Message Mappings involved in the whole scenario. First mapping is N:1 Mapping which will be used in BPM and second Mapping is 1:1 Mapping:
1. First Message Mapping  N: 1 Mapping between IDoc (occurrence 0...unbounded in Messages tab) to IDoc with changed occurrence of its top node (IDOC) as 0...unbounded.
Check these Blogs:
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
/people/stefan.grube/blog/2006/09/18/collecting-idocs-without-using-bpm
/people/sap.user72/blog/2005/01/28/setting-up-inbound-qrfc-queues-for-serializing-idocs-using-the-idoc-adapter
/people/prasadbabu.nemalikanti3/blog/2006/02/24/collecting-and-bundling-vendor-records-from-different-multiple-interfaces-file-systempeoplesoft-and-sending-to-sap-r3-system-part-1
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on May 13, 2008 11:21 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Apply this Blog for your requirement
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
REgards
Seshagiri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The problem is with the occurrence of idocs. Export idoc as xsd. Change the occurrence from 1..1 to 1..9999 and reimport it in XI as xsd. Use it for mapping
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
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.