Error in RFC Destination when CAF Application call RFC

I developed a CAF application, where I imported a RFC in "External
Services", like BAPI_FLIGHT_GETLIST, and I mapped it as "Application
Service".
Then for execute this CAF application, I created a RFC Destination in
CE 7.11 SP4 ("http://server:port/nwa/destinations") to configure my ECC
6.0 EHP4 backend.
When I execute the CAF application, in CAF project in NWDS, right click
in Application Service, "Test Service", occurs the follow erros:
com.sap.conn.jco.JCoException: (103) RFC_ERROR_LOGON_FAILURE: This
system rejects all logons using SSO tickets on tecs071 sysnr 00
at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException
(MiddlewareJavaRfc.java:612)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect
(MiddlewareJavaRfc.java:1279)
at com.sap.conn.jco.rt.ClientConnection.connect
(ClientConnection.java:661)
at com.sap.mw.jco.jra.JRA$ManagedConnectionImpl.<init>(JRA.java:3332)
at
com.sap.mw.jco.jra.JRA$ManagedConnectionFactoryImpl.createManagedConnection(JRA.java:2623)
at com.sap.engine.services.connector.jca.ConnectionHashSet.match
(ConnectionHashSet.java:371)
at
com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:330)
at
com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)
at com.sap.mw.jco.jra.JRA$ConnectionFactoryImpl.getConnection
(JRA.java:4637)
at com.sap.mw.jco.jra.JRA$ConnectionFactoryImpl.getConnection
(JRA.java:4654)
at
com.sap.caf.demo_sap_com.teste_caf_rfc.external.tecs071.bapi_flight_getlist.BAPI_FLIGHT_GETLISTBean.bapiFLIGHTGETLIST
(BAPI_FLIGHT_GETLISTBean.java:54)
Regards,
Fabiano Rosa
Edited by: Fabiano Rosa on Apr 5, 2010 7:21 PM

Before checking the jco/sso ensure to maintain same destination name in both 'nwa/destinations' and in ide nwds while importing rfc.This also causes error while testing the service.
Thanks,
Murthy.

Similar Messages

RFC destination with CIF application case !

Hi,
Can someone explain the difference between
Assigning a logical system to a RFC destination and
u201CAssigning a logical system to a RFC destination with CIF Application case" (there are 4 of them in all as i see - AC, RL, RQ, DG, AC- refers to availability check)
e.g I have 2 entries in the system landscape settings.
1) Logical system u2013 RFC destination
2) Logical system- application case AC u2013 RFC destination.
Even if I remove the 2nd entry, the relevant APO ATP FMu2019s are called (just a negative testing to see what goes wrong without application case) but am clueless about this concept of CIF application case. Why such a provision to begin with. The context help says. some transaction need to have synchrious RFC and hence the need but i see the same even without his entry.
Regards,
Loknath

Hello Loknath,
If I understand your query correctly,
1.Assign logical system to RFC destination is OK for you.
2.Assigning the RFC destination to a specific CIF application is used in the following case,
You have a system/service user set up for communicating with the R/3 system thru CIF & this is assigned to the RFC destination assigned to the point no:1
& for debugging purposed you need a dialogue user, so you may assign this dialogue user to a different RFC destination & assign it here in the customizing (Assign RFC to application cases) to the application Debugging..so that while the particulat application is called (Debugging...CIF cockpit...etc)the corresponding settings from the different RFC destinations will be used.
I could not understand your query, where u relate some ATP stuffs with this CIF topic...
Thanks,
Mahesh

Which sy variable is initiated when web dynpro application call rfc of r/3

Hi,
My question is that when i pressed my web dynpro application button which called rfc at r/3 at that time which system variable will initiated.
Regards,
Gurprit

Hi Gurprit,
All variables of sys structure will be intiated.
regards,
Ganga.

Error in Java Program when passing table to RFC function . JCO is used

