Status Confirmation: Triggering the SAP System (SAP Library - IDoc Interface/Electronic Data Interchange (BC-SRV-EDI))

Status Confirmation: Triggering the SAP System

As is the case with inbound processing of IDoc files, the external system must call the program startrfc. The status confirmation call differs from the inbound IDoc case only with regard to the function module parameters. The startrfc must therefore be started with different parameters for the status and inbound IDoc files.

Prerequisites

You require the startrfc program from the RFC library.

Procedure

Enter the startrfc command with the logon and function module parameters listed below. The command line could begin as follows:

startrfc -3 -d C11 -u EDIUSER ...

Logon parameters

Parameter	Value (example)	Description
-3		Logon to the R/3 System via RFC
-d	C11	R/3 System ID. This is displayed in the system bar, for example.
-u	EDIUSER	SAP user Enter the name in upper case letters. For security reasons, you should use a CPI-C user, as this user type cannot be used in a dialog. The user requires all of the necessary authorizations.
-p	PASSWORD	User password. Enter the password in upper case letters.
-c	001	SAP client (default: 000) as contained in the MANDT field in the control record.
-l	DE	R/3 System language (default: EN)
-h	arthur	Application server (message server): Call transaction SM51. The first part of the server name field (separated by underscores) stands for the application server. Note upper and lower case letters.
-s	00	Two-digit system ID (TCP/IP service): Call transaction SM51. The third part of the server name field (separated by underscores) stands for the system ID.
-g	arthur	Gateway host: 1. Call transaction SE38. 2. Enter the report name RSPARAM. 3. Select Execute and do not select the field Display also unsubstituted (the system variable values are then displayed) 4. Select Find (CTRL-F) 5. Enter rdisp/sna_g and confirm your entry 6. The name of the gateway host is displayed in the line rdisp/sna_gateway (you may have to scroll to the right) Note upper and lower case letters.
-x	sapgw00	Gateway service as in /etc/services : 1.-5. Repeat steps 1-5 for the gateway host (parameter -g) 6. The name of the gateway service is displayed in the line rdisp/sna_gw_service (you may have to scroll to the right) Note upper and lower case letters.
-t		Writes the log data to the file dev_rfc in the current directory.

Function module parameters for status reports

Parameter	Value (example)	Description
-F	EDI_STATUS_INCOMING	Only this function module reads status files!
-E	PATHNAME= /usr/sap/C11/SYS/global/ EXT/status/<file name>	Directory and name of the file which contains the status information for outbound messages (max. 100 characters)
-E	PORT=EXT	Logical name of the external system as defined in the port definition (max. 10 characters)

Result

You have notified the upstream system of the R/3 function module to be called and the parameters (file and directory) to be used. Store the logical name of the upstream system (EXT in the above table) in the Port definition (section "status") so that the R/3 System recognizes it and accepts the status records.

Once you have maintained the port definition, the process with triggering appears like the transfer of an IDoc file (see the graphic below):

The upstream external system writes the status confirmation to a sequential file in the IDoc status record format.

The external system starts the SAP System with the rfcexec program.

The name and directory of the file (as well as the port) are transferred to the SAP System as startrfc parameters.

The SAP system reads the status file and then deletes it. The status records must contain the numbers of the outbound IDocs that they refer to (field DOCNUM). In this way, these IDocs can be added to the database.

This graphic is explained in the accompanying text