Error in the RFCs

Hi friends. I've some problems when we generate PDF Files from the BI server, that run the PDFs in other ADS server. The error into the Visual Admin --> Services --> Destinations --> Aba Runtime --> HTTP and when I click in the RFC "save and test" I get this error: "Error during ping operation:Error while silently conncecting:org.w3c.www.protocol.http:HttpException:org.w3c.www.protocol.http:HttpException:Unable to contact target server mybiserver.net:8000 after 1 tries."
When I change in the RFC the number of the port to 50100, than run ok, but it's not correctly. It needs to run in the 8000 port. Can anybody help me? Thanks !

Marcos,
I am also facing the issue. Did you find a solution for this? If so, please let me know your findings.
Regards,
Ramesh

Similar Messages

ERROR in the RFC communication when parabatch is set to more 3 (default)

Hi experts,
We have a 10 blades BIA system connecting to our BW Production. When we set the parabatch to more than the default 3 (we set to 4 or 5), We keep getting 'Batchpara Error' and 'Error in the RFC Communication: Error when opening an RFC Connection' during the initial index build. Here are what we do and what we see:
1. set parabatch to 5 and build 1 initial index (cube is 46 mil rows, 22 GB in size) - Failed with the above errors
2. set parabatch back to 3 and build 1 initial index (same cube as above)- successful but slow
3. set parbatch back to 3 and build 2 initial indexes simultaneously (16 mil rows/4GB and 6 mil rows/2 GB) - Failed with the above errors.
In the BIA index log I see the following error:
Error in the RFC communication: Error when opening an RFC connection (TREX_BIP)
Message no. STREX005
In SM37 in one of the logs I see the followings:
Parabatch Error
Any light you can shed on why we are encountering this issue will be much appreciated. Also, I observed that there is a long idle time in all systems (BIA, DB2, BW) and seemed like their respective resources were not utilized at all. Once in a while I do see surge of cpu/memory usage in all systems but not too terrible. I'm puzzled by why there is such long interval of idle time in all systems while the initial index build is going on.
BTW...we did the same thing (set parabatch to 5, and run parallel initial builds) in our non-prod BIA (2 blades) and QA BW landscape and do not have any issue at all.
Thanks!
Kee

Hello
PLease check the sapnotes and check the developer trace for more information.
Note 314530 - Number of RFC/CPIC connections for external clients
Note: 1070034
It can also be because your system has reached it its max gateway connections...also check whether you are getting error message "Communication error, CPIC return code 017, SAP return code 450
" in sm21 ???
Regards
Karthikeyan.K

Error in the RFC Connection

Hi Expert,
First, I'm sorry if I post in the wrong thread.
I have a problem when creating RFC Connection. I want to create RFC Connection between BW systems to R/3 System in SM59.
I already insert the right IP Address to the target system, but when I test the connection, I got this error :
host name 'SAP-BO-01' unknown / CPI-C error CM_PRODUCT_SPECIFIC_ERROR
I already test the connection from BW to R/3 and vice versa, using ping in command prompt, and I got no problem. Also, I already create a log on to the target system, and it was successful, but the RFC Connection still error.
Did you have any clue or solution about this?
I really appreciate every helpful comment from you. Thank You...

Hi
Do you have mapping in the host file in the server? ask you basis team to check that.
If you can ping the server, that means connection is fine, only thing is there might be some entry missing in hosts or services file in the server.
During creation of RFC connection you can directly use the IP address also. as you said you are able to ping the server that means you got to know the IP address. Now use the below command to know the exact hostname.
ping -a <IP_ADDRESS>
Regards
Anindya

Error in the RFC LCRSAPRFC and SAPSLDAPI

Hi,
The RFC LCRSAPRFC and SAPSLDAPI TCP/IP connection to strike up and all SOAP interfaces stops in XI environment.
Yesterday the same problem occur. I checked if user is lock but not locked. Just after I restarted the environment (stopsap and starsap) and I made refresh full cache http://brjgs916:50100/CPACache/refresh?mode=full
the RFC´s TCP/IP LCRSAPRFC/SAPSLDAPI back to work.
The problem is intermittent occurs almost all days.
I found and implemented the notes 314530 and 316877 but I think this notes cannot solve this problem.
My XI environment is kernel 700 patche level 95 and Stack ABAP and Java
11, HP-UX with Oracle 10g.
Thanks so much for your attention
Douglas Brisola

Is the SLD running on the same server?
We had a similar issue and the hardware the SLD was running on was, er, unreliable! The availability is much better these days!

