RFC to SOAP - Not working

Hi
I am working on RFC to SOAP scenorio and the same is working fine, when i execute from XXX client, when the same is executed from YYY client it is giving dump, even i tried changing the communication channel to client YYY
I am getting the following error "lookup of alternativeServiceIdentifier via CPA-cache failed for channel"
Can you pls help
Regards
Madhan D

hi refre this thread too
lookup of alternativeServiceIdentifier via CPA-cache failed for channel
SAP Note - 730870
This alternativeServiceIdentifier error mostly appeared while changing the information of Business Systems ie.e Client information in communication channel.
As the Business system information from SLD will not be matched for the communication details. You are trying to override the metadata information of Business System maintained in SLD. This creates conflicts while connecting with the sender/receiver system
Refer
/people/danny.deroovere/blog/2008/02/26/change-client-in-scenarios-with-sap-business-system
lookup of alternativeServiceIdentifier via CPA-cache failed for channel
alternativeServiceIdentifier: party/service from channel configuration are.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0a8949b-098d-2910-2b8e-b5e9b7daeb26 Page No
Regards
Abhishek

Similar Messages

RFC SAPXPG_DBDEST_ DBHOST not working

Dear Experts,
RFC SAPXPG_DBDEST_<DBHOST> not working in our Production system (cluster), due to this I am not able to take backup from DB13.
I have updated latest "sapxpg" in /usr/sap/<SID>/exe/run still it is not working.
Any idea????????
Regards,

Po ssible points of this error:
1) After downloaded this file you have to RUN ./root.sh in kernel.
2) check the environment variable for given path of backup.
3) Also check the RFC connection before schedule the job.

RFC connections do not work after system restart

Hi PI experts!
We're facing a problem with our PI 7.0 system. After each restart of the system, all RFC sender communication channels do not work. When testing the connection in the sending SAP system, the connection test fails. Currently we workaround the issue by manually restarting the RFC adapter after system restart.
Does anybody has any idea how th fix that problem? <<text removed>>
Cheers,
Matthias
Edited by: Matt on Apr 29, 2009 3:26 PM - don't offer points

Mathias,
Your problem is due to the fact that SAP is not up and running when XI restarts.
there is a parameter in RFC adapter that you can modify in order to fix that
Please, see the following link and let me know: /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
best regards,
David

File Attributes from App Server by RFC (GET_FILE_ATTRIBUTES does not work )

Hello,
We have an Objects application that is started through an RFC BAPI call from a Java app. The Java app. passes a file to the BAPI. We want to test, as efficiently as possible, if the file is 0 bytes long. We have tried /epsf/get_file_attributes but there is a problem with it being called remotely. We have Remote Enabled the function module. Local tests work fine (GUI User), but when it is called by the Bapi(Technical User) we receive sy-subrc = 2. I think it is referring to a 'Communication Error'.
I found a nice class, CL_GUI_FRONTEND_SERVICES for the workstation server, but nothing comparable for the application server.
Help is greatly appreciated as I am pulling my hair out.
Best Regards,
Mark Lengel

Hello Andreas,
The GET_FILE_ATTRIBUTES fm is also from the EPS Function Group and provides the file size, it just does not work when called from Rfc/Bapi. Won't the GET_DIRECTORY_LISTING fm just return directory info ?
I am afraid I will have to resort to the OPEN, READ, CLOSE DATASET steps in order to check for a zero length file.
Regards,
Mark

RFC to SOAP ( not gettign the responce from the receiver)

Hi All,
I am implementing a new interface RFC to SOAP for send the data from SAP to SHARE POINT. We are able to post the data to the share point. But we are not getting the response from the share point to PI. But i have tested with SOAP UI with the same payload there i am able to see the response. Can you please help me where is the problem for XI not getting the response. I have configured everything correct.
Regards,
Rama

Hi Rama,
try to ping the webserver from PI (Transaction OS01).
Regards,
Udo

PI 7.11 - Alert creation for RFC Exceptions does not work

