Skip to Content
avatar image
Former Member

PI 7.40 - ABAP Mapping failed: MappingException: Unsupported mapping type: R3_ABAP

Hello,

we have the need to use a ABAP mapping on our PI 7.40 (dual stack) that converts a flatfile to an xml idoc (I know that there is a module operation for the receiver channel that does the same, but it is not working for us because in the sended flatfile the header information are missing)

I have added the needed parameter in the echange profile:

After that I have implemented the mapping in the OM field:

But every message that we try to send get's stuck with the following error:

Any suggestions what causes this error?

regards

Christian

2.jpg (106.3 kB)
3.jpg (60.1 kB)
1.jpg (18.1 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jan 08, 2015 at 05:49 PM

    I'm just guessing, but maybe you are using an "Integrated Configuration" and no "Classic Configuration" (Sender Agreement, Receiver Agreement, Receiver Determination, ...), and ICOs don't support ABAP Mappings as they don't use the ABAP stack at all?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      You were right! I tried to implement the java mapping in the ICO. This can not work.

      But unfortunately now I'm getting another error when useing a normal configuration:

      SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIServer/INBOUND_BINDING_ERROR; Params:  urn:sap-com:document:sap:idoc:messages, SDPICK.SDPIID01.SDPIID01; AdditionalText: null; ApplicationFaultMessage: null; ErrorStack: Error in sender agreement for party  service , interface namespace urn:sap-com:document:sap:idoc:messages, interface SDPICK.SDPIID01.SDPIID01 No sender agreement found for , , , , ,