JCO /RFC prog and SNC : snc params ignored

Hi all ,
I've written a simple JCO prog to connect to a SNC enabled R/3 system. It does this but skips the SNC parameters ..I know this as I can put in some false data
and it still works (R/3 system excepts insecure RFC) :
client = JCO.createClient("xxx", //Client
                           "YYY", //User
                           "EN", //Language
                          "zzzz", //password
                           "host1", //hostname
                           "nn" ) ; //sysnr
client.setProperty("jco.client.snc_mode", "1");
etc...
Why is it ignoring the snc_mode ?
Regards
Daniel

Hello Daniel,
perhaps you try to connect via a properties file as described in the TutorialConnect2.java coming with JCo in the demo directory. Then you can use this Parameters:
jco.client.snc_mode=1
jco.client.snc_partnername=
jco.client.snc_lib=
Or have you found another solution to make your RFC connection encrypted by SNC?
Regards
Gregor

Similar Messages

JCO RFC provider and JCO connection

Hi all:
Please share your thoughts on the following doubts I have. Thanks.
1. To my understanding, we use JCO RFC provider(define in Java side) and RFC destination(in SM59) when we have request from ABAP to Java side. Then we use JCO destinations(define in Web Dynpro Content Admin) if we have request from Java to ABAP. Is this correct?
2. When creating the JCO RFC provider service, why we need to create those entries for repository for example, the server name, the user used to log into repository? What is the repository used for?
Thanks!

Hai,
your understanding of JCO RFC and RFC Destination is right.But JCO Destination gets the metadata and model data from ABAP,thats what we mention the Dictionany meta data and Application data while creating them.
Yes, we need to mention the application host,sys no,client and userdetails while creating the JCO RFC provider,then only it will fetch the data from that host and that particular client.
Thanks and Regards,

Purpose of RFC and JCO-RFC destinations

Hi,
Can you please tell me what is the purpose of RFC and JCO-RFC destinations and where do we create them.
Regards
Rahul

Hi,
RFCs are SAP interfaces for communicating between SAP systems. They accept inputs, do the processing and return the output values. You can call rfcs through different applications like web dynpro.
http://help.sap.com/SAPhelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
JCO helps Java applications to connect and communicate with SAP backend systems. Using JCO we can make rfc calls. JCO will help in getting the rfcs in a java compatible format.
http://help.sap.com/saphelp_nw04/Helpdata/EN/6f/1bd5c6a85b11d6b28500508b5d5211/content.htm
Example for setting up jco destinations:
http://help.sap.com/saphelp_erp60/helpdata/EN/ca/115e4088dc0272e10000000a155106/content.htm
Regards,
Shyam.

SSO between EP and ECC-- JCo RFC Provider- Error-- JCO_ERROR_SERVER_STARTUP

Hello Everyone
I am setting Up SSO between my EP 7.0 and my ECC 6.0 system. During the phase JCO RFC PRovider i am giving the following values:
The following was done;
1. start Visual Administrator -> Service : Choose JCo RFC Provider
2. Created JCo RFC provider:
Program ID: SAPJ2EE_Port
Gateway host: EPDEV ( host of my EP System)
Gateway service: sapgw00
Server Count 5
Application Server Host: ERP6 ( Host of my ECC System)
System Number: 00
Client: 000
Language: EN
User: SAPJSF
Password: ..
When i click on SET i am getting the error " ERROR When ADDING TO BUNDLE" Check LOG FOR DETAILS".
I checked the DEFAULTTRACE.TRC and get the following MEssage :
Date , Time , Message , Severity , Category , Location , Application , User
03/01/2011 , 3:33:30:101 , Error changing bundle SAPJ2EE_PORT , Error , /System/Server , com.sap.engine.services.rfcengine.RFCRuntimeInterfaceImpl.addBundle(BundleConfiguration conf) , , Administrator
03/01/2011 , 3:33:30:085 , com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Tue Mar 01 03:33:30 PST 2011.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1 seconds.
Could not start server: Connect to SAP gateway failed
Connect parameters: TPNAME=SAPJ2EE_PORT GWHOST=EPDEV GWSERV=sapgw00
ERROR       partner 'EPDEV:sapgw00' not reached
TIME        Tue Mar 01 03:33:30 2011
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     1
I have configured my SLD as well. Any suggestions. Please Advise.

