Skip to Content

I know we are not new to error “Lookup of alternativeServiceIdentifier via CPA-cache failed for channel” issue in SCN .Many blogs and references are there I am sharing my experience with this error as encountered for first  time.This is my first blog in SCN too.

 

In my project we have  a standard Function function Module in SAP ECC system which communicates using RFC in SAP PI(7.1).

The  error I received in outbound queue of ECC system “Lookup of alternativeServiceIdentifier via CPA-cache failed for channel”

 

As per Error I followed the steps.

  • I monitored the sender RFC channel in SAP PI RWB.

Channel was green.Hence no error with channel.

  • I checked corresponding RFC destination in SAP ECC system with same Program ID as mentioned in channel.

RFC connection test was also fine.

Then I thought might be cache issue

  • I performed full cache refresh.

http://host:50000/CPACache/refresh?mode=full

Still the the same error while executing program in sap ECC.

 

Now I referred SCN threads.

e.g. https://scn.sap.com/thread/175402

  • As per SCN I got an Idea that there can be Issue with the Business system so as per Instructions I deleted and recreated new business system with same name and appropriate details of Technical system pointing to correct ECC system.

I Imported business system in Integration Directory.

Activated the business system and performed the cache refresh.

This time I assumed error should not be there,but found that same error was  there.

In the meanwhile I created new channel and sender agreement but it also did not work

🙁 🙁 🙁 🙁

Now nothing was working my way.

 

Then I again opened RFC destinations(SM59) in ECC system  and checked the RFC destination with same Program ID as  in Sender channel of SAP PI.

In my current project landscape we have Development, Quality,Training , Pre-Production, and Production  environments.This error was in Training environment

While checking the host configuration of RFC destination I came to know that this particular RFC destination was pointing to Pre-Production environment.

 

I have shared this blog in future if any body comes across such issue while dealing with with multiple environments we could miss out such silly things to check out initial stage.

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply