Skip to Content

While upgrading ERP 6.0 to EHP6, pre-processing phase, I encountered No suitable RFC destination could be found…

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR731XPRA90000126.SR1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2 EPU126XPost-import methods for change/transport request: “SAPK731XPRA90000126”
4 EPU111 on the application server: <hostname>
2 EPU122XPost-import method “FINB_TR_AFTER_IMP_METHOD” started for “FBLC” “L”, date and time: “20130319114545”
A2 EFINB_TR 096 Postprocessing of client cascade was skipped for client “000”
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client “001” started
A2EEFINB_TR 032 No suitable RFC destination could be found”001″
A2 EFINB_TR 098 Transport tool FINBASIS: Client cascade for client “001” finished
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client “166” started
A2EEFINB_TR 032 No suitable RFC destination could be found”166″
A2 EFINB_TR 098 Transport tool FINBASIS: Client cascade for client “166” finished
A2 EFINB_TR 097 Transport tool FINBASIS: Client cascade for client “400” started
A2EEFINB_TR 032 No suitable RFC destination could be found”400″

Solution:

Resolved using note 644610.

1. Stop the SUM, Update –> Stop Update.

2. Create an RFC (ABAP)  destination  to each of the clients like what you see above.

3. No need to specify language. You must explicitly indicate the client number, the COMMUNICATIONS (type) USER

plus the password.

4. Use transaction FINB_TR_DEST and fill up the entries and SAVE. No need to specify client 000.

5. Restart SUM. Continue with the upgrade using SUM.

Regards,

Joel

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply