An interface connection between SAP to Non-SAP

Today we successfully deployed in PRD an interface connection between SAP and Non-SAP. Here we send data from SAP to a German third-party tool. We set up the IDoc for that system.

We send the IDoc from the SAP Directory. Suppose take one name for the third-party tool as an example: QB.

Here is the Requirement: We need to send SAP data in the form of XML, and will give the access for our data from our directory.

SAP to QB Data Flow:-

Run the transactions >> Data will be created and saved in the database >> IDoc will be created according to the function module >> Saved in your directory >> Directory will be mounted with the interface server >> Data received >> Will be used.

1. Begin by creating a Logical System in SAP through SALE Transactions

2. Assign the created Logical System to the relevant SAP client in SAP through SCC4.

3. Use SM59 to create an RFC destination of type TCP/IP and assign RFCEXEC as the program in the technical settings.

4. Use WE21 to create a port as specified by the client.

5. Use BD64 to create a distribution model with the required message type.

6. Use WE20 to create a partner profile.

Here is the Explanation

Begin by creating a Logical System in SAP through SALE Transactions:

Assign the created Logical System to the relevant SAP client in SAP through SCC4.

Use SM59 to create an RFC destination of type TCP/IP and assign RFCEXEC as the program in the technical settings.

What is TCP/IP - RFC?

TCP/IP (Transmission Control Protocol/Internet Protocol) is a suite of communication protocols used to interconnect network devices over the internet.

A TCP/IP connection is used for an SAP Registered Program.

Purpose: For an RFC call using a TCP/IP connection, the SAP ABAP acts as the initiator, and the registered program serves as the acceptor of the communication.

RFCEXEC: RFCEXEC is an external RFC server program in SAP. It enables the SAP system to access various operating system functions. It is part of the classic RFC SDK (SDK is a Library) and is used to test whether programs can be registered on the Gateway.

Example: One example of such a connection is the communication between an ABAP system and to a Java server.

Create a port as specified by the client:- Choose XML as the format, enable Unicode, and specify the physical directory where files will be stored. Maintain the file directory in the system and share the directory details with the Interface Connection team.

This directory allows access to the files from your system.

Assign Function Module: Assign the standard function module EDI_PATH_CREATE_MESTYP_DOCNUM for creating the path.

Outbound Trigger File: Configure the outbound trigger file to use the specified RFC destination and the physical directory path.

Key Concepts:

Unicode: A universal encoded character set that supports the storage of information from any language using a single character set. It assigns a unique code to every character, regardless of platform, program, or language.

Logical Directory: Represents the file path in ABAP, allowing code to perform read/write operations.

Physical Directory: The actual file location visible at the OS level.

Use BD64 to create a distribution model with the required message type.

Use WE20 to create a partner profile, linking it with the Logical System.

Generate the IDoc:

Run the transactions in SAP.

The system will now generate an IDoc and save it in the specified directory.

Interface Connection and Processing:

The interface is mounted with the IP directory of our SAP system.

The interface server retrieves the IDoc XML files from the source directory and processes the data in their system.

Challenges:

Email is not in the Standard XML: We customized and added the Email tag in the XML Skeleton.