Best Practices for Importing S3 Data

Here are some tips & tricks for using Payroll History import that we have accumulated through our experience with the tool. Our team has been doing this for a while, so maybe this information will save you any trouble that may arise as you use the product. When we extract the data, we use the period end date field on all S3 records or stables. Basically, when it comes to your payment master, PR time, and pay deduction, we use this period end date(year/month) as a selection criterion for extracting those records.

I know we’ve said this before, only you can only export one month at a time. This is to control the sizing, to view those files in Excel, or to process in GHR. You don't want to overload the system with a whole year of data. We have a client where eight months for them is almost four million rows of data. To make it digestible, you can control the size by inputting one month at a time. For the first file, only load maybe 10,000 records. Do not process the pending payment until you have loaded all your files and the process is complete, double checking to be sure any errors are fixed.

That's the key thing here, and this is a good tip to keep in your back pocket. Don't reload a file and then process a pending payment and load the second file. Although it may work, you have no way to back out. Trust me - when you get to a month, you may have different data, you will hit a different error, and then you’ll definitely have no way to back out.

To keep your data integrity intact, load and completely process all your payment and Payroll History Import before moving onto the next one. At the end, complete a pending payment processing. This should go fairly smoothly because you use the import process to bring over your data. Another good tip is that when using your pay code to load this historical data, use a Z code pay code for this process alone, especially with the do not calculate function. This is an Infor recommendation, and there’s no way to get around it. If your pay codes already exist and it's set already to do not calculate, you don't need necessarily to create a Z code for it, but just keep in mind that the key is make sure that you do not calculate.

Back to Blog

Related Articles

The Impact of Interoperability on Healthcare Providers

Aside from patient benefits, improving interoperability would also make healthcare providers’ lives...

Tackling Technical Development in the Cloud

Over the last two weeks, Jean provided great information about what is really going on during a ...

A Logical Approach to Digital Transformation

In my time consulting with companies across industries, I have come to several conclusions. First,...