Before you can start client programming, you need certain information on the R/3 business objects you use and on the respective BAPIs. To get this information, you can use the following utlities:

• BAPI documentation.
• If you are allowed to access R/3 via SAP GUI, you can use these transactions:
• Use transaction SWO2 to call the Business Object Browser.
• Use transaction BAPI to call the BAPI Explorer.
• SAP Assistant provides a frontend application for an interactive RFC communication that runs under Windows. This allows you to call and test all remote function modules online (even those that implement BAPIs) without access via SAPGUI.
• DCOM Connector allows to display meta data of generated R/3 business components using ISAPCatalog interface.

SAP Assistant is part of the RFC SDK; you can install it on your frontend from there.

For programming client applications, you must execute the following steps:

1.  Create an instance for the session object.

2.  Assign the R/3 connection parameters to the session object. The connection parameters include:

• Destination
• Client
• UserID
• Password
• Language

Use method PutSessionInfo( ) if you transfer the connection parameters in a single function call rather than separately.

3.  Create the instance of the respective business objects.

4.  If SAPGUI is installed on the frontend, you can start SAPGUI from within the client program or debug the ABAP coding.

• Create a callback object RFC GUI Sink:
  Set GuiSink = CreateObject("RfcGuiSink.RfcGuiSink.1")
• Call method AdviseRfcGuiSink( ):
  oBO.AdviseRfcGuiSink(GuiSink, 1, 0)

5.  Actually process the business objects (call BAPIs).

6.  Complete R/3 session with CommitWork.

7.  Release the objects.