Hai All,
I developed a JAVA application to update data into SAP using JCO via RFC. When i pass table to the function module i am getting the below error
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Conversion from type T to D not supported.
Please let me know how to solve this.
Below is my code
IRepository m_Repository;
IFunctionTemplate ftemplate;
JCO.Table PwdReq;
JCO.Function function;
m_Repository = JCO.createRepository("MYRepository", client);
            ftemplate = m_Repository.getFunctionTemplate("Z_GESEFM_UPD_PWD_RESET_REQUEST");
// Create a function from the template
function = new JCO.Function(ftemplate);
// Feeding in input parameters
PwdReq = function.getTableParameterList().getTable("RESULT2");
String userid = "PATCHTEST14 ", reqDate = "",reqNo = "01",reqStatus = "03", boxID = "09",ind2 = "X",
                    lcode = "abcd",rem = "One record testing";
PwdReq.appendRow();
                PwdReq.setValue(userid, "USERID");
                PwdReq.setValue(reqNo,"REQ_NO");
                PwdReq.setValue(reqStatus,"REQ_STATUS");
                PwdReq.setValue(boxID,"BOX_ID");
                PwdReq.setValue(ind2,"IND2");
                PwdReq.setValue(lcode,"LCODE");
                PwdReq.setValue(rem,"OTHER_REMARKS");
            // execute the function with the input parameters
            client.execute(function);
Thanks & Regards,
H.K.Hayath Basha.

hi,
I am not very good in Java.
but try this code to giving input parameter.
function.getImportParameterList().setValue(userid, "USERID");
if you are not using Try and Catch blok then use Try and Catch blok,
Regards
Manoj

BCP to pass an Error Message to SSIS when the BCP call fails?

Hi,
Within SSIS I have an Execute SQL Task which calls BCP via a source variable given the dynamic nature of the BCP call.
When the BCP call fails it returns a number of records which give instructions on how to use BCP. SSIS then thinks that BCP has executed successfully, the component shows green and then the package continues to run.
But of course what I want the BCP call to do is return an error message which would then trigger the standard on error event handler within SSIS. How do I do this please?
It maybe the “Execute Process Task” could be a better SSIS component to use for this call
Using BCP Utility in SSIS. Does anyone have experience of doing this type of thing?
Thanks in advance,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Why don't you use the "Fast Load" option = BULK LOAD? Or the BULK LOAD stored proc?
The only other way I can think of this can be done is by directing errors to an error file which can be interrogated from the package and then a precedence constraint used to trigger an error if there was one.
Arthur My Blog

Decreasing amount of RFC-Destinations when using UD-Connect?

Hello,
I created an RFC-Destination in sm59 as well as JCO RFC Provider and used the SAP manual for UD-Connect/JDBC to a "foreign" Sybase-DB. The Connection is working properly and all DB-data is accessible, but our cutomer claims that there are more than 25 parallel rfc-connections from our Web AS to his Sybase-DB. My question is: How can I decrease the amount of parallel connections, because I don't think 25 connections to Sybase-DB are necessary. I know there is the maxConnection-Property in JCO RFC Provider but this parameter is globally affecting all RFC-connections and not only those that are associated with the Sybase-DB.
Is there actually a way to customize the amount of parallel connection via JDBC?
Best regards
Danny

Hi,
use transaction "smqs", select destination and click on registration change max number of connections.
Try to define rfc server group to control connections ...
Regards
Ben

RFC(?) on first Application call low performance

Hello All,
I've got a problem with a JCO connection. I have a WD application, that connects via aRFC to an R/3 system. When I open this application, it takes about 20 seconds, until I get the first screen. When pressing reload, it takes just about 1 or 2 seconds. Well, I thought, this could be the initialisation of the connections to the R/3 system. So I closed all the connection from the application server via SM04 on the R/3 system. But again, it takes just 1 or 2 seconds until the connections are established and the application is shown, when reloading the application. So I assume, the connections aren't the reason for the long waiting time at initial application start.
I don't think, it's J2EE compilation time, because the server isn't restartet over night, but the first time I open the application on the next day, it takes again 20 seconds.
The application runs on the same WAS as the enterprise portal. Even if I first log in to the Portal and after this open the appliation (in the same browser window without logging off), the first time it takes 20 seconds. So it shouldn't hava to do anything with the login.
I'm using 5 Models in this applications with TASK_Scope connections. Defined is a poolsize of 50 and 100 max connections, so this should be enough for me and shouldn't be the problem either. Metadata connections are configured to 1 pool and 5 max.
I've already read different threads, blogs and PDFs like "How to Configure the JCO Destination Settings". But nowhere I got an idea, why the initial start of this application should take so long and how I could find out, what the problem is.
It's NW04 SPS19, R/3: 6.40, SPS19
I hope, anybody here has a clue about this.
Best regards,
Christian Schebesta

Hi,
have you done a log entry to check how long the RFC call took and cheked it
in the default trace of the visual admin?
The Fast way for testing is to pass the URL Parameter: sap-wd-showInfo
like: http://..../Application?sap-wd-showInfo
this will show you the time the J2EE engine needed on javaside and also on the ABAP side in the Statusbar
You alse can use the codinglike:
long time = System.currentTimeMillis();
wdContext.currentBAPIElement().modelObject().execute();
wdContext.nodeOutput().invalidate();
System.out.println("Milliseconds used: " + (System.currentTimeMillis() - time);
Because I don't think it will have something to do with your RFC. I think it will more have something to do with the caching of your server.
Each time you deploy your application the Server has to restart and delete the old cache files of the application. So the First user taht will access your application has a longer responsetime because all the pages have to be generated and put into the work folder of the J2EE engine. And also it could be that the J2EE engine will release this cache also after some time to save memory.
Regards,
Dennis

Error code 0x645(1605) when using application supersedence

I've created a new version of an application that supersedes the previous version. I'd like the new version to uninstall the previous version, as otherwise it will install alongside it. Each version has a different MSI product code.
I created the application for the new version along with the supersedence rule, setting it to uninstall the previous version. I then set up a test VM with the old application and tried to install the new one via the Application Catalog. However, when the
Software Center begins the installation and tries to remove the old version, it fails with: "The software change returned error code 0x645(1605)"
I verified that the uninstall string for the old version is correct: I can even manually run it on the VM and it begins to uninstall the old version. I thought that 1605 indicated that the product that's trying to be removed is not present, but since the
uninstall string works I'm not certain what exactly is going on.
Any help that can be offered would be most appreciated. Thank you!

Thanks for responding so quickly! I ran it manually and the new version of the program installs ok. I used the same command line that I specified in the MSI deployment type (and there's only the one deployment type). So it seems that the error occurs when
SCCM implements the supersedence rule and tries to uninstall the old version.
I checked Event Viewer and I see two entries for when the program is attempting to uninstall, but they are simply the entries that say "beginning a windows installer transaction" and "ending a windows installer transaction." There's no error in Event Viewer.
The entries feature the MSI product code of the product; if I copy that product code and run msiexec /x with it, it uninstalls.

RFC destination exception

I am working in CE 7.2.
I am not able run my application importing RFCs in CAF Core proj, if I import webservices, it is working fine.
I have created provided systems in nwa -> soa ->technical confi -> system connections
I also created a Destination Template for the RFC. please advice if anything I need to add in SOA Manager in NWA.
But still I am getting the following error
nested exception is: com.sap.caf.rt.exception.CAFServiceException: Couldn't create ManagedConnection with . (jco.client.lang=EN, destination.name=, jco.client.jra_conn=true sap

I found the solution from forum link :
Error in RFC Destination when CAF Application call RFC
I have maintained the destination for my RFC and given the authentication details. in http://host:port/nwa/destinations
thanks a lot.

** End-to-End Monitoring - RFC destination error while save config in RWB

Hi Friends,
We have 2 RFC destinations in our XI server. 1) PMI<client>001 2) PMI<client><client>800. First one is for XI server. Next one is for Sender/Receiver System.
We want to activate End-to-End Monitoring in RWB. For this, when I save configuration, it throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
I have checked the user in the above destinations. For the first destination, we have assigned PIRWBUSER of XI system. Test Connection is OK, but unable to login remote. At the same time, PIRWBUSER is not locked.
For the second destination, I have assigned some login user of sender/receiver system. Test connection is OK. Able to login remotely.
There is no RFC user in our XI system. (I tried using RFCUSER* thru SU01 tcode).
There is no PIRWBUSER in the Sender/Receiver System.
In RWB, Configuration, 3 components are there. 1) XIIntegrationServer 2) Business System (for Sender/Receiver System) 3) XI Adapter Framework. I selected last two. (First one is already selected). Monitoring Level : Medium (for all 3). Send and Receive Check box is selcted for the last two.
So, what could be the problem for the above error?
Could you kindly clarifiy friends.
Thanking you
Kind Regards,
Jeg P.

Hi friends,
I have one RFC Destination PMI<sysid>001. (Abap Connction) in my XI system. This destination is for XI server. Connection Test is OK. Remote Logon by using the PIRWBUSER is also ok.
In the 'Configuration' tab of the Runtime Workbench, when we select 'Save Configuration', (Business System and Adapter Framework is not activated) with the default activation for XI Integration Server, the system throws the following error.
Incorrect RFC Destinations: When the configuration is saved, an RFC destination is created on the monitoring server for each XI component to enable end-to-end monitoring of the respective XI component. However, the test call failed for the destinations listed. Therefore, you must check the call and the authorization on the monitoring server for the destinations concerned, by using transaction SM59. Also check whether RFC user used for the destination is maintained in the relevant XI component. Note that a component can only be monitored when its RFC destination is maintained correctly.
When we save configuration, an one more destination is automatically created in the name as below.
PMI<sysid>001<yyyymmdd>. For Example, PMIPID00120080207.
When we test newly created RFC destination, connection is OK, but not able to remot login using the same user PIRWBUSER.
The difference between old and new RFC destination, in old, we have selected Load Balancing is 'Yes', but in the new it is 'No'. The system also tells the error below.
Name or Password is incorrect (repeat logon) - PMIPID00120080207
But, still remote login is possible in the old RFC destination using the PIRWBUSER.
So, What could be the problem ...?
Kindly reply, friends.

Transaction IDX1: Port SAPCP0 client , RFC destination contain errors

Hi Experts,
I am getting following error in SXMB_MONI in IDOC to JDBC scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>Transaction IDX1: Port SAPCP0, client , RFC destination contain errors</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: Transaction IDX1: Port SAPCP0, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i have created port in idx1 and i imported the idoc in idx2 and i have created rfc destination to R3 in XI, RFC destination is working fine.
Can anyone help me out of this.
Kind Regards,
Praveen.

hi,
>>><SAP:Stack>Error: Transaction IDX1: Port SAPCP0, client , RFC destination contain errors</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
>>>i have created port in idx1 and i imported the idoc in idx2 and i have created rfc destination to R3 in XI, RFC destination is working fine.
this means that you're checking an incorrect RFC dest
- open IDX1
- click on port SAPCP0
- double click on RFC dest which is over there to open it
- ctrl+F4
does it work?
Regards,
Michal Krawczyk

Calling RFC

Hi Team,
I am calling RFC fron ECC 6.0 to SAP 4.6c.
Destination is maitained in SM59.
Problem:
When i am calling RFC through my report program.
Sy-subrc is 1.
When running FM at orginal destination it is working fine.
Any helpful pointers...

Sy-subrc represents the value of the exception.
For example
CALL ZFUNC DESTINATION ZZ.
EXPORTING
IMPORTNG
EXCEPTIONS
data not found = 1. "Check this description for your case, This is your error
communication error = 2.
Whatever is defined for one is your problem

RFC destination definition with non-unicode external program

Hello All,
we have one issue with our RFID system connecting to WM system (SWD).
For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.
But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.
We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.
To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
Anyone know how to help ?

Hi Jeongbae,
as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
In earlier releases, this is not possible.
In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.
Please check SAP note 788239.
Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
In addition I would recommend to have a look at SAP note 1021459.
However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
Best regards,
Nils Buerckel
SAP AG

