User Interface: SAP RFC Integration
Remote Function Call (RFC) is an interface that allows SAP application programmers to use the Advanced Business Application Programming (ABAP) language to program or script calls to Loftware Enterprise SP.
The following panel and panes are available when you configure an SAP RFC integration by using Loftware Enterprise SP Integration for use with SAP® Applications.

The following commands are available from the ribbon in Integrations

Icon |
Command |
Description |
---|---|---|
![]() |
New |
Create a new object of a specific type. |
|
Open |
Open an existing object. |
|
Save |
Save the displayed object. |
![]() |
Delete |
Delete the displayed object. |
|
Undo Edits |
Reverse the most recent action on an object. |
|
Redo |
Reapply the previously undone action to an object. |

Command |
Description |
---|---|
Close |
Close the current object. |
Close All |
Close all objects that you have open. |
Save |
Save the object. |
Save As |
Save a copy of the object under a different name. |
Delete |
Delete the displayed object. |
Home
Button | Command | Description |
---|---|---|
|
Start Integration | Make an integration available. |
|
Stop Integration | Make an integration unavailable. |
|
Refresh |
Update the displayed data. |
View
Button | Command | Description |
---|---|---|
|
Properties | You can configure or view properties when you view any type of integration. For more information, see Properties below. |
|
Tags | You can categorize an integration by assigning tags to it. For more information about using tags, see Categorize an Integration. |
|
Service Management |
If your Loftware Enterprise SP environment is configured to support distributed services, View > Service Management allows you to configure failover of integration services between Loftware Application Servers. These options are also available in the Service Management page in System Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Loftware Application Servers on which it should be available to run and started on at least one. In an environment with only one Loftware Application Server, these types of services are automatically activated and started when they are created. For more information, |

The following options are available in the General panel when you use Loftware Enterprise SP Integration for use with SAP® Applications to configure an SAP RFC integration.
Note: You must configure each of the options displayed.
Option |
Description |
---|---|
Job Target Folder |
The unique folder in Loftware Enterprise SP to which status information about print jobs related to this integration should be directed. A different job target folder must be configured for each integration. For more information, see Configure a Job Target Folder. |
Default Process |
A process to be applied to the integration. Although this field is required, you can select the Generic Document Process in the root folder if you have not configured a custom process that should be applied. |
Transaction Size |
For a stacked job, the maximum number of labels to allow in a batch. This value is used during job management for packaging print job details into jobs and should be set to be greater than the size of any expected batch of print job details you may need to send. For example, if you have a stacked job with 200 labels to print to the same device, the transaction size should be set to 201 or greater. In this example, a transaction size value of 100 would produce 2 batches which may result in unexpected behavior. |
Run As |
A Loftware Enterprise SP user account under which requests received from outside of Loftware Enterprise SP are run. This account must have at least the INTEGRATOR role or equivalent permissions and is typically not an interactive user. For more information, see Configuring a Run As User for Integrations. |

The following options are available in the SAP panel when you use Loftware Enterprise SP Integration for use with SAP® Applications to configure an SAP RFC integration.
Note: You must configure each of the options displayed.
Option |
Description |
---|---|
SAP System Name |
The name of the SAP Application Server, typically 8 characters in length. |
SAP Client |
The three-digit identification number from SAP Transaction SCC4. |
SAP Username | An SAP user name. This is the client ID with which the SAP user specified by the SAP Username is authorized to log on. For information on the required SAP authorizations, see Configure an SAP User for Loftware Enterprise SP. |
SAP Password | The password for the user name provided in the SAP Username field. |
SAP Gateway Service | The port available for registration. |
Load Balance Connection |
Whether to support SAP Load Balancing connection mode or SAP Single Server connection mode. SAP Load Balancing permits multiplexing of communication with all SAP Systems in your environment.
Note: The mode that you specify determines which options are displayed immediately following the Load Balance Connection option. Note: SAP load balancing is not related to Loftware Enterprise SP distributed services. |
SAP Load Balancing Connection Mode
These options are displayed only if the Load Balance Connection check box is selected.
Note: SAP load balancing is not related to Loftware Enterprise SP distributed services.
Option | Description |
---|---|
SAP Message Server (MSHOST) |
The message server that performs load balancing of communication between application servers in an SAP System. This name must be the same on all application servers belonging to the same SAP System. |
SAP IP Address (GWHOST) | The IPv4 address of the SAP Application Server. |
SAP Group |
The SAP logon group. A load balancing group automatically optimizes the selection of application server for performance. |
SAP System ID (R3NAME) |
The name of the SAP R/3 System. |
SAP Message Server Port (MSSERV) |
The load balancing service. |
SAP Single Server Connection Mode
These options are displayed only if the Load Balance Connection check box is cleared.
Option | Description |
---|---|
SAP IP Address (GWHOST) | The IPv4 address of the SAP Application Server. |
SAP System Number |
The two-digit identification number for the SAP instance to which to connect. |

