If you are managing PeopleSoft HRMS environment, tax update is one of the important and routine procedure which you would be doing mostly once every two or three months. One of the uniqueness of HRMS applications is that it involves pay calc run very 15days (in US it is 15 days and other countries it may be once a month) and every pay calc is crucial as it involves every employee of the company including the top executives.

If the pay calc was wrong and the pay checks were sent out and the Bank files are transferred, then it takes lots of effort from the entire team to fix it back, besides the beatings from the management.

For that matter, if the pay calc does not go through well on time, even then it becomes visible in the company.

So tax update and testing them thoroughly before implementing in production and run the first pay calc just after the tax update would be very important.

I have put together a document, which I use to make sure that I do not miss anything before every tax update.

If you are Administrator or Business Analyst or Developer you may want to go through the document to make sure that each tax update goes through smoothly at your work place.

Here is the  link to the document. Feel free to write your comments if you feel anything can be added to it or anything is not required.

Take a look at the discussion about tax updates in the forum. You could post your comments/questions either here or in the forum.

To know more about Tax update Functional Fundas click here

Comments (4)

	1. 04-18-2008 17:58
	The list of testing taxupdates is good one. Many times we do not test all of them and get into trouble.    It is a good list to go for. Guest

Glen

	2. 04-22-2008 15:19
	Can you provide me the list of processes which are important to run/hold before or after the tax update? Guest

GOGET

	3. 04-22-2008 22:23
	There is no specific process or job that is been run by all the clients.  Some places a process might be run once a week, while some clients might run it twice a day.    But this is the basic way to check and hold them.    Go to People Tools--> Process Scheduler --> Process Monitor and query all the processes that are queued for next 99 days. Go through the list if there is any process that is scheduled during the tax update down time.     Then put that process on hold and after the tax update is completed and all testing comes ok, then release those processes/ jobs put on hold in the same sequence.    Also take a look at the list of "Scheduled Jobset Definitions" as they do not get scheduled and they get kicked off at the particular time.    Also check the backend interface jobs/crons including the backup jobs and make sure they are affected during the down time. http://psadmin.org Registered

RD

	4. 04-29-2008 17:03
	Thanks. good. Guest

GOGET

Write Comment

Thankyou for your comments. Feel free to comment if there are any mistake in the postings also. If you have a Blog or website, feel free to provide the link. We will take a peak. Just ensure to *Refresh* your browser for a new security code to be displayed prior to clicking on the 'Send' button. Keep in mind that the above process only applies if you simply entered the wrong security code.
Name:
Homepage
BBCode:
Comment:
Code:*
	I wish to be contacted by email regarding additional comments

Copy Right: AKOComments v.1.4.6