Who's Online Now
0 registered members (), 2 guests, and 16 spiders.
Key: Admin, Global Mod, Mod
Newest Members
MANISH KUMAR, Pallavi Negi, SalomeClara, Steph W, Aflexgis
1263 Registered Users
Recent Posts
RUP10 New Functionality
by delboy. 16/01/18 10:56 AM
EDI Replacement
by delboy. 16/01/18 06:33 AM
Happy New Year 2018
by CT. 02/01/18 08:30 AM
Recover an Advanced Grossup Payment
by Steph W. 21/12/17 11:34 AM
Top Posters(30 Days)
delboy 7
pat 1
CT 1
Popular Topics(Views)
433,897 PAYE RTI
51,502 HR_PF.K RUP4
Previous Thread
Next Thread
Print Thread
Rate This Thread
Page 2 of 3 1 2 3
#12014 - 29/08/17 02:30 PM Re: EDI Replacement ***** [Re: PaulD]  
Joined: Mar 2005
Posts: 1,262
delboy Online content
The Grand Daddy
delboy  Online Content
The Grand Daddy
*****

Joined: Mar 2005
Posts: 1,262
Somewhere in South of England
White Paper is now available. Suggests that only direct interface will be available, unless I am missing something. Does anyone know if that's the case. We currently use a third party software and in the short term will have to continue. I assume we will still be able to copy the output file and continue to transmit via this method?

#12057 - 05/10/17 09:19 AM Re: EDI Replacement [Re: PaulD]  
Joined: Aug 2016
Posts: 8
PaulD Offline
lurker
PaulD  Offline
lurker

Joined: Aug 2016
Posts: 8
Woking
The Oracle User Group Public Sector SIG was well attended with a lot of enthusiastic Oracle Local Government and University end users. Here are my notes from the meeting about the EDI Decommissioning changes

EDI Decommissioning

Attendees
Oracle: Alison Ford
HRMS: David Sutcliffe

21st September

Overview

The deadline for changing to the new XML format is April 19th (Last date for 2017/2018 TYE submission). Oracle advised that we pause applying the current version of the patches until the EAP has completed and any revised patches are released. Oracle confirmed that the EDI Replacement patch will include a XML Handshake Solution needed to connect to HMRC Gateway. If required an air gap may still be implemented.

HMRC said that dynamic IP addressing will be in-place for connecting to the HMRC Gateway, a static URL will not be used for security purposes.

XML File Storage Type

The new Oracle Connection Method has the options of
• File System and Database
• Secure Database
Oracle's response was that selecting Secure Database means that no output file is created, this is a security measure to better restrict access to the confidential employee information. If we are implementing an air gap between production and HMRC Gateway we will not want to select this option.

Inbound to HMRC

When running the new versions of the RTI processes (FPS, EPS, AFPS and EYU) there is a Gateway Test Indicator parameter. This allows the following options
• Yes
• No
• Test in Live
The Test in Live option is just that, the transmitted file is acknowledged as valid by HMRC but not credited to the client account.

HMRC Outbound

For the files sent from HMRC Gateway to JLP, items such as new tax codes, P6 and Student Loan notifications, SL1 & SL2, there is no facility to send a test file. Only live files may be sent.

When pulling files such as the P6, which may be sent daily, it is possible to reset the High Water Mark to be able to pull previously selected files. So if the mark was 10,000 on Monday but 12,000 on Friday, resetting it to 10,000 would allow those 2,000 records to be re-extracted from HMRC.

Once the new format linked to the HMRC Gateway account for JLP has been set to XML it cannot be changed back to the old format. This makes the testing of files from HMRC difficult to test outside of production. David did assure the audience that the file format from HMRC have been comprehensively tested (although that does not mean that Oracle will process the file correctly, as he was told by several of the audience members). That will be an issue for Oracle to help resolve but will be an issue for our testing.

*End*

According to oracle document 2262186.1, it appear that the final patch details are as follows
Patch #1D : Final Patch for EDI Decommissioning : Post EAP Program
Patches/Release Date : Tentative : 6th November 2017

Is there anyone out there on the EAP, is so how's it going?

#12060 - 11/10/17 05:33 AM Re: EDI Replacement [Re: PaulD]  
Joined: Mar 2005
Posts: 1,262
delboy Online content
The Grand Daddy
delboy  Online Content
The Grand Daddy
*****

