Sap-wd-arfc-useSys

Hi ,
I have tired to change the RFC destinations of the model that was created in design time , using the url parameter
sap-wd-arfc-useSys as specifed in :
http://help.sap.com/saphelp_nw04/helpdata/en/f4/651741f163f023e10000000a155106/content.htm
but it does not work , and I don't know why ,
Just to mention the RFC metadata and nodel data in design time are not the default ones .
It says on the link that the webdynpro application should not be running when configuring those destinations

Hi,
Right click ur project >properties>webdynpro References>JCo references-chage the metadata and modeldata.......rebild ur project and then deploy it...
I hope it will solve ur problem...
Regards,
Yash

Similar Messages

Mapping Logical Systems sap-wd-arfc-useSys

Hi all,
I saw many many threads about this issue because sometimes seems to work but it doesn´t works for me.
So far I did the following:
Configure 4 JCO´s:
SAP_R3_HumanResources
SAP_R3_HumanResources_Metadata
These two points to my Dev environment
SAP_R3_HumanResourcesQAS
SAP_R3_HumanResources_MetadataQAS
These two points to my Qas environment
For all this JCO´s I got a successfull ping and test.
Then, I put the sap-wd-arfc-useSys parameters like this:
http://server:port/webdynpro/dispatcher/sap.com/essarpdata/ZPer_Personal_AR?sap-wd-arfc-useSys=SAP_R3_HumanResourcesQAS:QAS&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetadataQAS:QAS but this does not do anything.
In this link http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/frameset.htm the parameter should be the SUFFIX_OF_MAPPED_SYSTEM is the system Id? the client? what should be?
Do you have any ideas of what could I be missing?
Regards,
Orlando Covault

Please use it as follows:
sap-wd-arfc-useSys=SAP_R3_HumanResources:QAS&sap-wd-arfc-useSys=SAP_R3_HumanResources_Metadata:QAS
It should be <Default System>:<Suffix of Mapped System>
Your default system is - SAP_R3_HumanResources
Mapped system is - SAP_R3_HumanResourcesQAS
So suffix of the mapped system is - QAS
Hope that explains it.
Check this doc (page 17) for more info:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/526bd490-0201-0010-038e-d3ff7eb1d16e?quicklink=index&overridelayout=true
- Shanti
Edited by: Shanti Mupkala on Mar 16, 2011 5:26 PM

Java webdynpro Iview accessing different SAP system

Hai,
I have created two Java webdynpro Iview for ess leave application, in the Iview application parameter, I have given the below value
IVIEW1
sap-wd-arfc-useSys=SAP_R3_HumanResources:200&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:200.
IVIEW2
sap-wd-arfc-useSys=SAP_R3_HumanResources:300&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:300
JCO SAP_R3_HumanResources is mapped to client 100, I have created two more JCO's and the metadata SAP_R3_HumanResources200 & SAP_R3_HumanResources300
We have a CUA system and the client number of this system in 099. Apart from that we have client 100, 200 & 300. My userid is created in client 099 and 200 and Iview "IVIEW1" is assigned to my userid. When I try to access the Iview from portal I am getting a error, I checked the trace file and found the connection is going to client 100.
Then I created my userid in client 100 also and try to access Iview1, its going to client 200 without error.
When I use "SAP_R3_HumanResources:200&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:200" it looks like system will first connect to SAP_R3_HumanResource and then connects to client 200. Is this behavior normal.
What I want to do is with the "SAP_R3_HumanResources:200&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:200" I want to access client 200 without creating a id in client 100. Please let me know how to do or is there any other solution to achieve it.
Regards,
H.K.Hayath Basha.

HI,
Edit the JCo's, try to point the JCo's to 200 Client.
so that the iview can points to the 200 client right,
May be it will help u,
Cheers,
Apparao

Passing a parameter while calling a web dynpro application on portal