Hi folks!
In our PI 7.11 SP04 system we have created an Alert Category as well as an Alert Rule to be informed about errorneous messages in the Integration Engine (ABAP).
The scenario is synchronous SOAP Axis to sRFC, where the RFC answers with an exception that is transferred to a SOAP Fault response message.
Now we see messages with Application Errors in the Integration Engine, but no alert is created. Having a look at the alert creation log using report SXMSALERT_LOGREADER shows us that the system even does not try to create an alert for these messages. Alerts are only created for errors in the Adapter Engine.
Question:
Why does the system not create alerts in this case and how can we achieve this?
Thanx for any hint!
Kind Regards,
Volker

Hi!
Additional information for all:
When forcing an error like "receiver not found" both kinds of alerts are created: AE Alert and IE Alert. Thus in general the alert configuration and the alert rule for IE errors are correct and working - only not for RFC exceptions ....
Regards,
Volker

RFC & proxy adapters not working

Hi Gurus,
We have PI 7.31 single stack installed on our company.
Since the last 2 days, we are not able to have a successful communication between PI and ECC on RFC and proxy adapters.
On the previous days, weeks and months there were no issues like this one.
The error that we are getting on the message monitor is next one for our incoming proxy interfaces:
From the Message Details tab:
Status
systemError
Status Details
Receiver delivery: Cannot determine receiver channel (Cannot find the receiver channel)
Error Category
XI_J2EE_ADAPTER_ENGINE
Error Code
CHANNEL_DETERMINATION_FAILED
From the Message Log tab:
29/04/2015 14:56:42.673
Information
Trying to put the message into the send queue
29/04/2015 14:56:44.448
Information
Message successfully put into the queue
29/04/2015 14:56:44.452
Information
The message was successfully retrieved from the send queue
29/04/2015 14:56:44.456
Information
Message status set to DLNG
29/04/2015 14:56:44.496
Information
Message selected to be processed again when the receiver channel is started
29/04/2015 14:56:44.501
Error
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Channel stopped by administrative task.
For OB proxy calls, this is the error that we get in the sxi_monitor on the ERP:
Status Details column: Error Parsing PI Message
Error while calling Integration Server:
com.sap.aii.af.service.administration.api.cpa.CPAChannelStoppedException: Channel stopped by administrative task. at com.sap.aii.af.service.administration.impl.cpa.CommonCPA.checkChannelState(CommonCPA.java:57) at com.sap.aii.af.service.administration.impl.cpa.LookupManagerDelegate.getCPAObject(LookupManagerDelegate.java:86) at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:487) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
Regarding the RFC adapter, this is the error we can see in the CCM:
Error in processing caused by: RfcException: [qlaspi00.xxx|eq610q0]
    message: CPIC-CALL: SAP_CMACCPTP on convId: 00000000
LOCATION    SAP-Gateway on host qlaerp01.xxx / sapgw01
ERROR       registration of tp eq610q0 from host
            qlaspi00.xxx not allowed
TIME        Wed Apr 29 16:20:22 2015
RELEASE     721
COMPONENT   SAP-Gateway
VERSION     2
RC          720
MODULE      gwxxrd.c
LINE        3644
COUNTER     5492
    Return code: RFC_SYS_EXCEPTION(3)
    error group: 102
    key: RFC_ERROR_COMMUNICATION
Exception raised by qlaspi00.xxx|eq610q0
On the SM59 tx in the ERP the test connections are failing for the RFC destinations that we are using on this environment, and these were working in the past.
Also, BASIS team notify us that the programs are registered so they don't know that else to do on their side.
The actions I took were:
CPA full refresh cache
Restart all PI components (done by BASIS team)
Stop and start channels
Inactivate and Activate channels
Please notice that all these processes were working in the past and there were NO modifications on the same.
Where can I continue looking on these errors to find the issue?
Any help will be very appreciated!
Thanks in advanced!
Regards.

Claudio
The error indicates that the channel has been stopped. Did you check the administrative logs in the comm channel monitor to see if someone or an ATP schedule has stopped the channel?
Rgds
Eng Swee

RFC to XI not working

