Ulrich Streit

RFC Remote Function Call

A remote function call RFC enables a computer to execute a program an a different computer within the same LAN, WAN or Internet network. RFC is a common UNIX feature, which is found also in other object-oriented operating systems. R/3 provides special DLLs for WINDOWS, NT and UNIX to allow RFC calls from and to R/3.

EDI and International Standards

With the growing importance of EDI the fight for international standards heats up. While there are many business sectors like the automotive industry and book distribution who use EDI for a long time and want to continue their investment, there are others who insist in a new modern standard for everybody.

Calling R/3 Via OLE/JavaScript

Using the OLE/Active-X functionality of R/3 you can call R/3 from any object aware language. Actually it must be able to do DLL calls to the RFC libraries of R/3. SAP R/3 scatters the documentation for these facilities in several subdirectories of the SAPGUI installation. For details you have to look for the SAPGUI Automation Server and the SDK (RFC software development kit).

IDocs Terminology And Basic Tools

This is a collection of expressions used in context with IDocs. You should be familiar with them. Some are also used in non-IDoc context with a completely different meaning, e.g. the term message, so avoid misunderstandings. Many fights in project teams arise from different interpretations of the same expression.

Sample Processing Routines

This chapter demonstrates on an example how an IDoc is prepared in R/3 for outbound and how a receiving R/3 system processes the IDoc.

Exercise: Setting Up IDocs

The best way of learning is doing it. This chapter tells you how to set up your R/3 system that it can send IDocs to itself. When sending IDocs to your own system you can test the procedures without the need for a second client or installation.

Batch Input Recording

The batch input (BTCI) recorder (SHDB) is a precious tool to develop inbound IDocs. It records any transaction like a macro recorder. From the recording an ABAP fragment can be created. This lets you easily create data input programs, without coding new transactions.

Partner Profiles and Ports

R/3 defines partner profiles for every EDI partner. The profiles are used to declare the communication channels, schedule and conditions of processing.

IDoc Outbound Triggers

IDocs should be sent out at certain events. Therefore you have to define a trigger. A lot of consideration is required to determine the correct moment when to send out the IDoc. The IDoc can be triggered at a certain time or when an event is raised. R/3 uses several completely different methods to determine the trigger point. There are messages to tell the system that there is an IDoc waiting for dispatching, there are log files which may be evaluated to see if IDocs are due to send and there can be a workflow chain triggered, which includes the sending of the IDoc.

Get a Feeling for IDocs

IDocs are relatively simple to understand. But, like most simple things they are difficult to explain. In this chapter we want to look on some !Doc and describe its elements, so that you can get a feeling for them.