Hi Ahmed,
Please do check the validity of the certificate.
Please do cross check these steps again.
1.     Transaction u2013 STRUSTSSO2 (Trust Manager for Logon Ticket)
2.     Double Click Owner certificate. It gets reflected under the certificate tab.
3.                  Choose Format Binary
4.                  Choose File Path.
5.                  Enter the File Name
6.                 saved in local drive.
You can import into portal as x.509 certificate.
check this thread -
Certificate no longer has signature (use restriction)
Renew certificate via SAP MarketPlace, and install from tcode slicense. If you are working on a trial version, there is a SAP license request application form. Fill the form with the hardware key. you will get the new license via email. Install using slicense. Then try exporting the certificate.
Thanks,
Divya
Edited by: Divya V on Mar 10, 2011 11:25 AM

Notes on JCO,RFC and ARFC?

Hi,
I need information regarding JCO,RFC,ARFC.
wht the main use of this?
Reply ASAP.
Regards
kiran

hi,
JCO
SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java. SAP JCo supports communication with the SAP Server in both directions: inbound calls (Java calls ABAP) and outbound calls (ABAP calls Java).
SAP JCo can be implemented with Desktop applications and with Web server applications.
SAP JCo is used as an integrated component in the following applications:
● SAP Business Connector, for communication with external Java applications
● in the Application Server, for connecting the integrated J2EE server with the ABAP environment.
SAP JCo can also be implemented as a standalone component, for example to establish communication with the SAP system for individual online (web) applications.
RFC
Communication between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
ARFC
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
The calling program can receive results from the asynchronous RFC.
regards,
Kris

Use PI between J2EE and CRM for JCO/RFC?