Joined: Mar 2005
Posts: 1,262
Somewhere in South of England
Thanks for the update Paul.

#12061 - 12/10/17 10:27 AM Re: EDI Replacement [Re: PaulD]  
Joined: Aug 2016
Posts: 8
PaulD Offline
lurker
PaulD  Offline
lurker

Joined: Aug 2016
Posts: 8
Woking
We've just had a visit from David Sutcliff, HMRC to answer some questions that we had with the EDI Decommissioning work. We're looking to go live in February with the B2B solution rather than sending the RTI output files to another server and then a 3rd party tfor transmission to HMRC. So once the final EDI patch is released in November we will start our testing.

Here are some updates he provided us.

David said that with compression enabled he expected >100,000 records per 20MB limit on file size. Without compression then his estimate was 25,000 records per 20MB limit. He also said that the file transfer to and from HMRC would be much quicker using XML compared to the old EDI interface. It seems that currently HMRC 'translates' the current EDI file format into XML, which slows the validation process. He also said that certain days of the month will be potentially slower if they coincide with pay dates for big employers, so last day of the month for the civil service for example. Obvious when you think about it!

Another recommendation was to only use the live server and setting the RTI processes parameter Gateway Test Indicator to 'Test in Live' for all testing purposes. This means that only one domain needs adding for development, System Test, UAT and Live. His rational for that was that there may be an issue with sending large files to the test domain as it's only supposed to be used for low volume testing.

Prior to 19th April 2018 the Incoming (from HMRC) files may be switched between the new XML format and the old EDI format. The 19th April is a brick wall, after that the format will be XML only, no going back! If the live domain is used for testing then we can easily reset the high water mark date to assist testing P6 and SL1/2 notifications.

It's sometimes worth looking beyound our Oracle world as there are some large, non-Oracle payroll, employers currently live using the new XML format, so that part of the system works, it just the Oracle part we need to fully test and that is more something under out control, right!? He was actually complementary about Oracle compared to another system supplier!

Hope this is useful

Paul D

#12068 - 23/11/17 11:17 AM Re: EDI Replacement [Re: PaulD]  
Joined: Mar 2005
Posts: 1,262
delboy Online content
The Grand Daddy
delboy  Online Content
The Grand Daddy
*****

Joined: Mar 2005
Posts: 1,262
Somewhere in South of England
Has anyone started testing the official EDI decommissioning patch yet to the point where a test file has been submitted to HMRC.

What's the HMRC URL that you connect to? Do you use your existing government gateway ID and password?

#12071 - 08/12/17 03:34 PM Re: EDI Replacement [Re: PaulD]  
Joined: Jan 2013
Posts: 81
Bagpuss Offline
hacker
Bagpuss  Offline
hacker

Joined: Jan 2013
Posts: 81
Bath, England
We require to carry on sending/receiving files via third-party client software. We've already started testing this in terms of the XML files Oracle Payroll was already able to generate from the outbound RTI processes.

