Last updated
Was this helpful?
Last updated
Was this helpful?
SAP enables SAP connection (RFC only) for requirements dispatch.
Take a look at the configuration options for the component. Parameters supported by are marked with (DB).
We recommend you to set Globals for the SAP environment, as shown below:
Globals:
environment = SAP environment
See the examples of the items listed, that must be replaced according to your need:
[rfc] = RFC name
[table] = Table related to RFC
[columns] = Table columns
For RFC connections, use the "SAP Json to RFC" capsule before the SAP component. That way, the call is transformed in the format expected by SAP. This is an example of RFC call syntax inside SAP:
Function call (RFC) BAPI_BUPA_ADDRESS_GETDETAIL inside JSON Generator component
For a RFC call, it's important to pay attention to the following points:
Always inform Sid - field Enviroment/SystemName/System Id previously mentioned.
RFC field - can be in the JSON file, as well as informed inside the component.
ImportParameters - function call inside SAP. Be specific only with the fields that must be filled out in the call.
IDOC Type: has a specific structure, that put into sequence the data transfered from one system to another.
IDOC TYPE EXTENSION (optional): specifies the IDOC extension, if it exists, of an IDOC produced by this endpoint.
SYSTEM RELEASE (optional): specifies the SAP Basis Release associated, if it exists, to an IDOC produced by this endpoint.
APPLICATION RELEASE (optional): specifies the Application Release associated, if it exists, to an IDOC produced by this endpoint.
See an example of template (XML):
{YOUR_ENVIRONMENT} must be replaced by your SAP SID.
If it's a single query, you can use the following syntax:
Elementary fields/Import Parameters
Example:
If it's a table query, use this syntax:
Table fields
Example:
Input
${type}: variable that must be provided inside a tag "body"
For the variable sapRequestTemplate, it's important to pay attention to these points:
the variable name can have the following signs: minus (-), period (.) and colon (:) in any position. But these characters need to be escaped with backslash (\). Otherwise, they'll be interpreted as operators.
it might be more convenient to use variables and conversion functions:
Output
The component expects a message under any format. However, it will look for a path inside the "modelPath" configuration property.
The output message will be the same as the input message, but replacing the model property according to the template definition (as a string). If there's an error, the "property_error" property will be created on the same level of the original property.
Read the for more information about connectivity related to SAP.
Discover more about the SAP component and how to use it on the Digibee Integration Platform.
Account
It's necessary to create a BASIC-type account to use the SAP credentials (user and password).
N/A
String
SAP Operation
Connection method in SAP - the component supports access via RFC or IDOC.
RFC
String
IDOC Type
Specifies the Basic IDOC Type of an IDOC.
N/A
String
IDOC Type Extension
Specifies the IDOC Type Extension of an IDOC.
N/A
String
System Release
Specifies the associated SAP Basis Release of an IDOC.
N/A
String
Application Release
Specifies the associated Application Release of an IDOC.
N/A
String
Host
Hostname of the SAP system - for "IP" and "Port" to be supported, it's necessary to have connectivity via VPN (you can define VPN through SAP GUI). To resolve the hostname to an IP address, you must add a mapping entry to the host file of the machine on which the agent is installed.
N/A
String
RFC
Name of the RFC used to connect with the SAP system - this field is informed by the client (the import parameters of the SAP funtion must be mapped).
N/A
String
Language
Language to be used in the connection with the SAP system (ex.: "EN" for English).
en
String
Client ID
SAP Client ID, normally with 3 digits, used to connect with SAP.
400
String
System Number
Normally with 2 digits, used to connect with the SAP system (you can find this information in SAP GUI).
01
Integer
Send as File
If this option is enabled, a file can be defined and sent.
False
Boolean
File Name
N/A
String
Template (XML)
Template Apache FreeMarker for the SOAP message sent in the request.
N/A
String
Fail On Error
If the option is enabled, the execution of the pipeline with error will be interrupted; otherwise, the pipeline execution proceeds, but the result will show a false value for the “success” property.
False
Boolean
Use Dynamic Account
When the option is active, the component will use the account dynamically. When deactivated, it will use the account statically.
False
Boolean
Account Name
N/A
String
Scoped
False
Boolean
File that contains the body to be sent to SAP server. Using this capacity is recommended in situations where the content is too large to be sent via the Template field. Use other components such as and to write the intended content.
Account name to be set. The name of the account is generated dynamically via the component.
When the option is active, the stored account is isolated to other sub-process. In that case, sub-processes will see their own version of the stored account data. To know more about the Scoped feature, check out the .