Rights to calls on RFC

Kind time of day.
There is a module caused on RFC. In system of development and test system all works perfectly. In product system at attempt to cause the module the mistake drops out: Problem retrieving JCO.Function object
Whether prompt as to check up there are rights to calls on RFC.

Hi
See this Thread
Rights required for BAPI calls
Kind Regards
Mukesh

Similar Messages

Problem while calling an RFC Function Module in Background

Hello,
I have created a RFC function module for reading data from an external DB system. The FM calls an external RFC program (coded in C++ using RFC SDK), which delivers the required data. This external program is maintainged as an TCP RFC Connection in SM59.
Further I have created a report, that calls the RFC function module to get the data from the external RFC programm.
My problem is, when I call the report in foreground, everything works OK, the RFC connection works and data can be read from the external program.
However, when I schedule the report to run in background as a job, the report is stating in the protocoll that there was a problem calling the defined RFC connection (although the connection is working properly at that time).
More funny is, this particular problem with running in background occurs only in the productive system, in test and development system the report works correctly also while running as a job in background.
Can you suggest the solution to this problem? Could it be something with authorisations or server settings?
I will be on holiday for the next 6 weeks, so take your time to answer .
Regards,
Dusan.
Edited by: Julius Bussche on Jan 22, 2009 7:19 PM
Please read the forum rules about u r g e n t ...

This is an external RFC server program, not a remote enabled ABAP RFC function module as the others seem to be assuming, right?
Is it possible that your DEV and QAS systems only have one application server, but the PROD has many and dedicated one(s) for processing low priority background jobs?
It might be that the target server of your TCP connection is not this BTC instance, and your RFC server is returning the data "locally" - so, into nirvana...
Just guessing, but might be worth checking.
Cheers,
Julius

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

How to call Custom RFC enabled Function Module in R/3 From XI

Hi Experts,
I want to call custom RFC enabled Function Module by sending some input parameters from XI.
How to do this
Thnx
RAMS

Hi RAMS,
1. Under the SWCV Go to the Imported Objects.
2. Right click on the RFC and click on the Import of SAP object.
3. Give the logon server name, system number the user name and pasword.
4. Select the RFC u want to import.
5. Execute the import and the RFC is imported under the SWCV.
Now u can use this Imported RFC in the scenarios of that SWCV.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

Calling BAPI(RFC function module) in java? Part 2

Hi
Can any body tell me or give me source code for calling give BAPI...i need to give the inputs to that parameters..
data l_order_header_in    like bapisdhd1.
data t_return             like bapiret2 occurs 0 with header line.
data t_order_items_in     like bapisditm occurs 0 with header line.
data t_order_schedules_in like bapischdl occurs 0 with header line.
data t_order_partners     like bapiparnr occurs 0 with header line.
*data t_order_condition_ex like bapicond   occurs 0 with header line.
*clear   t_order_condition_ex.
*refresh t_order_condition_ex.
clear l_order_header_in.
l_order_header_in-doc_type      = 'TA'.
l_order_header_in-sales_org     = 'ZZ02'.
l_order_header_in-distr_chan    = 'Z2'.
l_order_header_in-division      = 'Z2'.
*l_order_header_in-purch_no      = '12'.
clear   t_order_items_in.
refresh t_order_items_in.
t_order_items_in-itm_number     = '000001'.
t_order_items_in-material       = 'HAMAM'.                 " 'LBYA1'.
t_order_items_in-target_qty     = '0000000000001'.
t_order_items_in-comp_quant     = '0000000000001'.
append t_order_items_in.
clear   t_order_partners.
refresh t_order_partners.
t_order_partners-partn_role     = 'AG'.
t_order_partners-partn_numb     = '0000000006'.
append t_order_partners.
clear   t_order_schedules_in.
refresh t_order_schedules_in.
t_order_schedules_in-itm_number = '000001'.
t_order_schedules_in-sched_line = '0001'.
t_order_schedules_in-req_qty    = 1.
append t_order_schedules_in.
clear   t_order_partners.
t_order_partners-partn_role     = 'WE'.
t_order_partners-partn_numb     = '0000000006'.
append t_order_partners.
break kumars.
call function 'BAPI_SALESORDER_CREATEFROMDAT2'
exporting
SALESDOCUMENTIN               =
    order_header_in               = l_order_header_in
