Sage 100

Preconfigured Payroll Import Jobs (4.5+). Has anyone used these? I just re-realized the other day that the 4.5 release contains the following; completely had forgotten about it: Select Preconfigured Payroll Import Jobs: Five preconfigured import jobs are now available to select when importing payroll data using the Visual Integrator module. PR_ADP is configured to import delimited files in the ADP Paydata format. PR_FORMAT_2 is configured to import ASCII files that use a fixed field format and include a job number. PR_KRONOS is configured to import ASCII files in the Kronos Connect and Time Bank format. PR_KRONOS_NO_DP is configured to import ASCII files in the Kronos Connect and Time Bank format. PR_TIMETRAK is configured to import ASCII files in the Timetrak version 8.0 format. To make the jobs available in Import Job Maintenance, use the Job Import task to import the PayrollDataEntryImports.exp file, which is available in the \MAS90\PR folder. For more information, see Import Preconfigured Payroll Import Jobs in the Help system.

I have used the PR_FORMAT_2 and the PR_KRONOS import jobs. WARNING your mileage may vary. I had to make adjustments to the imports to make them work. Also there are several KB technical notes regarding the KRONOS formats, You will want to review those if working with the KRONOS import. I have several clients using Payroll VI imports. Let me know if you need help.

Used to be an issue with PR VI jobs regarding a dictionary problem that at one time required a manual fix. I know I ran into it once or twice on upgrades. Just an FYI - have no idea if it's still an issue but if you run into any funny errors or failure to import start searching the archives because I know a few of us ran into it (do not know if the pre-written VI jobs were impacted).

Also as a side note: If you have a client that is using a Payroll Extended Solution that calculates say a special limit on deductions during Payroll Data Entry. Be aware the Extended Solution may not work when you move to a VI import. You may have to have the Master Developer write additional VI Perform Logic to ""trigger"" the Extended Solution during the VI import.

I had a horrible time trying to get the preconfigured jobs to work properly. I think they were written as a very basic import job and not as a true replacement for the extended solution. I finally had my client renew the maintenance on their extended solution and continue with that.