Windows Rfcexec rfc's

Hi All,
We have some RFC's running in our server manually, everyday we execute those rfc's at OS level. Can anyone please suggest us is there any procedure to run those rfc's without executing daily at OS level.
How to register Program Id in SM59 like registered server program.
RFC's we execute at Os level :
1. -aSMASH_RFC_SERVER_TESTING -g HOSTNAME -xSAPGW00
2. -aSMASH_RFC_SERVER_TEST_DSS -g HOSTNAME -xSAPGW00
3. -aSMASH_RFC_SERVER_TEST_OF -g HOSTNAME -xSAPGW00
4. -aSMASH_RFC_SERVER_TEST_ZALI -g HOSTNAME -xSAPGW00
Thanks in Advance....
Regards,
Krishna.M

SGD opens up a new RDP session for every application. Since the Windows Terminal server does not see that it has been started by the same user (which should be seen because SGD just acts like a tunnel for this information) it takes a new User TSCAL for every connection. It is generally known that Windows has problems with the User TSCAL.
When using Device TSCALs this problem does not exist since Windows sees that the request is comming from the same client.

Similar Messages

  • TCP IP connection From Solaris to Window?

    Hello Friends,
                           I have SCM installed on Solaris OS,and SCM optimizer installed on WIndow OS.I need to Connect SCM Solaris to SCM window, Thought RFC type TCP/ip Connection.
    For Example  In Solaris SCM for TCP/IP-Program name is d:\apo\opt\ctm\bin\ctmsvr.exe and Host is Window SCM host name.
    i need to know whether this Connection will work or If does not work Please Give the any Solution Friends.

    Thank you all. I found an example in the internet http://documentation.softwareag.com/Crossvision/sap231/pages/drfc2rpc.htm. The situation force me to overpass my laziness and to use RFC
    Yours sincerely,
    Nguyen Hai Long

  • 8.1 update failure

    Trying to upgrade from Windows 8 Pro 64 bit to 8.1.  Just prior to finishing and after updating settings the installer says "a few more things" and then says it has encountered a problem and the system must reboot.  After rebooting
    it reverts to Windows 8.  Suggestions?

    Error log
    2014-03-06 10:48:11, Error      [0x0808fe] MIG    Plugin {65cbf70b-1d78-4cac-8400-9acd65ced94a}: CreateProcess(s) failed. GLE = d
    2014-03-06 10:49:20, Error                 MIG    Failed to check the certificate of the catalog file C:\WINDOWS\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\1.CAT.[gle=0x800b010a]
    2014-03-06 10:49:20, Error                 MIG    Failed to check the certificate of the catalog file C:\WINDOWS\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\2.CAT.[gle=0x800b010a]
    2014-03-06 10:49:20, Error                 MIG    Failed to check the certificate of the catalog file C:\WINDOWS\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\3.CAT.[gle=0x800b010a]
    2014-03-06 10:49:39, Error      [0x0808fe] MIG    Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: CBrgUnattend::CollectBridgeSettings failed: 0x1, 0
    2014-03-06 10:50:48, Error                 MIG    Failed to check the certificate of the catalog file C:\WINDOWS\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\1.CAT.[gle=0x800b010a]
    2014-03-06 10:50:48, Error                 MIG    Failed to check the certificate of the catalog file C:\WINDOWS\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\2.CAT.[gle=0x800b010a]
    2014-03-06 10:50:48, Error                 MIG    Failed to check the certificate of the catalog file C:\WINDOWS\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\3.CAT.[gle=0x800b010a]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\20000940\ATT00001[gle=0x00000005]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\20000940\RE
    last night.eml[gle=0x00000005]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\20000a6a\bottom.letterhead[gle=0x00000005]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\20000a6a\top.letterhead[gle=0x00000005]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\20000a6e\2012
    ED Performance Evaluation Final Rev 1_030412.docx[gle=0x00000005]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\20000a6e\DOC072213-001.pdf[gle=0x00000005]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\200020ca\image001.jpg[gle=0x00000005]
    2014-03-06 11:14:38, Error                 MIG    Failed to enable compression for \\?\C:\Users\George\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\LocalState\LiveComm\ce3155cd89c351a2\120712-0049\Att\200020ca\image002.jpg[gle=0x00000005]
    2014-03-06 11:16:12, Error                 MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
    2014-03-06 11:16:12, Error                 MIG    Failed to enable compression for \\?\C:\WINDOWS\ctfile.rfc[gle=0x00000005]
    2014-03-06 11:16:37, Error                 MIG    Failed to enable compression for \\?\C:\WINDOWS\assembly\pubpol180.dat[gle=0x00000005]
    2014-03-06 11:16:59, Error                 MIG    Failed to enable compression for \\?\C:\WINDOWS\System32\Drivers\PcaSp60.sys[gle=0x00000005]
    2014-03-06 11:17:00, Error                 MIG    Failed to enable compression for \\?\C:\WINDOWS\System32\oobe\info\IBPBG.jpg[gle=0x00000005]
    2014-03-06 11:17:00, Error                 MIG    Failed to enable compression for \\?\C:\WINDOWS\System32\oobe\info\oemlogo.bmp[gle=0x00000005]
    2014-03-06 11:17:00, Error                 MIG    Failed to enable compression for \\?\C:\WINDOWS\System32\oobe\info\oemlogo2.bmp[gle=0x00000005]
    2014-03-06 11:17:06, Error                 MIG    Failed to enable compression for \\?\C:\WINDOWS\SysWOW64\drivers\PcaSp60.sys[gle=0x00000005]
    2014-03-06 11:17:08, Error      [0x0808fe] MIG    Plugin {C939EC0F-2F56-4CE8-AF56-2336596A5FA7}: failed to get pnpx db file size
    2014-03-06 11:17:08, Error      [0x0808fe] MIG    Plugin {C939EC0F-2F56-4CE8-AF56-2336596A5FA7}: Failed to migrate the pnpx db
    2014-03-06 11:17:09, Error      [0x0808fe] MIG    Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: query bridge presence key failed 0x139f, bridge present = 0
    2014-03-06 11:17:09, Error      [0x0808fe] MIG    Plugin {6CF7C0FC-91DD-4D47-9B6F-0769F8AE68D2}: [TpmScr] - check completion signature failed, skip this folder. file=C:\$WINDOWS.~BT\Sources\WorkDir\MachineSpecific\Working\srcworking\agentmgr\CCSIAgent\005A9238\completed.txt
    2014-03-06 11:17:11, Error      [0x08038d] MIG    Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll", CLSID={43CCF250-2A74-48c6-9620-FC312EC475D6},
    ThreadingModel=Apartment}. Error: 0x80070002
    2014-03-06 11:17:11, Error                        Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment.
    Will return 2[gle=0x000000cb]
    2014-03-06 11:17:18, Error      [0x080390] MIG    Failure while calling IPostApply->PostApply for Plugin={ServerPath="%windir%\system32\icfupgd.dll", CLSID={2f593f80-46a4-4da9-aad8-83a71d1f4333}, ThreadingModel=Apartment}. Error:
    0x800700B7
    2014-03-06 11:17:18, Error                        Error READ, 0x000000B7 while gathering/applying object: post-apply, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\WorkDir\MachineSpecific\Working\agentmgr\CCSIAgent,%windir%\system32\icfupgd.dll,{2f593f80-46a4-4da9-aad8-83a71d1f4333},Apartment.
    Will return 2[gle=0x000000cb]
    2014-03-06 11:19:31, Error                 MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
    2014-03-06 11:20:24, Error      [0x0808fe] MIG    Plugin {52776FBF-403C-49cc-b7cb-dd557f36096A}: MigrateRatingSystem failed: 0x80070002
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP\{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804)
    = 2
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration RegOpenKeyEx for plugin Source returned 0
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Skipping Migrating Inbox plugin - Event Forwarding Plugin
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Migrating plugin - Microsoft.PowerShell
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Plugin registration check returned 0
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Migrating plugin - Microsoft.PowerShell.Workflow
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Plugin registration check returned 0
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Migrating plugin - Microsoft.PowerShell32
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Plugin registration check returned 0
    2014-03-06 11:20:26, Error      [0x0808fe] MIG    Plugin {E550301A-B9D0-4ff9-B22A-BD4A1DD34C20}: Plugin Migration Skipping Migrating Inbox plugin - WMI Provider

  • Error in connecting SAP r\3 6.4 to BW 7.0

    hello.
    try to create source system to R/3 system.
    after window log in as administration appear window with RFC connection
    when I try to test authorization it show error. logon is failed. but this user in BW created and Password is correct
    what have I do to save that RFC connection correctly?
    thank you for any advise.
    BTW read B84: BW Connectivity and
    link: http://help.sap.com/saphelp_nw04/helpdata/en/80/1a61e5e07211d2acb80000e829fbfe/frameset.htm
    may be I understand something wrong..

    in source system run tran sm59.
    open my rfc destination.
    try to check authorization. and its show error: incorrect login or password (try again).
    user have all rights (sap_all and S_BI-WHM_RFC)
    login and password correct.
    what's wrong with rfc?
    profile parameter auth/rfc_authority_check is set to 1.
    is any solution to connect sap r/3 6.4 and sp bw 7.0?

  • Regading getting data to and forth between 2 programs through SUBMIT

    Hi All,
    I have a issue regarding fetching internal table data from one program to another.
    Actually I have <b>Main Program</b> from that through SUBMIT statement i am calling another program and executing it for every 100 records - Actually this program is having BAPI running in it, By result i will get an internal table data. Now i want to get that internal table data back into my MAIN Program so that i can use it for next process.
    <b>EXPORT & IMPORT statements are working from MAIN Program to Other Program.</b>
    <b>EXPORT & IMPORT statements are not working from Other Program[SUBMIT'ed Program] to MAIN Program.</b>
    So can anybody tell me how can i get that data in other program into MAIN Program[Back].
    Thanks in advance.
    Thanks & Regards,
    Rayeez.

    When you submit the program is then running in parallel with the program which submitted it.  There is no mechism that you are using to stop the calling program and wait for the submitted program to finish and bring back some data.   Most likly program 1 ends before program 2 is finished updating the material master. You can do this kind of thing with Function modules.   You would put your call to the submitted program inside of a function module,  then call that function module saying STARTING IN NEW TASK,  then you can wait for it to be done and get the results using the RECIEVING statement.
    Here is the F1 Help.
    +
    CALL FUNCTION
    Variant 2
    CALL FUNCTION func ...STARTING NEW TASK task name.
    Additions:
    1. ... DESTINATION dest
    2. ... DESTINATION IN GROUP group name
    3. ... DESTINATION IN GROUP DEFAULT
    4. ... PERFORMING form ON END OF TASK
    5. ... EXPORTING  p1 = f1    ... pn = fn
    6. ... TABLES     p1 = itab1 ... pn = itabn
    7. ... EXCEPTIONS syst_except = rc MESSAGE mess
    Effect
    Starts the function module func asynchronously ina new session. In contrast to normal function module calls, the callingprogram resumes processing as soon as the function module is started inthe target system. It does not wait until the function module hasfinished. Through CALL SCREEN,the called function module can, for example, display a screen and thusinteract with the user.
    Notes
    This variant applies only from R/3 Release 3.0, so boththe client system and the server system must have Release 3.0 orhigher.
    With this variant, the called function module must also be flagged inthe Function Builder as externally callable, even if it is executedlocally (without the addition DESTINATION).
    There can be no function call to the destination 'BACK' in thecalled function module (for more information about the destination 'BACK', see CALLFUNCTION func DESTINATION dest).
    This variant does not support the execution of externalprograms accessible via the destination of the TCP/IP type asasynchronous calls (see the Transaction Tools ¨Administration, Administration ¨ Network ¨ RFC destinations formaintaining destinations).
    You cannot display screens (screens or lists asamodal windows in RFC communication using SAP Router.
    From Release 4.0, you can check the load of each RFC destination moreclosely (in the RFC destination maintenance for an R/3 connection, choose Destination -> ARFC options). This checks whetherthe target host has sufficient resources before the function module isexecuted. If the target host is overloaded, the system delays executingthe function module. The algorithm for calculating the load on thetarget host is the same one used in an asynchronous RFC call using the DESTINATION IN GROUP addition. Note that this option can only beused with target hosts running Release 3.1H or higher. Note also thatit is the default setting.
    In principle, parallelization makes sense whenever applicationservers have the necessary resources. In this case, the applicationservers must be configured with at least 3 dialog work processes.
    A program that is run in the background and uses RFC parallelizationrequires at least 1 dialog work process per application server becausedialog processes use parallel execution.
    If the instance profile parameter 'auth/rfc_authority_check'is set (to 1), the system automatically performs an RFC authorizationcheck. The authorization check refers to the relevant function groupfor the function module to be called. If no authorization is found, aruntime error occurs. You can check the authorization in advance withthe function module AUTHORITY_CHECK_RFC. If the communication takes place in the same system with thesame user context (same client and user ID), there is no authorizationcheck. For further information, refer to the RFCAuthorization Concept.
    When you are using asynchronous RFC to implement parallel windows,all these windows are closed if the caller session is the only sessionand terminates.
    ABAP_ADDITION_1&
    ... DESTINATION dest
    Effect
    Executes the function module externally as a RemoteFunction Call (RFC); dest can be a literal or a variable.The R/3 System where the function module is executed depends on thespecified destination. Externally callable function modules must beflagged as such in the Function Builder (of the target system).
    Note
    If the destination is not explicitly specified, the systemuses the default destination 'NONE'.
    Note
    If, during a RemoteFunction Call, an error occurs in the target system, detailsof the error message are passed bac to the calling system in thefollowing system fields: SY-MSGNO, SY-MSGID, SY-MSGTY, SY-MSGV1,SY-MSGV2, SY-MSGV3, and SY-MSGV4. These fields areinitialized before every RFC. If a short dump or a type X messageoccurs, the short text of the dump is transferred to the caller, andthe contents of SY-MSGID, SY-MSGTY, SY-MSGNO, and SY-MSGV1 assigned by the system.
    In RFC-enabled function modules, no ABAP statements are allowed thatwould end the RFC connection (for example, LEAVE, SUBMIT or the ANDRETURN addition).
    Note
    Note that a database commit occurs at eachRemote Function Call (RFC). Consequently, you may not use RemoteFunction Calls between pairs of statements that open and close adatabase cursor (such as SELECT ... ENDSELECT).
    Addition 2
    ... DESTINATION IN GROUP group name
    Addition 3
    ... DESTINATION IN GROUP DEFAULT
    Effect
    You use this addition to perform parallel execution offunction modules (asynchronous calls) on a predefined group of R/3System application servers.
    You use addition 2 (DESTINATION IN GROUP group name) toperform parallel execution of function modules on a predefined group ofapplication servers. To maintain the RFC groups, choose Tools ¨ Administration ¨ Administration ¨ Network ¨ RFCdestinations ¨ RFC ¨ RFC groups. The application programmer isresponsible for the availability of RFC groups in the productionsystem.
    You use addition 3 (DESTINATION IN GROUP DEFAULT) to performparallel execution of function modules (asynchronous calls) on all currently available R/3 System application servers. However,instead of this variant, you are recommended to use an RFC group withappropriate resources for parallel processing of asynchronous calls (atleast for performance reasons). Please note that the additionDESTINATION IN GROUP ' ' has the same effect as the additionDESTINATION IN GROUP DEFAULT.
    When you first call a function module with these additions, thesystem initializes the specified RFC group (provided no explicitinitialization has already been performed).
    To obtain current information about resources (that is, the number ofresources available to process function modules), you can alsoinitialize the RFC group explicitly in the program via the functionmodule SPBT_INITIALIZE. You must perform this actionbefore the first function module call.
    In both cases, the system first determines the number of currentlyavailable resources (work processes) on the available applicationservers (either a group of servers or all servers). By checking thecurrent system load of each application server, the system determineshow many work processes are available to execute asynchronous calls.
    After determining the available resources, the asynchronous call isexecuted at one of the destinations. If no resources are available atthat particular time, the system executes the exception routine RESOURCE_FAILURE (see the addition EXCEPTIONS). In thecase of an asynchronous function module call, this exception must be handled by the application program (see example).
    Parallel processing cannot take place if any of the resourcethresholds are exceeded.
    Notes
    In order to be taken into consideration for RFC parallelprocessing, an application server must have at least 3 freedialog processes.
    The system triggers the exception RESOURCE_FAILURE only forasynchronous RFCs with the additions DESTINATION IN GROUP groupname and DESTINATION IN GROUP DEFAULT.
    At present, only one RFC group per program environment issupported for parallel execution of asynchronous calls. Using both theadditions DESTINATION IN GROUP group name and DESTINATION INGROUP DEFAULT in a program is thus not allowed.
    To find out which destination was automatically selected, call thefunction module SPBT_GET_PP_DESTINATION immediately after thefunction module call with the two additions. This returns the selectedRFC destination.
    If you want to delete an application server from the list of theconfigured RFC group at runtime (for example, when the applicationserver is not accessible for technical reasons), use the functionmodule SPBT_DO_NOT_USE_SERVER.
    Addition 4
    ... PERFORMING form ON END OF TASK
    While the parameters for receiving results (i.e. IMPORTING andTABLES parameters) are specified directly as additions in thecase of "conventional" function modules (see variant 2), these arelogged in the FORM routine form when making anasynchronous call (see RECEIVE).
    Notes
    If a function module returns no result, and you are notinterested in error messages that arise when executing the functionmodule, this addition (... PERFORMING form ON END OF TASK) canbe omitted.
    If you want to handle the error messages that arise when executingthe asynchronous function module call, you must use thisaddition. Also, when receiving the results in the FORM routine(see RECEIVE), you must reactaccordingly to the system exceptions SYSTEM_FAILURE andCOMMUNICATION_FAILURE.
    With asynchronous RFC, the task name uniquely identifies theasynchronous connection and thus the context called.
    If several asynchronous function modules are executed consecutivelyto the same destination, you must assign a different task name to each.
    A calling program that starts an asynchronous RFC with PERFORMINGform ON END OF TASK cannot switch roll areas or change to aninternal session. This is because the asynchronous function module callreply cannot be passed on to the relevant program. You can perform aroll area switch with SUBMIT or CALL TRANSACTION.
    If a calling program makes asynchronous calls, finishes, and thenexpects responses, these responses cannot be delivered.
    To wait for the reply to a started asynchronous function module, usethe WAIT command with the additionPERFORMING form ON END OF TASK. Here, WAIT must be in thesame program context (session).
    Note that the execution of the asynchronous calls involves a changeof roll area. This means that the FORM routines for receivingthe external calls can be processed while you are making furtherexternal calls. This means that the developer must ensure thatthe FORM routines can be executed at any time. You cannotmake any assumptions about the processing sequence.
    Addition 5
    ... EXPORTING p1 = f1 ... pn = fn
    Effect
    EXPORTING passes values of fields and fieldstrings from the calling program to the function module. In thefunction module, the formal parameters are defined as importparameters.
    Addition 6
    ... TABLES p1 = itab1 ... pn = itabn
    Effect
    TABLES passes the contents of internal tables.
    Addition 7
    ... EXCEPTIONS syst_except = rc MESSAGE mess
    Effect
    While any exceptions arising in the called functionmodule are handled by the second addition (in the FORM routine),this addition can handle two special system exceptions, as withfunction module calls with the addition DESTINATION:
    SYSTEM_FAILURE
    is triggered, if a system crash occurs on the receiving side.
    COMMUNICATION_FAILURE
    is triggered if there is a connection or communication problem.
    In both cases, you can get a description of the error with theoptional addition
    ... MESSAGE msg
    Note
    In principle, you should always react to these twosystem exceptions, whether you are making an asynchronous functionmodule call or receiving results.
    Examples
    Asynchronous call to a transaction and display in a separate session.
    DATA: MSG_TEXT(80) TYPE C. "Message text
    Asynchronous call to Transaction SM59 -->
    Create a new session
    CALL FUNCTION 'ABAP4_CALL_TRANSACTION' STARTING NEW TASK 'TEST'
      DESTINATION 'NONE'
      EXPORTING
          TCODE = 'SM59'
      EXCEPTIONS
        COMMUNICATION_FAILURE = 1 MESSAGE MSG_TEXT
        SYSTEM_FAILURE        = 2 MESSAGE MSG_TEXT.
      IF SY-SUBRC NE 0.
        WRITE: MSG_TEXT.
      ELSE.
        WRITE: 'O.K.'.
      ENDIF.
    Using RFC groups to parallelize function module calls (RFC parallelprocessing)
    TYPES: BEGIN OF TASKLIST_TYPE,
           TASKNAME(4) TYPE C, "Task administration
           RFCDEST LIKE RFCSI-RFCDEST
           END OF TASKLIST_TYPE.
    DATA: INFO LIKE RFCSI, C,  "Message text
          JOBS TYPE I VALUE 10,  "Number of parallel jobs
          SND_JOBS TYPE I VALUE 1,  "Sent jobs
          RCV_JOBS TYPE I VALUE 1,  "Received replies
          EXCP_FLAG(1) TYPE C,  "Number of RESOURCE_FAILUREs
          TASKNAME(4) TYPE N VALUE '0001',  "Task name administration
          TASKLIST TYPE TABLE OF TASKLIST_TYPE,
          WA_TASKLIST TYPE TASKLIST_TYPE.
    DO.
      CALL FUNCTION 'RFC_SYSTEM_INFO'
           STARTING NEW TASK TASKNAME DESTINATION IN GROUP DEFAULT
           PERFORMING RETURN_INFO ON END OF TASK
           EXCEPTIONS
             COMMUNICATION_FAILURE = 1
             SYSTEM_FAILURE        = 2
             RESOURCE_FAILURE      = 3.
      CASE SY-SUBRC.
        WHEN 0.
    Administration of asynchronous tasks
          WA_TASKLIST-TASKNAME = TASKNAME.
          CLEAR WA_TASKLIST-RFCDEST.
          APPEND WA_TASKLIST TO TASKLIST.
          WRITE: /  'Started task: ', WA_TASKLIST-TASKNAME COLOR 2.
          TASKNAME = TASKNAME + 1.
          SND_JOBS = SND_JOBS + 1.
          JOBS     = JOBS - 1.  "Number of existing jobs
          IF JOBS = 0.
            EXIT.  "Job processing finished
          ENDIF.
        WHEN 1 OR 2.
    Handling of communication and system failure
        WHEN 3.  "No resources available at present
    Receive reply to asynchronous RFC calls
          IF EXCP_FLAG = SPACE.
             EXCP_FLAG = 'X'.
    First attempt for RESOURCE_FAILURE handling
             WAIT UNTIL RCV_JOBS >= SND_JOBS UP TO '0.01' SECONDS.
          ELSE.
    Second attempt for RESOURCE_FAILURE handling
             WAIT UNTIL RCV_JOBS >= SND_JOBS UP TO '0.1' SECONDS.
          ENDIF.
          IF SY-SUBRC = 0.
            CLEAR EXCP_FLAG.  "Reset flag
          ELSE.  "No replies
            "Endless loop handling
          ENDIF.
        ENDCASE.
    ENDDO.
    Receive remaining asynchronous replies
    WAIT UNTIL RCV_JOBS >= SND_JOBS.
    LOOP AT TASKLIST INTO WA_TASKLIST.
      WRITE:/   'Received task:', WA_TASKLIST-TASKNAME COLOR 1,
            30  'Destination: ', WA_TASKLIST-RFCDEST COLOR 1.
    ENDLOOP
    FORM RETURN_INFO USING TASKNAME.
      RECEIVE RESULTS FROM FUNCTION 'RFC_SYSTEM_INFO'
        IMPORTING RFCSI_EXPORT = INFO
        EXCEPTIONS
          COMMUNICATION_FAILURE = 1
          SYSTEM_FAILURE        = 2.
      RCV_JOBS = RCV_JOBS + 1.  "Receiving data
        IF SY-SUBRC NE 0.
    Handling of communication and system failure
        ELSE.
          READ TABLE TASKLIST WITH KEY TASKNAME = TASKNAME
                              INTO WA_TASKLIST
          IF SY-SUBRC = 0.  "Register data
            WA_TASKLIST-RFCDEST = INFO_RFCDEST.
            MODIFY TASKLIST INDEX SY-TABIX FROM WA_TASKLIST.
          ENDIF.
        ENDIF.
    ENDFORM
    Note
    If you encounter problems, refer toTypical RFC problems and theirsolutions.
    Note
    Runtime errors:
    Note
    Runtime errors:
    CALL_FUNCTION_NO_RECEIVER:
    Data received for an unknown CPI-C connection.
    CALL_FUNCTION_DEST_TYPE:
    Destination type not allowed.
    CALL_FUNCTION_NO_DEST:
    Specified destination does not exist.
    CALL_FUNCTION_NO_LB_DEST:
    Specified destination (in load distribution mode) does not exist.
    CALL_FUNCTION_TABINFO:
    Data error (info internal table) in a Remote Function Call.
    CALL_BACK_ENTRY_NOT_FOUND:
    The called function module is not released for use in RFC.
    CALL_FUNCTION_FIELD_NOT_FOUND:
    The function parameter that you passed is not recognized on therecipient side.
    RFC_NO_AUTHORITY:
    The user does not have RFC authorization.
    CALL_FUNCTION_SINGLE_LOGIN_REJ:
    No authorization to log on as a trusted system. The error codeshave the following meanings:
    0) Valid security key but wrong logon data 1) Calling system is not a trusted system, or security key is invalid 2) User either does not have RFC authorization (authorization object S_RFCACL), or logged on as one of the protected users 'DDIC' or 'SAP*' 3) Timestamp of the logon data is invalid
    CALL_FUNCTION_DESTINATION_NO_T:
    Missing communication type (I for internal connection, 3 for R/3) in anasynchronous RFC
    CALL_FUNCTION_NOT_REMOTE:
    The function module called is not flagged as "RFC supported"
    CALL_FUNCTION_REMOTE_ERROR:
    An error occurred during the Remote Function Call. This has been loggedin the target system.
    CALL_FUNCTION_SIGNON_INCOMPL:
    The logon data for the user is incomplete.
    CALL_FUNCTION_SIGNON_INTRUDER:
    You cannot log onto a target system using an internal call.
    CALL_FUNCTION_SIGNON_INVALID:
    External RFC without a valid user name.
    CALL_FUNCTION_SIGNON_REJECTED:
    Attempt to log onto a target system without a valid user name. Theerror code can have the following meanings:
    1) Wrong password or invalid user ID
    2) User locked
    3) Too many logon attempts
    4) Error in authorization buffer (internal error)
    5) No external user check
    6) Invalid user type
    7) Validity period of user has expired
    CALL_FUNCTION_SYSCALL_ONLY:
    RFC without a valid user name only allowed when calling system functionmodules. For the meaning of the error codes, refer toCALL_FUNCTION_SINGLE_LOGIN_REJ.
    CALL_FUNCTION_TABLE_NO_MEMORY:
    No memory available for a table to be imported
    CALL_FUNCTION_TASK_IN_USE:
    Asynchronous RFC only: Task name already in use.
    CALL_FUNCTION_TASK_YET_OPEN:
    Asynchronous RFC only: The specified task is already open.
    CALL_FUNCTION_SNC_ERROR:
    Error reading the SNC information for the destination.
    CALL_RPERF_SLOGIN_READ_ERROR:
    No valid trusted system entry for the calling system.
    CALL_RPERF_SLOGIN_AUTH_ERROR:
    No trusted authorization for the RFC caller and trusted system.
    +
    Regards,
    Rich Heilman

  • Doubt in call function

    Hi,
    Call Function 'FM' starting new task task-name
    Exporting
    What does this statement does.

    Hi
    chk this out
    CALL FUNCTION STARTING NEW TASK
    Variant 2
    CALL FUNCTION func ...STARTING NEW TASK task name.
    Extras:
    1. ... DESTINATION dest
    2. ... DESTINATION IN GROUP group name
    3. ... DESTINATION IN GROUP DEFAULT
    4. ... PERFORMING form ON END OF TASK
    5. ... EXPORTING  p1 = f1    ... pn = fn
    6. ... TABLES     p1 = itab1 ... pn = itabn
    7. ... EXCEPTIONS syst_except = rc MESSAGE mess
    Effect
    Starts the function module func asynchronously in a new session. In contrast to normal function module calls, the calling program resumes processing as soon as the function module is started in the target system. It does not wait until the function module has finished. Using CALL SCREEN, the called function module can, for example, display a screen and thus interact with the user. Note that taskname must be a valid string of at least 2 characters, preferably fewer than 8 characters. You cannot use either ' ' or SPACE as tasknames.
    Notes
    Note that under certain circumstances, an RFC may cause a database commit. For this reason, do not insert an RFC between two OpenSQL statements that open and close a database cursor (such as SELECT...ENDSELECT).
    This variant applies only from R/3 Release 3.0, so both the client system and the server system must have Release 3.0 at least.
    With this variant, the called function module must also be flagged in the Function Builder as externally callable, even if it is executed locally (without the addition Destination).
    There can be no function call to the destination 'BACK' in the called function module (for more information about the destination 'BACK', see CALL FUNCTION func DESTINATION dest).
    This variant does not allow you to execute external programs that you access from a TCP/IP-type detination asynchronously. (See the Transaction Tools -> Administration, Administration -> Network -> RFC destinations for maintaining destinations).
    Neither does this variant allow you to display images such as lists or screens in a separate window during RFC communication using a SAProuter.
    From Release 4.0 onwards, you can carry out a new, stricter system load check on RFC destinations. (In RFC destination maintenance of an R/3 connection, choose Destination -> ARFC-Optionen). Before the function module is executed, the system checks that the destination has sufficient resources available. If not, the system delays execution of the function module for a given period of time. The algorithm used to determine the system load on the target machine is the same as that used for an asynchronous RFC with the DESTINATION IN GROUP addition. Note that this option is only available for target systems from Release 3.1H onwards. This procedure is active as default.
    In principle, parallel processing makes sense whenever application servers have the necessary resources. In this case, the application servers must be configured with at least 3 dialog work processes.
    A program that is run in the background and uses RFC parallel processing requires at least 1 dialog work process per application server (because parallel processing takes place in a dialog work process).
    If the instance profile parameter 'auth/rfc_authority_check' is set to 1, the system automatically performs an RFC authorization check. The authorization check refers to the relevant function group for the function module to be called. If no authorization is found, a runtime error occurs. You can check the authorization in advance with the function module AUTHORITY_CHECK_RFC. If the RFC communication takes places in one system and in the same user context (that is, the same client and User ID) the system does not perform an RFC authority check. For more information, see: RFC Authorization Concept.
    When you are using asynchronous RFC to implement parallel windows, all these windows are closed if the caller session is the only session and terminates.
    Note that asynchronous tasks that have been started are not necessarily closed when the calling program ends.
    See also RFC Logons to the Target System (Remote Logon).
    Addition 1
    ... DESTINATION dest
    Effect
    Executes the function module externally as a Remote Function Call (RFC); dest can be a literal or a variable. The R/3 System where the function module is executed depends on the specified destination. Externally callable function modules must be flagged as such in the Function Builder (of the target system).
    Note
    If the destination is not explicitly specified, the system uses the default destination 'NONE'.
    Note
    If, during a Remote Function Call, an error occurs in the target system, details of the error message are passed back to the calling system in the following system fields: SY-MSGNO, SY-MSGID, SY-MSGTY, SY-MSGV1, SY-MSGV2, SY-MSGV3, and SY-MSGV4. These fields are initialized before every RFC. If a short dump or a type X message occurs, the short text of the dump is transferred to the caller, and the contents of SY-MSGID, SY-MSGTY, SY-MSGNO, and SY-MSGV1 assigned by the system.
    In RFC-enabled function modules, no ABAP statements are allowed that would end the RFC connection (for example, either LEAVE or SUBMIT without the AND RETURN addition).
    Note
    Note that a database commit occurs at each Remote Function Call (RFC). Consequently, you cannot use Remote Function Calls between pairs of statements that open and close a database cursor (such as SELECT ... ENDSELECT).
    Addition 2
    ... DESTINATION IN GROUP group name
    Addition 3
    ... DESTINATION IN GROUP DEFAULT
    Effect
    You use this addition to perform parallel execution of function modules (asynchronous calls) on a predefined group of R/3 System application servers.
    You use addition 2 (DESTINATION IN GROUP group name) to perform parallel execution of function modules on a predefined group of application servers. To maintain the RFC groups, choose Tools -> Administration -> Administration ->Network -> RFC destinations -> RFC -> RFC groups. The application programmer is responsible for the availability of RFC groups in the production system. In this case the group name variable must be of the type RZLLITAB-CLASSNAME
    You use addition 3 (DESTINATION IN GROUP DEFAULT) to perform parallel execution of function modules (asynchronous calls) on all currently available R/3 System application servers. However, instead of this variant, you are recommended to use an RFC group with appropriate resources for parallel processing of asynchronous calls (at least for performance reasons). Please note that the addition DESTINATION IN GROUP ' ' has the same effect as the addition DESTINATION IN GROUP DEFAULT.
    When you first call a function module with these additions, the system initializes the specified RFC group (unless the group has already been explicitly identified).
    To obtain current information about resources (that is, the resources available to process function modules), you can also initialize the RFC group explicitly in the program using the function module SPBT_INITIALIZE. You must perform this action before the first function module call.
    In both cases, the system first ascertains the currently available resources (work processes) on the available application servers (either a group of servers or all servers). By checking the current system load of each application server, the system determines how many work processes are available to execute asynchronous calls.
    After ascertaining the available resources, the asynchronous call is executed to one of the
    destinations. If no resources are available at that particular time, the system executes the
    exception routine RESOURCE_FAILURE (see the addition EXCEPTIONS). In the case of
    an asynchronous function module call, this exception must be handled by the application
    program (see example).
    No resources are made available by the system if resource availability limits are exceeded:
    Notes
    To be taken into consideration for RFC parallel processing, an application server must have at least 3 free dialog processes.
    The system triggers the exception RESOURCE_FAILURE only for asynchronous RFCs with the additions DESTINATION IN GROUP group name and DESTINATION IN GROUP DEFAULT.
    At present, only one RFC group per program environment is supported for parallel execution of asynchronous calls. Using both the additions DESTINATION IN GROUP group name and DESTINATION IN GROUP DEFAULT in a program is thus not allowed.
    To find out which destination was automatically selected, call the function module SPBT_GET_PP_DESTINATION immediately after the function module call with the two additions. This returns the selected RFC destination.
    If you want to delete an application server from the list of the configured RFC group at runtime (for example, when the application server is not accessible for technical reasons), use the function module SPBT_DO_NOT_USE_SERVER.
    Addition 4
    ... PERFORMING form ON END OF TASK
    While the parameters for receiving results (that is IMPORTING and TABLES parameters) are specified directly as additions in the case of "conventional" function modules (see variant 2), these are logged in the FORM routine form when making an asynchronous call (see RECEIVE).
    Notes
    If a function module returns no result, and you are not interested in error messages that arise when executing the function module, this addition (... PERFORMING form ON END OF TASK) can be omitted.
    If you want to handle the error messages that arise when executing the asynchronous function module call, you must use this addition. Also, when receiving the results in the FORM routine (see RECEIVE), you must react accordingly to the system exceptions SYSTEM_FAILURE and COMMUNICATION_FAILURE.
    With asynchronous RFC, the task name uniquely identifies the asynchronous connection and thus the context called.
    If several asynchronous function modules are executed consecutively to the same destination, you must assign a different task name to each.
    A calling program that starts an asynchronous RFC with the PERFORMING form ON END OF TASK addition cannot switch roll areas or change to an internal mode. This is because the asynchronous function module call reply cannot be passed on to the relevant program. You can perform a roll area switch with SUBMIT or CALL TRANSACTION.
    If a calling program makes asynchronous calls, finishes, and then expects responses, it cannot receive these responses.
    To wait for the reply to a started asynchronous function module, use the WAIT command with the addition PERFORMING form ON END OF TASK. Here, WAIT must be in the same program context (mode).
    Note that executing asynchronous calls is subject to a roll area change.That is, subroutines performed to receive asynchronous calls can take place while other asynchronous calls are being made. Thus as a developer you must ensure that subroutines can be executed at any time. You must not make assumptions about the implicit processing sequence.
    Addition 5
    ... EXPORTING p1 = f1 ... pn = fn
    Effect
    Passes values of fields and field strings from the calling program to the function module. In the function module, the formal parameters are defined as import parameters.
    Addition 6
    ... TABLES p1 = itab1 ... pn = itabn
    Effect
    Passes references to internal tables.
    Addition 7
    ... EXCEPTIONS syst_except = rc MESSAGE mess
    Effect
    While any exceptions arising in the called function module are handled by the second
    addition (see the FORM subroutine RETURN_INFO), this addition can handle two special
    system exceptions, (as with function module calls with the DESTINATION addition):
    SYSTEM_FAILURE
    is triggered, if a system crash occurs on the receiving side.
    COMMUNICATION_FAILURE
    is triggered if there is a connection or communication problem.
    In both cases, you can get a description of the error with the optional ... MESSAGE messaddition
    Note
    In principle, you should always react to these two system exceptions, whether you are making an asynchronous function module call or receiving results.
    Examples
    Calling a transaction in a seperate session.
    DATA: MSG_TEXT(80) TYPE C. "Message text
    Asynchronous call to Transaction SM59 -->
    Create a new session
    CALL FUNCTION 'ABAP4_CALL_TRANSACTION' STARTING NEW TASK 'TEST'
      DESTINATION 'NONE'
      EXPORTING
          TCODE = 'SM59'
      EXCEPTIONS
        COMMUNICATION_FAILURE = 1 MESSAGE MSG_TEXT
        SYSTEM_FAILURE        = 2 MESSAGE MSG_TEXT.
      IF SY-SUBRC NE 0.
        WRITE: MSG_TEXT.
      ELSE.
        WRITE: 'O.K.'.
      ENDIF.
    Using RFC groups to parallelize function module calls(RFC parallel processing)
    TYPES: BEGIN OF TASKLIST_TYPE,
             TASKNAME(4) TYPE C, "Verwaltung der Tasks
             RFCDEST     LIKE RFCSI-RFCDEST,
          END OF TASKLIST_TYPE.
    DATA: INFO LIKE RFCSI, C,  "Message text
          JOBS TYPE I VALUE 10,  "Number of parallel jobs
          SND_JOBS TYPE I VALUE 1,  "Sent jobs
          RCV_JOBS TYPE I VALUE 1,  "Received replies
          EXCP_FLAG(1) TYPE C,  "Number of RESOURCE_FAILUREs
          TASKNAME(4) TYPE N VALUE '0001',  "Task name administration
          TASKLIST TYPE TABLE OF TASKLIST_TYPE,
          WA_TASKLIST TYPE TASKLIST_TYPE.
    DO.
      CALL FUNCTION 'RFC_SYSTEM_INFO'
           STARTING NEW TASK TASKNAME DESTINATION IN GROUP DEFAULT
           PERFORMING RETURN_INFO ON END OF TASK
           EXCEPTIONS
             COMMUNICATION_FAILURE = 1
             SYSTEM_FAILURE        = 2
             RESOURCE_FAILURE      = 3.
      CASE SY-SUBRC.
        WHEN 0.
    Administration of asynchronous tasks
            WA_TASKLIST-TASKNAME = TASKNAME.
            CLEAR WA_TASKLIST-RFCDEST.
            APPEND WA_TASKLIST TO TASKLIST.
            WRITE: /  'Started Task: ', WA_TASKLIST-TASKNAME COLOR 2.
          TASKNAME = TASKNAME + 1.
          SND_JOBS = SND_JOBS + 1.
          JOBS     = JOBS - 1.  "Number of existing jobs
          IF JOBS = 0.
            EXIT.  "Job processing finished
          ENDIF.
        WHEN 1 OR 2.
    Handling of communication and system failure
        WHEN 3.  "No resources available at present
    Receive reply to asynchronous RFC calls
          IF EXCP_FLAG = SPACE.
             EXCP_FLAG = 'X'.
    First attempt for RESOURCE_FAILURE handling
             WAIT UNTIL RCV_JOBS >= SND_JOBS UP TO '0.01' SECONDS.
          ELSE.
    Second attempt for RESOURCE_FAILURE handling
             WAIT UNTIL RCV_JOBS >= SND_JOBS UP TO '0.1' SECONDS.
          ENDIF.
          IF SY-SUBRC = 0.
            CLEAR EXCP_FLAG.  "Reset flag
          ELSE.  "No replies
            "Endless loop handling
          ENDIF.
        ENDCASE.
    ENDDO.
    Receive remaining asynchronous replies
    WAIT UNTIL RCV_JOBS >= SND_JOBS.
    LOOP AT TASKLIST INTO WA_TASKLIST.
        WRITE:/   'Received Task:', WA_TASKLIST-TASKNAME COLOR 1,
              30  'Destination: ', WA_TASKLIST-RFCDEST COLOR 1.
    ENDLOOP.
    FORM RETURN_INFO USING TASKNAME.
      RECEIVE RESULTS FROM FUNCTION 'RFC_SYSTEM_INFO'
        IMPORTING RFCSI_EXPORT = INFO
        EXCEPTIONS
          COMMUNICATION_FAILURE = 1
          SYSTEM_FAILURE        = 2.
      RCV_JOBS = RCV_JOBS + 1.  "Receiving data
        IF SY-SUBRC NE 0.
    Handling communication and system failure
       ELSE.
         READ TABLE TASKLIST WITH KEY TASKNAME = TASKNAME
                    INTO WA_TASKLIST.
         IF SY-SUBRC = 0. "Daten registrieren
           WA_TASKLIST-RFCDEST = INFO-RFCDEST.
           MODIFY TASKLIST INDEX SY-TABIX FROM WA_TASKLIST.
         ENDIF.
       ENDIF.
    ENDFORM.
    plz reward if useful

  • Trouble in creating source system

    Hi,Alles.
    I want to create a source system(R/3) for BW, I create a new background user'SYS100' in client 100(R/3), then I create source system in BW,after inputed all parameters and continue to logon R/3 system, a window jumped out'User already exists in source system,Only continue if profile and password are correct.' I selected 'Continue'.Then window displayed 'RFC destination already exists in source system,Do you want to use this destination, check, or cancel source system connection?',I selected 'check',it displayed that 'the system already exist' is the BW self system(can't be changed and deleted).What the reason? Give me some hints,Thanks.

    http://www.sapgenie.com/sapgenie/docs/MySAP%20BW%20Cookbook%20Vol%202.pdf
    Try this link.
    Cheers!!!!!!!!!
    pls do assign points, if you feel answer to your questions are valuable.
    Message was edited by: BI Project

  • What is the default file name of BAPI trace?

    hi expects,
    what is the default file name of BAPI trace?

    What BAPI trace?.. Did you mean RFC trace?
    In Windows the RFC trace filename starts with "RFC" followed by the process ID of the client program. The trace must be activated first, naturally.

  • RFCEXEC running as a windows service

    Hello,
       Is it possible to run rfcexec.exe from the RFC SDK as a Windows service (other than being launched by srvany.exe, for example) ? Thanks in advance for your input.
    Peter DOUGHERTY

    If you have Visual studio installed, create a windows service project with all the parameters, see the following example:
    Shell (rfcexec.exe -a  XXXXXX  -g xxxxx -x sapgw01)
    Compile it as exe file.
    use SAP provided ntscmgr program to register this as a windows service.
    This is working great in my environment.
    Thanks,

  • Call RFC from DELPHI Windows Services Program

    Hi all,
    Are there any way to call RFC from DELPHI Windows Services Program?
    Best regards.
    Munur EBCIOGLU

    Hi again Bhagat,
    1. Yes, it's included on 7.4 ABAP Stack (SAP NetWeaver 7.4 SP8 - Optimized for SAP HANA, Cloud and Mobile - Service Release 2 available now!). In a recent customer, SAP licences GW by user but there are other license model like session licensing: https://store.sap.com/sap/cp/ui/resources/store/html/SolutionDetails.html?pid=0000009470&catID=&pcntry=US&sap-language=EN&_cp_id=id-1385059687642-0
    2. You could install as an AddOn on your 7.3 system, there are many options depending on your desired infrastructure: SAP Gateway deployment options in a nutshell For example our customer have deployed Central Hub Gateway in a standalone stack ABAP to act as an standalone oData bridge between ABAP/nonAbap systems.
    3. You could deploy SAPUI5 apps in 7.x, Java Web Servers or HTTP Web Servers. You must consider your SSO scenario:
    - SSO Logon Tickets. You will need to configurate SSO Logon Tickets between SAP NW Portal & SAP NW Gateway & your backend (ECC, etc). In order to pass SAP session cookie you will need setup SAP Web Dispacther and access portal & gateway throught SAP WD with the same domain.
    - SAML2 Tickets. This scenario lets you provide portal & gateway on different domains enabling SSO. You could configure SAP NW Portal as an Identity Provider and other systems must trust SAP Portal as IdP.
    Cheers

  • RFC - Calling Function Module in a local Windows Program (.exe) on user PC

    Hi Gurus !
    Has anyone ever tried to call a local program on the user side through RFC ? Actually, this programme should allow the use of function module from ABAP programs.
    Indeed we want to use some device locally installed, here a device to pay using Credit Cards.
    However, we've almost successfully filled our requirements if the destination RFC is activated as a Registered Program. But a user B tries to access device of a user A if the code and destination are the same. So we need to create as many RFC destination as users.
    So, we'd like the frontGUI to call the local EXE. This EXE would be coded in VB btw. But we can't figure out how to set the program to register on SM59, using "Start on Front-End Station" option.
    Has anyone any clue on how the program should look like ?
    Thx in advance,
    N H

    Hi MxG,
    I guess we're close to the solution.
    So, using the .Net Connector, and declaring inside our program the Host and Server Class, we've managed to use it, as a registered Server Program. Actually our Registered Program is a Windows Service running on the local computer that the RFC Function Module refers to.
    While testing this it's appeared that user B was trying to use device on User A, event thought devices and services were installed on both computers.
    I guess there's something we're misunderstanding or missing when we try to convert our solution to a Front-End solution. The program is obviously incomplete, something is missing. But I can't find any example or start-up for that program. Even in SAPHelp, there's only something saying that "you can do your own program for front-end and RFC"...   :/
    Well, I've just realized I've reformulated my issue, but since it's confusing for me, it's actually not easy to describe and make sure it's understandable !
    Regards,
    N H

  • RFC call from a Windows Service

    Hi All,
    I have created a simple windows service which is making an RFC call to R/3 system. This is not working. Whereas the same piece of code written in a windows application projects(exe) works properly. Does anyone had similer issues working with Windows services ? Is it a known issue of RFC calls from windows service ???
    Thanks & Regards
    Ganesh Datta

    Hi Juergen,
    After I put the debug statements I figured out that connection to R/3 system is unsuccessful.
    I am using the SAP .Net Connector 2.0. I wrote a windows service which is manually started. Withing my service I am using Single sign on to connect .This is what was causing the problem. If I disable Single sign on and supply userID and password then connection is successful and also subsequent RFC calls.
    I guess within windows service Single sign on does not work.
    Thanks for your reply
    Best Regards
    Ganesh Datta

  • Record File in Window Server with RFC to File Interface

    Hi ALL,
    I´m with problem to record files in Windows Server through RFC to File Interface.
    Tried to record in my local machine (C:TEMP), without success.
    Can someone help me?
    Tks.
    Rodrigo

    Then Pooja,
    It don´t message with error.
    In SXI_MONITOR display with sucess but not record file in windows directory...
    Tks

  • Creatting RFC  Server as a windows service

    Hi,
    How to create RFC server as a windows service using sap.net connector.Please send me the sample code.

    hi, I don't know which problem do you meet.
    As I know, there is a console RFC server sample in the SAP dotnet connector install directory, you can have a reference.
    And I thinks as a dotnet developer, it is not a problem to convert a console application to a windows service.
    Especially using VS.net, it is single to develop a windows service. You can search a sample in MSDN.
    Hope it is useful

  • RFC library on 64-bit Windows platforms?

    The download site offeres the RFC libraries for Solaris, HP-UX and Win32.
    Does anyone know if the libraries are available for Windows Itanium or Windows EM64T?
    Does anyone know if the Win32 libraries can run in a Win32 process on Windows EM64T?

    Dear Katrina, the problem has finally been solved, with the help of a computer-savvy friend of mine who came round this afternoon. As a courtesy, and to thank you for all your help in this matter, I want to share the solution with you.
    A piece of the puzzle was missing, as you said, and it lay in the tenth line of the XML document I relayed to you....
    <key>Music Folder</key><string>file://localhost/C:/Users/Simon/Music/iTunes/iTunes%20Media/</string>
    My friend spotted that the command string contained a sub-folder of the iTunes folder called "iTunes Media". iTunes was expecting to find all my music there, but that folder didn't exist.
    So I created a new folder called "iTunes Media", and moved all my musical content into it, leaving all the command files in the original iTunes folder.
    Then I moved the "iTunes Media" folder into the "iTunes" folder, so that it was a sub-folder of the latter.
    Then I re-opened iTunes and - joy of joys! - everything works once again. I am re-united with all of my music, and without having to make over 14,000 manual location exercises. I can't tell you how exciting that is.
    The mystery is solved, and what had me so puzzled seems obvious now. Thanks again for your help. Without you I might never have got to this point.

Maybe you are looking for