Prior to this set of patches, has anyone successfully processed XML format inbound files from HMRC and, if so, did it require some additional configuration? Unlike the outbound files, the initial test failed (I'll find out more soon) so I was just interested if anyone had already gone down the XML route for the files they were receiving from HMRC and the steps taken?

From reading through the Read Me, a large proportion of the EDI abolition patch content appears to be the B2B functionality which we do not initially intend to use.

#12072 - 11/12/17 11:45 AM Re: EDI Replacement [Re: Bagpuss]  
Joined: Mar 2005
Posts: 1,262
delboy Online content
The Grand Daddy
delboy  Online Content
The Grand Daddy
*****

Joined: Mar 2005
Posts: 1,262
Somewhere in South of England
Originally Posted by Bagpuss
We require to carry on sending/receiving files via third-party client software. We've already started testing this in terms of the XML files Oracle Payroll was already able to generate from the outbound RTI processes.

Prior to this set of patches, has anyone successfully processed XML format inbound files from HMRC and, if so, did it require some additional configuration? Unlike the outbound files, the initial test failed (I'll find out more soon) so I was just interested if anyone had already gone down the XML route for the files they were receiving from HMRC and the steps taken?

From reading through the Read Me, a large proportion of the EDI abolition patch content appears to be the B2B functionality which we do not initially intend to use.


So, are you sending XML files via your current third-party client software. What software do you use as we may have to purchase something new?

#12075 - 15/12/17 03:09 PM Re: EDI Replacement [Re: PaulD]  
Joined: Dec 2017
Posts: 3
Steph W Offline
stranger
Steph W  Offline
stranger

Joined: Dec 2017
Posts: 3
Hi All,

We have just completed the EDI Decommissioning setup in a non production environment and we are planning on using the B2B solution. We will hopefully start UAT shortly so will keep you posted on how we get on with the file submissions!

:eek:

#12086 - 12/01/18 10:58 PM Re: EDI Replacement [Re: delboy]  
Joined: Jan 2013
Posts: 81
Bagpuss Offline
hacker
Bagpuss  Offline
hacker

Joined: Jan 2013
Posts: 81
Bath, England
Originally Posted by delboy
Originally Posted by Bagpuss
We require to carry on sending/receiving files via third-party client software. We've already started testing this in terms of the XML files Oracle Payroll was already able to generate from the outbound RTI processes.

Prior to this set of patches, has anyone successfully processed XML format inbound files from HMRC and, if so, did it require some additional configuration? Unlike the outbound files, the initial test failed (I'll find out more soon) so I was just interested if anyone had already gone down the XML route for the files they were receiving from HMRC and the steps taken?

From reading through the Read Me, a large proportion of the EDI abolition patch content appears to be the B2B functionality which we do not initially intend to use.


So, are you sending XML files via your current third-party client software. What software do you use as we may have to purchase something new?


Apologies for delay in replying - three weeks off and forgot all about this post (and pretty much everything else!).

We currently send and receive in EDI format. We already upgraded our client software to get XML tested and tried an outbound file from Oracle Payroll in XML (prior to the decommissioning patches) and it passed the HMRC test successfully.

However, I was just curious why our operations team weren't able to upload the inbound XML files into Oracle Payroll as easily. Prior to diving in, I was just interested if anyone has already started using inbound XML files (prior to Oracle adding B2B and removing EDI formats).

Anyway, the patches will change things again so it's only my curiosity. We use AVCO Systems' software and, so far, it all seems to be working nicely - we'll test the inbound XML files once we've applied the Oracle patches and configuration.

So far, so good...

Last edited by Bagpuss; 12/01/18 11:14 PM.
#12087 - 15/01/18 06:39 AM Re: EDI Replacement [Re: Bagpuss]  
Joined: Mar 2005
Posts: 1,262
delboy Online content
The Grand Daddy
delboy  Online Content
The Grand Daddy
*****

Joined: Mar 2005
Posts: 1,262
Somewhere in South of England
Originally Posted by Bagpuss


We currently send and receive in EDI format. We already upgraded our client software to get XML tested and tried an outbound file from Oracle Payroll in XML (prior to the decommissioning patches) and it passed the HMRC test successfully.

However, I was just curious why our operations team weren't able to upload the inbound XML files into Oracle Payroll as easily. Prior to diving in, I was just interested if anyone has already started using inbound XML files (prior to Oracle adding B2B and removing EDI formats).

Anyway, the patches will change things again so it's only my curiosity. We use AVCO Systems' software and, so far, it all seems to be working nicely - we'll test the inbound XML files once we've applied the Oracle patches and configuration.

So far, so good...


Thanks for that. Seems that AVCO and ODEX are the two front runners for the software. Hopefully, we won't be far behind you in testing the files using one of these companies.

Last edited by delboy; 15/01/18 06:39 AM.
Page 2 of 3 1 2 3

Moderated by  CT, delboy 

Forum Statistics
Forums48
Topics2,200
Posts11,895
Members1,262
Most Online90
Mar 5th, 2017
Today's Birthdays
No Birthdays
Recent vacancies
Top Posters(All Time)
CT 2,088
bcooper 1,285
delboy 1,262
paulgos 431
SBi 425
Gus 252
pat 250
vkumar 223
January
S M T W T F S
1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.025s Queries: 16 (0.006s) Memory: 2.8172 MB (Peak: 3.0179 MB) Zlib disabled. Server Time: 2018-01-18 11:56:44 UTC