RFC with External Systems In the SAP System, the ability to call remote functions is provided by the Remote Function Call (RFC) interface. This interface allows for remote calls between two SAP Systems (R/3 as of Release 2.1 and R/2 as of Release 5.0D), or between an SAP System and a non-SAP system. The present section describes how to write RFC partner programs that run in non-SAP Systems. If you are writing RFC programs in an SAP System, see RFC-Programming in ABAP [Ext.]. Client and Server Programs RFC programs for non-SAP Systems can function as either the caller or the called program in an RFC communication. There are two kinds of RFC programs: RFC client and RFC server programs: The RFC client is the instance that calls up the RFC to execute the function which is provided by an RFC server.
Read the rest of this entry »

• 0 Comments

The function library in R/3 provides a facility for generating and then downloading RFC programs to a workstation or PC. This facility is the RFC Interface Generator. With this tool, you can create RFC stub programs (that call SAP function modules) and example programs (that show how to call stub programs). The RFC Generator is only available for and in R/3 Systems and not for R/2 Systems. Generating RFC Stubs: RFC stub programs contain all the parameter-handling and communications necessary to call SAP function modules from a non-SAP System. Once a stub has been exported to your machine, you can compile it as a library file or DLL (dynamic-link library) routine. DLL routines can be called without having been linked together with your program at compile time. You can call DLL routines from any programming language whose compiler offers DLL options. (This includes, for example, most recent C and BASIC compilers.)
Read the rest of this entry »

• 0 Comments

DCOM provides a standardized basis for creating and integrating distributed software components. External client applications can use DCOM as infrastructure for their communication with SAP servers, to access R/3 components. With this technology, R/3 components such as BAPIs or remote function modules appear as COM objects and use the runtime environment of the Microsoft Transaction Server (MTS). The DCOM Connector provides a C++ Template Library developed by SAP, which you can use to create COM objects from business objects of the R/3 system and administer them. The two scenarios below describe the different uses of the DCOM Connector: PC Client Applications
Read the rest of this entry »

• 0 Comments