Sage 100

Extended Sol - PR1031 Payroll Data Entry Import Utility - upgraded to v 4.50.1 - the GOOD the BAD and the UGLY: The GOOD - months before the release of version 4.5, I was planning (pricing) this upgrade with the client. I would get conflicting responses from SAGE as to would the client need to purchase Visual Integrator because SAGE decided to ""upgrade"" PR-1031 to a VI script instead of incorporating in the Payroll module like was previously announced. Well I waited until my client received their v 4.5 download and found that Visual Integrator was included in their upgrade - GOOD! The BAD - Sage has included five VI import scripts as the replacement for PR-1031, they included scripts for ADP, two Kronos scripts, TIME TRACK, and a script they labeled ""generic"". The five scripts are located in the PR directory in the file PayrollDataEntryImports.EXP. You import this file into VI and can choose which script you will need. HOWEVER, after you import the script into VI you are prompted to compile the script. If you do, you will get a message ""Job validations contain obsolete file references that no longer exist in the dictionary. Job will be deleted."" - The script is automatically erased! This will happen to ALL FIVE scripts! What you have to do is import these scripts into a version 4.30 VI and delete on the validation tab the field CHECK_BANK_CODE. Once you are able to import and compile the VI script in version 4.50 you will need to add the CHECK_BANK_CODE back in. - That's BAD The UGLY - I'm working with the first KRONOS script and trying to get it to import the time entries that were successfully imported in version 4.20 using PR-1031. I cannot get the records to import via VI in version 4.50. The Kronos VI script includes some ""KRONOS"" perform logic that I'm trying to understand. The error message I'm getting is INVALID RECORD OTHER EARNINGS CODE-FIELD$(36,2). - This is UGLY! I long for the days when you could upgrade a McCabe enhancement and it would Just Work! HAPPY THANKSGIVING!

Wow, you would have thought Sage would have learned a lesson when PR VI were impossible to import into v4.4 because of the job cost validations. Guess some things are best to remain consistent. If the client has a fully loaded version of VI, I guess you can always rewrite the import so that it works from the get go (though you shouldn't have to). Are the earnings codes in columns instead of one per row in Kronos? Look on the bright side of this turkey, you now have VI to do lots of other neat things for the client (e.g. import journal entries from Excel, import vouchers into AP, clean up the various databases, import the new pricing grids into the IM, etc.) Go enjoy the football games and cat nap for the Black Friday marathon!!!!!

This is a known VI issue. You will need to delete references to two fields. I think one is cost code. Have to look up details.

I've never had the VI puke on the check bank code reference, only on the JC references. What is surprising is that i thought the VI puked on the JC codes because the client didn't have the JC module when I imported my standed PR VI. So why is the VI hurling over the bank code reference? BTW Pardner (er Wayne), I thought you were lassoing turkeys today and tomorrow?

@Jeff and @ Wayne - Here are the fixes that was used to fix this problem in Payroll version 4.4 PU6 . This was posted here on October 6, 2011: http://www.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=525271 http://community.90minds.com/2010/09/24/why-did-my-mas-90-payroll-import-delete-after-upgrading-to-v44/ I followed these instuctions to get the VI script to load into version 4.50.1. However I believe my problem is something else. @Jeff - A free VI module would be nice for an advanced MAS 90 end user. However my client is a conservative government supported agency. They only use MAS 90 General Ledger, Accounts Payable and Payroll., with Payroll being the most important module. Also, the Kronos output file is an ASCII fixed length type file with three colums of earnings codes per row/line. If each row was a different earnings code, it would be easier to make the VI script work. Thanks for you replies to this posting.

Kronos is pretty good at creating a custom feed.

In the instances where our client's import file had one row per employee with multiple columns for earning codes and hours, we just create an Access database to create one row per earning code. Much easier to import and we don't have to spend time with MAS scripting.

Where to I find, and how do I read the KRONOS perform logic that is shown in this PR_KRONOS VI script: Job Start .../PR/PRWV12;KRONOS_FORMAT_START After Write .../PR/PRWV12;KRONOS_ADDL_RECORDS Before Write .../PR/PRWV12;KRONOS_VALIDATE_ADDL_RECORDS

Very interesting. I just imported the EXP job mentioned above and NOT one blew up as described. My install was a clean install so it appears there are some events that aren't happening across the board.

So was anyone one successful in recreating pr-1031 with VI on v4.5? We are about to run across this issue.

I recreated one of the formats just using VI (client was on 4.4), but I can't tell you which one off the top of my head.

Jim, I haven't seen pr-1031 so I can't speak to it. But I have several clients running a VI import into PR. The key for VI to work is that each line needs to have a different earnings code. So if your import file has one employee per line with five columns of earnings, then you need to message the file into five lines for that employee, each with one earnings code.

Or string a bunch of jobs together, which is what I had to do for this job. Too much work to move it around. (HUGE number of employees)

I don't move it arround. In our situation, we just write an Access db. Import the file, run the macro to manipulate the data, export to a csv file. Takes seconds and you only have one import to run.