on 06-08-2015 11:00 AM
Hi Gurus,
I want to split single sender file to 2 messages using multi mapping to send to target system.
I heard that Multi Mapping is not possible if idoc is at receiver side.
but here
Sender adapter : File
Target adapter : Idoc and we are using PI 7.1 dual stack.
The file is split in to 3 messages, so that Mutiple IDOCs will be posted on target SAP system.
Sender side we are getting the XML file this is going to split in to 2 messages for below two different idoc which needs to be posted on Target SAP system.
CONF21.CONF21
MBGMCR.MBGMCR03
Please help any one to achieve this requirement with out using BPM as idoc is at receiver end.
Thanks and Regards,
Teja.
Hi Teja,
This can be achieved using Multimappings. pls ckh following links for details:
Hope it helps
Regards,
Azhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
Thanks for all your replies.
I am going to design and configure the objects in the following way please correct me if any thing goes wrong.
Sender (File) Receiver (Idocs)
-------------------------- ------------------------------------
ESR part
One data type importing two idocs (No DT.MT and SI's)
One Message type
One Service Interface
Message Mapping (Multimapping)
Operation Mapping
ID Part
One BS/BC Two BS for two idocs
Sender CC Two Receiver Communication Channels
One Sender Agreement Two Receiver Agreements
Receiver Determination
Interface Determination
I am going to plan to develop interface in above specified way.
Please any one guide me if any thing goes wrong.
Regards,
Teja.
Hi Teja,
Both are IDOCs only right, and which would go to Same SAP system, hence we could go for generic IDOC channel.
Normally, for SAP side communications, we would go for generic channels until and unless, if there is some specific requirement for the creation of another channel.
Regards
Vishnu
Hi Teja,
Yes, there would be one Sender Agreement(one message), one Receiver determination(one receiver which is SAP system), one Interface determination(one interface mapping in ESR) and , two receiver agreements(two different IDOC messages), but I think Rajashekar(in the blog) means only one generic channel in the receiver agreements.
Just try this out in your scenario. Lets see on the outcome..
Regards
Vishnu
>>> How you can create two receiver Agreements with One CC
This should be very much possible. We don't create separate receiver channel for every interface when the connecting system is same.
Receiver agreement should be unique for sender systesm, receiver system, inbound interface and inbound interface namespace but channel has got nothing to do.
Hi Hareesh,
Thanks for your reply.
As now i understood that There is no need to create another Receiver Communication channel for second Idoc as the connecting system is same.
Here we are going to post the data on ECC for different Idocs. So the connecting system is same.
So in ID part we are going to create One Receiver Communication Channel and two Receiver Agreements.
@Vishnu : Thanks
Regards,
Teja.
Hi Teja,
Please refer the below blog for reference.
File to Multiple IDOC Splitting without BPM - Process Integration - SCN Wiki
The only difference in this blog and your case is that you have two IDOCs but in the blog it is mentioned multiple IDOCs of the same IDOC.
Please check and let me know if you get struck anywhere.
Regards
Vishnu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.