Pay Proration Rules

Question: How does Proration rules work in Payroll:

Answer:

Effective Date:

The effective date is critical in determining how an employee is paid. When you hire an employee, the effective date becomes the hire date and the original hire date. If an employee is hired in the middle of a pay period, the system automatically calculates the percentage of pay that the employee is due, and creates a corresponding paysheet entry.

Similarly, if you add an entry to an employee's job record, such as a promotion or pay rate change, and that change goes into effect in the middle of a pay period, the system creates two pay earnings entries on the paysheet and prorates the earnings accordingly. The system stores rules for proration on the Pay Group table.

When the effective date falls in the middle of a pay period, the paysheet process prorates the employee’s pay for the period by creating additional pay earnings records. Earnings are prorated for all frequencies. Proration rules in Payroll for North America process a single week at a time, Sunday through Saturday. Because of this, problems with proration may occur with employees whose schedule may not fit this pattern.

Proration Rules

An employee is considered eligible for partial pay whenever a job record has an effective date in the middle of a pay period. The system uses work schedule to determine the number of workdays per year and the number of workdays per week.

Mid-period Job Changes

On the Pay Group table, specify a work schedule and a proration rule to calculate prorated pay when there is a partial pay period due to mid-period job changes:

An employee is considered eligible for partial pay whenever a job record has an effective date in the middle of a pay period.Mid-period job changes that can cause partial pay include hiring, termination, or pay data changes. Transfers and promotions might result in pay data changes.

Elements of the Proration Calculations :

The work schedule and proration rule work together to calculate prorated pay. Other factors are the employees standard hours and standard work period, and frequencies specified on the Pay Group table.

This table defines the variables used in the proration rule formulas:

Proration Rules for Mid-pay Period Changes

Salaried Proration Rule and Hourly Proration Rule options on the Pay Group table define how earnings and hours are prorated during paysheet creation for employees eligible for partial pay.

• The system creates a separate pay earnings record with the corresponding hours or earnings for each part of the pay period.
• When an employee is transferred to a new pay group, the system pays the employee for the correct number of hours based on the effective dated change.
• When an employee transfers to a new tax location in the middle of a pay period, the system creates a separate pay line for each state, locality, or both on the paysheet.
• The system uses the work schedule and proration rules on the Pay Group table during paysheet creation to determine how to break out the earnings.

Pay Proration Rules

Read more...

PeopleSoft Document Resources

Helpful PeopleSoft Documents (PeopleTools/Technical Related) from Metalink:

Red Paper Topic	Description	Meta Link
Online Performance Configuration Guidelines for PeopleTools 8.45, 8.46, 8.47, 8.48 and 8.49	Practical guide for technical users, installers, system administrators, and programmers who implement, maintain, or develop applications for Oracle PeopleSoft Enterprise Applications.	rp_e_opcg_845_846_847_848_849.pdf (440.33 KB)
Online Performance Configuration Guidelines for PeopleTools 8.1x, 8.4, and 8.44	Learn how to diagnose a PeopleSoft Online Transaction environment, including Pure Internet Architecture® and Enterprise Portal configuration.	Download PeopleSoft 8.1x Red Paper (PDF: 740KB) Download PeopleSoft 8.4 Red Paper (PDF: 844KB) Download PeopleSoft 8.44 Red Paper (PDF: 930KB) Download UNIX shell scripts (ZIP: 5KB) that accompany these red papers.
LDAP Red Paper with Troubleshooting Tips for PeopleTools 8.x , 8.4x		LDAP Red Paper (1,820.02 KB)
Red Paper on Securing Your PeopleSoft Application Environment	How to secure PeopleSoft PIA environment	Red Paper (1,382.04 KB)
PeopleSoft PS/nVision Configuration & Troubleshooting Tips		RP_nVision_guide (1,204.22 KB)
Red Paper on Implementing Clustering and High Availability for PeopleSoft		Clustering_and_High_Availability-_840.pdf (1,983.35 KB)
Clustering and High Availability for Enterprise Tools 8.4x - 8.50	This Red Paper provides guidance for building Webserver and Application Server clusters.	PeopleTools Clustering Red Paper (2,827.3 KB)
Configuring a PeopleSoft Portal	This Red Paper provides guidance on a variety of aspects involved in configuring a PeopleSoft portal. It is organized into topics that prove to often be problematic for portal implementation teams	configuring_ps_8_portal_v1.pdf (1,259.16 KB)
Troubleshooting WebLogic 8.1 and 9.2 Issues		Troubleshooting_Weblogic_81.pdf (234.52 KB) Troubleshooting_Weblogic_92.pdf (1,367.93 KB)
Approval Workflow Engine (AWE) for HCM 9.0	This White Paper discusses how to implement and set up the Approval Workflow Engine (AWE), including how to define all the required support objects	Approval Workflow Engine (AWE) for HCM 9.0 (672.01 KB)
PeopleSoft Performance Monitor Red Paper	Performance Monitor system for troubleshooting performance problems in your environment.	Performance_Monitor_RedPaper.pdf (3,326.46 KB)

