Troubleshoot Integration for Use with SAP® Applications

For information about how to configure a Loftware Enterprise SP Integration for use with SAP® Applications, see Integration for Use with SAP® Applications. For information about managing access to integrations, see Controlling Access in Loftware Enterprise SP.

For information about Loftware Integration Command Line Interpreter (CLI) for SAP Applications, see Getting Started with Loftware Integration Command Line Interpreter (CLI) for SAP® Applications.

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, see High Availability with Distributed Services.

Important! In an environment with distributed services, to permit a user to perform administrative tasks related to services you must assign Read and Write permissions for Servers. These permissions must be assigned for each server in Access Control . Examples of administrative tasks related to services include creating a data service, a device connection, an integration, or a facility. Core services can only be configured by the SuperAdmin or SystemAdmin user.

Tip: You can check the version of Loftware Enterprise SP and obtain information about its components, the Loftware Application Server, and your Loftware Enterprise SP license (including the integrations allowed) by clicking Help Help > About.

Important! Before SAP BC-XOM integrations can be fully used in Loftware Enterprise SP, Loftware Integration Command Line Interpreter (CLI) for SAP Applications must be installed on the SAP Application Server by an SAP Basis Administrator. Also, a dedicated Loftware Enterprise SP user for Loftware Integration CLI for SAP Applications must be configured in Loftware Enterprise SP. If you have upgraded Loftware Enterprise SP, then you must also upgrade Loftware Integration CLI for SAP Applications.

Symptom	Resolution
Problems are encountered with an integration for use with SAP applications.	One of the following approaches may resolve the issue: If print jobs are not printing, you must determine whether the issue is due to the integration, the process and business rule, or the device and device driver. In label templates in Label Design , ensure that only uppercase text is used in the Data Ref fields. By default, Data Ref fields are case sensitive. In SAP BC-XOM integrations, ensure that the Integration Name matches the name included in the Submit command in the Logical Output Management System (LOMS) on the SAP Application Server. The length of this name must be 12 characters or fewer. For more information, see Configure SAP ERP for BC-XOM Communication.

Symptom

Resolution

Problems are encountered with an integration for use with SAP applications.

One of the following approaches may resolve the issue:

If print jobs are not printing, you must determine whether the issue is due to the integration, the process and business rule, or the device and device driver.
In label templates in Label Design , ensure that only uppercase text is used in the Data Ref fields. By default, Data Ref fields are case sensitive.
In SAP BC-XOM integrations, ensure that the Integration Name matches the name included in the Submit command in the Logical Output Management System (LOMS) on the SAP Application Server. The length of this name must be 12 characters or fewer. For more information, see Configure SAP ERP for BC-XOM Communication.

Note: Loftware Connector for SAP Applications uses a configuration file (saprfc.ini). This file is not used by Loftware Enterprise SP. Instead, configuration is performed in integrations within Loftware Enterprise SP.