Skip to Content

Enhanced receiver determination, mapping failed

Hi experts,

I am facing this issue with the AEX system.

scenario 1:N mapping, the Sender file adapter is to poll from a NFS dir. and the ping is successful with binding existence as well, but thr is no msg formed and following error is thrown directly:

Error: com.sap.aii.adapter.xi.routing.RoutingException: Error while executing receiver determination mapping.

I've run this scenario as 1:1 and it works fine with the same source file etc.

I've gone thru: and few other posts but all are expecting the source message somehow, before this error.

Plz help.

--

rgds

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • avatar image
    Former Member
    Jan 31, 2014 at 04:19 PM

    Hi Subhnam

    If your input file splits into multiple files of same structure and you want to send them to multiple folders of same server based on some payload value, then you have to do it in the below way

    1. you need to create one receiver and one communication channel.

    2. you have to use ASMA to check the folder name dynamically.

    3. You have to write an adapter module for generating the folder name dynamically. You can use variable substitution if you want to send the xml file.

    But if you want to split the input file into different files with different format and wants to send them different server and different folder, then you have to do it in the below way

    1. create one receiver and multiple communication channel.

    2. in the operation mapping use 1:N mapping which will generate multiple inbound interface.

    3. Create receiver agreement for each of the inbound interface and use different channel for different interface.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 27, 2014 at 07:07 PM

    Hi Shubhnam - Have you done the configuration through eclipse if so can you validate the configuration (F7-check) using swing client.

    Also are you using enhanced receiver determination for your multi mapping?

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 27, 2014 at 08:26 PM

    Hi Shubhnam,

    It is very wierd error when scenario work for 1:1 and not for 1:n. Can you check the source payload in monitoring?

    if you are unable to view the source payload then apply the setting as per below link.

    http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/11/06/message-staging-and-logging-options-in-advanced-adapter-engine-of-pi-73x

    regards,

    Harish

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 28, 2014 at 07:23 AM

    Hi

    Can you please let us know why you are using extended receiver determination??

    What mapping are you using in extended receiver determination ??

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Indrajit,

      I am using 1:N split for a file to brk into multiple file based on the first field value. I needs to be sent to different folders accordingly.

      Mappings used are typical, 1 mapping for the msg n another for receivers (MT n SI frm basis/system).

      --

      rgds

  • Jan 31, 2014 at 01:00 PM

    Hi Hareesh, Harish and Indrajit,

    Thnx for ur replies.

    Sorry cudnt reply any earlier as i was away frm this project for a few days.

    Still stuck tho!!

    --

    rgds

    Add comment
    10|10000 characters needed characters exceeded

    • Hello,

      Which version of PI u are using?

      And could u explain ur scenario, i am not sure why RD is bothered abt the type of message 1.1 or 1..n? I mean multimapping concept will only be applicable at message mapping level, so at least RD step should be executed?

      BTW, just a thought, hope ur XML message is fully compliant as per the MT structure?

      Thanks

      Amit Srivastava

  • avatar image
    Former Member
    Apr 15, 2014 at 01:04 PM

    Hi Shubhnam.

     

    Not sure if the request is still actual, but anyway. Have you configured the staging part? I guess for the extended receiver determination it is essential that the staging is activate at a very early stage (something like BI). Because the operational mapping needs to a very early stage the message information to perform dynamically the receiver determination. If there is no proper message at this stage available the extended receiver determination can’t identify the right receiver and failed. We had a similar error after changing the global settings of the staging configuration.

    Cheers

    Add comment
    10|10000 characters needed characters exceeded