PeopleSoft Document Resources

Read more...

Test E-mail workflow functionality

Sometimes, you would come accross this situation:

"the mail is not going to the mail user and i am not even getting any error messages. I checked my SMTP in my server its all working fine . I dont know what is the issue. I even tried using Sent Mail function till its not working as expected.... "

Answer:

To troubleshoot this issue, there might be different reasons. You need to have appropriate setup and test the setup to see if your SMTP settings are working in the first place.

Below are setups the required for enabling or using Workflow notifications/emails:

1. The first and foremost thing is to setup: SMTP server Application server/Process scheduler used for the development.

2. E-mail should be enabled and configured for the instance in which the workflow is developed. eMail id's should exist in PSOPRDEFN and PSEXLATOPR tables; Also, emails are triggered using Person Profile.. in some places.

3. The User Profiles for the Roles are already in Place with proper Worklist ID s and Permissions.

Configure the SMTP in your psappsrv.cfg as well as in psprcs.cfg:

Setup the SMTP server ip-address and port number in App. Server / Process scheduler
Invoke the PSADMIN.exe in the PS_HOME/appserv directory and in the application server configuration, SMTP settings section specify the ip-address for the machine where SMTP server is installed.



Under the Setup WorkFlow Defaults:

Make sure the check boxes ‘Worklist Active’, ‘Worklist Active’ ‘HR installed’ and checked. If not, check the checkboxes and reboot the application server

Enable workflow for User Profiles :

For the users who will be using workflow routing (e-mail, Worklist) make sure that the following things are done.
1. They have a valid Worklist-id in PeopleSoft User profile.
2. E-mail and Worklist are enabled for the users

Test the E-mail workflow functionality :

1. Enter the User Id to whom the test mail has to be sent
2. Enter the test mail subject message
3. Save the component
Once the component is saved, it should trigger e-mail to the test users Worklist id specified in the user profile.

If mails are not generated, here are couple of things that will help you to troubleshoot the issue:

1) Since there are a lot of different reasons to get this particular error. In order to get better detail as to why the failure is occurring, you should set the LogFence=5 on the appserver to get SMTP tracing in your appserver log . This only works for the app server,not the Scheduler.

SMTP mail log is created under the PS_HOME\APPSERV\PRCS\\LOGS; This would give you a specific reason of the issue and can help you to troubleshoot the issue.

2)Make sure your SMTP server is working; to test this:

• Locate an SMTP mail server that you specified in SMTP settings under your App or Prcs Server SMTP settings
• Prove the mail server is accessible by connecting via telnet or pinging it.

3) Make sure the email id specified is active and exists.

Test E-mail workflow functionality

Read more...

PeopleSoft Benefit Rate Type Table

Question:

We are on PeopleSoft version below 9.0 and we have seen that All benefit rate data like Flat Rate table, Age Graded table etc are consolidated into one table i.e Benefit Rate Type Table;

We use the PROV_COVRG_RATE field in order to establish the total amount that is paid to an insurance provider and back into the administration fees.

we used to use PROV_COVRG_RATE field under Flat-Rate table in 8.8 (also available in 8.9) , where or how do I use it in on HR 9.0 or in 9.1?

Answer:

All benefit rate data is consolidated into a single common structure. The individual Age-Graded, Flat, Salary-Percent and Service tables will be dropped, and all rate data migrated to the new Benefit Rate Tables. This refers to AGE_COVG_TBL, FLAT_RATE_TBL, SALARY_RATE_TBL and AGE_RATE_TBL are being replaced by BN_RATE_TBL and BN_RATE_DATA.

The new Ben Rate Table provides the flexibility for the user to define different rates including Provider Rates if they choose to do so. Below Screen shots would provide you some idea:

