on 03-20-2007 2:53 PM
We have the following scenario :
1. XI receives a orders05 idoc - xml and does a first message map - splitting this xml into two - a lookup key msg type and a copy of orders05 msg type ( 1:n )
2. These two messages from the first mapping are used in a second message mapping ( of type multi-mapping too ) ( n:1) to create the final orders05 message.
3. These two message maps are put sequentially in the interface mapping.
orders05 -> MessageMapping1 -> MessageMapping2 -> orders05 . Please note that our objective is to send one single ORDERS05 idoc into the end R3 system - using the idoc adapter. The use of multi-mapping is in the interim - and not in the idoc adapter.
Issues:
a. the "ns0:Messages" and "ns:Message[n]" tags are not being created automatically.
b. In the interface determination we do not see the interface mapping when we select the 'enhanced' option.
Any ideas, pointers as to what I am missing here ? I am on a critical timeline to implement this and can't understand whats going wrong ?
"b. In the interface determination we do not see the interface mapping when we select the 'enhanced' option"
for this ,can you please check the occurrences of Message types in MM as Chandra said and also in the Interface mapping occurences,then you should be able to see in Interface determination in ID with enhanced option.I did same mistake once.
Babu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
1. first chaeck the occurance of message types in the message mapping .whether it is 1:N or not.do the appropriate interface mapping
2. Then in the Interface determination check the enhanced key and there you have to specify 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
I don't think you can use 1:N and N:1 mappings in one interface mapping....
solution
create two interface mappings and use one message mapping
per one
this way it will work for sure - did it many times
Regards,
michal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply Michal. One question - does the series of interface mappings still do what I am looking for - i.e does i2 ( intf mapping 2 ) take the target messages of i1 and act on it to produce the final target messages ? This means we are executing two muti-mappings in sequence using two interface mappings to execute one after the other ?
Karthik.M
Michal,
In your suggestion - to use two interface mappings - how I can configure the two interface mappings as a part of a single interface determination so that they execute one after the other . Or is it two interface determinations - one for each interface mapping - how do I relate these two ?
Also, I assume that since the message mappings in the interface mappings are multimappings , I need to use enhanced interface determination .
Could you share one of the scenarios wherein you had two interface mappings execute in a series - ? Thanks for your time.
Hi,
yes you can use .
a. the "ns0:Messages" and "ns:Message[n]" tags are not being created automatically.
--In messages tab checkthe message occurrences .
b. In the interface determination we do not see the interface mapping when we select the 'enhanced' option
-- check the Interface mapping which was created for final one with two mappings , imean check the message type source and target msg in Interface mapping , in general , based these it will pouplate. if it is inbound the corresponding interfacs is selected in IM or not.
Regards
Chilla
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 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
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.