Top PeopleSoft Jobs

Showing posts with label Time and Labor. Show all posts
Showing posts with label Time and Labor. Show all posts

PeopleSoft PeopleBooks

Thursday, February 11, 2010

Question:


Where can i find Documenation like PeopleBooks related to PeopleSoft?


Answer:

Check the below link that would give you links to PeopleBooks for PeopleSoft Application 9.0, 8.x versionsand PeopleTools 8.4x




Share/Save/Bookmark

Read more...

TL_TIMEADMIN runcontrol Process Thru Date

Question:

I have a question regarding TL_TIMEADMIN runcontrol.

Our end users are convinced that the 'Process Thru Date' is not an important piece of the runcontrol, and that it does not matter what it is. We do check the 'Use Reported Time for POI'. We do NOT check 'Use Current Date'.

In the past, when I've filed cases with Oracle/Metalink/GSC, I was told repeatedly by them to use the last day of the current pay period. However, our end users say that a consultant told them that date did not matter and to put anything in there.

We have multiple issues that this creates. One, the earliest change date doesn't get updated properly, creating a larger period of interest when TL_TIMEADMIN runs the next time.

We have other issues that we are dealing with, and we are up to 253 batches (Utopian batch count for our org would be about 8!) While I cannot blame all of the issues on the runcontrol Process Thru Date, I don't think this is helping and is causing extraneous issues which we don't need.


I have ran multiple traces, and that date is used repetively in that app engine. Has anyone else ever dealt with this issue?

Does anyone feel this field is unimportant? Granted, people are getting paid, but it does leave extraneous issues. And, it is against what Oracle says to do. Can anyone give me specifics of issues they have encountered when that date is off?

Answer:



Here's some explantion about the Run Control Fields when you submit the Time Admin Process:

• You must select the Forecast Payable Time option to use the results of the Time Administration process for budgeting or other business purposes, but not send the results to payable time.
• You would check the Use Reported Time for POI option to have the system consider reported time after the process date; if this option is not selected, the system uses the earliest change date and the current workgroup period to calculate the period of interest.
You will select the "Use Current Date option" to use the current system date for processing, or enter a date in the Process Date field to use that date instead. The system selects time reporters with an earliest change date that is equal or less than the specified date.

For Example, if you are processing Payroll Till 09/30/2009, but an employee submits his vacation hrs for October 1st week which is for Future time, If the Use Reported Time for POI option is selected, the system includes the future vacation time in its calculations. Clear the check box to have the system ignore the future time.
How Time ADmin Processes with ECD / Process Date:The system processes only time reporters whose Run Time Administration field is Y and whose Earliest Change Date field is less than or equal to the current or process date specified on the TA Run Control page. You can set the run control date to either the current date or another date (the process date) depending on whom you want to process and what periods you want to process.

We usually put the process date as the Pay End Date. For Example, if we are processing Bi-Weekly payroll, and for week1 time entries, we put the week1 end date, and for week2, we put the Pay End Date. we DO NO select the Use Reported Time for POI option at all.

So, it is an Important field if you are not using "use current date"; and I believe whatever Oracle has said equally important..

Hope this helps

Share/Save/Bookmark

Read more...

User Exits in Time and Labor

Question:

how to use user exits in TL rules?Hi, We are planning to use User Exits in T & L. This is what we did:Added a section in TL_TA_RULES AE prgram - Test01Then in Rule ID creation we used user exits - Test01 mapped to AE section - Test01. Now in the rule program we are not able to find this RULE ID. So how will this Peoplecode Rule ID be triggered if we are not able to attach it in the Rule Program? Are we missing something here?Please suggest.

Answer:


In Time and Labor, there are 4 different ways to create TL Rules. One of them is by using User Exit.

What is a User Exit?
Time and Labor User Exits are simply rules that you develop outside of the Time andLabor rules interface. Instead of compiling a rule to create an AE section, you create theAE section first, and then perform a few additional steps to register the section as a rulein Time and Labor.
One of the main reason to use User Exit in TL is to exploit the rich benefits the App Engine Programming Offers which is basicallyPeopleCode. Also, you would prefer it, if you are expert/comfortable in AE programming; Whenever any program is processed, you would want some log activity put in Process Monitor message log files, so you can also include this in User Exit. when you build rules through other online tools methid, there is no log activity for the rule you develop.
When you write user exits, you must add AE sections to the AE program TL_TA_RULES. You can use all the AE constructs supported by PeopleTools (SQL, PeopleCode, looping constructs like Do When, Do While, and so on).

Steps to create user exit:1.Create an Application Engine section with steps and actions to process the rule.Open TL_TA_RULES in Application Designer, and insert a new section and add your rule logic using SQL, PeopleCode, looping constructs like Do When, Do While etc. You must have the Public Access Checked on the section name as shown below:If this option is NOT selected, Time Administration will end abnormally with a message indicating that the rule does not allow access.


2. Define the AE Section in Time and Labor.Select Set Up HRMS, Product Related, Time and Labor, Validation Criteria, AE Section Definition. Here you add a new value, and enter the AE section as a User Exit.

3. Create the rule definition.Select set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Rules. Add a new value, and make sure to check the User Exit checkbox. The AE Section Name field must match the actual section name for the rule.


4. Add the rule to a rule program.Add the rule to a rule program.




During Migration of TL Rules:If you have written user-exit rules, you will need to include those AE Sections along with AE Steps from AE program: TL_TA_RULES in a project to be exported/imported (copied).

Share/Save/Bookmark

Read more...

About This Blog

Have you got a PeopleSoft Question? Post it in the forums section or in your preferred place or in comments section, so that we can answer it for you in detail with screen shots;

Learn PeopleSoft functionality and how to use the setups and process flow offered in different modules;

Hope this would give you some ideas...

Blog Archive