Let's take an example:

Employee Amt: 60.00 Employer Amt: 40.00 Provider Amt: 99.00
In this example, the total deduction amount (non-tax and before-tax) is not paid to the provider. The difference (in this example $1) is kept by the employer as an internal administration fee.
It is used in a custom report process that calculates vendor insurance premiums.”

Here’s the screen shot of Flat Rate Table (in PS version 8.8 or 8.9) showing the Provider Amount:

How It Can Work in 9.0 and above:

The different Rate Tables of 8.8 or 8.9 are lumped into 1 component in 9.0 and above, differentiating them by Benefit Rate Type in new Benefit Rate Table

In this case, need to define Flat Rate. Using same example from 8.8, here’s 9.0/9.1 counterpart.

what’s missing is the previous Provider Rate of 99.0. This can easily be defined in 9.0 and above by using same component with Benefit Type of Flat Rate as illustrated below with Employee Rate of 99.0:

To access the Employee Rate above that is defined as Provider Rate, use Record PS_BN_RATE_DATA field BN_EMPL_RATE.

To access the Employee and Employer Rate for ‘RT1’:

SELECT
,E.BN_EMPL_RATE
,E.BN_EMPLR_RATE
FROM PS_BN_RATE_DATA E
WHERE E.RATE_TBL_ID IN (’RT1’,’RT1P’)
AND (E.EFFDT=
(SELECT MAX(E1.EFFDT)
FROM PS_BN_RATE_DATA E1
WHERE E1.RATE_TBL_ID=E.RATE_TBL_ID
AND E1.EFFDT <= current date or whatever effective date required)

Then in your SQR or batch program, add logic to match up Employee/Employer Rates to the corresponding provider rate, e.g.:

IF RATE-TBL-ID = ‘RT1’
THEN TOTAL-DEDUCTION = BN-EMPL-RATE + BN-EMPLR-RT

IF RATE-TBL-ID = ‘RT1P’
THEN PROV-COVRG-RATE = BN-EMPL-RATE

CO-ADMIN-FEE = TOTAL-DEDUCTION - PROV-COVRG-RATE

Or if you have naming convention schema for RATE_TBL_ID’s between the Employee/Employer Rates and Provider Rates, e.g. 1st 3 characters of the RATE_TBL_ID match, then you can join or add it in the program instead of hard coding it in the program.
You can also use the Benefit Rate Type to identify Coverage Provider Rates, e.g.:

When defining the Coverage Provider Rate, use the new Provider Rate Type just created:

To extract Provider Rate Types from table and corresponding Provider Rate:

SELECT
,R.RATE_TYPE
,P.BN_EMPL_RATE
FROM PS_BN_RATE_DATA P
, PS_BN_RATE_TBL R
WHERE P.RATE_TBL_ID = R.RATE_TBL_ID
AND (P.EFFDT=
(SELECT MAX(P1.EFFDT)
FROM PS_BN_RATE_DATA P1
WHERE P1.RATE_TBL_ID=P.RATE_TBL_ID
AND P1.EFFDT <= current date or whatever effective date required)
AND P.EFFDT = R.EFFDT

In batch program, add the logic to match up the Provider Coverage Rate to its corresponding Employee/Employer Rates. In our example the Rate Table ID ‘RT1P’ Rate Type ‘RT1’ in Benefits Rate Table matches with Rate Table ID ‘RT1P’. Hence you can create a schema where the Provider’s Rate Type matches with the corresponding Rate Table ID of Employee/Employer Rate in Benefits Rate Table.

Another option is to have one Provider Rate Type that applies to multiple Employee/Employer Rates, e.g. Benefit Rate with Rate Type of ‘RT1’ contains the Provider Coverage Rate for Benefit Rate ID’s ‘RT1’, ‘RT2’ and ‘RT3’.

PeopleSoft Benefit Rate Type Table

Read more...

PeopleSoft TAM / Recruiting Site ID's

TAM Question:

I have a question regarding multiple Sites. How do we enable multiple sites on the same Portal?

Answer:

What is PeopleSoft TAM related Site ID:

Site IDs define the default parameters for an organization’s online application website and determine which job openings appear on the organization’s internal and external websites.

Row security is used to determine which job openings are available to the site. Job search criteria, such as Recruiting Locations and Job Family, use Set ID to display appropriate drop-down values.

Navigation of Site Set Up > Set Up HRMS -> Product Related ->Recruiting, Sites :





Define multiple Site ID's as you need in the Site ID Setup:
Also, make a note of the Site ID here,which is 1111.



This is the Internal Career's Portal CREF (through self-service) which is linked to default site id:




The Portal structure will not allow multiple instances of the same menu.component combination. However, the use of Additional Parameters in the Component Parameters groupbox allows the Portal to recognize the entry as unique. For example, adding a CREF to the Careers Home page for TEST Site (Site ID 1111) would look like this:

When CREFs exposed, the menu would then look like this in your portal:

Also, take a note of the below point if you are HCM 9.0 and above:

The link to the Job Opening and the Site is established through the Recruitment Source. The Recruitment Source can be setup by navigating to Set Up HRMS >> Product Related >> Recruiting >> Recruitment Sources >> Recruitment Sources >> Source Setup. In the Source Setup page select the appropriate "Source Type". The source type that you select determines which pages appear in the Source Setup component. The Source Setup component consists of three pages. The Source Setup and Contacts pages appear for all source types. The third page that appears depends on the source type that you select.

The Recruitment Source is linked to the Site in the second page. Here one or more sites can be selected for a Recruitment Source. When a recruiter or hiring manager creates a job opening and selects to post the job opening to this source, the system posts the job opening to all of the sites that you select here.



Hope this helps...

PeopleSoft TAM / Recruiting Site ID's

Read more...

Question on Shift Calculation

Question:


Dear Gurus

Does PS Timekeeper allow for the assigning of percentages to specific hours in the workday, so that if a non-exempt employee works those hours, they get a differential paid to the for that hour only.

For example, Jane Doe works the even shift (6pm to 2am) one day a week. When putting her hours in the timekeeper, she records normal hours (8am to 5pm) Monday through Thursday, and 6pm to 2am on Friday. Would she be assigned a shift code at the employee level (lets say 5%) that gets applied to all hours no matter what? OR could the system recognize normal pay for Monday - Thursday, and apply the differential to the hours worked Friday night only?

I Appreciate your early response.

Thanks in Advance

Keyrun

Answer:


You need to understand how Shift Differential is paid through PeopleSoft. here's some background on how you can setup shifts and shift differential or shift premium payment.

Methods to Setup Shift Pay:

This diagram lists some methods for setting up and calculating shift pay:



Earnings Code Based on Other Earnings.

This is the preferred method if you need to express shift pay as separate earnings on the paycheck or advice. Create a separate earnings code for shift differential based on another earnings code or a special accumulator of earnings and pay it out as additional pay. You can set it up as a percentage or a flat rate. A flat rate must be hours-based. Do not select Eligible for Shift Differential on the Earnings table.

Pay Group SetID and Shift Table
Create each applicable shift type on the Shift table. Assign each employee to one of these shifts. Select Eligible for Shift Differential for eligible earnings codes.

Earnings Code With Earnings or Rate Adjustment Factor
Add a rate adjustment factor to applicable earnings on the earnings table to add that rate to the employee’s hourly rate. Or add an earnings adjustment factor to the total earnings. This method does not result in a separate earnings line on the paycheck


Compensation Rate Codes
You can define non-base compensation rate codes to indicate the rate that is paid on the paycheck when assigned to an earning. For example, if the employee is paid overtime at time and half and the employee’s hourly rate is $10.00, the paycheck would show the $15.00 rate for overtime.

Use Time and Labor Rules
Customers who license PeopleSoft Enterprise Time and Labor set up rules to define shift differential.

One important thing to note is that: The Eligible for Shift Differential check box has no bearing on PeopleSoft Enterprise Time and Labor.

So for your case, you need to define a Time and Labor rule for calculating a shift premium instead of using payroll shift differential.



You can try using the Premium Zone Templates:

1) Template 100 :

If a time reporter works between x and y o'clock, then pay premium. i.e. When a time reporter works between (1)SPECIFIED_START_TIME and (2)SPECIFIED_END_TIME, create a shift premium only for those hours worked within the specified time, to be charged to TRC (3)SPECIFIED_TRC.

2) Template 090:

