RFC  fm in CSS system

Hi,
Is there any RFC FM in CSS system, which will retrive Message status.
Regards,
Swetha

Pramod,
check the base thing first.. what is your job log saying at that particular moment.. so simulate that part, you can just write a code with that RFC FM call only.. and schedule it in background... see whats coming in job log...
and one more thing.. The FM which you are calling(the RFC FM), does it require GUI at any stage? check that as well.
pass the FM name here if its not a customized FM.. we can try..

Similar Messages

  • Unable to open RFC connection to SAP System NSP

    Hi all,
    During installation i am getting an error which is as follows,
    "Unable to open RFC connection to SAP System NSP.
    Solution: Start the system."
    And the second problem is that there are no connections shown in SAPGUI.
    Please help me out.
    Thanking you,
    Kranthi

    HI Kranthi,
    Have you checked this thread NW Preview Installation error?
    Regards

  • 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

  • Error in RFC & to Solution Manager System

    Hi,
    Error in RFC & to Solution Manager System
    can anyone tells me why this error occurs???
    With regards
    kulwinder

    FYI
    We have just had same issue thaat in certain scenarios with RFC communication BACK to Solution Manager from Satellite system we got the error.  We resolved this by looking at the RFC user used in the BACK connection (i.e. SOLMAN<SID>) on the Solution Manager and changing the user type from communications.
    Hope this helps someone else, I spent ages digging around for an answer to such a simple fix
    Paul

  • RFC connection to source system is damaged , no Metadata uploaded

    Hello Friends,
    I need your help to understand and rectify why my transport is failing again and again.
    RFC connection to source system BT1CLNT200 is damaged ==> no Metadata upload
    Environment - Production Support (Dev - Quality - Testing - Production)
    Alive scenario - Need to create two InfoObject and incorporate the fields in to data targets and reports.
    What we have did?
    1st request - We have created new request and captured two Infoobjects in to the request.
    2nd Request - We have captured the replicated Datasource along with that the below sequence displayed by default in the same package.
    Communication structure
    DataSource Replica
    Transfer Rules
    InfoSource transaction data
    Transfer structure
    3rd Request - we have captured DSO and Cube only in this request.
    4th Request - Captured 2 update rules (ODS) Update Rule (Cube)
    The above 3rd request failed in the testing system (successful in Quality System) and ODS is inactive in the Testing system.
    Testing system Error Message:
    The creation of the export DataSource failed
    RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
    RFC connection to source system BT1CLNT200 is damaged ==> no Metadata uploa
    Error when creating the export DataSource and dependent Objects
    Error when activating ODS Object ZEOINV09
    Error/warning in dict. activator, detailed log    > Detail
    Structure change at field level (convert table /BIC/AZEOINV0900)
    Table /BIC/AZEOINV0900 could not be activated
    Return code..............: 8
    Following tables must be converted
    DDIC Object TABL /BIC/AZEOINV0900 has not been activated
    Error when resetting ODS Object ZEOINV09 to the active version
    So we have captured the data mart Datasource and created a new( 5th ) request (transported only 5th request )and transported in the below sequence
    Communication structure
    Datasource Replica
    Transfer Rules
    Infosource transaction data
    Transfer structure
    development to Quality - Successfully
    Failed in testing system again.
    How to rectify this error, please help us
    Thanks,
    Nithi.

    Hello All,
    *Question -1*
    I have checked the connections and typed the steps below - what i have seen in the screen.
    Steps :
    R/3 Connection - I have double clicked on the BT1CLNTXXX and tested the connections.
    Connection Type :
    Logon - 0KB , 10 KB , 20KB, 30 KB
    R/3 connection:
    5 msec, 0msec, 1msec,1msec,1msec
    Please let me know whether RFC connection is OK or not.
    Question - 2
    I want to know is there is any option to check before transporting the TR from Developement to Quality - "Preview Check " the sequence , so that we can avoid the Transport failure because of TR sequence.
    Regards,
    Nithi.

  • The definition of the READ RFC to the managed system could not be found. Pl

    Hi there,
    i try to setup a managed system on our Solution manager for E2E Analysis... but the Setup gave me a sort of errors
    The definition of the READ RFC to the managed system could not be found. Please make sure to run the RFC creation assistant in SMSY, as described in setup documentation
    and
    No RFC Read User (SOLMANSOX001 or SM_SID) was found at ABAP Host=HOST sys=00 client=001 for roles assignment. Please make sure you have run the RFC creation assistant for this system, in SMSY. If a user name different  from the default 'SM_<SID>' or 'SOLMAN<SID><CLIENT>' was specified in the SMSY RFC creation assistant, you need to assign by hand the following roles & profiles to the Read RFC User :  SAP_SATELLITE_E2E (role), S_AI_SMD_E2E (profile)
    So which documentation means the setup where is described how to create the RFC Destinations with SMSY.. Thanks
    Regards
    Edited by: Bjoern Bayerschmidt on May 17, 2010 5:45 PM

    Hello,
    The documentation is located at [Help|http://help.sap.com/saphelp_smehp1/helpdata/en/b3/64c33af662c514e10000000a114084/frameset.htm]
    Then navigate Basic Settings > Solution Manager System Landscape >  Create Systems > Generate RFC Connections
    You can:
    Assign an existing RFC destination to a client with Assign and Check RFC Destinations.
    Generate RFC destinations for your managed systems
    Change existing RFC connections.
    Delete RFC destinations.
    Resolve RFC Generation Errors
    I hope you find this information helpful.
    Regards,
    Paul

  • RFC Destination and Logical System

    Hi Friends,
    Can anybody tell me how the RFC Destination and Logical System are related to each other?

    Hi,
    In any ALE scenario u need one sender and one receiver system.
    Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
    Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want  to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
    In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
    Thanks.

  • Sender RFC from Third Party System

    I have a vendor who is actually communicating through RFC from third party Application to SAP R/3. Now we are trying have XI in between. Where as with minimal impact on both sides.
    Solution.
    1. Have the RFC made as ZRFC in XI. Let the vendor call the RFC in XI ABAP and internally make an RFC call through XI Interface to R/3 as Sync Interface. Because we need to report the information back to the system where the request initiated.
    2. Have RFC INI file copied as SAP Suggests under one of the folders. Develop the regular RFC to RFC Interface via XI.
    Is there any other alternatives other than the above mentioned solutions? Or out of those 2, which one will provide the best performance
    Appreciate any feedback. Please advice

    That's exactly what we are trying to achieve here. By Eliminating direct connection R/3, we are placing XI in between. But with the budget/timeline constraints from the Partner side, we are trying to have minimal change on the partner side. They might not change something to web service etc...
    Here is the text about INI file
    You can configure the non-SAP RFC client to connect to the sender communication channel in the following ways:
    ■       By defining the parameters PROGID, gateway-host, and gateway-service within the saprfc.ini-file using RFC-SDK.
    ■       By using appropriate parameters in the function RfcOpenEx.
    If you use the saprfc.ini-file, the respective RFC destination has to be of type R.
    All the parameter values used within the saprfc.ini-file or with the function RfcOpenEx should match the entries maintained within the corresponding sender communication channel.
    Example for the saprfc.ini-file is as follows:
    DEST=RFCCLIENTEXT
    TYPE=R
    PROGID=P106646.HKExternalClient
    GWHOST=pwdf2153
    GWSERV=sapgw40
    Please check the following link, for the same  text on RFC Sender
    [Help.SAP|http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm]
    Using the same Sender RFC for non-SAP System, please share any ideas

  • Call a remote RFC from one sap system to to other sap system

    Hi experts,
    I'd like to know how to connect two sap systems via RFC. The two systems are in the same network and I'd like to know how to set up the SM59 in order to create the destination to the RFC.
    Any help in configuring the SM59 to stablish the communication?
    thanks a lot.

    <b>You can do that from t-code SM59 or SALE</b>
    This step is to create the Logical system for the remote system.
    A logical system allows SAP internal functions to interface with external systems, either an SAP system or a non-SAP system. We also need to have a logical system name for the SAP system,.
    SALE is the transaction.
    Expand the Sending and receiving Systems and then the Logical systems click on define logical system.
    You will receive the informational message, “The table is cross-client.” Click the green check icon to continue.
    Now click on the New Entries.
    The Screen appears like this here you will be giving the LS name and the description of that.
    After u click on the save button a window will be displayed like the bellow asking for the Request ID. Here we can create our own  or we can use the existing one.
    After that we see the message blow as DATA SAVED.
    Now the step is to Link the LS to the client.
    Click on the Assign Client to LS .
    The Screen as below will be appearing. 
    Double click on the client on which u r going to work and there specify the SAP LS(IDS47800) and you also need to specify the City and Std Currency and the client role as Test for the drop down box.
    Register the RFC server module with the
    SAP gateway
    The RFC (Remote Function Call) destination is a logical name used to define the
    Characteristics of a communication link to a remote system (in our case, LS for the remote system) on which a function needs to be executed. In ALE, the RFC specifies information required to log on to the remote SAP system to which an IDoc is being sent.
    To register the RFC Sever Module as the RFC destination:
    SAP transaction code: SM59 – Type /nsm59 on the SAP input window and press the
    Enter key.
    Expand the TCP/IP connections directory.
    Give some name to the RFC Destination (ALESERVER), Connection type as T. and fill the Description field.
    In technical settings give the program name as you desired.
    Click on save
    regards,
    srinivas
    <b>*reward for useful answers*</b>
    Message was edited by:
            XI_Novice
    Message was edited by:
            XI_Novice

  • RFC lookup to PI system or other ERP system.Which is better?

    Hello experts,
    I have a scenario[RFC>PI(RFCLOOKUP,SOAP LOOKUP)->SOAP] where I have to  fetch or update  the data in the table using RFC lookup in the mapping.
    To store or update  the data ,I have created a table in PI system and through RFC LOOKUP I am fetching the data in the message mapping.
                                                                                    Some PI developers prefers not to create this elements in the PI system  and suggested a way to create them in the ERP. 
    I wanted to crosscheck with you all  whether Lookup to PI system is better or to ERP system in terms of  performance, security and std maintenance.
    -Conceptually, they see PI as a communication tool, not the best option for storing data, which is an ERP function.                                                                               
    some prefer  ERP option  to Simplify the upgrade / system patching processes. As No Z-Objects makes the checking process much easier and there is no need to adapt those objects to the new release environment.     
    I appreciate your valuable suggestions.

    Hello Souvik,
    Thank you so much for your reply.
    But in my case the RFC lookup will be executed twice because the authorization data(token ans sign values which is stored in PI) is valid for 12 hours.
    if I find that these data is expired ,I have to do a soap lookup to get these details from a webservice and also have to update the same in the PI table using RFC lookup.All these activities are done in message mapping.
    so first RFC LOOKUP is used  to fetch the data and if expired,I get these details from a webservice and update(executing second time RFC LOOKUP) in PI table ,so that next time when request comes ,I will fetch these details from PI table instead from webservice to send message  to the receiver.
    same functionality is required for 4-5 scenarios,all acessing the same PI table.
    So Kindly advice considering these situation,will the performance,security,maintenance  be good when doing RFC lookup to other ERP instead of doing RFC lookup to PI system .
    Kind Regards,
    Kubra.

  • Getting problem when creating RFC Destination on XI system

    hi,
    I m trying to create RFC Destination on XI system using sm59 tcode. In technical setting tab at  Target Host field, i gave SAP  ECC server IP address. and in Logon Tab I gave Login parameters for SAP ECC server  (Client 400, User : 05 & Password for user 05). Current user and Unencrypted Password fields are unchecked. also Logon Scree is also unchecked in Security Option.
    Problem is, when i click on Remote logon tab, It shows me Logon screen with client 000, User : 04 (which is XI system's user name) and Password. so it doesn't take given login setting for ECC system and if i tried this thing more than 3 times, ECC server block my pwd.
    Please suggest me the required solution
    Thanks & Regards
    Ritesh

    Hi ritesh
    First check if the user exists in ths system. Check the password especially. Because the password space (Number of characters)in SM59 screen is more than password character in SU01 screen.Check the password.
    Secondly, Check if you have given the proper client in the destination box of SM59.
    Check for the unicode test also.
    If possible change the user type as service user.
    When everything is perfect am sure the rfc connection should be fine...

  • Port number while mentioned the RFC for reciever business system

    hi
      Could somebody tell me what is the port number to be mentioned while specifying the RFC for reciever busines system in the integration builder)configuration phase

    Hello..
    This might point to an unhanded exception. There should be a backend dump (ST22) available and that would help in more analysis. You might need a ABAPer to look into the dump. You may paste the dump here for more analysis.

  • RFC connection to source system ABPCLNT310 is damaged

    Hello,
    I'm importing a transport in BW Prod (condition type data for billing and orders), but receive this error message in STMS:
    The creation of the export DataSource failed
    Reading the Metadata of 0SD_O05 ...
    Creating DataSource 80SD_O05 ...
    RFC connection to source system ABPCLNT310 is damaged ==> no Metadata upload
    RFC connection to source system ABPCLNT310 is damaged ==> no Metadata upload
    Error when creating the export DataSource and dependent Objects
    Error when activating ODS-objekt 0SD_O05
    The creation of the export DataSource failed
    The import worked fine in BW QA system. Why do I get this error? It is possible to manually generate the export data source from the ODS object, but when I try to import again, it once again fails...
    Best regards,
    Fredrik

    hi Fredrik,
    check if helps oss note 597326, 886102, 184322
    RFC connection to source system Damaged
    Error when transporting ODS Object
    597326 - Activating ODS: Error when creating the export DataSource
    Symptom
    When you activate or transport ODS objects, the following errors appear in the log:
    "The creation of the export DataSource failed". Message number RSBM 035
    "Error &1 in function module &2". Message number RSBM 006
    "Error when creating the export DataSource and dependent Objects". Message number RSDODSO 169
    "Error when activating the ODS object &1". Message number RSDODSO 168
    Other terms
    RSBM 035, RSBM 006, RSDODSO 169, RSDODSO 168
    Reason and Prerequisites
    A characteristic involved is active but it is using new or inactive attributes.
    Characteristics involved are all characteristics used in the ODS object.
    Solution
    Check all characteristics involved as described in the following:
    Check the Compounding and Attributes tabs in the characteristics maintenance.
    All characteristics here must be active. This is displayed by a green icon.
    If this is not the case for a characteristic involved (a gray icon is displayed on one of the two tabs), activate the characteristic involved. This also activates the inactive dependent characteristics.
    After you have checked and repaired all the characteristics involved as described above, the loading/maintenance of master data should work again

  • SWCV still contains IDocs/RFCs from an SAP system

    Hi
    I have imported Idoc to a SWCV. Now am trying to create one more namespace under it. When I try to create another namespace, it automatically selects the check button Import of Idoc and RFC interfaces from SAP systems permitted. If I select not permitted and try to create namespace it gives me this message
    Unable to save object XYZ , 1.0 of ABC
    Indicator cannot be undone since the software component version still contains IDocs/RFCs from an SAP system 
    Delete the objects first.
    Is it possible for me to create another namespace under a SWCV, to which I have already imported Idoc, by selecting the option " Not permitted ". I want to create another namespace and I don't want to select that option as I have already imported Idoc

    Hi,
    You no need to touch that check box, you can still create the namespace under software component.
    Just double click lick on software component, goto edit mode and click on + symbol to insert namespace and save then activate.
    Note:- As you have already imported the RFC and IDoc under your software component(not namspace as you mentioned), you keep that check box import of RFC and IDocs permitted. Dont try to uncheck that.
    thanks,
    madhu

  • Creating RFC Destination For UNICODE system From NON-UNICODE system

    hi
    how can i create RFC Destination For UNICODE system( XI ) From NON-UNICODE (R/3) system.
    thanks and regards
    Mithlesh Kumar Jha

    Hi,
    Check these blogs , Hope u would be getting some idea
    <b>/people/thomas.jung3/blog/2004/06/24/bsp-150-a-developer146s-journal-part-v-xml-for-rfcs
    /people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices
    /people/sap.user72/blog/2004/06/19/how-i-started-with-sap-web-development</b>
    Regards,
    Sridhar Reddy

Maybe you are looking for