cancel
Showing results for 
Search instead for 
Did you mean: 

Interface migrated from XI to PI 7.1 - NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION

Former Member
0 Kudos

Here are the things I did and followed

1. SRM Proxy to File interface is working great on XI3.0 box

2. Exported repository scenario from XI3.0 into TPZ file

3. Imported that file into PI7.1 ES Repository

4. Builder Config -

    1. Added Business systems for SRM and Business Service for File System
    2. Prepared a File/FTP communication channel for  "File System"
    3. Prepared receiver determination and added "Service Interface", sender and receiver
    4. Added Receiver agreement and Interface determinations
    5. As this is proxy to file scenario, I didn't have to create communication channel for SRM and aso Sender agreement

5. Tested scenario from Builder config simulator, worked great.

6. Error: When i tested from SRM, I am getting the following error messages

    1. SXMB_MONI - Gives <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>. No receiver could be determined</SAP:Stack>
    2. From RWB, Message Monitoring got same message
    3. From PI ABAP, went to SMQ2 and found failed message with error "XI Error NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION"

7. To diagnose, here are all the things i did

    1. All cache release (SXI_CACHE and also from exchange profile)
    2. Recreated builder config bunch of times
    3. Cleared and removed queue
    4. Restarted servers
    5. SRM has proper RFC destination connection. validated all

Either I am missing something small  or I shouldn't import from XI Repository.

Really appreciate your help.

Accepted Solutions (0)

Answers (4)

Answers (4)

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

I think the reason that you are encountering this issue is because your SRM is still pointed to the old XI system and that the config objects are no longer there. Can you check in your SRM system which integration server it is pointed to?

1. sxmb_adm -> Integration Engine Configuration

2. find the name of the rfc destination e.g dest://IS would mean that in Tcode SM59, a type H destination is existing with the name of IS

3. check the hostname/service in which the IS in step 2 is pointed to and verify if it is pointing to the PI system

Hope this helps,

Mark

former_member205101
Participant
0 Kudos

As other folks said: Suitable Receiver not found during Message Run.

1) Check Receiver Determination whether all the details are correct

2) If applicable Check condition used to identify the receivers in receiver determination and check the payload value for that field

3) Check all Cache

4) If nothing works Please recreate the receiver agreement and Receiver determination and try..May work (if it is in dev system)

5)I hope receiver file system is defined Business service for your scenario then no need to check SLD.

Thanks

Praba

baskar_gopalakrishnan2
Active Contributor
0 Kudos

There is some problem with your receiver determination object. Check thoroughly.

http://www.riyaz.net/sap/xipi-sap-xi-troubleshooting-guide/372/

smavachee
Active Contributor
0 Kudos

Cross check configuration once again with configuration test tool ?

Regards,

Sunil

Former Member
0 Kudos

Config test tool is all green. Still issue.