If a time reporter clocks in between x and y o'clock, then pay premium. i.e When a time reporter punches IN between (1)SPECIFIED_START_TIME and (2)SPECIFIED_END_TIME, create a shift premium for all hours worked, to be charged to TRC (3)SPECIFIED_TRC.
If the time reporter punches in within the specified time period, this rule creates a TRC for all hours worked, even when the time reporter punches out after the specified time period.


So, in your case, you would put the start time and end time of friday to pay .05 percent shift premium. Your Shift Premium TRC should have .05 as the multiplication factor.

Hope this helps. Please add comments.

Question on Shift Calculation

Read more...

Presheet Audit errors with blank descriptions

Question:

Hello - We are having errors show on the Presheet Audit Report pay034 where theerror description is blank. Any ideas on where the error messages are stored and how to correct this problem?


Answer:


The Presheet Audit report is used to provide a detailed error listing of set up data (employee, benefit, deductions) that can cause errors in the Create Paysheet process (PSPPYBLD). So basically you need to run to identify setup issues prior to creating and calculating paysheets



The SQR uses descriptions that are defined in PS_STRING_tbl. There are 95 rows defined for Pay034.sqr program in 9.0 version.



Navigation to the String Table is - PeopleTools -> Utilities -> Administration -> Strings Table and look for PAY034 program id.

