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 SAP system using RFC
-d	`C11`	SAP 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 CPIC 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`	SAP 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 that this field is case-sensitive.
-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: Call transaction SE38. Enter the report name RSPARAM. Select Execute and do not select the field Display also unsubstituted (the system variable values are then displayed). Select Find (CTRL-F). Enter `rdisp/sna_g` and confirm your entry. The name of the gateway host is displayed in the line rdisp/sna_gateway (you may have to scroll to the right). Note that this field is case-sensitive.
-x	`sapgw00`	Gateway service as in /etc/services: Repeat steps 1-5 for the gateway host (parameter -g). Then: The name of the gateway service is displayed in the line rdisp/sna_gw_service (you may have to scroll to the right). Note that this field is case-sensitive.
-t		Writes the log data to the file dev_rfc in the current directory.
-balanced		Load balancing option: If you choose this option, calls are automatically sent to the application server with the shortest current response time. Prerequisite: You use load balancing for RFC in your SAP system. For the '–balanced' option, you must also specify the following parameters: -h, -s, -g, -gui. Note For more information on RFC with load balancing, see http://service.sap.com/connectors: RFC Library Media Library RFC Library Guide.pdf. End of the note.
-gui		Starts the SAPGUI. This option allows you to process screens and graphics.

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 SAP 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 ("Status" section) so that the SAP 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 startrfc 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.