hi
I am having a web dynpro application which retrieves data from R/3 system via RFC using Jco destinations define in the Portal.
Now we have different kinds of portals running on the same WAS, now I want the application to run which access data from different R/3 systems thru different JCo destinations.
I need to create a logic such that mu application runs fine on any portal with any Jco destination.
Is there any provision to achieve this.
kindly let me know about this.
Thanks and regards
kris

Gopi,
there's an parameter called "sap-wd-arfc-useSys" you can pass to the application, to change the used JCo-Connection (read more at http://help.sap.com/saphelp_erp2005/helpdata/en/f4/651741f163f023e10000000a155106/frameset.htm)
so, if you're running the WD-aaplication on <b>one</b> WAS and call it from different portals, you have to create three (or six with the META-connections) JCo-Connection on your WD-WAS.
In a WD-application you can access URL-Parameters with:
WDWebContextAdapter.getWebContextAdapter().getRequestParameter("<your URL Parameter-Name>");
kr, achim

Issue while accessing two web-dynpro application, ESS/MSS and Payroll

Hi All,
We are facing one Critical Server Issue in our systems. Following is the scenerio:-
Our Portal system was having one Application known as German Payroll application. Before last two week one more application of ESS/MSS i.e. Time Management has been deployed to our system.
Now the user has two application with two different roles in the portal.
When user try to navigate from Time Management Application to German Payroll application or German Payroll Application to Time Management Application then they are facing Critical Server Error issue.
But once the user try to refresh using CTRL+F5 then the problem got resolved.
========================================================================
German Payroll applications back end server details:P95.
Time Management Application back end server details: P23
Steps to reproduce the issue:
1-login to portalgot to Employee self service tab-wait for 3-5mins
& than navigate to german payroll applications----& faced crtical
server errors:
Log from deafult trace:-
=======================================================
1.#0021280FECEE0028000000A400005A4B0004A2FA644F345C#1305096215265#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdyn
pro.progmodel.generation.DelegatingComponent#km048893#2758##n/a##fa2a61757b9911e08e660021280fecee#SAPEngine_Application_Thread[impl:3]
_9##0#0#Fatal#1#/Applications/Xss#
Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
at
com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)
at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit
(ModelHandler.java:205)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit
(InternalModelHandler.java:428)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber
(FcXssMenu.java:570)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit
(FcXssMenu.java:292)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit
(InternalFcXssMenu.java:455)
at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit
(FcXssMenuInterface.java:165)
System 'P95' is not possible because RFC Metadata was retrieved using
System 'P23'. Please assure you have configured the RFC Connections
properly. A Server restart may
be necessary!#
==============================================================
here is the catch....When user is trying to navigate from ESS tab(using
custom jcos for Backend system P23) to German payroll(backend system
P95) after 3 mins ---getting crtical error...Still its using the
data/metadat jcos connection information of ESS applications from
cache...that you can see in default trace.
PS: Standards Jcos are configured for P23 systems:
====================================================
SAP_R3_HumanResources----created with P23
SAP_R3_HumanResources_MetaData----been created with P23
SAP_R3_SelfServiceGenerics----been created with P23
SAP_R3_SelfServiceGenerics_MetaData----been created with P23
=====================================================
P95----Germman payroll
P23---ESS/MSS
Name of Cutsomn Jcos created for bakcend P95 i.e. german payroll
A-P95
=======================================================
SAP_R3_HumanResources:D95
SAP_R3_HumanResources_MetaData:D95
SAP_R3_SelfServiceGenerics:D95
SAP_R3_SelfServiceGenerics_MetaData:D95 configured with sap-wd-arfc-
useSys.
Name of cutom jcos created for backend ESS/MSS P23
B-P23
=========================================================
SAP_R3_HumanResources_MetaData:X23
SAP_R3_HumanResources:X23
SAP_R3_SelfServiceGenerics:X23
SAP_R3_SelfServiceGenerics_MetaData:X23 configured with sap-wd-arfc-
useSys.
========================================================
Jcos parameter of P23 backend:
JCo Pool Configuration
Maximum Pool Size: 50
Maximum Connections: 100
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
Jcos parameter of P95 backend:
JCo Pool Configuration :
Maximum Pool Size: 5
Maximum Connections: 10
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
===================================================================
After more analyzing the situation we found that one web dynrpo component i.e. pcui_gp~xssutils is common to both the application and it is configured to standard JCO i.e.
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
My thinking is that this component is giving us the problem.
Please provide your comments and solution to rectify this issue.
Also, let me know in case you need more information.
Thanks in Advance
Kuldeep Verma

