The RF Projected Suspense Charges Report is a monitoring report that lists employees whose pay will be charged to the suspense account if no action is taken before running payroll.
Run this report before a payroll run to show which charges will go to suspense if no action is taken on an employee's record.
The following table describes the required and optional parameters to use to run the report:
Parameter |
Description |
|
Required Parameters |
||
Parent Organization |
Operating location of the organization. |
|
Payroll Name |
Type of payroll run. Select from the current List of Values to fill in this field. Select Biweekly. |
|
Start Pay Period |
Starting pay period for which the report will be run. Select Biweekly from the List of Values. |
|
End Pay Period |
Ending pay period for which the report will be run. Select Biweekly from the List of Values. |
The table that follows describe the report output:
Column Heading |
Description of Column |
Employee Name |
Person's last name, first name. |
Assign. Number |
Number from the Assignment form in the HR record. |
Assignment Status |
Status of the assignment for selected payroll period. |
Element Type |
Defines the element for which Element Level Labor Schedule was entered. This field will be blank if Schedule Type equals A. |
Schedule Type |
ET - Element-defined labor schedule (one element only charging instruction). |
Project |
Project Number (may be blank if no charging instructions). |
Task |
Task Number (may be blank if no charging instructions). |
Award |
Award Number (may be blank if no charging instructions). |
Expenditure Organization |
Expenditure Organizations from labor schedule (may be blank if no charging instructions). |
Expenditure Type |
Expenditure Type from labor schedule (may be blank if no charging instructions). |
Percent |
Precent from labor schedule (may be blank if no charging instructions). |
Reason |
Reason why future payroll transaction will process to suspense award if no action is taken before LD processes running for that payroll date. |
Period Start Date |
Beginning date of the pay period that will process to suspense award for the reason listed. |
Period End Date |
Last working date of the pay period that will process to suspense award for the reason listed. |
Rejection Reason Code |
Definition |
Action to Take |
AWARD IS NOT ACTIVE |
Award status is not applicable for processing transactions; status must be Active or At Risk to process.
|
Review award status for appropriateness. |
AWARD NOT FUNDING THE PROJECT
|
Funding relationship is not set up properly
|
Review funding relationship between project and award. |
ETYPE_SLINK_INACTIVE |
Expenditure type/expenditure type class inactive. The combination of expenditure type and expenditure type class is inactive as of the expenditure item date. |
Change cannot be made through LD once charge has been posted to Grants. Charge will need to be input through Grants batch with correct expenditure type. |
EXP ITEM DATE OUT OF AWD RANGE
|
Expenditure item date is outside of the award dates, including close date on award.
|
Review dates on award in relation to expenditure item date. Move close date on award to a date in the future, if needed. |
EXP_TYPE_INACTIVE
|
Expenditure type inactive. The expenditure type has been defined, but it is either not yet effective or has already expired as of the expenditure item date. |
Change cannot be made through LD once charge has been posted to Grants. Charge will need to be input through Grants batch with correct expenditure type. |
INVALID_EMPLOYEE |
Employee's HR assignment starts after the current system date. |
Wait until after employee's assignment start date equals or is greater than current system date and central office will need to rerun PSP: Summarize and Transfer process. |
NO_ASSIGNMENT
|
Employee in HR module does not have an active assignment to a specific organization (should not let you save this assignment without one) and job as of the expenditure item date. |
Change employee's HR assignment to add in missing job.
|
NO CHARGING INSTRUCTIONS |
A labor schedule was not created for this person. |
Before LD processes are run for a given payroll, enter a labor schedule. After LD processes are run for a given payroll, a distribution adjustment needs to be processed. |
NO LABOR SCHEDULE EXISTS |
A labor schedule was not created for this person |
Enter a labor schedule for this person in the Labor Distribution module. |
NO VALID SCHEDULE EXISTS |
The current labor schedule for this person contains an end date that is earlier than the end of the payroll period. |
Enter a valid labor schedule for this person in the Labor Distribution module. If the Project-Task-Award numbers are still valid through the end of the specified pay period, then extend the labor schedule, or create a new schedule line with different Project-Task-Award numbers for the remaining dates in the pay period. |
PA_EX_PROJECT_DATE |
Expenditure item date is not within the active dates of the project. |
|
PA_EXP_TASK_EFF |
Expenditure item date is not within the active dates of the task. |
|
PA_EXP_TASK_STATUS |
Under the Project, then Task to Task Details, the box for Allow Charges is unchecked. |
Check the box to allow for charges to be applied to this specific task to allow for charges to be posted. |
PA_EXP_TASK_TC |
Under the Project, then Task to Transaction Controls, the box for Limit to Transaction Controls is checked. |
Review the information under transaction controls compared to the transaction you are attempting to process. |
PA_NEW_TXNS_NOT_ALLOWED |
Project or Award status is not Approved, allowing transactions to be processed against it. |
Review the status of the project or award. |
PROJECT NOT ACTIVE |
Project status is not Approved. |
Review project status for appropriateness. |
SCHEDULE DOES NOT EQUAL 100% |
This affects biweekly employees only, as long as the correct organization is used in the HR assignment. |
Adjust labor schedule to account for 100% of paid amount. If the labor schedule does not total to 100%, a portion of the paid amount is posted to the suspense award. |
Effective Date: 3/18/2008 2:18:07 PM