How to catch the error if an RFC fails due to short dump

Hi All,
I was calling the RFC Function module in parallel processing depends on the number of work processors available. I am getting the return message from the Function module using the perform statement
PERFORMING task_return ON END OF TASK
But I am not able to catch the errors if the RFC has been terminated due to the dump or manually killing the RFC while running.
I need how to handle the RFC if the call has been terminated due to the dump or system failure. Does the RFC return the sy-subrc at this time or can we able to catch the error in any other way.
Thanks & regards,
Vijay

Hello Vijay,
If you're calling RFC from outside SAP using the OCX-SAPFunctions-Library, then you can catch the dump or any other exception occuring in your SAP-Function.
Assuming that, objRFCFunc is the RFC-Function you can get the Excepetion-Code through objRFCFunc.Exception.
It returns a String. If the error was a dump, the String is "SYSTEM_FAILURE". If it is a "regular" Exception you'll get the Exceptioncode. E.g. "NO_DATA_FOUND".
If you need any sample code e.g. VBA-code for use in Office-Applications, let me know.
regards
Sven

The RFC Destination ALESERVER is not available

Hi ,
I am getting the error message " The RFC Destination ALESERVER is not available " in my CRM Web UI screen.But when I login with another User ID , this error message is not showing.
RFC connections are maintained in transaction SM59 and BD97.but I m still facing with this issue.
Please advice what could be the cause of error.
Regards,
Ravi

Hello,
please check in SM59 the LOGON-User for this RFC-Destination.
Maybee the user where it works is maintained, the other not.
Or if there is a general RFC-User maintained the user where it does not work has maybee not the authorization in the target.
Best regards
Manfred

Getting Error while Creating the RFC Model

Hi All,
I am Creating the aRFC model. Now i am getting error in the creation of RFC.
In Single Server in am giving my R/3 Server IP. my usrname and password.
what i have to write in the Load Balancing. I am not getting any options in Load Balancing Tab.
When i press Next, Error is coming:
Connect to SAP Gateway Failed.
Error: Partner Not Reached.
So pls help out......
Regards,
Dhruv Shah

Hi Dhrruv,
You can check your SAP R/3 username and password with the BASIS person or Security person.
Once it is confirmed, give the following details:
Host Name : abcdefg.hij.xyz (ie.give the alias of the server )
System Number : 00
Client : (give ur client system number)
Logon Name : (ur SAP logon Name)
Password: (ur SAP Password)
Language : EN
Leave SAP Router blank.
Click next. It should work. Try this and let me know what happens.
If you get error please send me the screen shot of the details u filled in to [email protected]
Thanks
Kukku

Error while running the RFC on ECC 6.0 server

Hello Champs,
The problem I am facing while sending the data for validation and invalidation from RFC on ECC server to Pi server to be send to a webservice. This scenario was working perfectly fine when the RFC was run on R/3 4.7 server. On upgradation of R/3 server to ECC 6.0 server we found the folowing error while we run the RFC on ECC server.
alternativeServiceIdentifier:party/service from channel configuration are not equal to party/service from lookup of alt ..
I have also re-imported the RFC's from ECC server to PI server and activated it again to overcome this problem, but still I am getting this error. Also I have done the CPA cache refresh too. But the problem still persist.
Some times when we keep on clicking on this error continously then we are able to get the desired results ie either valid or invalid. Is there something which needs to be done when we migrate the RFC from R/3 server to ECC server? Pls let me know how to solve this problem... Any help on this on priority basis is highly appreciated.
Thanking You in Advance.
Regards
S Joshi

Dear Rajesh,
I did the activity as suggested by you but still I am getting the same error while sending the order ID number from ECC 6.0 server. But when check the error in the Moni transaction I am getting the error as follow:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Not enough message parts were received for the operation.
This indicates that there is a problem on the receiver side.. Pls guide me......
Thanks
With Best Regards
S Joshi

Error"SYSTEM Failure" while testing the RFC in SE37 : RFC to JDBC Scenario

Hi All,
I am doing RFC to JDBC scenario. When I am testing the RFC in SE37 using the RFC destination created in SM59, I get an error "SYSTEM FAILURE".
Please suggest.
Thanks,
Shyam
Edited by: Shyam Sreepada on Dec 18, 2007 5:46 PM

