SAP to SFTP simple Setup with a Windows Host

The aim of this blog is to give an easy way to setup an SFTP connection between a SAP system and an SFTP server.

Main problematic

As Said, SAP does not cover SFTP using SAPFTP. According to note 795131, the best solution is to use a third party software to do it and then call the third party software from SAP (using SM49/69 host command). Still, if the SAP system is running on a Unix Based system, everything is fine, because the syntax offered by Unix allow you to run SFTP command in Oneliner (using | eventually), but if the SAP system is running on a Windows NT based system, problems arise.

Simulate 3rd party, non-SAP systems and EDI partners to remove delays from complex SAP S/4HANA transformations

Why read this article

Service virtualization and testing (SVT) solutions like Int4 IFTT (Certified ABAP addon for SAP Solution Manager – SAP Solman) provide the developers and functional consultants with ways to quickly simulate the interfaces of any 3rd party, non-SAP systems as well as B2B partners – EDI. This allows not only to quickly run test scenarios during the development (DEV) and integration (SIT) phases of the project but also run the regression testing on any non-productive environment. Not having to install and maintain many new test instances of non-SAP systems also allows the SAP S/4HANA transformation projects to be more sustainable as projects use less resources and can be done much faster, therefore reducing carbon footprint significantly.

Passing Dynamic Signature (HMAC SHA256 algorithm) and Timestamp in SAP PI REST Adapter Header Using Java Mapping

Introduction:

This Blog will guide you to pass dynamic Signature and Timestamp in the Header of a POST Method Using REST Adapter in SAP PI. For calculating signature there are certain rules which will be mentioned in the Pre-Request Script of the Third-party service which you will be integrating into SAP. In this case, the Signature is calculated by the HMAC SHA256 algorithm and passed in the Header of the POST Service where the receiving third-party system will validate the signature.

Preface:

I recently worked with a Receiver Adapter integration with a Third-party and there was a challenge in Passing Headers. In general Integration scenarios in Headers, we used to pass Token or Authorization or some known parameters, the case which I have worked on has Signature and Timestamp to be passed in the Headers.