Sage 100

My client is on Sage 100 2017.  We import new employees from multiple states, including some states (TX for example) that do not have state taxes.  The import brings in Employee data (PR1), Fed Tax Data (PR3), State Tax Data (PR3), etc., in that order.  For WA, a manually entered PR3 record will have "WA " for the State Code and the Filing Status is blank.  When I import the state record for WA employees, I provide either an empty string (as I do successfully with TX state records)  or a 3 space string for the filing status.  To my dismay, the import overrides my value by forcing the Filing Status from the Filing Status field in the Federal record.  Then, the VI job log shows all these records as invalid records.  The log says that 'none are imported", but imports them anyway with the erroneous filing status.  If that wasn't enough fun, the VI job log also shows a "PR_40 PERFORM FAILED SEE ACTIVITY LOG".

I asked Sage if they could check the perform logic to determine if something special was being done with WA state records.  They said, "That's not the kind of thing they do.", and I should check out Sage City.

Has anyone run across this with WA, or is there some way for me to view the perform logic to see if the filing status is being forced on WA records for some reason?

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------

Have not had to deal with this before. Can you import an asterisk in the “Filing Status Ok?” field? Perhaps it’s trying to calculate something, obviously in error, and with that value it won’t calculate.

Michelle Taylor
ERP Consulting Manager
CS3 Technology
918-388-9772

------Original Message------

My client is on Sage 100 2017.  We import new employees from multiple states, including some states (TX for example) that do not have state taxes.  The import brings in Employee data (PR1), Fed Tax Data (PR3), State Tax Data (PR3), etc., in that order.  For WA, a manually entered PR3 record will have "WA " for the State Code and the Filing Status is blank.  When I import the state record for WA employees, I provide either an empty string (as I do successfully with TX state records)  or a 3 space string for the filing status.  To my dismay, the import overrides my value by forcing the Filing Status from the Filing Status field in the Federal record.  Then, the VI job log shows all these records as invalid records.  The log says that 'none are imported", but imports them anyway with the erroneous filing status.  If that wasn't enough fun, the VI job log also shows a "PR_40 PERFORM FAILED SEE ACTIVITY LOG".

I asked Sage if they could check the perform logic to determine if something special was being done with WA state records.  They said, "That's not the kind of thing they do.", and I should check out Sage City.

Has anyone run across this with WA, or is there some way for me to view the perform logic to see if the filing status is being forced on WA records for some reason?

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------

I tried the asterisk, and it still forced the FilingStatus.  Is there a specific order the "Filing Status ok" asterisk must be within the state import to get it to work?  I haven't used that before.

For now, I have added the Federal Filing Statuses to the WA tax table and the state records are importing without error.  Just not sure what effect there might be down the road, if any.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------

Original Message:
Sent: 05-14-2019 21:44
From: Michelle Taylor
Subject: Employee Import to PR1, PR3 where employee works in Washington State.

Have not had to deal with this before. Can you import an asterisk in the "Filing Status Ok?" field? Perhaps it's trying to calculate something, obviously in error, and with that value it won't calculate.

Michelle Taylor
ERP Consulting Manager
CS3 Technology
918-388-9772


Original Message------

My client is on Sage 100 2017.  We import new employees from multiple states, including some states (TX for example) that do not have state taxes.  The import brings in Employee data (PR1), Fed Tax Data (PR3), State Tax Data (PR3), etc., in that order.  For WA, a manually entered PR3 record will have "WA " for the State Code and the Filing Status is blank.  When I import the state record for WA employees, I provide either an empty string (as I do successfully with TX state records)  or a 3 space string for the filing status.  To my dismay, the import overrides my value by forcing the Filing Status from the Filing Status field in the Federal record.  Then, the VI job log shows all these records as invalid records.  The log says that 'none are imported", but imports them anyway with the erroneous filing status.  If that wasn't enough fun, the VI job log also shows a "PR_40 PERFORM FAILED SEE ACTIVITY LOG".

I asked Sage if they could check the perform logic to determine if something special was being done with WA state records.  They said, "That's not the kind of thing they do.", and I should check out Sage City.

Has anyone run across this with WA, or is there some way for me to view the perform logic to see if the filing status is being forced on WA records for some reason?

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------

Are two blank spaces getting imported or is it just an empty field?

------------------------------
Robert Wood
Consultant
90 Minds
Ocala FL
352-615-5898
------------------------------

