Skip to Content
avatar image
Former Member

Dynamic logon user RFC receiver SAP PI

Hi Experts,

I have a requirement where I need to use dynamic receiver RFC channel based on the plant id in the source message.

My current scenario is JMS to RFC scenario but the logon user in the RFC channel has one timezone only which is causing issue with people in different timezones. So we are looking for multiple approaches:

1) Break the interface into two :

JMS to SOAP and SOAP to RFC.In the second scenario I want to achieve Principal Propagation .So in order to do POC,i built second scenario and using SOAP client to push the messages.Now how to enable Principal propagation is the question.I got the steps to do at the receiver end but nothing on sender side which is SOAP UI.

2) Create multiple mappings/multiple channels and during runtime via condition we were able to achieve this but it's cumbersome to achieve for new plants everytime.

Problem is that there is no asma properties in receiver RFC adapter to dynamically send the logon user.

We are building it as ICO Java stack interface only and currently we are on SAP PI 7.31 SP10.

Thanks,

nazzyb

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 16, 2015 at 06:20 AM

    Hi Rohit,

    Referring your first point as far as i know the principal propagation is not supported by the JMS adapter (Configuration of Principal Propagation - Configuring Process Integration After Installation - SAP Library).

    For the second point, you can simplify the condition, you can use one of the alternatives of the value-mapping at mapping level to choose the receiver with the extended receiver determination:

    Defining Extended Receiver Determination (Advanced Adapter Engine) - SAP NetWeaver Process Integration - SAP Library

    Regards

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Rohit,

      The huge load is produced because you are using a RFC lookup, the best approach to use a Value-Mapping and to have the parameters in the Integration Directory directly. Another solution in order to have the parameters in the ID is to do a Value-Mapping replication scenario (Value Mapping Replication Scenario) but this approach is useful whether these parameters can change with certain frequency.

      Regards.