Enhancement in the RFC

Hi
we had done an enhancement to the RFC structure in R3 system and reimported the enhanced structure to the PI system and done the changes in the mapping as well >And even the enhancement was found in the request messager structre But in the response from the R3 we are not getting the expected results ( we are getting the response from the R3 as though The enhancement dint took place >I had tested the RFC in the R3 by passing the same values where I got 25 records but when the same request is given through we are getting only 20 records . Can any body tell me what might have gone wrong
thanks and regards
Nelakonda Praneeth
Edited by: praneeth nelakonda on Mar 10, 2008 9:45 PM

Hi
Try to create the mapping with the new RFC structure and then try it again.
and in the interafce mapping select the interafce again. this may also be the reason.
or may be cache is not getting refreshed.
Thanks
Rinku

Similar Messages

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 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 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

HOw to find out the RFC destination from BW system to ISU

Hi,
Currently my requirement is to call a function module which is written in ISU (remote enabled) from BW system.
I am unable to find out the rfc destination from BW to ISU system.
In CRM we have table like smofparsfa1. Is there any table in BW which can provide me the ISU destination?
I need to compare the records stored in isu as well as in BW system.
I need to call a function module which will provide me the data from isu.
please help me in this regard.
Krishna

Hi,
You can check it in SM59 if there are any RFC destinations for the above systems.
Alternatively ,check the table RFCDEST if any entries are maintained
Regards,
Lakshman.

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

Issue while calling the RFC in SAP quality system but not in SAP Dev sys

Hi,
Our scenario is FIle-RFC-File.
We are calling the RFC from XI system in Development environment. This is working fine in Development environment, but not in Quality environment.
This changes are moved/transported to Quality environment in both XI and SAP side. But we are getting the following error in Quality system:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please provide the inputs, what we can check at SAP side and XI side.
We have tried to test from XI Development to SAP quality environment, but we are getting the same error message.
Waiting for the precious inputs.
Thanks,
Ramesh.

Hi Ramesh,
This might be because your RFC adapter would not have been configured properly. Just do a check on it,in RWB(adapter monitoring) and activate it once more in ID.
Also check RFC comm. parameters such as host name/user id/password etc..
Also check whether your XML document is having a mismatch with your RFC XML.
Check with your payload ( from SXMB_MONI) and test it in your message mapping.
All the best!
cheers,
prashanth
P.S Please mark helpful answers

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

How to call the rfc in webdynpro abap..?

Dear Experts,
I need to add two numbers using RFC in webdynpro abap.
First we have to give the input then click the submit button.. The result will be shown in next screen with addition of two numbers... Please help me in this...
Thanks.

Calling an RFC Function module in Web Dynpro ABAP is nothing different from Classical ABAP
use Pattern button to call function module and use DESTINATION syntax to specify the RFC destination
http://www.octavia.de/fileadmin/octavia_files/content_bilder/Hauptnavigation/SAP_NetWeaver/WebDynpro/Web_Dynpro_Part_II.pdf?PHPSESSID=c528a60bf8857431c0fa6f6595639da7
In Above document, page no 7, there is a wizard for Service call, in that 4th step is select service where
you can specify the function module name and the rfc destination name
Abhi

How to Call the RFC in Webdynpro abap application

Dear Experts,
Good Evening to all...
I have to add two numbers using RFC in webdynpro abap application. If we give the numbers in the input screen then the RFC should add it and give it in the output screen. This is the application for that I have created the RFC.
But the problem is i don't know how to call the RFC in that Webdynpro abap application and how to link the input view and output view with that RFC...? I am new to Webdynpro abap. Please kindly help me on this... I am struggled here... I need your help in this....
Thank You.

Hi Jaga,
You asked the same question again.
Without closing the [previous one|Re: Where SAP store the uploaded files?].
I think Abhi has answered your question.
If not please elaborate on the problem.
The solution btw is to create a Service Call.
Sumit

It is possible to transpor the logical system definition and the RFC

Hello,
To define the back-end logical system we need to link the RFC destination SM59. If it is not possible to TRANSPORT the RFC destination from the development system to the quality one, I need to create the quality back-end logical system without transport.
In SRM there is a lot customizing in which we need to assing the back-end logical system. If I can not transport the back-end logical system definition from development to quality I must "re-create" a lot of customizing ditectly in quality (and later in production!)
This is the normal way to work in SRM? Do I have to create the RFC destination, the back-end logical system, etc. in each eviroment (development / quality / training / acceptance / production) or there is a way to transport this?
Cheers,
Marta

Hi Marta,
transporting in SRM is different from the other SAP areas. There are several
objects, which are normally customizing, but in SRM not part of the transportable
objects. You have to do quite a lot of settings manually in QA as well in PROD.
Start the discussion early to get the needed authorizations for doing the settings.
The following doc gives an overview and explains:
https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000310782007E
Cheers,
Claudia

How to call the RFC from R/3 to SRM, when we use webdynpro abap? (Urgent)

Hello
We use SRM Server 5.5 with classic scenario.
We want to call RFC in R/3 from webdynpro ABAP.
How can we do that?
We are developing the web report using webdynpro abap.
So we need some of R/3 data such like PR(EBAN)and PO(EKKO,EKPO).
When user choose the search parameter, report diplay the Shopping cart, PR and PO data on webdynpro. So we call the R/3 RFC to display the PR, PO data.
But I tired to call the RFC in R/3, We could not call it.
How to call the RFC from R/3 to SRM, when we use webdynpro abap?
Thank you,
Best Regards,
SH.

Hi
Please look at the following threads as well ->
WebDynpro in SRM
BAPI's /RFC's in SRM
BAPI to Change Shopping Cart by RFC
SRM60 and webdynpro
Webdynpro Services Exception
WebDynpro using BAPI has an error
SRM60 and webdynpro...
SAP uses META Function modules in SRM to get data from R/3 back-end.
For getting Purchase requistion data, use the function modules ->
META_REQUISITION_CHANGE Change purchase requisition
META_REQUISITION_CREATE Create Requisition
META_REQUISITION_DELETE Delete/close purchase requisition
META_REQUISITION_GETDETAIL Display requisition details
META_REQUISITION_GETITEMS Display requisition items
META_REQUISITION_GETRELINFO Get Releasease Info for requisitions
For getting Purchase order data, use the function modules ->
META_PO_CREATE Create purchase order
META_PO_DELETE Delete reservation
META_PO_GETDETAIL Display purchase order details
META_PO_GETITEMS Display purchase order items
META_PO_GETRELINFO Display purchase order release information
Hope this will definitely help. Do let me know.
Regards
- Atul

How to define the RFC in CUA

Hello expert,
We ran into a practical problem with defining the RFC connections for using CUA.
We are creating Composite roles in CUA which include the various Signle Roles of the child systems. These single roles are created in the CUA PFCG with the reference to the child system's RFC in the field "Target System".
Obvviously we want these Composites and single roles to be transported to the QA and PRD systems. However, currently the RFC connections are defines as "DE1CLNT110", "QE1CLNT110", etc. When transporting this is obviouslly going to cause problems as the RFC DE1CLNT110 does not exist in QA system.
Is there any best practice or SAP method to cover this 'gap' in CUA enviroments?
I see a few option:
1) Create the RFCs under an alias which is the same accross the landscape. (e.g CUA_ECC for ECC RFC, CUA_SRM for SRM RFC, etc..)
2) Only transport empty Composite roles and include the single roles manually in each system.
Transport Composites including single with RFC format "<system.client> (DE1CLNT110) and adjust the target system RFC manually in the next system.
In our view option 1 comes closed to a workable solution. However, we would like to have an expert advice on best practice as we cannot imagine this is not an known issue.
Thanks in advance,
Thomas

