Deploy the Tekst iFlow Package in CPI

Tekst provides an iFlow package that you deploy on your own SAP BTP Cloud Integration (CPI) tenant. Once the package is deployed and connected, Tekst calls its iFlows to exchange data with your SAP S/4HANA system - for example, fetching master data such as business partners, or creating documents such as sales orders.

This guide covers importing the package, configuring it, and deploying the iFlows. Setting up the role and service key is covered separately in the Set Up the SAP BTP Role and Service Key for Tekst article, and entering the credentials in Tekst in the Connect SAP S/4HANA via BTP Service Key article.

Before you begin

You need:

  • An SAP BTP account with Cloud Integration (CPI) active
  • An SAP S/4HANA system reachable from BTP (set up a Cloud Connector if it is on-premise)
  • S/4HANA set up for Tekst, as described in the Set Up SAP S/4HANA for Tekst article. From that setup you need the API host of your S/4HANA system and the communication user with its password.
  • The Tekst iFlow package file (.zip), provided by Tekst (for example, CP012-Tekst-SalesOrder-iFlows version 2.0.0)
  • The role and service key set up, as described in the Set Up the SAP BTP Role and Service Key for Tekst article

Step 1: Import the package

  1. Download the package .zip provided by Tekst, for example CP012-Tekst-SalesOrder-iFlows version 2.0.0.

  2. In your CPI tenant, open the Design (Integrations) workspace.

  3. Choose Import and select the .zip file.

The package and its iFlows appear in your workspace, ready to configure.

Step 2: Store the S/4HANA credentials in CPI

The data iFlows sign in to S/4HANA with the communication user from the S/4HANA setup. Store that user in CPI as a credential artifact:

  1. In SAP Integration Suite, go to Monitor → Integrations and APIs and open Security Material under Manage Security.

  2. Click Create → User Credentials.

  3. Enter a Name for the credential (for example, S4HANA_COMM_USER). In User and Password, enter the communication user and its password.

  4. Click Deploy.

User Credentials dialog in CPI with the Name, Type, User and Password fields and the Deploy button

Note the Name exactly as you entered it. You enter it in every iFlow in the next step.

Step 3: Configure the externalized parameters

The data iFlows expose externalized parameters that you must set before deployment so they point at your own S/4HANA system. Open the Configure dialog of each data iFlow and, on the Receiver tab under Connection, fill in:

Field What to enter
s4hana_base_url The API host of your S/4HANA system only, with no path and no trailing slash, for example https://myXXXXXX-api.s4hana.cloud.sap. The iFlow adds /sap/opu/odata/sap/... itself.
Credential Name The Name of the User Credentials artifact from step 2, exactly as you entered it.

Configure dialog of a data iFlow with the Address, s4hana_base_url and Credential Name fields

Do not paste a full service URL from S/4HANA into s4hana_base_url. The Address field already contains the path, for example {{s4hana_base_url}}/sap/opu/odata/sap/API_PRODUCT_SRV/A_Product, so a full URL doubles it.

If Credential Name does not match a deployed credential exactly, every call to S/4HANA fails with an error like No credentials for <name> available. Deploy suitable credentials or adapt credential name in integration flow.

The Proxy Type defaults to On-Premise. Change it to Internet if your S/4HANA is cloud-hosted.

Step 4: Deploy the iFlows

Deploy all iFlows in the package from your CPI tenant. Deployment usually takes only a few minutes.

Step 5: Connect in Tekst and verify

Add the SAP S/4HANA integration in the Tekst platform using your service key credentials, as described in the Connect SAP S/4HANA via BTP Service Key article.

The package includes a connection-test (health check) iFlow. After you add the integration, Tekst automatically runs it. The health check only confirms that Tekst can reach your CPI tenant.

To check the iFlows, open the SAP S/4HANA integration in Tekst and go to the iFlows tab. Every iFlow your blocks use should show green. A grey row means that iFlow is not deployed, and blocks that use it will fail. The Used by labels show which blocks use each iFlow.

iFlows tab of the SAP S/4HANA integration in Tekst, with green rows for deployed iFlows and a grey row for an iFlow that is not deployed

To confirm S/4HANA itself answers, run a flow with the Get product block on a product number you know exists.

0 comments

Please sign in to leave a comment.