Hey there! I want to address an issue that may arise in projects involving encryption/decryption within the SAP BTP iFlow and its embedded PGP engine. Scenario description Imagine you've installed the latest version of the gpg4win application (version 4.3.1) to generate public and secret keys
This guide aims to outline the steps required to create an API for iFlow and subsequently run the iFlow through the API. Step # 1. Develop an iFlow Begin by creating a simple iFlow. Deploy any changes made. Step # 2. Setting Up API Providers Navigate to the API section on the
This note contains an example of a Groovy script that may help the developer trace the payload within the iFlow, especially if it changes during its lifecycle. It is worth noting that the beauty of the script below is that it adds an attachment to the processed message that can
This brief note aims to highlight the possibility of overwriting standard iFlow header parameters, offering developers flexibility in addressing various requirements. Specifically, this discussion centers around the header parameters SAP_Sender and SAP_Receiver. See Headers and Exchange Properties Provided by the Integration Framework SAP allows developers to overwrite the
Regardless of your area of expertise within SAP, whether it's HCM or PM (Plant Maintenance), you may encounter IDOCs used for various business needs. The steps outlined below can help you understand what is required to process an IDOC developed in the SAP on-premise system and consume it
In this post, I'm going to provide the steps required to start using the RFC adapter within the iFlow on the SAP BTP Integration Suite. Step #1. Create the Remote-Enabled Function Module Create the FM that will be returning values from the ABAP system. Don't forget
I have no doubts that you've heard about SAP HANA. Moreover, I have no doubts that you've heard about SAP HANA Cloud. As for the last one, it is worth mentioning that this service could be activated on the SAP BTP instance, even if you'
I would like to describe a peculiar behavior of SAP BTP regarding iFlows with HTTP requests inside. Let me provide further details. Initial set up I have an iFlow that triggers an API and returns a JSON containing the request data. For some reason, I decided not to expose the
The SAP BTP Integration Suite offers various adapters for integration flow developers to utilize. Among these are frequently used options such as HTTPS, SFTP, OData, and Mail. See Configure Adapter in Communication Channels In this post, I would like to demonstrate one of the adapters that could potentially be used
In this post, I would like to consider a sequence of steps required for restricting access to iFlows within the BTP instance. Preface As you probably know, an Integration Flow could be triggered via the generated endpoint URL that you can find in the corresponding tile on the Monitoring dashboard.
In this post, I will provide a sequence of steps required to develop an API that generates an OAuth2 token, which can be utilized by other APIs within the same BTP instance for authorization purposes. Let's dive in. Requirement To develop an API capable of generating an OAuth2
I would like to present an example of the iFlow containing the PGP Encryption step, followed by further message storage in the DataStore. Requirement Develop an iFlow to process the sent data, encrypt it with the PGP public key, and save it in the DataStore. Step #1. PGP Keys Before