Skip to Content
Author's profile photo Former Member

Configuring HMRC Interfaces for PI7.31 AAEX

There is lots of information relating to eFiling, other EOY functions and the new RTI for HMRC, however this information only covers systems with ABAP stacks or upto PI 7.3.

I have recently implemented my first PI7.31 Java only stack and my first tasks were creating the HMRC interfaces.

The first thing I knew was that as of version 7.31 there is a new HTTP_AAE communication channel so I was aware I needed to make some changes to the standard content (SWCV EFILING GB 1.0)


Once all the HTTP Channels have been changed to HTTP_AAE you can move over to the Integration Directory.

use the menu and import Model from ES Repository


You then have to configure the scenario assigning the Business Systems to the Templates:


Once complete for all channels, you need to add the communication channels


You need to create the communication channel based upon the Template provided in the ESR Content



You then create all channels until green traffic lights show:


You can then save and activate your scenario.

When creating a scenario using the HTTP_AAE adapter, the majority of the steps are the same.

But before you activate the scenario, you need to ensure that you complete the connection details for HMRC:


you are now ready to test some of your scenarios.

I have a message open with OSS relating to this and will create part 2 after successfully correcting this issue.–part-2

This is my first blog post, so any comments are greatly received.  These are the steps i have run through to configure the HMRC interfaces using the Advanced Adapter Engine eXtended installation of PI7.31. 

Assigned Tags

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

      Hi Barry,

      Good blog. The example you have taken here is Employee_tax_code_update. As far as i remember that the this Scenario uses Soap adpater to connect to gateway. Do they no longer SOAP adapters? Have they moved to HTTP?



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


      the scenario for this instance was SOAP Adapter.  I added a note towards to the bottom mentioning that when you cover a scenario for HTTP_AAE, you need to go and add the details in to the communication channel before you activate.    this information is not held in the ESR like the SOAP Details.



      Author's profile photo Paul Abrahamson
      Paul Abrahamson

      Any response on your OSS Message? We can see that the latest version of E-FILING 1.0 Content is still only XI 7_0 so will need to import this for PI 7.4 Java only scenarios and follow a similar process to you.

      I wonder how converting these configurations to iFlows will look 🙂

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

      Hi Paul

      SAP only said they would update the guides on OSS - however as far as i am aware, they never got updated.  This has been running at a previous client for almost 18 months now and was upgraded as part of EOY activites 2013/2014 and still going strong.

      Let me know how you get on if you do convert the configurations to iFlows.  Maybe worth a blog of your own.