Whats wrong when the error message “lookup of alternativeServiceIdentifier via CPA-cache failed” shows up while sending a RFC call to the RfcAdapter?
A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose “Service” -> “Adapter-Specific Identifiers”. The values in the fields “R/3 System ID” and “Client” has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type “Business System”. If maintained in SLD, this fields will be filled automaticaly for services of type “Business System” and can be updated with the button “Compare with System Landscape Directory”.If a non-ABAP system is used to send RFC-calls to the RFC-Adapter sender channel it may is not possible to set the SYS-ID and CLIENT values in this external RFC client. The checking of these values can be disabled in the ‘RFC Server Parameter’ settings in the sender channel. Choose ‘Advanced Mode’ and deselect ‘Verify Sender System’.
Related Questions
- When I start Activity Keylogger, it shows message Connect failed, there has some crashed IExplorer threads. Please restart system and try again., How come?
- Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
- I get the error message displayed ‘Correlation sequence failed to synchronise?