Please take a look at the above table and see if you have this table populated?

Presheet Audit errors with blank descriptions

Read more...

PeopleSoft PeopleBooks

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

PeopleSoft PeopleBooks

PeopleSoft 9.1 PeopleBooks

PeopleSoft PeopleBooks

Read more...

Quarterly Tax Reporting

Question :

What are Quarterly Tax Reports and how to file them:

Answer:

Tax ReportsTax reports contain information related to wage reporting, and they provide the forms and formats required for reporting payroll data to federal, state, provincial, and local taxing authorities.Tax reports have the prefix TAX. The special numerical series in the TAX SQRs are as follows:


• CTX: Related to Canadian T4, T4A, RL-1, and RL-2 reporting processes.

• TAX103: W-4 exempt employees.

• TAX113: Reset W-5 EIC earned income credit (EIC) employees.

• TAX700-799: Tax tables.

• TAX800-899: Processes to create files for states that must submit quarterly state wage listings on magnetic tape.

• TAX900-999: Related to W-2 and 1099 wage reporting processes.

State Quarterly Wage Reporting FormatsUsing data generated by Payroll for North America, there are three ways that you can submit quarterly wage reports:

•Paper reporting - TAX002xx.SQR

• Electronic file - TAX810xx.SQR

•TIB-4 (old SSA format)

•ICESA (Interstate Conference of Employment Security Agencies)

• Magnetic media - TAX860xx.SQR

•State-unique formats

•EFW2 -SSA format (formerly MMREF-1 format)

TAX810XX and TAX860XX - Quarterly UI Wage Tape: The output is produce in the electronic/magnetic media format. It can be copied to diskette or tape before filing. Some states use the TAX860XX format, which creates the file using the MMREF format.

The state-specific versions of this report have self-explanatory prompts. You can specify the calendar year and quarter on the Define Tax Reporting Parameters page, found under the Quarterly Processing menu.

Where applicable, choose between the TAX810XX and TAX860XX formats from the choices displayed in the process list that appears after you click the Run button on the run control page.

To submit in Paper Format use - Quarterly State Employee Wage Listing (TAX002xx) SQR Report/Process.

Menu Path:

Payroll for North America, U.S. Quarterly Processing, State Quarterly Wage Reporting, State Wage Listing Report

To Submit in Magnetic media, not using the MMREF-1 format use Quarterly UI Wage Tape (TAX810xx) orTo Submit in Electronic or magnetic media using the MMREF-1 format use Quarterly UI Wage Tape (Tax 860xx).

Menu Path :

Payroll for North America, U.S. Quarterly Processing, State Quarterly Wage Reporting, Create Magnetic Media

When you run the Tax810xx or Tax860xx processes, you get the files as shown below:

•TAX810xx & TAX860xx

•One file created for companies with different company

•Exception is Nebraska

•TAX810xx.nnn

•One file created for companies with different company but multiple files may be created if the data will not fit diskette

•“.nnn” represents a volume number

•T810xxnn

•Separate files are created for each company EIN

•“nn” represents a volume number for each company

If you are not filing by magnetic media, use the TAX002xx report, which is designed to print directly on the state form for those states that require submission on their forms.