>
Thomas van Haaren wrote:
>
> I see a few option:
> 1) Create the RFCs under an alias which is the same accross the landscape. (e.g CUA_ECC for ECC RFC, CUA_SRM for SRM RFC, etc..)
>
a.) prerequsite: you adapt every destination in every system (landscape) in SM59 in a different way, let's say:
ERP_DEV, destination CUA_ECC has IP-address XXX.XXX.X.1, in ERP_QAS the same destination CUA_ECC has IP-address XXX.XXX.X.2 and so on and in every target destination the same in reverse. you would have to adapt every port in every locgical system and i think this is where it all gets pretty yuk ... transparancy?? btw. if you are refreshing your QAS-systems via system-copy you will have to do this all over again with every copy.
b.) you can proceed in this way, if the major condition for such a concept is fulfilled = in all the target systems (children) the role addresses with this name is exactly the same = the role, once changed in (for example) SRM_DEV is immediately transported to SRM_QAS and SRM_PRD. if the role of the same name differes in the children, things get even more confusing than under a.), since you are addressing different roles by 'on the surface' using the same name and the same destination name, only a different IP in the destination. that makes for some cruel searching in case of errors.
>
Thomas van Haaren wrote:
> 2) Only transport empty Composite roles and include the single roles manually in each system.
> Transport Composites including single with RFC format "<system.client> (DE1CLNT110) and adjust the target system RFC manually in the next system.
>
> In our view option 1 comes closed to a workable solution. However, we would like to have an expert advice on best practice as we cannot imagine this is not an known issue.
>
> Thanks in advance,
>
> Thomas
or ... adapt only the destination in single roles on tab 'menu', field target destination. i have my LSMW for that purpose.
not an ideal solution either, i admit.
am curious now, how do others do that?

Where should i call the rfc function module? in xi or in r/3

where should i call the rfc function module?
for the synch scenario: file < -- > xi <---> rfc
i know the type of rfc is tcp/ip; but i'm not sure with the followings,
and with some trials i can not even see any message via rwb even all the setting
can be activated without errors.
where should i create the rfc destination? in r/3 or xi
where should i call the rfc via abap program? in r/3 or xi
i guess the calling program should belong to the different server with the rfc itself....
so confused....
Thanks for your reply!!
Jun

if i create the destination in xi point to r/3, then i call the rfc use the destination in r/3 right ?
The call doesnt use the destination in R3. XI has the RFC destination which is just used to connect to the R3 system
but where i need to create the fm via se37? in xi or r/3 ?
In R3
Regards,
Prateek

Data from XI not reaching the RFC

hi,
in my scenario, XI is passing the data back to RFC in 4.6, but in my program where i call the RFC, the data is not received. what could be the issue.
CALL FUNCTION 'ZFFF' DESTINATION 'XI'
TABLES
INP = aaa
OUT1 = bbb
OUT2 = ccc.
COMMIT WORK.
it was working fine before when i had only OUT1. Later I added OUT2 and then onwards I am not getting data for any of the tables. I have checked in XI, data is being passed out of XI to RFC. No issues in that.
something seems to have gone wrong in the RFC modfication or the RFC call. can anyone please help.
thks

Hi,
Try to Re Import the RFC and check the structure of RFC and check the mapping structure and mapping and active it once .
While the import of RFC we are importing the structure(metadata) for SAP Interfaces RFC.
use the correct namespace ike
namespace for RFC
urn:sap-com:document:sap:rfc:functions
Regards,
sangeetha

Enhancement in the RFC

Similar Messages

Maybe you are looking for