Outbound Processing
The regulations for generating the outbound file are defined in outbound processing. When you trigger the receiving system using RFC, you also make the command file known (shell script). In the trigger instructions screen it is called out.script.
The user environment in the operating system is not evaluated. This means that you must set parameters explicitly in the command files and all directories must be specified absolutely.
Choose
.Position the cursor on File and choose .
Enter the name of your external system as the port. Enter a Definition and Version (see F1 Help) for the record types.
Choose Outbound File and enter a directory.
Enter a slash ( /) after the directory name, as the path and file are linked.
To generate the file names, choose an appropriate function module using F4 Help. We strongly recommend that you do not use a static file name, since this file is overwritten each time a new IDoc is sent. SAP recommends that you use the function module EDI_PATH_CREATE_CLIENT_DOCNUM.
To use "logical directories" see the F1 Help for the corresponding field.
If you want to trigger: Choose Outbound processing: Triggering and enter the full directory name for the shell script (without the name of the shell script itself) in the directory line. Enter a slash ( /) after the directory name. You have defined the logical destination in the section Outbound Processing: Triggering the Receiving System. Select Automatic start possible to activate triggering.
As well as the in the port definition you can test with the aid of report SRFCTEST whether program rfcexec correctly executed the command file. Choose the option RFC_REMOTE_EXEC in the report and enter your RFC destination and your command file as the command (or an explicit command for a pre-test).
Inbound Processing
If the upstream system triggers the SAP system with startrfc, the -E PORT= parameter value of startrfc must be entered as the port name. You have already specified the name of the port in step 3 for outbound processing.
When the system is triggered, the name and path of the file are determined by the upstream system. The following settings only provide default values for the test programs that use the file port. Otherwise, they have no effect. ...
Choose Inbound File and enter a directory as the input parameter for the data.
Enter a slash ( /) after the directory name, as the path and file are linked.
Enter a file name.
Status Files
If the upstream system triggers the SAP system with startrfc, the -E PORT= parameter value of startrfc must be entered as the port name. You have already specified the name of the port in step 3 for outbound processing.
When the system is triggered, the name and path of the status file are determined by the upstream system. The following settings only provide default values for the test programs that use the file port. Otherwise, they have no effect.
Choose Status File and enter a directory.
Enter a slash ( /) after the directory name, as the path and file are linked.
Enter a file name.
Configure the following values:
Value... |
For... |
EXT |
Name of the external system = port name |
/usr/sap/C11/SYS/global/EXT/in |
Directory for inbound IDocs |
/usr/sap/C11/SYS/global /EXT/out |
Directory for outbound IDocs |
/usr/sap/C11/SYS/global /EXT/status |
Directory for status data |