Hi
First try a very simple application with nothing in it just one text saying Hello World
Run it and see what happens.
Also check if your url uses FQDN name. something like https:
company.name.co:50000\.......
If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
dropdowns.
regards
Yuval.

Mapping Logical Systems -

Hi,
i want to connect to 2 backends to test ESS BP functionality.
The background is that i want to test functions for ERP 6.0 EhP3 and need to keep the old Webdynpro functionality.
The old java webdynpro (ESS) is running on the portal side, the new ABAP webdynpro is running on the ERP system.
I configured new JCODestinations as described in http://help.sap.com/saphelp_nw70/helpdata/EN/af/84a34098022a54e10000000a1550b0/frameset.htm
I could connect now to iviews like life events with the correct parameters.
The issue is now that i also need to switch the XSS Overview (XssMenu) pages.
So far i am always connected to the old system. I tried all properties of that iview and also created a new one.
Is it possible to connect to the old system?
Thanks,
Kai

Hi Christian,
We are also looking into this functionality but have not gotten it to work yet.
Our issue is that our DEV/QA users need to test with different backend clients.
So we want to be able to specify a different JCO as part of the WebDynpro URL that we issue.
For testing, we have created two new JCOs (one data and one metadata). The names of the new JCOs are the same as the old but with 3 unique characters appended to the name (e.g. "ABC"). Those new JCOs point to a different client.
Then when we call the URL for the WebDynpro, we append
?sap-wd-arfc-useSys=SAP_R3_HumanResources:ABC&sap_wd_afrc-useSys=SAP_R3_HumanResources_Metadata:ABC
to the end of the URL.
However, after authenticating, this URL fails with NullPointerException
Any idea about what the problem might be?
TIA ... Bart

Mapping Logical Systems with ECC 5.0/6.0 for WD

Hi there,
did anyone have a good documentation to implement this solution, to connect WebDynpro, especially BP for ECC5.0 and 6.0, to two different Backendsystems?
I´m searching the way, to configure the logical target system name in the WD Content Admin.
SAPHelp-Link is not informative....
http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/content.htm
Best regards
Christian

Hi Christian,
We are also looking into this functionality but have not gotten it to work yet.
Our issue is that our DEV/QA users need to test with different backend clients.
So we want to be able to specify a different JCO as part of the WebDynpro URL that we issue.
For testing, we have created two new JCOs (one data and one metadata). The names of the new JCOs are the same as the old but with 3 unique characters appended to the name (e.g. "ABC"). Those new JCOs point to a different client.
Then when we call the URL for the WebDynpro, we append
?sap-wd-arfc-useSys=SAP_R3_HumanResources:ABC&sap_wd_afrc-useSys=SAP_R3_HumanResources_Metadata:ABC
to the end of the URL.
However, after authenticating, this URL fails with NullPointerException
Any idea about what the problem might be?
TIA ... Bart

Open external URL from Homepage Framework

