Announcements‎ > ‎

PeopleSoft Announcements

News and announcements regarding PeopleSoft HCM (Human Capital Management) and PeopleSoft Finance.

Split Funded Position Distribution

posted Oct 20, 2017, 4:03 PM by Peyri Herrera   [ updated Oct 20, 2017, 4:03 PM ]

Distribution of taxes and deductions for employees with multiple positions can result in an amount being posted to the ChartString for a position that is not subject to that tax or deduction. It’s important to keep in mind the total amount of taxes and deductions charged and posted is correct, it is just the distribution that may be off. This only happens when the two positions’ earnings are charged to different chart of accounts (Scenario 1). If the only difference in the chart of accounts is the Object, then all of the tax or deduction will post to the correct Resource (Scenario 2). Please see the announcement titled How PeopleSoft distributes taxes and deductions for employees with multiple positions which helps illustrate the distributions for these two scenarios.

We are working toward a solution to assure taxes and deductions follow the funding source of the earnings that generated those taxes and deduction.

How PeopleSoft distributes taxes and deductions for employees with multiple positions

posted Oct 20, 2017, 4:01 PM by Peyri Herrera

Distribution of taxes and deductions for employees with multiple positions can result in an amount being posted to the ChartString for a position that is not subject to that tax or deduction. We have provided two scenarios to help illustrate the distribution. It’s important to keep in mind the total amount of taxes and deductions charged and posted is correct, it is just the distribution that may be off. This only happens when the two positions’ earnings are charged to different chart of accounts (Scenario 1). If the only difference in the chart of accounts is the Object, then all of the tax or deduction will post to the correct Resource (Scenario 2). We are working toward a solution to assure taxes and deductions follow the funding source of the earnings that generated those taxes and deduction.

Scenario 1: An employee in two positions has earnings that are charged to different Resources

Summary:
  • An employee is paid a total of $3000 from two positions, one charged against Resource 1234000 and the other against Resource 5678000. This scenario shows the total Social Security of $62.00 distributed to the different Resources. 
  • $41.35 in Social Security is distributed to Position A in Resource 1234000 based on the fact that Position A accounts for 66.7% of total earnings 
  • $20.65 in Social Security is distributed to Position B in Resource 5678000 based on the fact that Position B accounts for 33.3% of total earnings 
  • The total amount of taxes and deductions charged and posted is correct, it is just the distribution that is off. This only happens when the two positions’ earnings are charged to different chart of accounts as shown in this scenario. If the only difference in the chart of accounts is the Object, then all of the tax or deduction will post to the correct Resource. 
Scenario 1: An employee in two positions has earnings that are charged to different Resources

Breakdown:

An employee is paid a total of $3000 from two positions.
  • Position A has earnings of $2000, is not subject to Social Security and is charged against Resource 1234000. 
  • Position B has earnings of $1000, is subject to Social Security and is charged against Resource 5678000. 
When the amount of each tax and deduction is calculated, the system correctly calculates Social Security against the amount paid to Position B only.
  • Position A has no Social Security calculated against the earnings paid for Position A. 
  • Position B has $62.00 in Social Security calculated against the earnings paid for Position B. 
When payroll distribution is run, the system distributes the $62.00 in Social Security against all positions from which the employee is paid. It prorates the Social Security based on the earnings paid to each position.
  • Position A’s earnings of $2000 is 66.7% of the total earnings.
  • Position B’s earnings of $1000 is 33.3% of the total earnings. 
It distributes the total Social Security of $62.00 based on the proration of earnings charged to each Resource:
  • $41.35 in Social Security is distributed to Position A in Resource 1234000 based on the fact that Position A accounts for 66.7% of total earnings 
  • $20.65 in Social Security is distributed to Position B in Resource 5678000 based on the fact that Position B accounts for 33.3% of total earnings.

Scenario 2: An employee in two positions has earnings that are charged to the same Resource.

Summary:
  • An employee is paid a total of $3,500 from two positions with the same Resource. This scenario shows the total Social Security of $31.00 distributed to the same Resource. 
  • $26.57 of Social Security is distributed to Position C using 0100-1234000-1000-1110-3311000-000. 
  • $4.43 of Social Security is distributed to Position D using 0100-1234000-1000-1110-3312000-000. 
Scenario 2: An employee in two positions has earnings that are charged to the same Resource.

Breakdown:

An employee is paid a total of $3,500 from two positions with the same Resource.
  • Position C has earnings of $3,000 charged to 0100-1234000-1000-1110-1100000-000 and is NOT subject to Social Security. 
  • Position D has earnings of $500 charged to 0100-1234000-1000-1110-2900000-000 and is subject to Social Security. 
When the amount of each tax and deduction is calculated, the system correctly calculates Social Security against the amount paid to Position D only.
  • Position C has no Social Security calculated against the earnings paid. 
  • Position D has $31.00 in Social Security calculated against the earnings paid. 
When payroll distribution is run, the system distributes the $31.00 in Social Security against all positions from which the employee is paid. It prorates the Social Security based on the earnings paid to each position.
  • Position C’s earnings of $3000 is 85.7% of the total earnings 
  • Position D’s earnings of $500 is 14.3% of the total earnings. 
It distributes the total Social Security of $31.00 based on a proration of earnings charged to the same Resource:
  • $26.57 of Social Security hits Position C using 0100-1234000-1000-1110-3311000-000. 
  • $4.43 of Social Security hits Position D using 0100-1234000-1000-1110-3312000-000.

October 2017 Payroll Distribution Complete

posted Oct 20, 2017, 9:38 AM by Peyri Herrera

On Thursday, October 19, 2017, we sent an announcement asking you to hold off running PEDR reports until notified. This is a follow-up message. The Payroll distribution process is now complete. You can now run PEDR reports.

Please wait until the encumbrance calculation has finished before running an extract that includes encumbrances. The CRC will notify you when this is ready.

Guidelines for identifying Ineligible absence events

posted Oct 20, 2017, 9:38 AM by Peyri Herrera

The purpose of this announcement is to help you identify absence events that have a current forecast value of Ineligible that were previously Eligible.

M_AM_ABSENCE_EVENT_STATUS Query
To identify ineligible absence events, run the M_AM_ABSENCE_EVENT_STATUS - List Ineligible Absences query. This query has a company and date prompt. For more information about this query, please refer to p.12 of the HCM Query Reference Guide.

Why might some absence events that were previously Eligible now be Ineligible?
If an employee enters a future absence event that is Eligible and approved then subsequently enters another absence event with a begin date prior to the future-dated absence event(s) this can reduce the balance to a value that is lower than the number of hours required by the future event. This makes the previously Eligible future-dated event become Ineligible.

Example:
  • An employee has a vacation balance of 12.0 hours and requests 8.0 hours of vacation on 12/23. 
  • The event is forecasted as Eligible and approved. 
  • The employee decides to take 8.0 hours of vacation on 10/31. The event is forecasted as Eligible and approved. 
  • The vacation on 10/31 leaves a remaining vacation balance of 4.0 hours. This results in the 8.0 hour vacation on 12/23 as Ineligible since the employee now only has 4.0 hours of vacation available. 
If you have any questions please submit a HEAT Self-Service ticket.

PeopleSoft Finance (SDFP) was down briefly but is back up now

posted Oct 19, 2017, 11:56 AM by Barbara Thiss

PeopleSoft Finance (SDFP) was down briefly but is back up now. We apologize for the inconvenience.

You are no longer locked out of HCM/ESS (10/19/17)

posted Oct 19, 2017, 10:43 AM by Barbara Thiss

You are no longer locked out of HCM and ESS. The Payroll distribution process is not yet complete. Please hold off on running PEDR reports until notified.