Hi,
You must run RFC with RFC destination in background mode, I suggest to read following post in order to understand it better.
Syntax would be:
CALL FUNCTION func IN BACKGROUND TASK
[DESTINATION <your RFC destination>]
parameter list
http://help.sap.com/saphelp_nw04/helpdata/en/8f/53b67ad30be445b0ccc968d69bc6ff/frameset.htm
If you read it you will find that you can't test it directly from SE37, for this either you need to create dummy ABAP program or another RFC where you will call this RFC with background syntax.
Regards,
Gourav
Reward points if it helps you
Edited by: Gourav Khare on Dec 18, 2007 6:07 PM

Error Happened at RFC Server Cannot Open the Job Batch File.

We have BW 7.0 and Data services 12.1. We are scheduling a Infopackage in BW that triggers a job in Dataservices server.
We had checked the connection between Dataservices source system in BW and RFC server on Dataservices side and these connections are good. on the 3rd party sellections tab in infopackage we specify the batch file name that we exported in Dataservices server. When we execute the infopackage we get the following error.
Error Happened at RFC Server Cannot Open the Job Batch File.
This error started occuring from yesterday and prior to that it was working fine. We are not understanding what changed in the system to cause this error.
Can anyone suggest any solutions for the above issue.
Thanks,
Naveen.

I'm not sure what the root cause would be here. Is the file still available ? Did file permissions change ? ...
But I wanted to point your attention to the fact that in Data Services/Data Integrator XI 3.2 (=12.2) we significantly enhanced the integration with BW. In XI 3.2, the RFC server is now integrated into the Data Services Management Console (so no need to start as a seperate executable) and you can start jobs from BW by just specifting the job's name in the repo (no need anymore to export execution commands to .bat files). So if upgrading to XI 3.2 is an option, things should go much smoother.
More details on the wiki : http://wiki.sdn.sap.com/wiki/display/BOBJ/Loading+BW
Thanks,
Ben.

How to catch the CC's error in the alert inbox(RFC to File)