Hi,
We are building our new ESS functionality with Homepage Framework and I need to create some links to external URL. I would like them to open in a different window with no portal header at all. They should appear as services listed in the menu area. While this seems easy, I had tried several things with no success.
First, I created an URL iview in portal content. I marked the option "launch in external window" to Open in a separate window.
I create a resource that pointed to this Iview, and linked resource with a "java webdynpro" service, service with subarea and subarea with area. The service link is displayed correctly but it is always opened in the portal page, not in a different one. Have i forgotten any parameter that would make this work?
A second approach was to create a resource that includes the URL and an associated service, marked as "Direct URL launched in separate window".
This succeds in calling the URL in a differeny window but it adds some strange parameters at the end. So instead of calling http://www.google.com it calls something like http://www.google.com?sap-ext-sid=2J*HeTVW7295w3QWBZhQow--
jQDfzgrDHRt*yZ87GlXsgA--%2Fpcd%3Aportal_content%2Fcom.bshg%2Fpct%2Fhcm%
2FEURO%2FES%2FESS%2Froles%2Fcom.bshg.hcm.ess-es%2FESS%
2Fcom.bshg.hcm.infoLinks%2Fsap.com%2Fpcui_gp%7Exssutils%2FXssMenuArea%
2Fbase&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics%3AHR0&sap-wd-
cltwndid=WID1325147123879&sap-accessibility&sap-locale=es&sap-rtl&sap-
epcm-guid=validate&sap-wd-renderMode=viewArea&sap-pp-
consumerBaseURL=http%3A%2F%2Fu3d.bshg.com%3A80&sap-ep-
version=7.0108.20110207041646.0000&sap-wd-tstamp=1325147150353&sap-
cssversion=7.11.7.30.0&sap-pp-producerid=com.bshg.BSHG_HCM_EMEA&sap-wd-
app-namespace=zzzz&sap-cssurl=http%3A%2F%2Fu3d.bshg.com%3A80%2Firj%
2Fportalapps%2Fcom.sap.portal.design.urdesigndata%2Fthemes%2Fportal%
2Fcustomer%2Fbsh%2Fur%2Fur_ie6.css%3F7.1.8.0.1&sap-wd-finish-
rendering=false
While some pages can ignore those extra parameters, in other cases, this causes a "page not found" error.
Any ideas on how to solve this problem?
Many thanks in advance to all.

Hi Daniel,
Define Resource: you have to mention all the below details
1. object name :http:// (url ).
2.window name: "".
3.window Property : target="_blank".
and also check define service:
service type: Direct url launched in a seperate window.
And assign resouce to service -
>
service to sub area--->
sub area to area---->
area to areagroup.
hope it helps............,
Thanks,
cbr.

Calling a ESS WDJ COmponent with different Client no

Hi,
my task is to make ESS available on a different Client (100) instead of 001.
i was reading about the "Mapping Logical Systems" using the parameter sap-wd-arfc-useSys :
http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/content.htm
I did the following :
1. Create a new JCODestination :
SAP_R3_HumanResources_MetaDataHNL and SAP_R3_HumanResourcesHNL with the new client.
2. Call the URL
http://<portal>:<port>/webdynpro/dispatcher/sap.com/ess~lea/com.sap.xss.hr.lea.appl.LeaveRequest?sap-wd-arfc-
useSys=SAP_R3_HumanResources:HNL&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:HNL
Result : i get a 500 internal Server error after the login for this client.
Test 2: The same with the default JCO Destinations : same error
Test 3: The same without the additional parameter : working
The JCO Destination is only SAP_R3_HumanResources when i looked it up the Content Admin Area for Web Dynpro.
What is the point i am missing ? Has someone done it successfully to connect to 2 systems per sap-wd-arfc-useSys ?
Regards,
Kai

Hi Arun,
the JCODestination Tests (Metadata) are successful.
The Assignment for ess~lea is only for :
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
It is a standard ESS iview. How and why should i assign additional JCODestinations ?
I overweite it per parameter sap-wd-arfc-useSys
Regards,
Kai

ESS + JCO + Multiple backend support

XSS with multiple backends
Hi All, we have a portal running with the standard ESS business package u2013 we use the system for demo purposes, and would like to be able to connect to different backend systems u2013 depending on the user.
IE, user XX connects to system DP4 and user YY connects to system ID4 u2013 is this possible?
My own approach was:
I made 2 delta copies of the of the standard ESS role to two folders u2013 XX and YY
XX I didnu2019t change, and therefore it used the standard SAP_R3_HumanResources JCO connection, which points to system DP4.
Then in the folder YY, I changed the WebDynpro iView parameter to:
sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:ID4&sap-wd-arfc-useSys=SAP_R3_HumanResources:ID4
and in the Webdynpro Content administrator I created these systems and called them:
SAP_R3_HumanResources_MetaDataID4 u2013 as the guide from sap descripes.
This did however not seem to work, as metadata was still readout from DP4 while application data was Read out from ID4.
Then I noticed that the application eg. WhoIsWho also refers to som additional applications, such as
Xssfpmutil and so on u2013 and they use the JCO: SAP_R3_SelfServiceGenerics, so I created a
SAP_R3_SelfServiceGenericsID4, and added this to the parameter string, so I know looks like:
sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:ID4&sap-wd-arfc-useSys=SAP_R3_HumanResources:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:ID4
But this doesnu2019t work, some of the data is still read from Dp4 instead of ID4
So my question is u2013 is it possible to use ESS with two backends, or is this not supported?
Help is MUCH appreciated
Br Ronni

Hi stuart!
I made two copies of the standard ESS role
ESS_XX and ESS_YY, and then i changed i iview parameters for each iview
(by breaking the deltalink in both roles),
giving them the following application parameter:
sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:ID4&sap-wd-arfc-useSys=SAP_R3_HumanResources:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:ID4&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:ID4
But the problem is that while the user YY gets modeldata form system YY the user gets metadata from system XX
(assuming he is created on system XX, if not we get an error).
so i guess the parameters somehow dont match.
Has anyone used the same portal for different backends with sucess?
Br Ronni

WD Exception when pointing ESS Travel & Expense to multiple backend systems

Hi All,
I have a query regarding ESS Travel Management pointing to multiple backend systems.
ESS MSS is installed on a single portal(Portal1).
ESS MSS is currently pointing to Backend System1. The requirement is that ESS Travel from Portal1 should point to various multiple Backend Systems therefore making ESS Travel region-specific.
Is this possible? and if so what are the pros and cons?
This is what I have attempted:
1. Followed the documentation from "Multiple Back End Support for the Adaptive RFC Model" [http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/frameset.htm]
Therefore, I created 2 JCOs namely: SAP_R3_Travel_R1 and SAP_R3_Travel_MetaData_R1 pointing to Backend Sytem 2. SSO and JCO tests successfully.
2. On the iview properties for ESS Travel & Expenses, I added the following to the Application Parameters: sap-wd-arfc-useSys=SAP_R3_Travel:_R1&sap-wd-arfc-useSys=SAP_R3_Travel_MetaData:_R1
3. I additionally created a system in the Portal under System Configuration pointing to Backend System2 and adding the SAP_R3_Travel_R1 as the default System Alias. Do I need to add SAP_ITS_XSS and SAP_WebDynpro_XSS system alias, if so how since it is seeing as redundant because it is added in the system I created for Backend System1.
4. I then tested one of the ESS Travel & Expenses iviews. I have the following error:
Accessing System XYZ is not possible because RFC Metadata was retrieved using System ABC. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!
Your help is appreciated.
Thanks.
RD

Hi,
Can you please share the solution you got for this problem as we are also facing the same kind of problem.
thanks
Gaurav

JCo Scenario with multiple Backend Systems

Hello @ all,
Is it possible to use multiple Jco destinations to multiple Backendsystems in one WD application?
The scenario is as following: I want to call different function modules on different SAP Backend systems?

