Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Deductions Did Not Con...
Microsoft Dynamics SL (Archived)

Deductions Did Not Convert from 4.21

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee
Client "self-serviced" an upgrade from 4.21 to 2011. Afterwards, they received some errors calculating payroll and also noticed that the Employee History screen showed no deduction details prior to 2014. After doing some digging, I found that the Deduction table only has entries for 2014. Apparently the deductions did not convert correctly. Client did not check the log file after converting. I looked back at the raw deduction data from 4.21 and noticed that there was no CalYr field (obviously a change in methodology by SL). That shoots down my idea of using DTS to migrate the data... Any ideas would be greatly appreciated! Mike Lee mike.lee@itemllc.com

*This post is locked for comments

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Deductions Did Not Convert from 4.21

    I wrote a script to insert new records into Deduction based on existing Deduction records, modifying the CalYr field and created Deduction records for 2004-2013.  This worked because they never deleted detail in payroll, and the EarnDed table still had all of the entries back to 2004.  Employee History is now working.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Deductions Did Not Convert from 4.21

    The EarnDed table in the converted db has records all the way back to 2004.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Deductions Did Not Convert from 4.21

    Hi Elaine,

    SL is used only for payroll.  They hope to abandon SL and move to another package within 6 months.  The server housing version 4.21 is failing, so they thought that they would cover their backsides by getting 2011 running on another box.  So they need to be able to generate checks and inquire on history, but they don't anticipate generating any W-2's.

    Unfortunately, I remember all too well how the process worked in the DOS product!  Yes, you are correct though.  They obviously closed the 2013 payroll year in 4.21 BEFORE upgrading, thus no 2013 Deduction records.

    Mike

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Deductions Did Not Convert from 4.21

    Hi Mike,

    While I didn't support 4.21, if you don't have a calyr in your table, then you only had one year's records - the current year.  This is the way it worked  back in the DOS version prior to 4.21.    You had to either process W2s before you closed PR for the year or make a backup before you closed the year which you could restore to do W2s. Since the year is already closed and no W2s were processed,   a backup from prior to PR year end close will need to be restored. You can restore to a different application database name and keep your live, go forward database running as is.

    The W2 information is stored in the Earnded table.  No calyr in that table means  that it was zeroed out when closing PR for the year while still in 4.21.  

    Do you have an Earnings and Deduction report from the end of the year.  Maybe you could use that to determine the subjwages  and deduction amt.  Or,   could you use the Check Register to get your YTD numbers and then manually calculate the W2 amts.  Then you could enter these into W2 history while in Initialization mode.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Deductions Did Not Convert from 4.21

    Carolyn,

    Thanks for your input.  Very helpful.  So currently in the converted database, the Employee History screen does not show any deduction details for 2013 and prior, but does show them for 2014. Do you expect that loading the payroll tables will resolve this?  They have tran records back to 2004.  I wonder if I can DTS the tax tables from the old version...

    Also, in the upgraded db, calculating payroll seems to always result in error 14097 involving either a garnishment or a cafeteria plan deduction.  I have set the deduction sequence on everything in accordance with some KB article I found and fixed some Exemption/Credit ID's that mirrored the related Deduction ID, but the problems persist.  And everything seems to be applied to All Locations.  Any thoughts?

    Mike

  • Carolyn Kolpien Profile Picture
    Carolyn Kolpien on at
    RE: Deductions Did Not Convert from 4.21

    Hi Mike,

    I forgot to add that usually when you close payroll, all the deductions come forward into the new year so users don't need to create their deductions every year.  But in your client's case, to create the 2013 deductions, they will need to load the payroll tax tables and recreate the user entered deductions.  When they close 2014, they won't have this problem.

  • Carolyn Kolpien Profile Picture
    Carolyn Kolpien on at
    RE: Deductions Did Not Convert from 4.21

    Hi Mike,

    You are correct.  The CalYr field was added to the Deduction table and deductions are created for any given year by loading the tax tables.   To create most of the deductions for 2013, you can just load the payroll tax tables and put 2013 into the Calendar Year field.  Any other deductions that were set up by your client, such as 401K etc would need to be re-added in Deduction Maintenance for 2013.  They could use the 2014 deduction as an example.  I hope this helps.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,401 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans