Skip to Content

Traditionally any SAP HR implementation, will involve multiple interfaces. These interfaces are typically with Benefit, Time or Recruitment based systems.  The key business characteristics of such interfaces are

  1. Transmission of PII (  personal information, including Social Security Numbers, Salary etc.) data
  2. Ability to secure information both at rest and in transit
  3. Ability to transmit high volume of data, typically around employee demographics
  4. Predominantly file based interfaces

I have been a part of a few such implementations and observe that customers continue to use legacy file transmission processes (mostly FTP scripts etc.) for SAP integration and have not been very keen to use SAP PI.  The major concern was the inability of PI (until recently) to support their strong security needs, along with issues related to high volume data transfers.

 

In my opinion this leads to the following:

  1. A un-managed integration model, which involves multiple FTP programs, causing a maintenance nightmare
  2. Lack of central monitoring
  3. In ability to support orchestration requirements
  4. High effort to implement non-traditional ( non-file based integration) with cutting edge systems supporting cutting edge technologies like Cloud connectors, Rest based servers etc.

With the recent developments on functionality SAP PI can really be a Savior !

 

The following features can really help meeting the requirements:

  • Security in Transmission

With the availability of the B2B Add-on, SAP PI supports an SFTP adapter for SSH based communication.  This is in addition to SSL based FTPS communication which is available with the  vanilla FTP adapter.   These protocols support the requirements for security in transmission. To add, there is no additional cost associated with the SFTP adapter.

 

  • Security at Rest

Along with security in transmission, there is always a requirement to have encrypted files both within the network and externally. SAP PI supports a PGP module which can be used for the same.

 

  • Re usability – Publish Subscribe Model

HCM customers integrate with multiple vendors for business functions like employee benefits. Most of these vendors require employee demographic information (something like employee master data). SAP PI can be used as a publish-subscribe bus, with ECC generating the data via a generic interface, and PI mapping and transforming it to vendor format

  • Cloud Integration/Availability ( Success Factors)

With the advent of Success Factors which is a new cloud based offering from SAP to support global HR foundation spanning across the recruit to retire cycle along with advanced analytic,  SAP back-end system need to connect to this cloud based offering.  This integration is possible via an on -premise or a on-demand PI solutions.  There is standard SAP content available for this, and the integration is via the SOAP – Axis/SFTP adapters

 

This is in addition to consolidated Solution Manager based monitoring for PI and the Application systems, including defining of Alert Rules for critical interfaces like Payroll.

 

Overall this brings in the best practices to integration mechanisms by supporting the development of a consolidated message broker.

The additional cost that might be associated with PI, can be far more lesser than managing an unorganized interfacing architecture.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Jose Nunes

    I’m currently working on the PI implementation of HR integration with 13 different suppliers, 36 interfaces and I agree with you when it comes down to the technology involved with the integration of legacy systems.

    Five of these thirteen interfaces were file based due to the lack of investment on new API technologies by the legacy systems. As we don’t have the B2B AddOn installed on our systems, we chose to use FTPS in our integration scenarios where file was the only option available. One of these file interfaces is here just because the PI is not able to fully comply with a vendor REST API out-of-the-box.

    Regarding security, all the communications uses SSL/TLS, SNC to protect the communication from eavesdropping and all strictly confidential data is encrypted at the HR/HCM side using SSF library and decrypted at the receiver side, using public/private key. This was also required as we didn’t wanted to have strictly confidential data lying on PI unprotected, even having policies that prevent the payload visualization for 1st and 2nd support level.

    Right now we are planning on using the SuccessFactors Integration Package Add-On. As we’re in the decision phase, we’re considering joining the ramp-up phase for the version 2.0 but nothing is really defined yet.

    (0) 
    1. Abhishek Vinayaka Post author

      Hi Jose,

      I agree, PI can bring a paradigm shift for legacy HR integration. Just a few more points

      The SFTP/PGP add-on is actually a free install from SAP.  In general SFTP is a more robust protocol as compared to FTPS, you might want to try that option

      for the Rest integration, though Advantco Rest Adapter suits best, some work arounds can be done using the SAP PI SOAP – AXIS adapter as well

      Regards,

      Abhishek

      (0) 

Leave a Reply