Sage 100

Visual Integrator question. SAGE 100 ERP ver.4.50 PU2. Client has a working VI Payroll import job that imports only time entries and some earnings codes and amounts from a .csv file into Payroll Data Entry. Now they want to take advantage of the new Payroll feature ""Multiple Auto Earnings Codes"" that can be set up in the employee master file. What is the best way to approach this? a) Find the perform logic that kicks off the ""Multiple Auto Earnings"" routine and add it to the VI job? b) Create a VI job that performs the ""Multiple Auto Earnings"" function and chain it before the .csv import? c) Somehow hard code the ""Multiple Auto Earnings"" into the VI job and test the employee master file for the existence of ""Multiple Auto Earnings"" code?

@MichaelMcDonald - based on the time of your post, I certainly hope you weren't losing any sleep over this issue......... Looking forward to someone's response as it is a very interesting question.

@JeffSchwenk - Any recommendation on who in the group of 90 Minds - might be able to guide me in the right direction? Is it correct to assume that when you are importing via Visual Integrator, all built-in Payroll features other than scheduled deductions and payroll taxes are ""turned off"" or not available?

Best bet is someone who can peer under the hood. Alnoor is a good one for that. Also post the issue on The Community. Maybe someone there will respond.

Now all we do is wait....

I'm going to start by asking bonehead questions: 1) Where in Employee Maint do you turn it on (it's eluding me) 2) What does it do?That is how does one benefit from it while they are entering a payroll in Payroll Data Entry

Tab two in employee maintenance

My guess is that since P/R is non-business framework and unfortunately the new features are only available using the standard data entry. In order to take advantage of the new features you will need to add perform logic to the import. (Ie the features need to be written from scratch ). .On the other hand if the module you are importing into is BF then the vi uses the same business object and therefore the features will flow during the VI no perform logic needed. Bummer.

@AlnoorCassim - what the Multiple Automatic Earnings Code does is let's say executives get an allowance for downtown parking of $65 biweekly and all employees both hourly and salaried get a biweekly ""extra pay"" of $50 to help offset out-of-pocket medical expenses. When you startup the Payroll Data Entry these earnings amounts are automatically added to the employee's data entry before you even begin to enter your biweekly hours for hourly employees.

I believe that @JimWoodhead has described the Payroll limitation accurately. So it sound like I get to give my client the wonderful news that ""even though the feature is in Payroll, and is the reason you decided to stick with SAGE software and upgrade to version 4.50. It's going to cost you extra money (feature added by an MD)"". Please don't kill the messenger!

@MichaelMcDonald - Post a recap of your findings on linkedIn. Maybe we can get some action out of Rooker.

I looked under the hood and confirmed the Auto Earnings code found in Payroll D/E is not in PRWVIP (the P/R standard perform logic program). This is actually a common V/I issue with legacy modules. I remember back in 4.10 I had written up 3 bug reports for V/I import into P/O Entry about this same kind of missing perform logic. It was always related to new features in a module that were not co-coded into its corresponding mmWVIP (where mm= module code) perform logic programs. The answer from the well known V/I programmer was always ""V/I was never meant as a full replacement for manual data entry"".

Thanks @AlnoorCassim for your response. When SAGE decided to replace Extended Solution PR-1031 Payroll Data Import Utility with Visual Integrator I was concerned that V/I would not be up to the task. I guess I was right.

Fyi, DSD upgraded the pr-1031 to V4.4 and 4.5 so if your customer owns it you can get it at a reduced cost. It has the same functionality as before. Definitely better then using VI..

@JimWoodhead - This is GREAT news! Can you confirm that PR-1031 in version 4.50 would in fact handle the new features of SAGE 100 ERP Payroll, specifically the new Multiple Automatic Earnings Code processing?

It doesn't looks like it does but contact Jon Reiter and he can let you know what it will take. It looks like SAGE moved the data from PR_AE to PR_15 when they embedded PR-1018 into MAS. So the PR-1031 will need to be updated with the info.