IntegrationsConfigure an SAP Cloud Integration

Configuring an SAP Cloud integration allows you to specify whether Loftware Cloud Enterprise SP should integrate with SAP® Business Technology Platform or with SAP S/4HANA® Cloud Public Edition and to provide the SAP cloud authentication details to be used. You can also manage general options for running the integration in Loftware Cloud Enterprise SP.

You can configure as many SAP Cloud integrations as your Loftware Cloud Enterprise SP license allows.

Before You Begin:

  • If you are integrating with SAP BTP, you must have an SAP BTP account and access to the SAP BTP Cockpit. This account must either have the Global Account Administrator role collection or otherwise have administrative control of the subaccount used for print queue management. The account must be subscribed to the SAP Print Service and must be used to configure a receiver instance on the SAP Print Service. This receiver instance must have a role enabling it to manage print queues. It is not necessary to install SAP Cloud Print Manager.
  • If you are integrating with SAP S/4HANA Cloud Public Edition, you must have an SAP account with the SAP_BR_ADMINISTRATOR business role assigned so that you can create a communication arrangement and a print queue. The communication arrangement must include SAP users for inbound and outbound communication. It is not necessary to install SAP Cloud Print Manager.

Important! Before SAP Cloud integrations can be fully used in Loftware Cloud Enterprise SP, the Loftware Integration for SAP BTP and S/4HANA Cloud must be installed by Loftware.

Note: References to Loftware Enterprise SP in this topic apply to Loftware Cloud Enterprise SP.

To create an SAP Cloud integration that allows print requests to be processed by Loftware Cloud Enterprise SP, do the following.

  1. In Integrations Integrations, in the ribbon click > SAP Cloud to create a new SAP Cloud integration.
  2. In the General panel, configure the following details.
    1. A different job target folder must be configured for each integration. For Job Target Folder, select a unique folder in Loftware Cloud Enterprise SP to which status information about print jobs related to this integration should be directed.
    2. For Default Process, select either a process that you have created that should be applied to the integration, or else select the Generic Document Process in the root folder.
    3. For Transaction Size, enter the number of labels to allow in a batch. It is recommended to set this value 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 being printed to the same device, the transaction size should be set to 201 or greater.
    4. For Run As, select the Loftware Cloud Enterprise SP user account under which print requests from SAP applications should be run. This user account must have at least the INTEGRATOR role or equivalent permissions.
  1. In the SAP panel, for Print Service Type select whether you are integrating with SAP BTP or SAP S/4HANA Cloud.
  2. If you selected SAP BTP, configure the following details.
    1. For Region, enter the SAP BTP region into which the SAP applications that you are integrating with are deployed.
    2. For Subaccount, enter the identity zone for a subaccount on SAP BTP. The identity zone is specified in the SAP instance credentials for the subaccount and uses the following format:

      <subaccount name>-<identifier>

    3. For Client ID and Client Secret, enter SAP connection credentials for a receiver instance on the SAP Print Service to use with OAuth 2.0 authentication. The integration uses these credentials when authenticating to SAP BTP.
  3. If you selected SAP S/4HANA Cloud, configure the following details.
    1. For SAP System URL, enter the URL of the SAP System on SAP S/4HANA Cloud with which to integrate.
    2. For SAP Username and SAP Password, enter SAP connection credentials for a user for inbound communication for this integration to use when authenticating to SAP S/4HANA Cloud using Basic Auth authentication.
  1. In the Archive Options panel, it is recommended that you clear Archive Original Job File and Archive XML check boxes except during testing. However, for Archive Folder you must enter a UNC path to a shared folder or a path to a local folder on the Loftware Application Server to which files can be saved if archiving is turned on. For example, \\Server01\Archive or C:\Archive. If the folder does not exist, it is created.
  2. In the Properties pane, enter a description of the purpose of the integration.
  3. Click File > Save or click Save Save in the toolbar.
    1. In the Save dialog box, enter a name for the integration.

      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.

    2. In the left pane of the Save dialog box, select the folder in which to save the integration. You can click a folder to display subfolders.
    3. Click OK to save the integration. Creation information is displayed in the Properties pane.
  4. In the ribbon, click Home > Start Integration.
  5. To verify that the integration has started, view the Status in the Properties pane.

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.