ORDER_HEADER_INX              =
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
IMPORTING
SALESDOCUMENT                 =
tables
    return                        = t_return
    order_items_in                = t_order_items_in
ORDER_ITEMS_INX               =
    order_partners                = t_order_partners
    order_schedules_in            = t_order_schedules_in
ORDER_SCHEDULES_INX           =
ORDER_CONDITIONS_IN           =
ORDER_CONDITIONS_INX          =
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
break venkat.
call function 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT          =
IMPORTING
RETURN        =
Awaiting for ur responses..
Thx
PRadeep

To call an RFC, you need to import that first. For that right click on the project into which you need to add the rfc.
Import >>import RFC modules from r/3>>Give the package name and a port name for the rfc.
set the server options as your r/3 server properties.
Then you can search the Function name >> it will be displayed in the result area>> select it and press finish.
The RFC will be imported to your project.
Then you need to create JCO for calling that rfc.
Here is a sample code which calls an RFC and setting jco..
import com.sap.mw.jco.JCO;
import com.sapportals.portal.prt.component.*;
public class rfc extends AbstractPortalComponent
     private JCO.Client jcoClient;
     Insert_pgm_PortType insFunc=new Insert_pgm_PortType();
     Zinsert_Pgm_Input ip=new Zinsert_Pgm_Input();
     Zinsert_Pgm_Output op=new Zinsert_Pgm_Output();
    public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
    this.connect();
     insFunc.messageSpecifier.setJcoClient(jcoClient);
//setting input params
     ip.setAssociate_Id1("44");
     ip.setCourse_Objt1(2);
     ip.setQlty_Content1(5);
     ip.setSeq_Content1(2);
     ip.setTraining_Id1("22");
//calling RFC
     try{
     op=insFunc.zinsert_Pgm(ip);
     }catch(Exception e){}
          response.write(op.getMessage());
          this.disconnect();