Hello,
I have a question concerning the use of PI RFC-Adapter:
is it possible to use PI as an intermediator between a Netweaver J2EE System which connects to another system (eg. ABAP) using JCO/RFC (giving the following setting:
[NW Java -> JCO] -> [PI] -> [RFC-Receiver-System]
To be more specific, we plan using CRM eCommerce Shop. This Java based shop connects to CRM backend using JCO/RFC. The Java based shop needs to be placed in a different network zone than CRM system and the only (allowed) way to have a connection from the zone with the shop is through PI.
Best regards,
Manuel

Hello Rajeev,
yes, this would be the best way - but unfortunately the policy does not let us connect directly using jco/rfc. Only ways using PI (decentral advanced adapter engine) are allowed.
Is this possible to use PI to transfer the jco/rfc requests between the two network zones or does PI not support this scenario?
Regards,
Manuel

JCo RFC Provider Service

Hello
This topic may be not relevant to this forum but has anyone used JCo RFC Provider service for maintaining RFC Destinations?
What I am trying to do is to store the RFC Destinations over here and have a lookup on JCo RFC Provider service (or on its program id) from mapping tool.My code looks like
javax.naming.Context ctx = new InitialContext();
ctx.lookup("JCo RFC Service"); or
ctx.loopup("Program id name");
But while testing it gives Object Not Found exception.
I am expecting it to return JCO object which I can use to connect to SAP for executing RFCs.
Thanks in advance.
Regards
Rajeev

Hi rajeev,
Did u check if the Prog Id mentioned in JCo RFC provider is running (started in visual admin).
Did u perform ur lookup properly
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
p.put(Context.PROVIDER_URL, "server:50004");
p.put(Context.SECURITY_PRINCIPAL, "Administrator");
p.put(Context.SECURITY_CREDENTIALS, "password");
javax.naming.Context ctx = new InitialContext();
ctx.lookup("JCo RFC Service");
Hope this helps you.
Cheers,
Siva Maranani.

JCO RFC provider: Server function not found, short dump

Hi all,
I'm trying to use the JCO RFC provider service of NW04s (SP15) together with an ABAP 4.6C system. I've followed all the documentation that I could find, but couldn't get it to work yet. This is what I've done so far:
Using SM59 I've had a destination APP_JK1 created for me on the R/3 system. AFAIK it's set up correctly and marked as a "registered server", connection tests were successful.
On the portal, I've created a RFC portal destination using my R/3 credentials and successfully tested it. Then I created an entry in the RFC provider service, using the correct values for system, id & gateway, and let it point to my RFC destination for the repository connection. The program ID is also APP_JK1.
Next, I created a stateless session bean which is part of an EAR, gave it a JNDI name of "RFCTEST" and added a method like this:
    * @ejb.interface-method view-type="both"
    * @param function called function
   public void processFunction(com.sap.mw.jco.JCO.Function function) {
      JCO.ParameterList input = function.getImportParameterList();
      String query = input.getString("I_STRING_SEARCH");
      JCO.ParameterList output = function.getExportParameterList();
      output.setValue(query, "ECHOTEXT");
(The project uses xdoclet for the creation of J2EE stuff)
In application-j2ee-engine.xml located in the META-INF directory of my EAR, I've added:
<reference reference-type="hard">
     <reference-target provider-name="sap.com" target-type="library">com.sap.mw.jco</reference-target>
</reference>
The application deploys without errors, and besides from my RFC connection works as expected. In the JNDI registry view of VisualAdmin I see the corresponding entry: "rfcaccessejb/RFCTEST" is a local reference to my stateless session bean.
On ABAP, I have a tiny little program that calls my function, mainly looking like this:
CALL FUNCTION 'RFCTEST' DESTINATION 'APP_JK1'
EXPORTING
    I_STRING_SEARCH = query
IMPORTING
    ECHOTEXT = t1.
Unfortunately, it short dumps immediately. The error message is:
JCO.Server could not find server function 'RFCTEST'
I'm lost. What could be wrong? Any help is greatly appreciated. Kind regards,
Christian Aust

Hello Perry song,
You got the short dump bcoz, there is no perform by the name you provided in the program,
for example. consider there are 2 programs.
Program 1 :
REPORT ZPGM1.
*Calling a perform SNAME1 , the code of perform is written in ZPGM2.
perform sname1 IN PROGRAM ZPGM2.
Program 2 :
REPORT ZPGM2.
perform sname1 .
Form SNAME1 .
write : 'Text in form SNAME1' .
endform.                    " SNAME1
(here SNAME1 is found and it works perfectly )
Change in Program 1 :
REPORT ZPGM1.
*Calling perform DELTA ,
perform DELTA IN PROGRAM ZPGM2 IF FOUND.
Now the perform statement will search for perform " DELTA " in ZPGM2 , but there is no perform by name DELTA , so here we need to mention the condition " IF FOUND " , so now by mentioning the condition " IF FOUND " in perform statement , if the perform DELTA is not found then it wont go to DUMP.
If condition " IF FOUND " is not mentioned in perform statement like
perform DELTA IN PROGRAM ZPGM2 . ( This gives DUMP )
just type " IF FOUND " when u r calling a perform from other program ( i guess this will solve the problem ).
Hope it might be helpfull,
Regards ,
Aby
Edited by: abhi on Nov 6, 2008 10:14 AM

Error while loading service JCo RFC Provider

When I click on the "JCo RFC Provider" node under services in Visual administrator, I get an error:
"Error while loading service JCo RFC Provider"
Does anyone know what has gone wrong here, and how I go about fixing it?
Thanks in advance
Regards
Richard
PS. We're using EP6sp14

You have to use the correct Visual Admin version:
if your netweaver is 6.40 use VA 6.40 ... and for 7.00 the same, VA 7.00
(you get them from OS where netweaver is installed)
other possiblity: use Administrator login and check if it works, then correct your permissions (mostyl 'Administrators' group is missing)
Regards,
Chris

Services in JCo RFC not getting started after Changing the client from 001

Hi SAP Stars,
I have recently Installed Quality and Production servers with PI 7.1 on windows 2003, Sqlserver 2005, when I'm doing Post Activities(http://host:port/nwa) in which I try to change the client from 001 to 300(newly created) in JCo RFC(4 services) and start the service it is throwing error when I again change it to 001 client and start the service it is getting started, Could anyone help me in solving this issue same issue I facing in PI 7.1 Quality and Production
Thanks In Advance
Anil Kumar

Hi Anil,
All these JCo RFCs are client specific RFCs.
Please logon your PI NWA
Choose Configuration Management - Infrastructure- JCo RFC Provider
Then, Select the RFC
Under Details -> Choose Repository Configuraton
Change the client name to 300 (your new client)
Save
And repeat the same for all JCo RFC that you want to work for your newly created client.
Please ensure that you are using SAPJSF user & correct password for all these RFCs.
Ideally, these rfcs shuould work now if now please restart your PI (mostly Java alone also do)
I hope this helps you.
Regards
Sekhar
Edited by: sekhar on Dec 17, 2009 11:39 AM

Third party system (JCO) ---RFC--- PI ---RFC--- ECC

Hello all,
We are trying to implement the following scenario:
Third party system (JCO) -RFC-> PI -RFC-> SAP ECC
The third party system connect to PI via Java Connector API with a know user id in PI. After that third party system tries to obtain the RFC that is already implemented and remote enabled in SAP ECC environment. But at this step there is something wrong in third party system software because we are not able to obtain the RFC interface and metadata from PI repository.
1. This step is working correctly. Connection is OK.
            JCO.Client mConnectionPI = JCO.createClient("100", // SAP client
                                                                                "user_id", // userid
                                                                                "********", // password
                                                                                "pt", // language
                                                                                "10.x.x.x", // application server host name
                                                                                "01"); // system number
            mConnectionPI.connect();
2. This step is not working correctly:
            JCO.Repository repository = new JCO.Repository("TestRep", mConnectionPI);
            IFunctionTemplate ftemplate = repository.getFunctionTemplate("Z_RFC_XXX"); - not found exception
We would like to know if there is something missing in any environment that we have to configure or implement in order to fix this issue. Thanks a lot.

Hi Primini,
couple of stupid-but-necessary questions:
1) have you imported the RFC model in PI Repository?
You don't need to have the RFC metadata in PI ABAP stack (there is no point in doing that), but rather in the PI Repository/ESR, within the SWCV you've created.
Check the "Activities" session of this link for more details:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/2b/a48f3c685bc358e10000000a11405a/frameset.htm
2) if you have done 1), have you configured the RFC Sender scenario properly?
I mean, have you ran the configuration wizard to create the agreements & determinations, setting the RFC interface as both the sender and the receiver interface? Of course, the systems would be different: as the sender system, you'll have a Business Service representing the legacy/JCo system; as the receiver, you'll have the ERP Business System.
This should make your scenario work.
If it doesn't, try one more thing: in the JCo code, just for the metadata repository connection, use a connection to the ERP system. But for the actual call, use the PI system.
Let us know the results.
Best regards,
Henrique.

