Skip to Content
avatar image
Former Member

SAP PI SOAP Loop Back Scenario

Hi Experts,


I need your help on this one.


I read this blog about SOAP Loop Back Scenario in SAP PI. This scenario is similar to my concern.
This scenario is already running for 3 years and there's a new development for another Partner.

Current Set-up:

1st Stage (1st ICO)

IDOC --> PI (Soap Receiver under the same business component)

Routing condition is based on Receiver Partner Number maintained in WE20 for vendor


The request message is sent to the messaging System by Java Proxy runtime


2nd Stage (2nd ICO)

PI (Soap Sender under the same business component) --> Partner

Routing condition is based on output xml value from IDOC/VENDOR/DUNS (output from 1st ICO)


Triggered IDOC from SAP failed in PI on 2nd ICO due to "Receiver Determination did not find any receivers at all".

Simply because it didn't met the requirement of 2nd ICO routing condition which is based on IDOC/VENDOR/DUNS. DUNS value for this new Vendor was not produced.


Question is how do these segments got generated or filled in with details after 1st ICO or when picked up by Soap Sender? These segments are not mapped in 1st mapping (1st ICO)


Your help will be very much appreciated.

Thank you in advance!

j7g7i.png (14.8 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Mar 19 at 06:56 AM

    Hi Jeffrey!

    When using SOAP Loopback, result message from the first ICo is sent as source message in the second ICo without any changes. So if you can't find the elements you need in second ICo's source message - this means that first ICo's interface mapping produced none of it.

    Regards, Evgeniy.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jeffrey!

      You also should check other possibilities like ASMA attributes of sender adapter, UDFs in mapping, Value Mapping Groups, any kind of custom adapter modules and so on.

      Regards, Evgeniy.

  • avatar image
    Former Member
    Mar 20 at 02:44 PM

    Hi Evginey,

    As per checking, ASMA Attributes are disabled on SOAP Sender Adapter 2nd ICO, NO UDFs and NO Value Mappings; and NO customer adapter modules in all Channels for both ICOs.

    Soap Receiver Channel (1st ICO):

    Soap Sender Channel (2nd ICO) – with the same BC

    NO UDF – 1st ICO Mapping

    Target Structure:

    VENDOR and COMPANY Elements are grayed out as these are not used.

    Regards,

    Jeffrey

    Add comment
    10|10000 characters needed characters exceeded