PI 7.1 : 1:2 Multi-Mapping IDoc to IDoc scenario error

[arkesh_sharma]

Hi Experts,

I am trying out a scenario in PI 7.1. The scenario is from IDoc to IDoc. I am trying to create a 1:2 scenario with this. On the source side I have IDoc as INVOIC and on the target I have kept two IDocs - INVOIC and ACC_DOCUMENT.

Each time the IDoc INVOIC comes from the source, it should generate two IDocs in the target (i.e. INVOIC and ACC_DOCUMENT). The receiver of the two IDocs are the same.

I have configured one business component for sender(BS_A) and one for receiver(BS_B). I have configured one interface determination, one receiver determination and two receiver agreements (for two different IDocs).

When I try to run the scenario from "Test Configuration" option in ID, I get an error for receiver agreement.

Problem occurred in receiver agreement for sender -BS_A to receiver -BS_B,http://tsdmp.mm/mpc/xi/Invoice.MI_Invoice_Out: No standard agreement found for , BS_A, , BS_B, http://tsdmp.mm/mpc/xi/Invoice, MI_Invoice_Out

When I run the scenario from RWB, it gives a mapping error but when I test the Operation Mapping, it is working fine and also my Message Mapping works fine with the sample payload from the Production System.

I am unable to understand what is the possible cause of problem in this simple 1:2 IDoc to IDoc scenario. I request you to please help me and guide me in this regard.

Thanks,

Arkesh

[Former Member · Accepted solution]

Hi,

Since it is IDoc-To-IDoc and multi-mapping scenario, you will have to use BPM in this.

Without BPM, for two different IDOcs, this scenario will not work.

-Supriya

[arkesh_sharma · Accepted solution]

Hi Supriya,

I agree with you but as Raja mentioned in his message above that you can do it using external definition at the target which can be employed.

Please have a look at the Raja's blog.

Thanks,

Arkesh

[Shabarish_Nair]

avoid a BPM.

Use the logic of having two mappings and two interface determinations to help you out here.

Note: Multimapping without BPM doesnt work for IDoc scenarios

[arkesh_sharma]

Hi Shabarish,

I have a new scenario where I have to filter the source data into two records i.e. "Success Data" and "Error Data". This is a file to file scenario and I need to send the two target data in two separate directories.

I tried the similar steps as above but my interface is failing with the below error.

Also, I have mentioned two target interfaces in Interface Determination and two target service interfaces in Operation Mapping.

Error:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

 Request Message Mapping 

-->

- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">MISSING_INTERFACE</SAP:Code>

<SAP:P1>2</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>No interface specified for parameter 2</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

[rajasekhar_reddy14]

Hi Sharma,

We can develop this requirement using 2 approches

1)Developing two ddifferent message mappings and operaion mappings.

2)using multi mapping concept'

refer below my blog

Regards,

Raj

[arkesh_sharma]

Hi Raja,

I have employed the same logic as you had mentioned in the blog. I have 1 occurence of the IDoc in the source and I have used XSDs in the target with "unbounded" occurence. My scenario is that I have to use 1 source and map it to 2 targets (so that two IDocs are generated) and I do not wish to use BPM so I thought "0..unbounded" would work but it is not working.

Please let me know how can I fix this?

Thanks,

Arkesh

[rajasekhar_reddy14]

in my case i have not used sender side IDoc message.

What is the error message are you getting?

[arkesh_sharma]

Hi Raja,

Sorry for the delay in response. I am getting the below error while running the "Test Configuration" option in ID.

Problem occurred in receiver agreement for sender -BS_A to receiver -BS_B,http://tsdmp.mm/mpc/xi/Invoice.MI_Invoice_Out: No standard agreement found for , BS_A, , BS_B, http://tsdmp.mm/mpc/xi/Invoice, MI_Invoice_Out

Thanks,

Arkesh

[rajasekhar_reddy14]

Your ID configuration not correct.

why are you using MI_Invoice_Out for IDoc scenarios? you suppose to use IDoc message only abstract interfaces only we creare message interface for IDoc.

[arkesh_sharma]

Thank You Raja for pointing that out !!!!

Do I need to do the same for both the source and the target interface (i.e. remove the interface name from the IDoc and keep only the IDoc in the interface) ?

thanks,

Arkesh

[rajasekhar_reddy14]

yes true.. dont create any message interfaces, in operation mapping add IDoc message. IDoc it self act as a message interface

search in sdn for IDoc scenario and follow those steps.