The following options are available in the Advanced panel when you use Loftware Enterprise SP Integration for use with SAP® Applications to configure an SAP RFC integration.
Option | Description |
---|---|
Connection Count |
The maximum number of connection threads (concurrent job requests) that can be open from the SAP Java Connector (JCo) to the SAP Application Server (identified by the RFC Program ID). The default for this setting is 20. Consider the maximum number of connections and total users allowed on the SAP instance when setting Connection Count. |
RFC Program ID | The registered server program ID for the RFC destination defined in the SM59 Transaction Code within the SAP system. |
Ignore Empty Fields | If selected, empty field names are ignored and do not cause a job to fail. |
Ignore Invalid Field Names | If selected, invalid field names are ignored and do not cause a job to fail. |

The following options are available in the Archive Options panel when you use Loftware Enterprise SP Integration for use with SAP® Applications to configure an SAP RFC integration.
Option |
Description |
---|---|
Archive Original Job File |
Whether to save a copy of the original print job file to the Archive Folder when the print job is completed.
Note: Selecting this option is recommended only while testing because it generates additional files. |
Archive XML |
Whether to save a copy of the XML file produced by Loftware Enterprise SP to the Archive Folder when the job is completed.
Note: Selecting this option is recommended only while testing because it generates additional files. |
Archive Folder |
A UNC path to a shared folder or a path to a local folder on the Loftware Application Server, such as \\Server01\Archive or C:\Archive. The folder that you specify is created if it does not exist. Using a path to a mapped drive is not recommended. Job files and associated XML files produced by Loftware Enterprise SP can be archived to this folder. Note: This option is displayed only if Archive Original Job File or Archive XML is selected. |

The following properties can be configured or viewed by clicking View > Properties when you view any type of integration with Loftware Enterprise™ SP.
Option | Description |
---|---|
Integration Name |
A unique name for this connectivity bridge between Loftware Enterprise SP and another application. Required. ![]() The following characters are permitted in the name: letters, numbers, parentheses, square brackets, ampersands, plus signs, commas, semi-colons, and tildes. Additionally, the following characters are permitted but cannot begin or end the name: spaces, double quotation marks, single quotation marks, hyphens, underscores, periods, and grave accents. For letters, the case that you specify is displayed, but case is ignored when Loftware Enterprise SP interprets a name. If you will be installing the Loftware Enterprise SP application on a computer running Windows Server, and transferring data between Loftware Enterprise SP instances, see the "Transferring Data in a Compressed File" section of the Loftware Enterprise SP Data Transfer Guide. |
Description |
A description for this integration. |
Integration Type |
The type of integration. One of the following values is displayed: File Drop, Oracle, Cloud, SAP RFC, SAP BC-XOM, Event JMS Producer, Event JMS Consumer, Event ActiveMQ Connection, Event Amazon SQS Connection, Event Oracle AQ Connection, Event Direct Processing, Event Message Converter, Event Socket Consumer, Event File Consumer, Event File Producer, Event Email Consumer, or Event Email Producer |
Configured Status |
This property is not displayed until the integration has been saved for the first time.
|
Status |
This property is not displayed until the integration has been saved for the first time.
|
Creation |
|