cancel
Showing results for 
Search instead for 
Did you mean: 

Data flowing into incorrect CC when triggered from a SAP - RFC

former_member188885
Active Participant
0 Kudos

hi Experts,

I have a RFC to SOAP scenario. Data is triggered from SAP through RFC. Initially, this was done from client 200. Now for the same system there is one more client 210 from which data needs to be triggered.

I completed the configuration. But when data was triggered from client 210, the communication channel of the client 200 is showing the following error.

Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'ECQCLNT200'/'CC_SAP_RFCEproPOSender', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'ECQ#210' returned party/service of ''/'ECQCLNT210')

The client 210 communication channel is not showing any message. Also no messages are seen in moni.

Waiting for your replies.

Accepted Solutions (1)

Accepted Solutions (1)

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Check your RFC Communication channel ,Sender agreement and Receiver Determination There is a mismatch values in specifying system names and parameters. After checking, reactivate all the above three components and update cache.

Answers (4)

Answers (4)

stefan_grube
Active Contributor
0 Kudos

Did you use a different program id for both channels and did you assign the correct program id in SM59 connection in each client?

former_member188885
Active Participant
0 Kudos

The application server is the same and only the clients are different. so the same program id is maintaied for both.

deepak_shah
Contributor
0 Kudos

Hi,

Please verify the adapter specifc identifiers(R/3 System ID and Client) in your business system.

If it is blank then you can sync it with SLD.

Refer below thread :

Regards,

Deepak

Former Member
0 Kudos

Hi,

As mentioned earlier in the post check the Logical system name to the business system of your client 210..

whether it contains the logical system name or not..if not need to maintain the same for the Business system..

HTH

Rajesh

former_member188885
Active Participant
0 Kudos

Thank you for your reply everyone.

I cleared the cache and now am getting the following error in the communication channel of client 210.

Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'ECQCLNT200'/'CC_SAP_RFCEproPOSender', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'ECQ#210' returned party/service of ''/'ECQCLNT210')

I have created the communication channel under the bussiness system of client 210 and also have created the receiver agreements and sender agreement specific for the client 210. Still getting the error.

Need your help in solving this.

baskar_gopalakrishnan2
Active Contributor
0 Kudos

How about your Receiver determination and Interface determination objects. Are they using the right business system? Activate all your scenario ID objects....

See any default * appears in party or sender system field in Receiver determination or Interface determination .

Former Member
0 Kudos

Hi,

Check your business system for 210 client is having the correct logical system name in the adapter specific identifiers..

looks like you are using the same business system for two scenarios..if yes then create the separate business system for 210 client..

HTH

Rajesh

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi ,

When ever you want to use new client , i hope you have completed below steps

1)Creating business system in SLD for client 210 and assign the same in ID.

2)Create communication channel under 210,it should have details about 210 client.

3)Complete all ID steps for 210.

if you still have an error do cache refresh,it will work.

Regards,

Raj