The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
For the first part of this, let us look at the select statement for a single employee for a single check date. Below is the initial code.
inner join UPR30300 on UPR00100.employid = UPR30300.EMPLOYID
where UPR00100.employid = 'ACKE0001'
and UPR30300.CHEKDATE between '02/01/2014' and '02/01/2014'
Now, before you mention anything, yes, I have left out all the good UPR00100 stuff like the employees' first name, last name, etc. Let us concentrate on just getting these two tables connected; you can add the other fields later.
While this appears to work and for my TWO database it does return six records, to know what an employee actually make you cannot just add UPR30300.UPRTRXAM together and get the right number.
You must understand a little bit more about the UPR30300 table and what it contains.
For instance, notice the UPR30300.PYRLRTYP field. This field is incredibility important.
If the value of this field is equal to "1" then that is PAY to the employee. Notice I typed PAY, if you have an employee reimbursement, on a check, even though we all know that an employee reimbursement is not taxable, it is still PAY on the check itself. In other words, the amount is a positive amount of money due to the employee.
If the value of this field is equal to "2" then that is a deduction, in other words the amount is a negative amount of money due to the employee.
If the value of this field is equal to "3" then that is a benefit, in other words it is an amount of money paid on behalf of the employee, by the employer, to someone else like an insurance company. Thus, it does not affect the amount of the check at all.
If the value of this field is equal to "4" then that is the State Taxable amount. Yes, the UPRTRXAM field is the amount of State TAX withheld. Also notice, that when this field is equal to "4" the TXBLWAGS field has an amount in it. This amount is the amount of taxable wages for the state represented in the PAYROLCD field.
Now I did not get into local or city taxes, however, I am sure you can look at you own physical check and this table and figure out the codes, if not feel free to drop me a line. In addition, I did not get into things like FICA, Federal Tax, Tips, and such but I will save that for another time.
Table of Contents
Business Applications communities