JCo Error in EP6.0

Hi All,
I have developed a custom iview in EP6.0 which retireves data from R/3 using Jco and display the data in various controls like dropdown.
When I try to run the application I am getting a runtime error (while accessing the model).
I am using a JSPDynPage with a java bean for pulling the data thru JCo.
When run as a standalone the the java class for JCo is working fine, and the bean is also working fine with static data.
Is there is anything that needs to be added in portalapp.xml file?.
Any help is greatly appericiated.
Thanks,
Vasu.

Vasu,
This is what I picked up in the EP6->Java Development->Documentation area.
"JCo in the Portal Platform
JCo is included in the portal platform. However SAP JCO/ JCOClientService should not be used anymore in Enterprise Portal 6.0 and above.
Webservices or the "Java Connectivity Architecture" implementation "SAP Connectorframework" is recommended instead. This Framework provides additional functionality, especially the connection management, which allow tp programm scalable connections "
You should probably follow the example code to connect to SAP using Java Connector functionality as suggested by SAP.
Hope this helps.
Thanks
GO.

Similar Messages

  • Error while deploying the aplication-jco error

    Hello Experts,
    i know   thousends of questions in jco error. I have followed that threads , still i am getting an error.
    Plz help me out from that error.
    My EP server is running on was 6.20,
    and xi server is running on was 6.40.
    what i have done:
    I have downloaded fightslist  application from sdn.
    i have deployed that application to was 6.40.
    i created one technical system for abap.
    i configured sld.
    i entered service name(sapms147 3600/tcp(this is ides(4.7) serversid and port)) in servicefile in was 6.40 machine.
    when maintaing jco connections the following error has come:
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=mlbpsap06 GROUP=PUBLIC R3NAME=I47 MSSERV=sapmsI47 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapmsI47' unknown TIME        Fri Dec 01 15:27:10 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 MODULE      ninti.c LINE        494 DETAIL      NiPGetServByName2: service 'sapmsI47' not found SYSTEM CALL getservbyname_r COUNTER     7 
    My doubts are:
    1.where i have to enter service i.e which machine (6.40  or 4.7 machine).
    2.while creating technicalsystem which product i have to choose).
    3while creating jco connection
        whichone i have to choose either dictinory mata data or applicationdata.
        in message server connection which user id & password i have to give means 4.7 userid or xiserver userid & password.
    Plz helpme out from this.
    Thanks in advance.

    Hello Sai,
    NWDS is local means which machine i am using.
    My EP 6.0 SP2 in 172....202 but it is reunning on was 6.20.(mlbpsap02)
    and here was 6.40 ip is 172.....203 IP ,but XI is installed on this server)(mlbpsap03)
    and R/3 ECC ip is 172......201.(mlbpsap01)
    no sneak preview edition and all.
    I have downloaded application(sample flight) in webdynpro.
    and i configured sld in 203(cim test connection is successfull) ip.and also entered the service name(sapmsecc 3600/tcp).After entering the service name i restarted the server
    and created technical system for abap (and here selectiong products ecc components are not there.)
    in webdynpro content admin while maintaing jco , the above error is coming.
    i am unable to find where the problem is
    the main thing is ep is not in was 6.40
    further what i do
    and where i enter the host ip and aliases.

  • Org.apache.jasper.JasperException; JCO error when Importing SAP Roles in C

    Hello experts,
    I have installed BOXI 3.1 SP3, Integration kit SP2, BW/BI 7.0 and ECC 6.0 on Windows 2008/64bit.
    My goal is to import the roles into CMS from SAP BW/BI but getting the follwoing errors:
    JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
    JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc
    C:\Windows\SysWOW64\sapjcorfc.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform.
    java.library.path [C:\Windows\SysWOW64\;D:\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\]
    org.apache.jasper.JasperException
    I followed the note 1292144 - JCO error when Importing SAP Roles in CMC,but unfortunately without success.
    I installed SAP JCo Release 2.1.9 (64bit)
    Best regards
    Lutz
    Edited by: Lutz Heinrich on Aug 12, 2010 4:17 PM

    Install the 32bit version of the Java connector. BOBJ is 32bit so even on 64bit Windows you need the 32bit version of the Java Connector.
    Regards,
    Stratos

  • JCo error when calling from webmethods sap adapter to SAP BAPI

    Hi,
          I am getting an error "[SAP.102.9000] JCo error: (104) RFC_ERROR_SYSTEM_FAILURE - connection closed without message (CM_NO_DATA_RECEIVED)"  when webmethods sap adapter is calling BAPI in SAP. The BAPI is working fine in SAP.
         Can anyone suggest me a possible solution.
      Thanks,
      Sarath.

    BAPI-step by step procedure
    http://www.sapgenie.com/abap/bapi/example.htm
    list of all BAPI's
    http://www.planetsap.com/LIST_ALL_BAPIs.htm

  • JCO Error in Quality Portal

    Hi ,
    When i am running WDJ apps in dev portal , it's working fine . But when i am running through QA , it's showing the following JCO error .
    Could not create JCO connection .Please ensure that you have nesured RFC destinations and/or logical system name properly for this model .
    I tested the JCO in QA and it's working fine . Can anybody help me out regarding this .
    And one more question , how to check JCO connections for WDJ apps inside NWDS  ?
    Thanks a lot .

    Hi Jain,
    While using RFC Models in the WD application, we maintain JCo dstinations.
    These are specifically used to create a JCo Connection between 1 Web Application Server and 1 R/3 System. If any one of them changes, you need to update the same in the JCo destinations created.
    The point here is, as you have changed the Dev System to QA System, i.e. your Web Application Server, you will need to create / maintain the JCo Destination with the same name on the Quality System for use of the application.
    The JCo connection that you have been testing, is, may be on your developemnt system.
    Hope it helps.
    Regards,
    Alka.

  • Java portal to bw hana sp08 JCO error

    Dear Team
    I am facing an issue after BW Hana migration.
    Senario:1(BEFORE MIGRATION)
    ORACLE DB/ BW NW 7.3+ JAVA PORTAL  7.01, EACH ON SINGLE STACK
    HOSTNAME: xxxxx
    DOMAIN: xxx.LOCAL
    DATABASE: ORACLE11G
    SYSTEM : ABAP + JAVA SEPARATE STACKS
    PLATFORM: NW 7.3
    JAVA 7.01
    Senario 2
    ( MIGRATION ENTIRE ABAP STACK)
    HDB/ BW NW 7.3
    HOSTNAME: YYYYY
    DOMAIN: xxxx.LOCAL
    DATABASE: HDB SP08
    SYSTEM : ABAP
    PLATFORM: NW 7.3
    Migrated only Abap stack and Java portal still runs with older database(oracle)in Older system(Xxxxx). I did the re-deployment on java portal with new HANA db configuration and it was success but.
    When connecting Jco it is throwing error
    Test Connection with Connector
    Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
    Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    only the issue with Jco  rest of all connectivity working fine, anybody face the same issue   ?

    Hi,
    Issue got resolved .
    OOPS N BUGS !!!: Java portal to bw hana JCO error / Connection failed. Make sure that Single Sign-On is configured corre…
    Thanks
    Yoonus

  • Using JCO error Wrong repository version = 0 encountered.

    Hi Guru,
    We convert our existing Java Jco program to call RFC Sender adapter and XI should forward the request to RFC receiver adapter to our ECC.
    We found that when we create client connection using gwhost, gwserv and tpname which is config in RFC sender adapter.
    In our Java program throw error in the step of mRepository.getFunctionTemplate.
    The error is "Wrong repository version = 0 encountered.".
    It seems the program can not access function template from repository.
    Anyone have this experience before, please advise
    Thanks you.

    It's working now.
    For your knowledge, it seems it was something wrong inside the jrfc.jar.
    The problem is not exactly the same but the solution is to apply OSS note 816491.

  • Jco: Error Connecting using sapgw04

    Hi,
    I have a problem using Jco to connect to a SAP-System.
    I'm trying to connect to SAP using the following configuartions:
         sysnr:           04
         GWServ:      sapgw00
         GWHost:      XXX.YYY.com
         ASHost:      XXX.YYY.com
    The code to create a repository for this configuration is:
         JCO.addClientPool(poolname, maxpoolsize, "538", "username", "password", "DE",
                   "XXX.YYY.com", "04", "XXX.YYY.com", "sapgw00");
    When I use this pool to get a function I get an Exception:
    com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template '[FUNCTIONNAME]'
    caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect from SAP gateway to RFC server failed
    Connect_PM 
         GWHOST=XXX.YYY.com , GWSERV=sapgw00, ASHOST=XXX.YYY.com , SYSNR=04
    LOCATION   
         SAP-Gateway on host h33e / sapgw00
    ERROR       partner not reached
         (host XXX.YYY.com , service <b>sapgw04</b>)
    The strange thing is the sapgw04 in the error-message.
    Somehow JCO wants to use sapgw04 to connect to the RFC-Server. Is this an error in the SAP-Configuration or do I have to change the configuration of Jco?
    How can I tell Jco not to use sapgw04 but sapgw00?
    Any help would be appreciated!
    Thanks
    Torsten

    Hi Torsten,
    please check how you log on to your system.  You are giving a system number 04, which corresponds to sapgw04.  I'm not sure why the method needs all the information, seems to be duplicate to me (please comment if I'm wrong); it should be sufficient to use:
    addClientPool(String key,
       int max_connections,
       String client,
       String user,
       String passwd,
       String lang,
       String ashost,
       String sysnr)
    If you don't want to use sapgw04, just specify "00" for the sysnr.
    Hope this helps, harald

  • JCO Error - SAP ER

    Dear all,
    I'm facing this issue during the SAP reconciliation.
    Could you please help me?
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= Start Stack Trace =======================
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] oracle.iam.connectors.sap.common.parser.SAPIDOCListener$ThrowableListener : serverExceptionOccurred
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] Description : (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    [2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable. (raised by system hgrs-hbk-s0340|a_rfc)[[
         at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:664)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2443)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
         at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
         at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
         at java.lang.Thread.run(Thread.java:736)
    Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
    message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by hgrs-hbk-s0340|a_rfc
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2832)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2646)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2537)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2358)
         ... 4 more
    Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
    message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by hgrs-hbk-s0340|a_rfc
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3378)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2827)
         ... 7 more
    Caused by: com.sap.conn.idoc.IDocRuntimeException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:240)
         at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
         at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3349)
         ... 8 more
    Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
         at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)
         at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
         at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
         at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:143)
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.createIDocDocumentList(DefaultJCoIDocServerWorker.java:301)
         at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:199)
         ... 10 more
    [2012-09-18T13:54:32.482+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= End Stack Trace =======================

    Hi Arun,
    I did that step as well,
    4.copy the Sapjco3.jar into the "CIA" directory of mercury folder and copy the sapjco.dll into the c:\windows\system32 file.
    Any clues?
    why this error?

  • Jco error

    Hi Friends,
    Itu2019s a support issue. Messages have failed in integration engine and inbound queues
    I am getting different errors in different areas of xiu2014
    In Integration engine Problem while determining receivers using interface mapping u201CCommunication failureu201D during JCO CALL
    Similarly another error in other message in Integration engine unable to find URL for adapter engine.
    In SMQ2 error is XI Error JCO_SYSTEM_FAILURE.MAPPING: Queue stopped.
    Pls help !!

    As suggested by Prateek, please check whether the SM59 destination AI_RUNTIME_JCOSERVER is working or not.  If this is not working, search for AI_RUNTIME_ZX2 in smgw=>Goto=>Logged on Clients. 
    If you find the program ID AI_RUNTIME_ZX2 in TP name column and still have issue, please ensure that the user-id id PI_JCO_USER is not locked or the password has not been changed.
    If you can not find the  AI_RUNTIME_ZX2 in TP Name column, that means there is an issue with JCo RFC provider. In Visual Admin(PI 7.0) / NWA (PI 7.1),  do the necessary stuff which makes the program ids to appear in smgw logged on clients. Basis should know about this.
    Hope this helps.

  • JCO error when calling BAPI

    Hello guys,
    I have an scenario R3 -> XI -> R3.
    From the first R/3 we call a function in a program to execute a BAPI in the second R/3, so the BAPI doesn't exist in the R/3 that starts the interface.
    We have configured the TCP/IP connection and with the same program ID in the Sender RFC adapter. All the connectios are running successfully but when we execute the program we have the error:
    JCO.Server could not find server function 'Z_TEST'
    Do you know if the BAPI has to be created in both systems, or it's only necessary in the R/3 destination to run.
    All connections are running so the question is what we remarked before, the BAPI must be created in both R/3 systems?
    Regards,
    Xavier.

    Hi Xavier,
    strange, i answered to a very similar question a hour before, there was no reaction by Gerardo Mondragon .
    How can the sender adapter get the metadata? If the FM is just in the receiver system? Maintain the meta data connection at Communication Channel to the receiver system...
    Regards,
    Udo

  • UWL: Time Out Error in EP6

    Hello,
    We are on EP 6.0.
    We have configured UWL for R3 and CRM systems. Recently user started getting below error message
    "Time out occured. Time taken is more than 30 seconds"
    I know In EP7 we have this parameter in Optional Configuration under UWL admin. But this is not present in EP6.
    Can you please tell me the place where I can configure this parameter ?
    Regards,
    Vinod

    Hi Vinod,
    I believe that this parameter is not available on the UI for your version.  Can you please check the following:
    On the portal go to System Admin, System Configuration, System Landscape.
    Scroll down in the system landscape and try to find your CRM system that you are connecting to.
    Once you have found this right click and select open.  Next select, connection tests.  Click on the boxes, and select test.
    This provides useful information as to why the connection isn't working or is timing out.  Another thing that you can do is to check the UWL log files.
    Could you please post the outcome of the connection tests?  The tests need to be successful for the UWL to work properly.
    Will you be upgrading soon?  The reason why I am asking is because there are many excellent features in the newer versions of the Universal Worklist, like the real-time refresh feature.
    Beth Maben
    EP - Senior Support Consultant
    AGS Primary Support, Business Suite & Technology
    Please see the UWL Wiki @
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/bpx/uwl+faq  ***

  • JCo error while viewing MSS iviews

    Dear SDN Community,
       When I am trying to view any of the MSS iViews like photo, orgchart, personal data, I get the following error message.
      com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=sapdev GROUP=ED0LG R3NAME=ED0 MSSERV=sapmsED0 PCS=1 ERROR service 'sapmsED0' unknown TIME Fri Aug 03 11:59:07 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 4
    The JCo connections SAP_R3_HumanResources and SAP_R3_HumanResources_Metadata are tested successfully and I see the gree light for these 2 in the WebDynpro console.
    Can you please advice me here.
    Thanks,
    Vivek.

    Vivek,
    open the services file of your portal server box. This file will be in the location C:\WINDOWS or WINNT\system32\drivers\etc folder. In that enter an entry as below:
    sapmsED0   36XX/tcp
    where XX is the system no of your R/3 system. So if R/3 system number is 30 the line would be sapmsED0  3630/tcp.
    Save the file and then try accessing iView again. This error message would be going off.
    Regards,
    Shubhadip

  • Meta Data JCo Error

    Hi All,
    I am Created Application JCo's it is successfully tested then i created Metadata JCo then i tested and i got the following Error. 
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=ptgsap10 GROUP=PUBLIC R3NAME=EC6 MSSERV=sapmsEC6 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner 'ptgsap10:sapmsEC6' not reached TIME        Thu Jul 19 19:20:00 2007 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -10 MODULE      nixxi.cpp LINE        2764 DETAIL      NiPConnect2 SYSTEM CALL connect ERRNO       10061 ERRNO TEXT  WSAECONNREFUSED: Connection refused COUNTER     3
    How to Rectify this Error?
    Thaks and Regards,
    Phanikumar.

    Hi Phani,
    Check the followin
    1. in your Back end system, go to SMLG -> check logon grp PUBLIC is there or not.. if nt create one
    2.  Check out that, from EP server you can ping ECC system and its gateway services, message server services.
    3. In your case, u shud be able to ping ptgsap10 from EP server and shud be able to access sapmsEC6 service.
    4. If u cant ping host, maintain host file entry with IP address and host name
    If u can cant access sapmsEC6 , then maintain services file
    sapmsEC6  <message server port>/tcp
    Cheers!!
    Ashutosh

  • Jco error RFC adapter field PT F not defined

    Hi Experts,
    I am in a strange situation as I have become clue less on this issue
    It is a file to XI to RFC scenario.. runs fine in dev environment
    When I change the parameters in teh rfc communication channel  to point to QAS it throws
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_TRAX_PO_CHG_IV in remote system (RfcClient[CC_QAS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Field selection PT F not defined:
    There is no such field as PT F and besides the version of the bapi in QAS is in sync with the dev..
    pls help me ou ton this
    Edited by: Ravindra Teja on Feb 27, 2011 8:45 AM

    Hi,
    First of all, can you please elaborate what you want?
    secondly, why don't you transport your developments to QAS?
    Third, what is the reason behind changing the receiver RFC adapter parameter to QAS?
    4th, do you want to post data to QAS, if yes, did you transported the RFC to QAS ? Please re import the rfc to your swcv from QAS system.
    Please check communication channel if you getting any error?
    Regards
    Aashish Sinha

Maybe you are looking for