Dear All,
I'm now have a question about catching the CC's error.
The interface is RFC to File, when the sender CC had a error(for example:RFC adapter's connection information was wrong) , there was not error message in the alert inbox even though I set all the condition of the alert rule with "*".
where is the problem?
thanks,
Sam

Hey
First of all check SLG1 if any alerts were triggered for the error.
Secondly uncheck "Suppress multiple alerts of this rule" option in alert configuration in RWB,it might be checked right now.
Thanks
Aamir

Getting the following error in receiver RFC channel

Hi Folks,
Iam having two RFC channels one as SENDER and other as RECEIVER.Ensuring that all the required data is perfectly given while creating these two channels...the SENDER RFC channel status is green in channel monitoring and RECEIVER RFC channel is red!
Iam gettiing follwing error against RECEIVER RFC channel -
"Receiver channel 'Receiver_RFC' for party '', service 'BXT_100_IS'
Error can not instantiate RfcPool caused by:
com.sap.aii.adapter.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Name or password is incorrect. Please re-enter"
Even iam pretty sure about the user and pwd used in RECEIVER RFC channel...
and also i noticed "perform notification" status is failed in cache notification against my user id...
Can anyone help me in resolving this issue..
Thanks in advance..
Regards,
Ram.

Hi Ram,
Please change your password to UPPERCASE and try.
I have came across few instances where SAP converts passwords to uppercase while storing and so they dont match.
Hope this helps.
Regards,
Rahul.

Error-The RFC destination EDSCLNT900 is not available in ICWC

Hi All,
I'm working on CRM Utilities 2007. In the ICWC, I'm getting the error 'The RFC destination EDSCLNT900 is not available'. Kindly help me in resolving this error.
Regards,
Archana.
Edited by: archu_sap on Jul 15, 2009 10:30 AM
Edited by: archu_sap on Jul 15, 2009 10:33 AM

Hi,
You have to maintaine RFC Destination EDSCLNT900 in the CRM system.
generally we have to maintain RFC (t-code SM59) in the sytem where Function Module is present.
Suppose you are having FM in ECC system and you want to call in CRMsystem, then you have to maintain RFC destination (EDSCLNT900) in ECC system.
Thanks & Regards.
ShreeMohan

Error on reviever RFC side

Getting following error on reciever RFC side
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.
The custom RFC used in this case has export parameter as a table containing list of matching entries. There is no export parameter by the name RETURN.
Regards,
Amol

Hi Amol,
go to your RFC receiver determination and uncheck under "Advanced Mode" the fields "Commit Handling for Single BAPI Calls" and "BAPI Advanced Mode".
If you have BAPI and non-BAPI calls with the same R/3 system, you need seperate communication channels".
Regards
Stefan

Unable to call the RFC from the WD java Program

Hi All,
I have a table and three buttons Create, Edit, Save in the layout.
If no record available in the R3 the the end user will click on create and then he will click on save so that the insert RFC will be called accordingly and the record will be inserted.My table is limited to 5 records only. If i enter all the 5 records and Click on submit the record is inserting in the backend , but if i enter less than 5 records im unable to call the RFC what might be the issue.
My insert RFC takes one Table node and 4 import parameters i'm passing all of the all the mentioned import parameters.
Code:-
View Controller code
// This file has been generated partially by the Web Dynpro Code Generator.
// MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
// ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
package com.gmr.ess;
// IMPORTANT NOTE:
// ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
// BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
// AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateAPPView).
// OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
// A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
// OF IMPORT STATEMENTS.
//@@begin imports
import java.math.BigDecimal;
import java.util.Date;
import java.text.DateFormat;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.ArrayList;
import java.util.Calendar;
import java.util.Collection;
import java.util.Iterator;
import com.gmr.ess.wdp.IPrivateAPPView;
import com.gmr.pck.Zst_Hr_Nominee;
import com.sap.tc.webdynpro.progmodel.api.IWDMessageManager;
import com.sap.tc.webdynpro.services.sal.um.api.IWDClientUser;
import com.sap.tc.webdynpro.services.sal.um.api.WDClientUser;
//@@end
//@@begin documentation
//@@end
public class APPView
Logging location.
private static final com.sap.tc.logging.Location logger =
 com.sap.tc.logging.Location.getLocation(APPView.class);
static
 //@@begin id
 String id = "$Id$";
 //@@end
 com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
Private access to the generated Web Dynpro counterpart
for this controller class. 
Use <code>wdThis</code> to gain typed access to the context,
to trigger navigation via outbound plugs, to get and enable/disable
actions, fire declared events, and access used controllers and/or
component usages.
@see com.gmr.ess.wdp.IPrivateAPPView for more details
private final IPrivateAPPView wdThis;
Root node of this controller's context. 
Provides typed access not only to the elements of the root node
but also to all nodes in the context (methods nodeXYZ())
and their currently selected element (methods currentXYZElement()).
It also facilitates the creation of new elements for all nodes
(methods createXYZElement()). 
@see com.gmr.ess.wdp.IPrivateAPPView.IContextNode for more details.
private final IPrivateAPPView.IContextNode wdContext;
A shortcut for <code>wdThis.wdGetAPI()</code>. 
Represents the generic API of the generic Web Dynpro counterpart
for this controller. 
private final com.sap.tc.webdynpro.progmodel.api.IWDViewController wdControllerAPI;
A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. 
Represents the generic API of the Web Dynpro component this controller
belongs to. Can be used to access the message manager, the window manager,
to add/remove event handlers and so on. 
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
public APPView(IPrivateAPPView wdThis)
 this.wdThis = wdThis;
 this.wdContext = wdThis.wdGetContext();
 this.wdControllerAPI = wdThis.wdGetAPI();
 this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
//@@begin javadoc:wdDoInit()
/** Hook method called to initialize controller. */
//@@end
public void wdDoInit()
 //@@begin wdDoInit()
 try{
 IWDMessageManager manager1 = wdComponentAPI.getMessageManager();
 IWDClientUser user = WDClientUser.getLoggedInClientUser();
 String logUser= user.getSAPUser().getUniqueName();
 wdContext.currentContextElement().setUserid(logUser);
 wdThis.wdGetAPPController().executeBapi_Employee_Getdata_Input();//Returns the user id for the employee
 Collection nomineeList = new ArrayList();
 wdThis.wdGetAPPController(). executeZ_Hrfm_Nominee_Disp_Input( );
 int nomineeTableSize = wdContext.nodeZ_Hrfm_Nominee_Disp_Input().nodeOutput_Nominee().nodeNominee().size();
 for(int i=0;i< nomineeTableSize;i++){
 IPrivateAPPView.IDisplay_table_nodeElement ele = wdContext.nodeDisplay_table_node().createDisplay_table_nodeElement();
 ele.setAddr(wdContext.nodeZ_Hrfm_Nominee_Disp_Input().nodeOutput_Nominee().nodeNominee().getNomineeElementAt(i).getAddr());
 ele.setDob(wdContext.nodeZ_Hrfm_Nominee_Disp_Input().nodeOutput_Nominee().nodeNominee().getNomineeElementAt(i).getDob());
 ele.setGuard(wdContext.nodeZ_Hrfm_Nominee_Disp_Input().nodeOutput_Nominee().nodeNominee().getNomineeElementAt(i).getGuard());
 ele.setName(wdContext.nodeZ_Hrfm_Nominee_Disp_Input().nodeOutput_Nominee().nodeNominee().getNomineeElementAt(i).getName());
 ele.setPerc(wdContext.nodeZ_Hrfm_Nominee_Disp_Input().nodeOutput_Nominee().nodeNominee().getNomineeElementAt(i).getPerc());
 ele.setRelat(wdContext.nodeZ_Hrfm_Nominee_Disp_Input().nodeOutput_Nominee().nodeNominee().getNomineeElementAt(i).getRelat());
 nomineeList.add(ele);
 wdContext.nodeDisplay_table_node().bind(nomineeList);
 wdContext.currentContextElement().setEdit_val_attr(true);
 if(nomineeTableSize<=0){
 wdContext.currentContextElement().setCreateButtonEnable(true);
 wdContext.currentContextElement().setEditButtonEnable(false);
 else{
 wdContext.currentContextElement().setCreateButtonEnable(false);
 wdContext.currentContextElement().setEditButtonEnable(true);
 catch(Exception e){
 wdComponentAPI.getMessageManager().reportException("",true);
 //@@end
//@@begin javadoc:wdDoExit()
/** Hook method called to clean up controller. */
//@@end
public void wdDoExit()
 //@@begin wdDoExit()
 //@@end
//@@begin javadoc:wdDoModifyView
Hook method called to modify a view just before rendering.
This method conceptually belongs to the view itself, not to the
controller (cf. MVC pattern).
It is made static to discourage a way of programming that
routinely stores references to UI elements in instance fields
for access by the view controller's event handlers, and so on.
The Web Dynpro programming model recommends that UI elements can
only be accessed by code executed within the call to this hook method.
@param wdThis Generated private interface of the view's controller, as
 provided by Web Dynpro. Provides access to the view controller's
 outgoing controller usages, etc.
@param wdContext Generated interface of the view's context, as provided
 by Web Dynpro. Provides access to the view's data.
@param view The view's generic API, as provided by Web Dynpro.
 Provides access to UI elements.
@param firstTime Indicates whether the hook is called for the first time
 during the lifetime of the view.
//@@end
public static void wdDoModifyView(IPrivateAPPView wdThis, IPrivateAPPView.IContextNode wdContext, com.sap.tc.webdynpro.progmodel.api.IWDView view, boolean firstTime)
 //@@begin wdDoModifyView
 //@@end
//@@begin javadoc:onActionGetData(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onActionGetData(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionGetData(ServerEvent)
 //$$begin ActionButton(-535519310)
 //wdThis.wdGetAPPController().executeZ_Hrfm_Nominee_Disp_Input();
 //$$end
 //@@end
//@@begin javadoc:onActionEdit(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onActionEdit(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionEdit(ServerEvent)
 //$$begin ActionButton(-535519310)
 displayTablesize=wdContext.nodeDisplay_table_node().size();
 if(displayTablesize<5){
 for(int i=0;i<size-displayTablesize;i++){
 IPrivateAPPView.IDisplay_table_nodeElement ele = wdContext.nodeDisplay_table_node().createDisplay_table_nodeElement();
 wdContext. nodeDisplay_table_node().addElement(ele);
 operation="MOD";
 wdContext.currentContextElement().setTableReadOnly(true);
 wdContext.currentZ_Hrfm_Nominee_Ins_Mod_InputElement().setOperation(operation);
 //$$end
 //@@end
//@@begin javadoc:onActionCreate(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onActionCreate(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionCreate(ServerEvent)
 int month=0,year=0,day=0;
 String month1,day1,year1;
 try{
 displayTablesize=wdContext.nodeDisplay_table_node().size();
 wdContext.currentContextElement().setEdit_val_attr(false);
 if(wdContext.nodeDisplay_table_node().isEmpty()){
 if(displayTablesize<5){
 Calendar cal=Calendar.getInstance();
 month=cal.get(Calendar.MONTH)+1;
 if(month==1||month==2||month==3||month==4||month==5||month==6||month==7||month==8||month==9){
 month1="0"+month;
 else{
 month1=""+month;
 day = cal.get(Calendar.DAY_OF_MONTH);
 if(day==1||day==2||day==3||day==4||day==5||day==6||day==7||day==8||day==9){
 day1= "0"+day;
 else{
 day1=""+day;
 year = cal.get(Calendar.YEAR);
 year1=""+year;
 String strFormat=day1"."month1"."year1;
 wdContext.currentOutput_NomineeElement().setBegda(strFormat);
 wdContext.currentOutput_NomineeElement().setEndda("31.12.9999");
 for(int i=0;i<size-displayTablesize;i++){
 IPrivateAPPView.IDisplay_table_nodeElement ele = wdContext.nodeDisplay_table_node().createDisplay_table_nodeElement();
 wdContext. nodeDisplay_table_node().addElement(ele);
 operation="INS";
 wdContext.currentZ_Hrfm_Nominee_Ins_Mod_InputElement().setOperation(operation);
 wdContext.currentContextElement().setTableReadOnly(true);
 catch(NullPointerException npe){
 wdComponentAPI.getMessageManager().reportException("No Data Available",true);
 //@@end
//@@begin javadoc:onActionSaveData(ServerEvent)
/** Declared validating event handler. */
//@@end
public void onActionSaveData(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionSaveData(ServerEvent)
 float percentage=0;
 float dupePercentage=0;
 boolean isTest = false;
 Collection DispTList = new ArrayList();
 IWDMessageManager manager1 = wdComponentAPI.getMessageManager();
 try{
 displayTablesize = wdContext.nodeDisplay_table_node().size();
 //for(int i=1;i<=displayTablesize;i++){
 for(int i=0;i<displayTablesize;i++){
 BigDecimal share = wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getPerc();
 String name = wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getName();
 percentage = share.floatValue();
 dupePercentage = dupePercentage + percentage;
 if(name!=null && share!=null){
 Zst_Hr_Nominee nominee = new Zst_Hr_Nominee();
 nominee.setAddr(wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getAddr());
 manager1.reportSuccess(wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getAddr());
 nominee.setDob(wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getDob());
 manager1.reportSuccess(""+wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getDob());
 nominee.setGuard(wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getGuard());
 manager1.reportSuccess(""+wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getGuard());
 nominee.setName(wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getName());
 manager1.reportSuccess(""+wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getName());
 nominee.setPerc(wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getPerc());
 manager1.reportSuccess(""+wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getPerc());
 nominee.setRelat(wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getRelat());
 manager1.reportSuccess(""+wdContext.nodeDisplay_table_node().getDisplay_table_nodeElementAt(i).getRelat());
 DispTList.add(nominee);
 wdContext.nodeZ_Hrfm_Nominee_Ins_Mod_Input().nodeNominee_ins().bind(DispTList);
 if((dupePercentage)!=100)
 wdComponentAPI.getMessageManager().reportException(
 "The sum of the share Percentages is not 100. Modify the percentages accordingly",true);
 wdContext.nodeZ_Hrfm_Nominee_Ins_Mod_Input().nodeNominee_ins().bind(DispTList);
 IWDMessageManager manager = wdComponentAPI.getMessageManager();
 String beginDate = wdContext.currentOutput_NomineeElement().getBegda();
 manager.reportSuccess(wdContext.currentOutput_NomineeElement().getBegda());
 String endDate=wdContext.currentOutput_NomineeElement().getEndda();
 manager.reportSuccess(wdContext.currentOutput_NomineeElement().getEndda());
 wdContext.currentZ_Hrfm_Nominee_Ins_Mod_InputElement().setBegda(beginDate);
 wdContext.currentZ_Hrfm_Nominee_Ins_Mod_InputElement().setEndda(endDate);
 wdContext.currentZ_Hrfm_Nominee_Ins_Mod_InputElement().setOperation(operation);
 wdComponentAPI.getMessageManager().reportSuccess(operation);
 wdThis.wdGetAPPController().executeBapi_Employee_Getdata_Input();
 wdThis.wdGetAPPController().executeZ_Hrfm_Nominee_Ins_Mod_Input();
 //wdContext.currentContextElement().setTableReadOnly(false);
 catch(Exception e){
 e.getMessage();
 //@@end
The following code section can be used for any Java code that is
not to be visible to other controllers/views or that contains constructs
currently not supported directly by Web Dynpro (such as inner classes or
member variables etc.). 
Note: The content of this section is in no way managed/controlled
by the Web Dynpro Designtime or the Web Dynpro Runtime.
//@@begin others
int nomineeTableSize = 0;
int displayTablesize = 0;
String operation= null;
int size=5;
// float dupePercentage=0;
//String mod_op="MOD";
//@@end
content of obsolete user coding area(s) -
//@@begin obsolete:javadoc:onActionSave(ServerEvent)
// /** Declared validating even
Component controller code
// This file has been generated partially by the Web Dynpro Code Generator.
// MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
// ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
package com.gmr.ess;
// IMPORTANT NOTE:
// ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
// BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
// AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateAPP).
// OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
// A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
// OF IMPORT STATEMENTS.
//@@begin imports
import java.util.Iterator;
import com.gmr.ess.wdp.IPrivateAPP;
import com.gmr.pck.Bapi_Employee_Getdata_Input;
import com.gmr.pck.Bapip0002B;
import com.gmr.pck.Z_Hrfm_Nominee_Disp_Input;
import com.gmr.pck.Z_Hrfm_Nominee_Ins_Mod_Input;
import com.gmr.pck.Zst_Hr_Nominee;
import com.sap.lcr.api.util.SetProfileConnect;
import com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException;
import com.sap.tc.webdynpro.progmodel.api.IWDMessageManager;
//@@end
//@@begin documentation
//@@end
public class APP
Logging location.
private static final com.sap.tc.logging.Location logger =
 com.sap.tc.logging.Location.getLocation(APP.class);
static
 //@@begin id
 String id = "$Id$";
 //@@end
 com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
Private access to the generated Web Dynpro counterpart
for this controller class. 
Use <code>wdThis</code> to gain typed access to the context,
to trigger navigation via outbound plugs, to get and enable/disable
actions, fire declared events, and access used controllers and/or
component usages.
@see com.gmr.ess.wdp.IPrivateAPP for more details
private final IPrivateAPP wdThis;
Root node of this controller's context. 
Provides typed access not only to the elements of the root node
but also to all nodes in the context (methods nodeXYZ())
and their currently selected element (methods currentXYZElement()).
It also facilitates the creation of new elements for all nodes
(methods createXYZElement()). 
@see com.gmr.ess.wdp.IPrivateAPP.IContextNode for more details.
private final IPrivateAPP.IContextNode wdContext;
A shortcut for <code>wdThis.wdGetAPI()</code>. 
Represents the generic API of the generic Web Dynpro counterpart
for this controller. 
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdControllerAPI;
A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. 
Represents the generic API of the Web Dynpro component this controller
belongs to. Can be used to access the message manager, the window manager,
to add/remove event handlers and so on. 
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
public APP(IPrivateAPP wdThis)
 this.wdThis = wdThis;
 this.wdContext = wdThis.wdGetContext();
 this.wdControllerAPI = wdThis.wdGetAPI();
 this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
//@@begin javadoc:wdDoInit()
/** Hook method called to initialize controller. */
//@@end
public void wdDoInit()
 //@@begin wdDoInit()
 //$$begin Service Controller(1490375209)
// wdContext.nodeZ_Hrfm_Nominee_Ins_Mod_Input().bind(new Z_Hrfm_Nominee_Ins_Mod_Input());
 Z_Hrfm_Nominee_Ins_Mod_Input input = new Z_Hrfm_Nominee_Ins_Mod_Input();
 input.addNominee(new Zst_Hr_Nominee());
 wdContext.nodeZ_Hrfm_Nominee_Ins_Mod_Input().bind(input);
 //$$end
 //$$begin Service Controller(-932523997)
 wdContext.nodeZ_Hrfm_Nominee_Disp_Input().bind(new Z_Hrfm_Nominee_Disp_Input());
 //$$end
 //$$begin Service Controller(-368783613)
 wdContext.nodeBapi_Employee_Getdata_Input().bind(new Bapi_Employee_Getdata_Input());
 //$$end
 //@@end
//@@begin javadoc:wdDoExit()
/** Hook method called to clean up controller. */
//@@end
public void wdDoExit()
 //@@begin wdDoExit()
 //@@end
//@@begin javadoc:wdDoPostProcessing()
Hook called to handle data retrieval errors before rendering.
After doModifyView(), the Web Dynpro Framework gets all context data needed
for rendering by validating the contexts (which in turn calls the supply
functions and supplying relation roles). In this hook, the application
should handle the errors which occurred during validation of the contexts.
Using preorder depth-first traversal, this hook is called for all component
controllers starting with the current root component.
Permitted operations:
- Flushing model queue
- Creating messages
- Reading context and model data
Forbidden operations:
- Invalidating model data
- Manipulating the context
- Firing outbound plugs
- Creating components
@param isCurrentRoot true if this is the root of the current request
//@@end
public void wdDoPostProcessing(boolean isCurrentRoot)
 //@@begin wdDoPostProcessing()
 //@@end
//@@begin javadoc:wdDoBeforeNavigation()
Hook before the navigation phase starts.
This hook allows you to flush the model queue and handle any
errors that occur. Firing outbound plugs is allowed in this hook.
Using preorder depth-first traversal, this hook is called for all component
controllers starting with the current root component.
@param isCurrentRoot true if this is the root of the current request
//@@end
public void wdDoBeforeNavigation(boolean isCurrentRoot)
 //@@begin wdDoBeforeNavigation()
 //@@end
//@@begin javadoc:wdDoApplicationStateChange()
Hook that informs the application about a state change.

This hook is called e.g. to tell the application that will be
<ul>
<li>left via a suspend plug and therefore should go into a suspend/sleep
 mode with minimal need of resources. errors that occur. Firing
 outbound plugs is allowed in this hook.
<li>left due to a timeout and could write it's state to a data base if the
 user comes back later on
</ul>
The concrete reason is available via IWDApplicationStateChangeInfo

Important: This hook is called for the top level component only!
@param stateChangeInfo contains the information about the nature of the state change
@param stateChangeReturn allows the application to ask for a different state change.
 The framework is allowed to ignore it considering i.e. the current resources situation.
//@@end
public void wdDoApplicationStateChange(com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo stateChangeInfo, com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeReturn stateChangeReturn)
 //@@begin wdDoApplicationStateChange()
 //@@end
//@@begin javadoc:executeBapi_Employee_Getdata_Input()
/** Declared method. */
//@@end
public void executeBapi_Employee_Getdata_Input( )
 //@@begin executeBapi_Employee_Getdata_Input()
 //$$begin Service Controller(1705750894)
 IWDMessageManager manager = wdComponentAPI.getMessageManager();
 Iterator itrGetData = null;
 Bapip0002B out = null;
 try
 wdContext.currentBapi_Employee_Getdata_InputElement().modelObject().execute();
 wdContext.nodeOutput().invalidate();
 itrGetData = wdContext.currentOutputElement().modelObject().getPersonal_Data().iterator();
 while (itrGetData.hasNext()) {
 out = (Bapip0002B) itrGetData.next();
 empNo = out.getPerno();
 wdContext.currentZ_Hrfm_Nominee_Disp_InputElement().setPernr(empNo);
 wdContext.currentZ_Hrfm_Nominee_Ins_Mod_InputElement().setPernr(empNo);
// manager.reportSuccess(empNo);
 //wdThis.executeZ_Hrfm_Nominee_Disp_Input();
 catch(WDDynamicRFCExecuteException e)
 manager.reportException(e.getMessage(), false);
 //$$end
 //@@end
//@@begin javadoc:executeZ_Hrfm_Nominee_Disp_Input()
/** Declared method. */
//@@end
public void executeZ_Hrfm_Nominee_Disp_Input( )
 //@@begin executeZ_Hrfm_Nominee_Disp_Input()
 //$$begin Service Controller(-366407911)
 IWDMessageManager manager = wdComponentAPI.getMessageManager();
 try
 wdContext.currentZ_Hrfm_Nominee_Disp_InputElement().modelObject().execute();
 wdContext.nodeOutput_Nominee().invalidate();
 catch(WDDynamicRFCExecuteException e)
 manager.reportException(e.getMessage(), false);
 //$$end
 //@@end
//@@begin javadoc:executeZ_Hrfm_Nominee_Ins_Mod_Input()
/** Declared method. */
//@@end
public void executeZ_Hrfm_Nominee_Ins_Mod_Input( )
 //@@begin executeZ_Hrfm_Nominee_Ins_Mod_Input()
 //$$begin Service Controller(1524028406)
 IWDMessageManager manager = wdComponentAPI.getMessageManager();
 try
 wdContext.currentZ_Hrfm_Nominee_Ins_Mod_InputElement().modelObject().execute();
 wdContext.nodeOutput_nominee_ins_mod().invalidate();
 catch(WDDynamicRFCExecuteException e)
 manager.reportException(e.getMessage(), false);
 //$$end
 //@@end
The following code section can be used for any Java code that is
not to be visible to other controllers/views or that contains constructs
currently not supported directly by Web Dynpro (such as inner classes or
member variables etc.). 
Note: The content of this section is in no way managed/controlled
by the Web Dynpro Designtime or the Web Dynpro Runtime.
//@@begin others
String empNo = null;
//@@end
Suman
Edited by: sumankumar kurimilla on Dec 23, 2008 9:26 AM

Hi,
I have checked from RFC side that is working fine only java app its not working can you tell any thing needs to be changed from my application end.
Please check in Savedata action.
Regards,
Suman
Edited by: sumankumar kurimilla on Dec 23, 2008 11:01 AM

Error in the RFCs

Similar Messages

Maybe you are looking for