Hi Mehmet
Alternatively you could try switching the destination through URL parameters
http://<Host-Name>:<Port-Nummer>/webdynpro/dispatcher/local/Example_Project/Example?sap-wd-arfc-useSys= WD_MODELDATA_DEST:SyB&sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:
SyB
Check this link (I havent tried it though)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/651741f163f023e10000000a155106/frameset.htm
Regards
Pran

Multiple backend systems for business package ESS/MSS

Hi,
I would like to know whether there is a smart solution for connecting the business package ESS/MSS with multiple backend systems (up to 10 systems).
I am aware of the possibility using parameter "sap-wd-arfc-useSys", but this implies, that content needs to be duplicated n-times in order to be able to maintain the Jco destination suffix.
Any hint, also for custom built solutions are very welcome!
Best regards,
Johannes

Johannes
There is some problem with the link
See this.
Connecting multiple SAP Systems
Thread name is 'Connecting multiple SAP Systems'
Krishna Murthy

Business Package ESS with more than one backend

Hi,
i need to implement a business package (ESS or MSS) two time in one portal system to access two backends. The portal landscape will completely be in the SAP standard, so we only want to implement a two system landscape (DEV and PROD) for the portal. On ERP side we have a three system landscape. So the aim is to implement the business package in the DEV portal two times and access both, the DEV and the QAS ERP system.
Are there any informations concerning this or has someone already performed this?
It think the steps are:
- Copy of the BP in PCD
- New Alias for the second system and change the alias at all PCD object in the copy
- Copy of the used JCo Destinations and adding them as a parameter to all iviews (the sap-wd-arfc-useSys=SAP_R3_HumanResourcesXYZ)
What do you think?
Kind regards,
Christian

I don't think you can do that for Jco Destinations.
You might create the copies of JCo Destinations.But you might need to change the new Jco names in the standard ESS/MSS Development Components which is quite difficult..
May be you can make JCo Destinations to point to Dev initially and then change it to quality for testing

Problem in switching JCOs

Hi,
I have a very peculiar situation out here :(. I have a single webndynpro application and need it to connect to multiple backends.
The DC structure is as follows:
1) DC_UTILS - this DC contains components that actually execute the model objects. It has its own SINGLE model that consists of proxy classes for many RFCs. At the time of creation, these model classes were created with JCOs, "WD_MODELDATA_ABC" and "WD_RFC_METADATA_ABC".
2) DC_FAP - This DC uses DC_UTILS. It contains the entire business logic and screen flow and calls methods exposed by DC_UTILS.
3) DC_RUN - This DC uses DC_FAP. It has an application called 'RunApp' that calls the "Window Interface View Controller" of a component within DC_FAP.
I have tried to add the "sap-wd-arfc-useSys" parameters in the URL and fire the application, 'RunApp'. I am doing this by adding the above parameters to the URL dynamically in the "onPlugDefault" event handler of RunApp's Window interface View Controller. But somehow, the classes within DC_UTILS seem to get executed BEFORE the "onPlugDefault" method of the Window Interface View Controller (and hence the model proxies are generated with the JCO that I had used at design time)... and hence JCO switching doesn't take place.
I tried the above method in a single DC that contains the model classes, business logic and execute methods and it worked absolutely fine. The problem arises when I start using one DC in another. Somehow, the used DC's model classes get initialized with the JCO names set at design time , EVEN BEFORE THE onPlugDefault of the Window Interface View Controller of the USING DC is called. Is there any method / event in the USING DC that is called BEFORE the classes in the USED DC are initialized ?
regards,
Navneet.

Hi,
I tried using caps for the password......it didnt work.
The parameters given are the same as in dev but i get this error when I ping the JCO created : "com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect."
Are there any priveleges which are needed for JCO creation to use the same userid/pwd in staging?
What could be the other possibility?
Please suggest.
Regards,
Rajani

Sap-wd-arfc-useSys

Similar Messages

Maybe you are looking for