Response Route SAP ALE
Introduction: Phase 6.
Note: The SAP service must be licensed and activated on the Integration Server to use this Response Route. Please contact our support or sales staff.
This Response Route implements the connection to an SAP system via the SAP ALE interface.
Note: For the appropriate destination structure see sections Loading an IDoc Structure from Lobster_data and Loading an IDoc Structure from SAP Repository.
(1) The SAP alias of the connected system (see section SAP).
(2) The following additional parameters are accepted.
|
<empty field> |
All segments are sent to SAP. That is the default case. |
|
mode=default |
Only segments starting with E, Y or Z are sent to SAP. |
|
mode=uppercase |
Only segments that do not begin with a lowercase letter are sent to SAP. |
|
mode=regex;regex=... |
Only segments that match the regular expression are sent to SAP. |
|
<any other, non-empty content> |
Only segments that do not start with lowercase letters r or p are sent to SAP. |
You can also specify the path to a text file in the additional parameter. The file then contains the parameter. The purpose of this parameter is to send only parts of the destination tree to SAP and to be able to also use the destination tree for another Response Route. You could, for example, trigger a subsequent profile before or after you send to SAP, which then receives additional data (the rest of the destination tree) in addition to the IDoc segments. To mention another example, you could implement the profile as a web service and send back a response with data to the web service client.
Note: If the system variable VAR_SYS_SAP_TID is defined in the profile, the returned TID is stored there and can be read in a subsequent profile (called via Response Route Message). Option Execute response in own thread may not be selected in that case. Of course, the prefix MSG_CALL_ is to be used in the subsequent profile. See section Variables with Prefix MSG_CALL_.