Hello,
I have created a program that calls a RFC function and sends de result to XI server. I've done that exactly how that blog tells:
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
I've configured and tested SM59 RFC destination and the conection is succeful.
Then I've designed my RFC2File mapping and configured the integration directory, and in that step I've done something wrong but because XI is not receiving RFC result.
How can I know what I'm doing wrong? The RFC communication channel must be well configured because the conection test works in SM59 but if I go to SXMB_MONI after executing my report I don't see any message there and I don't know how to discover what's happening with my data when I execute this on R3:
CALL FUNCTION 'ZSCM_GET_MATERIALES'
    EXPORTING
      TIPO_EXTRACCION       = TEXTR
      CENTRO                      = CENTRO
    TABLES
      IT_MATERIALES         = IT_MATS.
Dummy RFC to send the result async
CALL FUNCTION 'ZZSCM_GET_MATERIALES'
    IN BACKGROUND TASK DESTINATION 'SAPXIGATEWAY'
    TABLES
      IT_MATERIALES         = IT_MATS.

Hi Marshal
Check out this link.This could be helpful to you.
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
Please make sure that the program id is same in R/3 as well in Sender channel.
Thanks
-Mitesh

RFC Destination does not work for /sap/xi/adapter_plain service

Hi
We are facing a strange issue. Our business partner is trying to connect to our XI box, RFC Detination type 3 through a reverse proxy at our end. If he used /sap/xi/engine service, he gets a 500 response " empty request received". Howerevr if he connects using /sap/xi/adapter_plain, he is not getting any response, just a green tick at the bottom with no message. SMICM shows " wrong content in header response"
Regards
Monika

Hi
We are able to send data to our business partner. When he is trying to send data to us, he is not able to do so.
He needs to do so via a reverse proxy. We have replicated the scenario on our side to cross check.
We are able to connect to our XI with http/https without reverse proxy. However with reverse proxy we are not able to do so.
Also in case of http without reverse proxy, the message processing does not happen even thought RFC Connection test is successful/
Regards
Monika

RFC adapter does not work

I create a RFC Receiver CC, I got the following trace error in XSMB_MONI in receiver call adapter phase：
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">old values in cache (no lock found) - start reading from SLD</Trace>
<Trace level="1" type="T">error reading SAP_XIAdapterFramework from SLD</Trace>
<Trace level="1" type="T">error reading details from SLD for Adapter Engineaf.di1.usmdlsdowa122</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
</Trace>

You have to create a business system of type WEB AS ABAP. In the corresponding Technical System specify all the details of SAPR3 server on which this RFC exists.
Then import the RFC in IR and this Business system in ID.
And create your Receiver CC under this business system.
-Gouri
Award points if helpful

Parameter Mapping with RFC Callable Object not working

Hi Folks
Scenario
I have a process scenario like this
Interactive Form Callable Object A -triggers> Process [Interactive Form Callble Object B -> Interactive Form Callble Object C -> RFC Callable Object ]
All the forms A, B, C use same form template, different sections of it lets say i, j and k are filled by different guys.
Now my parameter mappings are as follows -
a) Page level meeting between B & C called P Map.
b) Process parameter mapping with Form A and appropriate section of P Map lets say section i
c) fields of Form C are mapped to RFC callable object fields
Problem
The data filled in Form A [section i] disappears when I open and see the Form B.
If I remove the mappings of fields of Form C with RFC callable objec fields, I am able to see it.
Has anyone faced it before!

Hi,
This is a known issue on SP10 and it will be fixed in the next patch for SP10.
Hope this helps!
Best regards,
David

RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'Hulst

Hi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha

IGS rfc not working BI 7.0

Hi All,
We have upgraded our BWD system from 3.5 to 7.0, in smicm restart j2ee server option is disabled only Icm restart option is enabled. I have checked the services both the SMTP and HTTP are active and HTTP is activated as External also.
I have checked the Http server ->display data: it's showing that ABAP and J2EE configured true but J2ee server operational = false.
If j2ee server is not working plz suggest me how to start the j2ee server.
If j2ee server is not working does IGS RFC work ? presently we are facing the problem with IGS rfc we have given the paramters according to note 844669 in instance profile still no luck .... please suggest..
Thanks,
Subhash.G
Message was edited by:
subhash gadde

