Skip to Content
Author's profile photo Former Member

POV: SAP PI as a Managed File Transfer Tool

Any typical SAP implementation landscape would contain a multitude of 3rd Party or B2B partners. These might include banks, payment agencies, collection desks, customers placing order or suppliers receiving Purchase orders. In most cases sensitive data is passed in such transmissions and secured/Managed file transfer is mandated.

In my opinion the core features of an MFT solution include :

  • Encryption, Tokenization, Key Management
  • Streaming Delivery for large File Transfer
  • Security Protocol Support – e.g. SFTP/ FTPS/SSL
  • DMZ node
  • Routing of FTP processes
  • Scheduling of File Transfer Processes
  • Compliance and Auditability
  • Trading Partner Management

  Customers typically invest into an MFT solution, to satisfy requirements.    

How does SAP PI fare on the above parameters?  

  1. Encryption, Tokenization and Key Management –  Till recently SAP PI did not have an out of the box mechanism for file encryption, and had to depend on third party vendors for support.  With SAP PI 7.1 SP08 ( or equivalent for 7.3 or 7.31), the SFTP and PGP add-on is available. This add-on can support PGP encryption requirements for a customer. PI always had a robust key management mechanism. 

  1. File Streaming –   SAP PI till recently  did not support, streaming delivery for large file.  In fact large file transfer was not even a viable option.  The recent releases of PI, support file chunking mechanism, which satisfy this requirement.


  1. Security Protocol Support –   With the new SFTP Add-on, PI now fully supports SFTP along with FTPS file transmission protocol. AS2 is supported via the B2B add-on.

  1. DMZ node –  The DMZ node comes into play, when an external or B2B partner would push a file for SAP to consume.  In such a case, the a typical MFT solution would have a node in the DMZ which would be accessible to the external partner.  SAP PI  does not support a DMZ node, hence cannot be used in an Inbound push scenario. This is one of the major disadvantages which PI has over an MFT solution.


  1. Routing of File Transfer Processes –   SAP PI being a robust middleware can be configured to support single or multi-receiver routing. It also provides mechanism to reuse transformations between routing rules.

  1. Scheduling of FTP Processes – SAP PI has scheduling capabilities on the communication channels via ATP (availability time planning),  also it can be easily integrated with a scheduling tool like CPS redwood.  This is achieved by means of the http based external control mechanisms in PI.


  1. Compliance and Auditability – SAP PI supports, traceability/auditability and logging in multiple ways. Various levels of logging can be configured.

  1. Trading Partner Management – This is a common feature of SaaS based MFT solutions,  in which the MFT solution acts as a mailbox or post office,  managing addition of newer trading partners, whereby reducing IT costs. There is no such feature in SAP PI.

The limitations above (Lack of  a DMZ node and robust Trading partner management)  elude PI from becoming a robust managed file transfer solution.  Most middlewares today like TIBCO support a fully functional MFT solution, whereby reducing customer TCO. 

The SaaS or Cloud based MFT mechanism, are available as a part of SAP Information Interchange  (SAP-Crossgate), and have a strong trading partner management feature. It needs to be seen, if this can be integrated with SAP PI.

With PI 7.31 being now used as an enterprise middleware, it would exciting if the above limitations become features.  This would definitely reduce the total cost of ownership of an SAP integration solution.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Jason Scott
      Jason Scott

      Hi Abhishek, I have to disagree with you on point 4. PI works just fine for situations requiring incoming data. Firstly you have always been able to install a decentral adapter engine in the dmz. Typically bi find that customers I work for already have something setup in the dmz anyway that allows b inbound file transfers.

      The trading post type features are highly overrated in my opinion as well....

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Hi Jason,

      This is correct.  PI has always had an De-central adapter engine.  Architecturally it is exactly similar to the Adapter engine, and the FTP communication is done via the communication channels. ( an FTP sender adapter)

      Typical MFT solutions, provide a DMZ zone or a node, where an external partner can drop off a file ( inbound - push scenario).

      Even with a de-central adapter engine, PI can only support a pull. External systems would not be able to push files into it. 


      Author's profile photo Nageshwar Reddy
      Nageshwar Reddy

      Hi Abhishek,

      Thanks for sharing your thoughts. I agree with @Jason_Scott on point 4(DMZ). Considering TCO, file exchange mechanisms can be designed to overcome these issues. Have you seen any customers choosing standalone MFT when PI can largely meet the requirements?

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Thanks Nageshwar,

      Yes, in cases, where PI needs to act as secured FTP Client , customer do not invest into an MFT.

      In other cases, when there is a server requirement,  MFTs are used.  Other file mechanisms can be built, e.g. file mover programs, but they dont assure auditability or tracebility.

      Author's profile photo Jason Scott
      Jason Scott

      I've worked at a number of sap customers and we had incoming files working with PI and no need for an MFT solution. From my experience PI does very well at MFT.

      Author's profile photo Former Member
      Former Member

      Agreed that de-central AE in DMZ can poll for files from external business partners. But Abhishek point is that PI doesn't come with a built-in component like FTP server that other clients can push the files to...PI has always been FTP client but not a server.

      Author's profile photo Former Member
      Former Member

      Hello Abhishek,

      You have quoted some very valid pros and cons of SAP PI over MFS's. So based on your understanding and other practical experiences can you please comment if you have further inputs that:

      With the roll-out of SFTP adapters and the updated FTP/S File Adapters can this be convincingly suggested that SAP PI/PO will now provide the same benefits as provided by Connect::Direct or other Managed File Services especially in terms of:

      • Reliability
      • Security



      Author's profile photo Former Member
      Former Member

      Hello Guys,

      Can any one provide documentation or any helps for integrating MFT with SAP BODS through a Adapter or any other means.

      Thanks in Advance!!