Original Message:
Sent: 05-15-2019 09:39
From: Chris St. Amand
Subject: Employee Import to PR1, PR3 where employee works in Washington State.

I tried the asterisk, and it still forced the FilingStatus.  Is there a specific order the "Filing Status ok" asterisk must be within the state import to get it to work?  I haven't used that before.

For now, I have added the Federal Filing Statuses to the WA tax table and the state records are importing without error.  Just not sure what effect there might be down the road, if any.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------


Original Message:
Sent: 05-14-2019 21:44
From: Michelle Taylor
Subject: Employee Import to PR1, PR3 where employee works in Washington State.

Have not had to deal with this before. Can you import an asterisk in the "Filing Status Ok?" field? Perhaps it's trying to calculate something, obviously in error, and with that value it won't calculate.

Michelle Taylor
ERP Consulting Manager
CS3 Technology
918-388-9772


Original Message------

My client is on Sage 100 2017.  We import new employees from multiple states, including some states (TX for example) that do not have state taxes.  The import brings in Employee data (PR1), Fed Tax Data (PR3), State Tax Data (PR3), etc., in that order.  For WA, a manually entered PR3 record will have "WA " for the State Code and the Filing Status is blank.  When I import the state record for WA employees, I provide either an empty string (as I do successfully with TX state records)  or a 3 space string for the filing status.  To my dismay, the import overrides my value by forcing the Filing Status from the Filing Status field in the Federal record.  Then, the VI job log shows all these records as invalid records.  The log says that 'none are imported", but imports them anyway with the erroneous filing status.  If that wasn't enough fun, the VI job log also shows a "PR_40 PERFORM FAILED SEE ACTIVITY LOG".

I asked Sage if they could check the perform logic to determine if something special was being done with WA state records.  They said, "That's not the kind of thing they do.", and I should check out Sage City.

Has anyone run across this with WA, or is there some way for me to view the perform logic to see if the filing status is being forced on WA records for some reason?

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------

For the Filing Status, I have tried 3 and none.  Neither works, although Texas, which is similar to Washington, works with none (empty string).

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------

Original Message:
Sent: 05-15-2019 12:29
From: Robert Wood
Subject: Employee Import to PR1, PR3 where employee works in Washington State.

Are two blank spaces getting imported or is it just an empty field?

------------------------------
Robert Wood
Consultant
90 Minds
Ocala FL
352-615-5898
------------------------------


Original Message:
Sent: 05-15-2019 09:39
From: Chris St. Amand
Subject: Employee Import to PR1, PR3 where employee works in Washington State.

I tried the asterisk, and it still forced the FilingStatus.  Is there a specific order the "Filing Status ok" asterisk must be within the state import to get it to work?  I haven't used that before.

For now, I have added the Federal Filing Statuses to the WA tax table and the state records are importing without error.  Just not sure what effect there might be down the road, if any.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems


Original Message:
Sent: 05-14-2019 21:44
From: Michelle Taylor
Subject: Employee Import to PR1, PR3 where employee works in Washington State.

Have not had to deal with this before. Can you import an asterisk in the "Filing Status Ok?" field? Perhaps it's trying to calculate something, obviously in error, and with that value it won't calculate.

Michelle Taylor
ERP Consulting Manager
CS3 Technology
918-388-9772


Original Message------

My client is on Sage 100 2017.  We import new employees from multiple states, including some states (TX for example) that do not have state taxes.  The import brings in Employee data (PR1), Fed Tax Data (PR3), State Tax Data (PR3), etc., in that order.  For WA, a manually entered PR3 record will have "WA " for the State Code and the Filing Status is blank.  When I import the state record for WA employees, I provide either an empty string (as I do successfully with TX state records)  or a 3 space string for the filing status.  To my dismay, the import overrides my value by forcing the Filing Status from the Filing Status field in the Federal record.  Then, the VI job log shows all these records as invalid records.  The log says that 'none are imported", but imports them anyway with the erroneous filing status.  If that wasn't enough fun, the VI job log also shows a "PR_40 PERFORM FAILED SEE ACTIVITY LOG".

I asked Sage if they could check the perform logic to determine if something special was being done with WA state records.  They said, "That's not the kind of thing they do.", and I should check out Sage City.

Has anyone run across this with WA, or is there some way for me to view the perform logic to see if the filing status is being forced on WA records for some reason?

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------