Setting a different rfc destination if code is run on a particular server ?

Hi,
I need to fetch blocked data from GTS server....
I am doing the same using the function module '/SAPSLL/BLCK_DOCS_SD_R3' present in the transaction '/SAPSLL/BL_DOC_SD_R3' ...
Now as per my requirement, i need to fetch data from a different rfc destination if the code is run on a particular server.... ie I need to set the RFC destination in that particular case....
I do not want to copy the whole function group and make changes in the place where the RFC destination is determined.
Is there any other way to get through this.   ....
Thanks....

Hello
The RFC destination to the GTS server is determined within fm /SAPSLL/BLCK_DOCS_LS_FETCH_R3:
*------- RFC-Destination Legal Services ermitteln
CALL FUNCTION '/SAPSLL/CD_ALE_RECEIVER_GET_R3'
       IMPORTING
            EV_RFC_DEST                   = LV_RFC_DEST
       EXCEPTIONS
            NO_RFC_DESTINATION_MAINTAINED = 2
            CUSTOMS_SERVER_NOT_UNIQUE     = 4
            OTHERS                        = 8.
IF NOT ( SY-SUBRC IS INITIAL ) .
    MESSAGE ID     SY-MSGID TYPE SY-MSGTY
            NUMBER SY-MSGNO
            WITH   SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
            RAISING ERROR_ALE_SETUP.
    EXIT.
ENDIF.
*------- Daten fuer RFC-Aufruf vorbereiten
PERFORM BLOCKED_DOCS_REF_PREPARE USING    IV_APP_LEV
                                   CHANGING CT_DOCUMENT_NUMBER
                                            LT_OBJECT_DOCUMENT .
*------- Prozessindikator
IF NOT ( IS_OUTPUT-SHWMSG IS INITIAL ) .
    CASE IV_APP_LEV.
      WHEN GC_APPLICATION_LEVEL-SALES_ORDER.
        PERFORM PROGRESS_INDICATOR USING IS_OUTPUT-SHWMSG
                                         TEXT-M05.
      WHEN GC_APPLICATION_LEVEL-OUTBOUND_DELIVERY.
        PERFORM PROGRESS_INDICATOR USING IS_OUTPUT-SHWMSG
                                         TEXT-M06.
      WHEN GC_APPLICATION_LEVEL-INVOICE.
        PERFORM PROGRESS_INDICATOR USING IS_OUTPUT-SHWMSG
                                         TEXT-M07.
      WHEN OTHERS.
*------- Nada
    ENDCASE.
ENDIF.
*------- FB: RFC-Aufruf in Legal Services
CALL FUNCTION '/SAPSLL/LC_BLCK_DOC_SELECT_RFC'
    DESTINATION LV_RFC_DEST
    EXPORTING
Calling fm /SAPSLL/CD_ALE_RECEIVER_GET_R3 the system tries to find the RFC destination from a distribution model (transaction BD64) for
- OBJECT = 'BUS6801'
- METHOD = 'SYNCHRONIZEIFR3'
If we are already on the GTS server I assume that the fetched RFC destination should be 'NONE'.
If you are on another system (<> GTS server) then you should create the appropriate distribution model which allows the system to determine the RFC destination to the GTS server.
Regards
Uwe

Rfc Destination problem in RFC Sender Adapter

Hi experts
I created a Rfc destination type TCP/IP for Rfc Sender adapter.
while creating i passed following parameter:
1) I selected Activation Type option-> Registered Server
2)Given a Program id , same as i given in Rfc sender Adapter config.
3)Gateway option:
   i) Gateway Host:Server IP address where i created Rfc.
ii) Gateway Service:sapgw00
After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

Hi
please check for the following things.
1. check the RFC destination using the connection test tab in the R/3 system.
2. check whether the program id that u have given is registered or not.
to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
check for ur program id name in the table.
3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
if u still face the problem please reply me back.
Thanks
Rinku

Error in RFC Destination when CAF Application call RFC

Similar Messages

Maybe you are looking for