//creating JCO connection
     private void connect() {
               try {
                    jcoClient =
                         JCO.createClient("Client","userid","password","Language","servername","Systemid");
                         jcoClient.connect();
               } catch (Exception e) {
                    System.out.println("Error connecting to SAP ::" + e.getMessage());
                    e.printStackTrace();
     private void disconnect() {
               try {
                    jcoClient.disconnect();
               } catch (Exception e) {
                    System.out.println(
                         "Error dis-connecting to SAP ::" + e.getMessage());
                    e.printStackTrace();
Hope this Helps
gEorgE

Jobs not getting Scheduled when it is called from RFC

Hi Everyone,
I have Functional module in system1 which in turn creates a background Job, but when i call this Function module from System2 using RFC then the background job is not created. THought i debugged and the Function module on system1 is called successfully with right input parameters. M i missing anything ? Please advice
Regards,
Nikesh Kumar

Hi Chen,
Thanks for the reply. Actually the main problem is not with how the Background job is getting executed. Actually my function module schedules are job in system1 , but if the same func module is called via RFC from other system, it gets called successfully with same inputs (checked in debugging), but the background job does not get created.
Regards,
Nikesh Kumar

JCOProxy error while calling a RFC

Hi,
When i tr to call a RFC "CBIF_GLM1_BATCH_READ", i get a fatal error.The error message is:
"JCOProxy error: Problem retrieving JCO.Function object."
When i checked if i was able to connect to any of the functions other than BAPI's i got the same error.
Is there something that i need to turn on in SAP?
I am using SAP xMII 11.5.3 SR03 and SAP 4.7 Enterprise.
Any help appreciated.
Thanks,
Ram

Ram,
I tried loading this RFC, CBIF_GLM1_BATCH_READ, using my version of xMII 11.5.3 and it worked without a problem. Are you sure that this RFC was not modified in your system that causes it to not work properly? Also, when you tested the RFC in se37 did you try to run it without setting any parameters? What about using the Web DynPro interface to see if it generates the XML properly? Just a couple of things to look into, but I know it's not xMII. If you did modify the RFC you will have to restart the ServletExec service to clear the xMII JCO API cache. Hope this helps.
-Sam

Calling a RFC using connection pool

Can I use connection pool to call a RFC from my R3? I'm using SAP Enterprise Connector but I don't want to pass user/password hardcoded.
Thanks in advance.

Hi Kiran,
Yes I used SAP JRA and it works.
You need JRA deployed and configured on WAS, your basis guy can do it for you. The next step is download this PDF <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ad09cd07-0a01-0010-93a9-933e247d3ba4">Accessing BAPIs Using the SAP Java Resource Adapter</a>.
Follow this document, it's very easy to do so.

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

How to call two RFC in a single JAVA method.

Dear all,
I just want to know that how to call two RFC in a single java method which is defined in CRM implementation file. I'm using NWDS as the customization IDE & working on ISA 7.0.

Hi Sunil,
In the Backend Implementation class, in any method you can call multiple RFCs.
It will be the same way as you do for the single RFC call.
Following syntax is for your reference.
Get the JCO connection
JCoConnection connection = getDefaultJCoConnection();
JCO.Function func = connection.getJCoFunction("ZXXXXXXX");
set the import parameters
Execute it.
connection.execute(func);
get the data from export / table parameters
Now call the second RFC
func = connection.getJCoFunction("ZYYYYYYYYYY");
set the import parameters
Execute it.
get the data from export / table parameters
close the connection
Hope this will help you.
-Chandra.
Edited by: Chandra Sekhar Seeli on Jan 13, 2011 2:04 PM

How can I call a RFC from dynpage ?

Hi!
I would like to know how can I call a RFC from a Portal aplication, dynpage or jspdynpage. there include some libraries ?
any idea?
thanks

for deploying SAP Jra :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ad09cd07-0a01-0010-93a9-933e247d3ba4#search=%22how%20to%20use%20jca%20sapjra%20site%3Asap.com%22
For lookup of SAP Jra use:
com.sapportals.connector.connection.IConnectionFactory connectionFactory =(IConnectionFactory) initctx.lookup( "deployedAdapters/SAPFactory/shareable/SAPFactory");
Using SAP Jra
http://help.sap.com/saphelp_nw04s/helpdata/en/47/13044258bdd417e10000000a1550b0/content.htm
The important jars required are:
connector.jar
Genericconnector.jar
prtjndisupport.jar
Thanks

Calling Synchronous RFC Function Module in Background

Hi all,
Currently we are working on some requirement where in we have to retrieve data from one system(CRM) and update the same into another system(ECC). We have developed a RFC Function in CRM system and it is being called from ECC system as in synchronous mode via a batch program.
Now since all sychronous call to a RFC function will be dialog there is a constraint on the runtime which is being set by maximum run time for each dialog work process. So my question is there an option to call an RFC function synchronously in background (background task) so there is no runtime performance.
The standard TRFC, QRFC calls in background runs asynchronously and so I am trying to check with the SDN world as whether has anyone tried SRFC(Synchronous) call in background?
Thanks in advance,
Jagath

So my question is there an option to call an RFC function synchronously in background (background task) so there is no runtime performance.
One solution would be to increase the value of the "time out" parameter defined the CRM system. This i feel is not a fool-proof solution as the run-times cannot be predicted. Check this thread: Re: RFC timeout profile parameter
For me a better solution would be to implement tRFC call instead of a synchronous call. Any reasons why you don't want to implement a tRFC ?
BR,
Suhas
Edited by: Suhas Saha on Jun 26, 2010 8:52 AM

Calling a RFC Function Module

Hello Guys,
I have a question regarding calling a RFC function module.
In BW - BI 7.0 I call a RFC function module:
(The ABAP program in BW-BI 7.0 is below)
CALL FUNCTION ''ZTESTFUNCTIONMODULE' " Function module in ECC
     DESTINATION 'DECCLNT110' " ECC system
    TABLES
      it_gl_item   = it_gl
      it_errlog_gl = it_errlog_gl.
The 'ZTESTFUNCTIONMODULE'   is RFC enabled in the ECC system.
The purpose is we retarct the data from BW to ECC.
When I run the function module it always asks for the user id and password.
The SAP logon screen appears and it asks for the user id and password.
The destination is maintained in the SM59 transaction and also the user is maintained there. I think it should login automatically into remote system and return the tables. is it correct. How to skip the logon screen.
Do I have to pass the user id and password in the function module. I think it should take the user id from the SM59 destination. Is it correct.
Please advise. As always thanks for your help guys.

Hi Senthil,
I think you answered your query in your question itself
The user ID and password need to be maintained in RFC destination in SM59.
Go to SM59 and then click on test connection..if it does not ask for ID and passwoed that means correct ID and password is maintained in SM59 otherwise maintain it.
Regards,
Atish

How to call a RFC of a remote system from an ABAP webdynpro component

Dear Experts,
I am a newbie in ABAP Webdynpro.
I am working on a requirement where I have a webdynpro component on ECC system.I need to call a RFC located on CRM system from my webdynpro component on the ECC system.
How do I do that ?? Please help.
Regards,
Mamai.

Calling RFC from some other system is same as local except the difference is that you have to give destination name while calling.
And the regarding the method of calling it depends on your FM.
if it is big RFC with complex structure, you can create the service call for it with destination given as RFC desitination.
if it is simple straight forward RFC you can directly call it.
for creating RFC service call call use this method
1. Starting the Wizard
To start the wizard, position the cursor on the Web Dynpro component to be edited in the object list at the left margin of the
workbench window. Open its context menu and choose the entry Create->Service Call. The wizard is started and leads you
through the creation process.
Press Continue.
2. Choice of Controller
On the second dialog window of the wizard, you can choose whether the service call is to be embedded in an existing
controller or whether a new controller is to be created for this purpose. Service calls can only always be embedded in
global controllers u2013 that is, in the component controller or in additionally created custom controllers. It is not possible, to
embed service calls in view controllers.
a. Select radio button Use Existent Controller
b. Do not change the default entry for component: <CC name>
c. Enter for controller COMPONENTCONTROLLER
d. Press Continue.
3. Service Type and Service Selection
a. You now select, which service type should be used for this service call. Select radio button Function Module. Fill the
destination here. Press Continue.
b. Select the service: for Function Module enter <RFC name>. Press Continue.
4. The Required Methods and Context Elements
On the two subsequent dialog windows, default values are listed for giving names to the context nodes and attributes
required by the service call as well as to the required methods. The proposed names are based on the names of the
embedded service, but you can change them as required. However, heed the respective notes in the corresponding dialog
box.
a. Adapt Context: Select from Nodes/Attributes . Press Continue.
b. Specify Method Name: leave all entries as provided: Component: Controller: COMPONENTCONTROLLER Method: EXCUTE_ Press Continue.
5. Completing the Choice
When you have confirmed the last dialog box, the generation is triggered. Afterwards you now have the required methods
and contexts at your disposal for using them within your Web Dynpro component.
or if you want to call directly the use the call statement with destination

Finding an error while calling an RFC

Hi,
My requirement is as follows.
The internal table(ITAB) which i am using has a field X of length 20 and the Internal table(RFCITAB) field Y found the RFC is of length 10. Here i am creating another 3rd internal table(ITAB1) with field Z of length 10 and i am moving the content of field X from ITAB to ITAB1 and i am passing Z value of ITAB1 to the RFC.
While executing it i am getting the error 'Interface data error'.
please let me know why this error is getting populated.
Regards,
Sumi

Hi,
I have a field lenght of 20 digits in BKPF-AWKEY and it has value of only 10 digits.
I am moving this 10 digits to a new field in a new internal table and i am passing this value to the RFC.
I am getting error while calling the RFC.
Regards,
Yamini.A

Rights to calls on RFC

Similar Messages

Maybe you are looking for