LCRSAPRFC is missing in Visual Admin (JCo RFC Provider)

H y,
I'm facing a problem while connecting our SolMan via RFC to SLD.
Found documents explainig how to set up connection to SLD.
SAPSLDAPI (was present in Abap and Java - wrong credentials - repaired)
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
How can be the LCRSAPRFC added to JCo RFC Providers?
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Thanks in advance
Tom

Hi,
Do I have to create the RFC Conn LCRSAPRFC again in Abap/SM59 to get the LCRSAPRFC visible again in Visual Admin?
Not Required.
LCRSAPRFC (only present as RFC CONN in ABAP, but missing in Java, Visual Administrator JCo RFC Provider
Usual Process
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination:LCRSAPRFC
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: LCRSAPRFC_<SID>
where <SID> is the SAP system ID of your Integration Server host.
Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host.
To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and
gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in
Target System.
8. Save your settings.
Java Stack
SAP J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the SAP J2EE
Engine administration tool.
If you do not know how to start, see section How to start the SAP J2EE Administration Tool .
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for LCRSAPRFC that you used in the step Maintaining the RFC connection above.
Additionally, set the number of processes to 3.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client
and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
Testing
After you have maintained an RFC destination in both the ABAP and Java environment,
you can check it as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection.
No error should be displayed.
Regards,
Rao.Mallikarjuna
Edited by: Rao Mallikarjuna on May 31, 2008 11:40 AM

Question: Can Jco RFC Provider registers Program Id for BW7.3

Hello, Friends
I encounter the following issue and I wonder whether it is supported by Netweaver product. Please help answer.
My scenario is to create RFC (TCP/IP Connection) in ABAP server with program id registered by Jco RFC Provider (Visual Admin of NW7.02 Java)
If my ABAP BW NW server is 7.02 version, RFC can be tested successfully. However, for this time, I worked on another ABAP BW NW 7.3 Server and I create the RFC(TCP/IP Connection) with program id registered by Jco RFC Provider. As a
result, the RFC cannot find the program id registered by Jco NW 7.02 Java. Does Netweaver support ABAP 7.3 RFC with Program id registered by Nw 7.02 java Jco RFC provider?
Thanks a lot!
Welkin

Hi, Ejersbo
If you are using 7.3 portal, you can refer to the following on how to register Jco RFC provider on 7.3 Java:
(1) Open http://<server>:<port>/nwa
(2) Search for "Jco RFC destinations", open "Jco RFC destinations"
(3) Create a Jco RFC destination, with program id in the same name as the one which is used in your ABAP RFC in SM59
Welkin

JCO RFC Provider: "Bean not found" when calling EJB from ABAP via RFC

Hello,
I'm having trouble calling an EJB in a CE 7.1 system from ABAP via RFC. I'm trying to use the JCO RFC Provider service, which mean that I want to expose an EJB so that it can be called via Remote Function Call.
I have documented everything, including the code and the deployment descriptors I wrote, in this thread in the CE forum: Jco RFC Provider: Bean not found
If there's any chance you can help, please do me a favour and look into the problem.
Thanks a lot!
Thorsten

Hi Vladimir,
Thank you very much, your help was immensely valuable.
I just had to add the function declaration to the Home Component interface, everything else was correct, and now it works.
Cheers,
Thorsten

Difference In RFC Adapter and XI proxy

I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
Thanking you
sridhar

Hi,
Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.
In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
RFC Adapter :
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
For FAQs about the RFC adapter, see SAP Note 730870
The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
The RFC adapter maps the following RFC calls to XML messages and the other way around:
Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
●     Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
●     The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
You require the sender adapter if you want to use the Integration Engine or the PCK to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine or the PCK.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
Proxy :
Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
·        Interfaces designed for message exchange between application systems
·        Interfaces used by a cross-component integration process to receive or send messages, or both
Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
Interfaces are an essential component of SAP Exchange Infrastructure:
·        You define the interfaces to be used in an integration scenario.
·        Cross-component integration processes use interfaces to exchange messages.
·        You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
·        You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
·        You generate proxies to implement your scenario based on message interfaces.
You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

JCO /RFC prog and SNC : snc params ignored

Similar Messages

Maybe you are looking for