cancel
Showing results for 
Search instead for 
Did you mean: 

map outbound IDOC in 2 different mappings

Former Member
0 Kudos

map outbound IDOC in 2 different mappings

Dear all, this is our case .

We have two sap transactions on our R3 system, each of which produces an IDOC of the same type .

When those two idocs are produced, the resulting output is of different structure though.

One of them has a segment called eg A1 while the other one has a segment B1, which is under segment A1.

What we need, is to have a different mapping depending on which actual structure we have .

The receiving RFC is the same for both cases, yet we could use two distinct RFC's if this could help solve the problem .

Every help would be appreciated .

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

thank you both, problem solved .

Former Member
0 Kudos

Hi Markos

Good to hear Would you like to share the solution.

You can close the thread if its resolved.

Thanks

Gaurav

Former Member
0 Kudos

Yes it was actually the solution both of you gave, using two MM etc .

Former Member
0 Kudos

Hi Markos

You can implement this with two MM and IM and make a decision in ID

Another way can be one mapping and enhanced Receiver / Interface determination

http://help.sap.com/saphelp_nw70/helpdata/EN/43/a5f2066340332de10000000a11466f/content.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/42/ed364cf8593eebe10000000a1553f7/content.htm

Thanks

Gaurav

Former Member
0 Kudos

One option is :

  • You create two different MM and IM.

  • In the Interface Determination, add two inbound ( receiver ) message interfaces along with the two interface mapping recpectively.

THe moment you will save your Interface Determination, you will see a "Condition" colume will be added between "Message interface" and "Interface mapping" columns in the Interface Determination.

Under the Condition, you can provide the rule which determines at runtime time , which mapping to execute.

Thanks,

Pooja

Edited by: Pooja Pandey on Dec 18, 2008 2:49 PM