The SAP R/3® Guide to EDI and Interfaces

Frontmatter

1. Where Has the Money Gone?

Abstract

EDI projects can soon become very expensive. However, when analysing the reasons for high costs, one finds quickly that it is not the technical implementation of the EDI project that lets explode the total costs.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

2. What Are SAP R/3 IDocs?

Abstract

IDocs are SAP’s file format to exchange data with a foreign system. This chapter is intended as an introduction to the concept.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

3. Get a Feeling for IDocs

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

4. Exercise: Setting Up IDocs

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

5. Monitoring IDocs

Abstract

There are some utilities in R/3 that help monitoring all the IDocs in the system. They allow viewing them, analysing eventual cause of error and retrying IDoc processing in case of failure.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

6. Sample Processing Routines

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

7. IDocs Terminology

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

8. IDocs Customizing

Abstract

Let aside the writing of the processing function modules, IDoc development requires the definition of the segment structures and a series customizing settings to control the flow of the IDoc engine.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

9. IDoc Outbound Triggers

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

10. IDoc Recipes

Abstract

The chapter shall show you how an IDoc function is principally designed and how R/3 processes the IDocs.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

11. Partner Profiles and Ports

Abstract

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

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

12. RFC Remote Function Call

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

13. Calling R/3 Via OLE/JavaScript

Abstract

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).

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

14. ALE — Application Link Enabling

Abstract

ALE is an R/3 technology for distribution of data between independent R/3 installations. ALE is an application which is built on top of the IDoc engine. It simply adds some structured way to give R/3 a methodical mean to find sender, receiver and triggering events for distribution data.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

15. Workflow Technology

Abstract

There are two faces of workflow in R/3. There is once the business oriented workflow design as it is taught in universities. This is implemented by the SAP Business WorkflowTM. However, the workflow is also a tool to link transactions easily. It can be used to easily define execution chains of transactions or to trigger user actions without the need to modify the SAP standard code. This can even be achieved without laboriously customizing the HR related workflow settings.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

16. Batch Input Recording

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

17. EDI and International Standards

Abstract

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.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

18. EDI Converter

Abstract

R/3 does not provide any tool to convert IDocs into international EDI format like ANSI X.12, EDIFACT or XML. This conversion needs to be done by an external add-on product which is provided by a variety of companies who specialized in general EDI and e-commerce solutions.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

19. Appendix

Abstract

There is a couple of transactions which you should know when working with IDocs in any form. I suggest to call each transation at least once to see, what is really behind.

Axeö Angeli, Ulrich Streit, Robi Gonfalonieri

Backmatter