Hi Markus,
We have fixed the IGS problem the RFC IGS pointing is wrong destination.
We have given the program IGS.Pjazzsap6 in the RFC destination.
I do not have any information about Pjazzsap6 exactly what does it mean?
our EP dev server which is connecting to BWD is pointing to Pjazzsap6 in IGS destination . Is Pjazzsap6 is kind of program file ? please suggest...
Thanks,
Subhash.G

Sender Soap Channel is not working - Service Temporarily Unavailable [503]

dEAR FRIENDS,
We are facing one critical issue in sender soap adapter. After upgrading our system to PI 7.1 The sender soap channle is not working. From source system it is not reaching PI : the log from source system as follows:
org.springframework.ws.client.WebServiceTransportException: Service Temporarily Unavailable [503]
      at org.springframework.ws.client.core.WebServiceTemplate.handleError(WebServiceTemplate.java:627)
      at org.springframework.ws.client.core.WebServiceTemplate.doSendAndReceive(WebServiceTemplate.java:551)
      at org.springframework.ws.client.core.WebServiceTemplate.sendAndReceive(WebServiceTemplate.java:502)
      at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:351)
      at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:345)
      at org.springframework.ws.client.core.WebServiceTemplate.marshalSendAndReceive(WebServiceTemplate.java:337)
      at com.palm.txnengine.wsclient.DailyRevenuePostingWSGateWaySupport.postToSap(DailyRevenuePostingWSGateWaySupport.java:23)
      at com.palm.txnengine.wsclient.DailyRevenuePostingImpl.execute(DailyRevenuePostingImpl.java:93)
      at org.springframework.batch.core.step.tasklet.TaskletStep$2.doInChunkContext(TaskletStep.java:264)
      at org.springframework.batch.core.scope.context.StepContextRepeatCallback.doInIteration(StepContextRepeatCallback.java:67)
      at org.springframework.batch.repeat.support.RepeatTemplate.getNextResult(RepeatTemplate.java:352)
      at org.springframework.batch.repeat.support.RepeatTemplate.executeInternal(RepeatTemplate.java:212)
      at org.springframework.batch.repeat.support.RepeatTemplate.iterate(RepeatTemplate.java:143)
      at org.springframework.batch.core.step.tasklet.TaskletStep.doExecute(TaskletStep.java:239)
      at org.springframework.batch.core.step.AbstractStep.execute(AbstractStep.java:198)
      at org.springframework.batch.core.job.AbstractJob.handleStep(AbstractJob.java:348)
      at org.springframework.batch.core.job.flow.FlowJob.access$0(FlowJob.java:1)
      at org.springframework.batch.core.job.flow.FlowJob$JobFlowExecutor.executeStep(FlowJob.java:137)
      at org.springframework.batch.core.job.flow.support.state.StepState.handle(StepState.java:60)
      at org.springframework.batch.core.job.flow.support.SimpleFlow.resume(SimpleFlow.java:144)
      at org.springframework.batch.core.job.flow.support.SimpleFlow.start(SimpleFlow.java:124)
      at org.springframework.batch.core.job.flow.FlowJob.doExecute(FlowJob.java:105)
      at org.springframework.batch.core.job.AbstractJob.execute(AbstractJob.java:250)
      at org.springframework.batch.core.launch.support.SimpleJobLauncher$1.run(SimpleJobLauncher.java:110)
      at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
      at org.springframework.batch.core.launch.support.SimpleJobLauncher.run(SimpleJobLauncher.java:105)
      at org.springframework.batch.core.launch.support.CommandLineJobRunner.start(CommandLineJobRunner.java:207)
      at org.springframework.batch.core.launch.support.CommandLineJobRunner.main(CommandLineJobRunner.java:254)

Hi,
Please check this generic description:
The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
u2022 Refer SAP Note 803145,807000,791655
May it helps.
Regards,
Caio Cagnani

Sender RFC is not working

Hi
I am working on RFC to SOAP Scenorio
I configured Sender RFC Communication Channel.
Using the same program id, i created RFC destination.
The RFC Destination is working fine.
When i test it using program, i am getting the
error alternativeServiceIdentifier via CPA-cache
Can you pls help
Regards
Madhan D

hi,
did you configure as per my blog:
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards,
Michal Krawczyk

RFC to SOAP - Not working

Similar Messages

Maybe you are looking for