All users will be locked out of PeopleSoft HCM and Employee Self-Service (ESS) on Wed. 10/18/17 at 5:00 pm

posted Oct 18, 2017, 3:51 PM by Barbara Thiss

At 5:00 pm tonight, Wednesday, October 18, 2017, all users' access to PeopleSoft HCM and ESS (Employee Self-Service) will be removed until payroll is confirmed, typically through the middle of the next day. This means you will not be able to access HCM or ESS during this time. You will have access to the system once payroll is confirmed. We will notify your organization's PeopleSoft HCM contacts when access has been returned.

PeopleSoft Third Thursday Demo (10/19/17): What’s New in PeopleSoft?

posted Oct 17, 2017, 11:26 AM by Peyri Herrera

Third Thursday Demo

This month's Third Thursday topic is "What's New in PeopleSoft?" This is a high level overview of (1) What is currently in Production, (2) Phase 2 projects, and (3) the PUM system upgrade occurring in April 2018. 

Date/Time: Thursday, October 19, 2017 from 11:00 am - 12:00 pm (REMINDER: The Great California Shakeout is at 10:19 am)

Registration: https://register.gotowebinar.com/register/5969207231869704449. Registration is required. Upon registration, look for an email from Citrix/GoToWebinar with connection information.

Topics:
Please note that the content addresses both HCM and Finance topics at a very high level.
  1. What is currently in Production? 
    1. Employee Self-Service (ESS) 
    2. Excel-to-CI for HCM 
    3. Personnel Action Form (PAF) 
    4. Travel & Expenses (T&E) 
    5. Hyperion 
    6. Query Manager 
    7. Web Services 
    8. PeopleSoft Sandboxes 
  2. Phase 2 Projects 
    1. HCM – Recruitment 
    2. Finance – Projects, Contracts, Grants 
    3. Business Intelligence 
  3. “PUM” System Upgrade 
    1. PUM – What is it? When is it? What does it mean for me? Key issues resolved? 
This session was offered at last week’s PeopleSoft User’s Conference. Because numerous conference attendees suggested that the “What’s New” session is offered again during 2017-18, we are repeating it as this month’s Third Thursday Demo. Here is some feedback and takeaways provided about this session:
  • “I enjoyed this session a lot and thought it was good to see what is coming and what currently exists or is optional to turn on.” 
  • “Several HR modules (PAF, Recruitment) are being developed that [my district] may want to look into.” 
  • “I was thrilled and look forward to the new BI [Business Intelligence] tool that's currently under development. This would save me so much time.” 
  • “Looking forward to what is new in Peoplesoft and how we can improve our processes and workflow with updates!” 
Handout: What’s New in PeopleSoft? (PDF, 18 pp.)

Can’t join us live? This session will be recorded and available for playback on our Third Thursday webpage at http://crc.sdcoe.net/calendar/peoplesofttraining/thirdthursdays.

Possible impacts to PeopleSoft performance during the weekend of October 21, 2017

posted Oct 17, 2017, 9:51 AM by Barbara Thiss

Please note that during the weekend of Saturday, October 21 thru Sunday October 22, 2017, PeopleSoft maintenance will be performed that could result in performance degradation. There will be no downtime. Scheduled processes will not be impacted.

There is a small chance that there could be an issue with one of the Application Servers following this work. Please enter a HEAT ticket if you experience intermittent behavior where a process works for one user but not another. Check the Application Server you are on by clicking Control + Shift + J. If you are on AP03, log completely out of PeopleSoft and the log back in. This is to try and get you on a different Application Server so your process can work.

Error message on eProcurement and Supplier pages has been resolved

posted Oct 16, 2017, 12:14 PM by Barbara Thiss

Error message on eProcurement and Supplier pages has been resolved. The web server was restarted and a security sync process was run. If you are getting any other messages, please clear your cache. As always, if you encounter any other problems, please submit a HEAT ticket. Thank you for your patience.

1-10 of 1153