Skip to Content

Configuring HMRC Interfaces for PI7.31 AAEX – Part 2

Part 2 goes into how to make the necessary changes for 2013 (SMP log on required) details the steps to take if you are using the Configuration Wizard.

The standard configured integration scenarios in the delivered content are:


Whilst waiting for SAP to release either content or configuration guides, I had to configure the following scenarios:
Employer Payment Submission (EPS)
Full Payment Submission (FPS)
Employee Alignment Submission (EAS)
Early Year Update(EYU)

First things I did were having to find the 2013 content based upon the documents in the above note.





Then I had to create the associated actions:


I will show EAS as an example (and I based this upon RTI):


The send action:


The Receive Action:


You can now log onto the Integration Directory and consume the scenarios as in my first blog

the same steps are followed for the other scenarios until you have created the following:


during the conversations i had with SAP as i trying to get past an annoying P/S/A error from SAP ECC they ensured me new guides would be available for this content soon.  whether the content gets updated, i am unsure, but in the mean time, hopefully someone can find this blog of use.

You must be Logged on to comment or reply to a post.
  • Hi Barry,

    Thanks for the very informative blog. In our landscape we have PI 7.4 dual stack system and need to configure HMRC interfaces. I have gone through some of the latest guides available on the Service Market Place for RTI scenarios for 2014-15 tax year, and they still talk about the dual stack approach of configuring the HMRC interfaces.

    Would you recommend that we use the dual stack approach in our project or shall we use the single stack approach as explained in your blogs, considering that going forward SAP might stop supporting dual stack PI installations.

    Thank you so much for your help.



    • Hi Jyotika

      if you have the dual stack, it makes sense to continue to use this as normal.

      I wrote this blog as there was no information on SAP (and i still can't find any) for configuring this on a single stack.  You may find that some of the terms are slightly different to the configuration guide provided by SAP, but on the whole, the process is the same.

      I wanted to make people aware of some of the difficulties i faced.

      good luck.


      • Thanks Barry for the reply.

        Please can you guide me through one more query.

        As of now, the BASIS team in my project have enabled PI for SSL, using Java as the SSL provider. I understand that, with the dual stack approach, we will have to import HMRC's certificates onto the ABAP stack of PI (tcode STRUST) and not into the NWA. So would it create any problems if on one hand PI is SSL enabled on Java and the Government's certificates are on the ABAP stack. Please advise.



          • Ok, so just to confirm, we can have PI enabled for SSL on both Java as well as ABAP stacks and import HMRC's certificates into STRUST and have our type G HTTP destinations created in SM59, and the scenarios would work. Please correct me if I am wrong.