For Filing with different states, you need to check each state unemployment website. If your employer is multistate, then have a document with all links pointing to the state unemployment tax sites. If you file using electronic filing, your payroll or tax department should register first using your company FEIN or State Employer Identification Number with the respective state and then use the ID to submit the file. Depending on the state validation process it may take time to get back the results of the upload. Some of the tax data might be incorrect. So, your payroll or tax department must make sure that the tax balancing reports (like TAX900, TAX017, TAX010ST ,TAX010FD , TAX004, TAX004ST etc) and run at regular intervals.

Check here how PeopleSoft Quarterly balancing is done

Example: if you want to file for Wyoming, here are the steps:

1. Make sure that Quarterly tax reporting parameters are setup.

2. Run the Quarterly UI Reports Wyoming (TAX810WY.SQR) or (TAX002.SQR)

3. Get the file TAX810xx.nnn (if filing through electronic) from the server

4. This must be FTP'd to the Payroll or Tax user who submits it to state

5. Verify the tax file is correct format.

6. Use https://doe.state.wy.us/wire/ to login and upload the file

7. Get validated results if the submitted file is OK or NOT OK.

8. If file not ok, fix the TAX Data and re-submit.

Take a look at this step by step document:

Click here

Quarterly Tax Reporting

Read more...

PeopleSoft Query Security

Question:

What do u mean by query security.How it is implemented in peoplesoft?

Answer:

When you talk about PeopleSoft Query Security, these are things that are taken into consideration:

1. Query Profiles...Specifies what query operations, such as create and run, are available to users. For example, you may want certain users to run only existing queries, not create new ones.

2. Query Access Group and Trees....Collections of record definitions in a query tree. After you build a query tree, you can query any table in the access groups that are accessible to you.

3. Define row-level security and query security records....Provides data permission security when you access data using the PeopleSoft Query tool.

All of these are utilized by PeopleSoft Query through user's security settings, row-level security, and primary permission list. Query Profiles are setup in Permission List (PTPT1000) , under Query Tab. Query Access Groups are attached to Permission List (HCSPQUERY), under Query Tab.

About Query Security Record:

One of the Security Feature in PeopleSoft is Data permission security, or row-level security

• It Controls access to user data on an individual or group basis.
• It Specifies the rows of data that user is permitted to retrieve.

For example, you might want users to be able to review personal data for employees in their own department, but not for people in other departments. You would give everyone access to the PERSONAL_DATA table, but would enforce row-level security so that they could only see rows where the DEPTID matches their own.

Since there is Query Tool, through which you can retrieve sensitive data, You can implement row-level security by having Query search for data using a query security record definition. The query security record definition adds a security check to the search.

To apply row level security:

1. Select PeopleTools, Application Designer to open the Application Designer, and open the record on which you want to apply row-level security.

2.With the record definition open in the Application Designer, click the Properties button, and select the Use tab from the Record Properties dialog box.

3.Select the security record definition (usually a view) in the Query Security Record list box.

4.Once you’ve set the query security record definition, click OK to close the Record Properties dialog box, then save the record definition.

The PeopleSoft system automatically adds a WHERE clause to the SQL, joining the user’s user ID, primary permission list, or row security permission list to the following key fields if they are present:

• OPRID
• OPRCLASS
• ROWSECCLASS

For Example, If you want to add a Query Security to PS_JOB record, you need to check the record properties (the query security comes pre-delivered)

and here's what the EMPLMT_SRCH_QRY sql looks like:

PeopleSoft Query Security

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

TL_TIMEADMIN runcontrol Process Thru Date

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).

User Exits in Time and Labor

Read more...

XML Publisher : Question

Question: XML Output options are disabled on the output page in XML Publisher

Hi
I am using peoplesoft HR9.In XMLP, when defining new record definition,the XML Output options are disabled on the output page. Please help Thanks

Answer:

Please make sure that you add 2 delivered permission list to the Peopletools Role:

PTPT2500 (XMLP Power User )
PTPT2600 (XMLP Report Developer )

Note that the delivered reports tend to use the PeopleSoft User role as the author ID. If you are configuring security stick to roles - rather than assigning security by individual users.

You can also change this through:Reporting Tools > XML Publisher > Setup > Report Category

Also, by default, when you load the Report Definition Page, the output page is enabled with all format output options for the template type you pick in the Definition Page. check this table to see if the data is loaded or not:

select * FROM PSXPTMPLOUTFMT

if the data is missing from PSXPTMPLOUTFMT, then you may have to get it from your Demo system.

XML Publisher : Question

Read more...