| id |
051ed60a-c188-4b1f-9946-2a57fd228624 |
| user_id |
8684964a-bab1-4235-93a8-5fd5e24a1d0a |
| job_id |
lycsagnn-7573 |
| base_model_name |
xevyo |
| base_model_path |
/home/sid/tuning/finetune/backend/output/xevyo-bas /home/sid/tuning/finetune/backend/output/xevyo-base-v1/merged_fp16_hf... |
| model_name |
Periodic Increment |
| model_desc |
Periodic Increment and Longevity |
| model_path |
/home/sid/tuning/finetune/backend/output/lycsagnn- /home/sid/tuning/finetune/backend/output/lycsagnn-7573/merged_fp16_hf... |
| source_model_name |
xevyo |
| source_model_path |
/home/sid/tuning/finetune/backend/output/xevyo-bas /home/sid/tuning/finetune/backend/output/xevyo-base-v1/merged_fp16_hf... |
| source_job_id |
xevyo-base-v1 |
| dataset_desc |
This PDF is a step-by-step operational guide used This PDF is a step-by-step operational guide used by HR, payroll, and personnel administration staff in the State of Washington’s HRMS (Human Resource Management System). It explains how to generate, interpret, and troubleshoot the Periodic Increment and Longevity Increase Projection Report—a tool that identifies when employees are scheduled to receive periodic salary step increases or longevity pay increases, and detects employees who missed increases due to system or data-entry issues.
It is part of the state’s official payroll and HR procedure documentation and is written in a clear, instruction-manual style.
🔶 Purpose of the Report
The report is used to:
Project upcoming salary step (PID) and longevity increases
Identify employees who missed a scheduled increase
Detect incorrect or missing coding in the Basic Pay Infotype (0008)
Verify payroll accuracy during processing cycles
The document emphasizes that this report is forward-looking only, not historical.
For historical data, users must instead run the Periodic Increment and Longevity Increase Historical Report.
📌 Core Components Explained in the PDF
1. Who should use this?
The procedure is intended for HR roles including:
Personnel Administration Processor
Personnel Administration Supervisor
Personnel Administration Inquirer
These roles must have access to HRMS transaction code ZHR_RPTPA803.
2. When the report should be run
The document provides precise instructions:
For projections: Run at any time to see future increases.
For missed increases: Run on Day 2 of payroll processing, after overnight updates.
3. How the period selections work
The “Period” section offers several options (Today, Current Month, Current Year, From Today, Other Period), each with different interpretations depending on whether “Display missed PID/Longevity” is checked.
The PDF details:
Which options are recommended
Which ones produce accurate projection results
Which ones expose missed increases
4. How to filter and customize selection criteria
Users can filter by:
Personnel number
Employment status
Organizational unit
Job or position
Work contract
Business area
The guide explains how filtering affects system performance and which fields are commonly used.
5. Understanding “missed increases”
The system flags employees who:
Should have received a periodic increment but didn’t
Are scheduled incorrectly
Have missing or incorrect Next Increase Dates in the Basic Pay Infotype
The PDF explains how missed increases are detected and how to fix related errors.
6. Output Layout and Fields
The report’s default output includes:
Business area, personnel area, org unit
Employee name, personnel ID
Current pay step and next scheduled step
Dates of current and projected pay-level changes
Pay adjustment reason
Years in level
New pay level and date
Additional columns can be added using “Change Layout.”
🔶 Troubleshooting and Example Scenarios
A major portion of the document explains real HRMS data problems, why they occur, and how to fix them. It provides three detailed case studies:
Example 1 — Incorrect Next Increase Date
A typo or incorrect override in Infotype 0008 prevents an employee from receiving the correct step increase.
Solution: Correct or create a new record with accurate dates.
Example 2 — Employee Previously in the Same Salary Range
The system won’t advance a step if it believes the employee already reached that step in the past.
Solution: Enter a manual override date for the next increase.
Example 3 — Missing Next Increase Date
Older pay records created before automation may lack required dates, resulting in missed increments.
Solution: Add a correct Next Increase date or create a new Infotype record.
⭐ Overall Purpose and Value
This document ensures HR staff:
Apply periodic and longevity increases correctly
Catch system errors before payroll is finalized
Maintain accurate pay-step progressions
Correct outdated or incorrect Basic Pay data
Keep employee compensation records complete and compliant
It is both a technical guide and a quality-control tool for payroll accuracy in state government.
⭐ Perfect One-Sentence Summary
This PDF is a complete HRMS user guide that teaches payroll and HR staff how to project, verify, and troubleshoot periodic salary step and longevity increases by using the state’s automated reporting system.... |
| dataset_meta |
{"input_type": "file", "source {"input_type": "file", "source": "/home/sid/tuning/finetune/backend/output/lycsagnn-7573/data/document.pdf", "num_examples": 39, "bad_lines": 0}... |
| dataset_path |
/home/sid/tuning/finetune/backend/output/lycsagnn- /home/sid/tuning/finetune/backend/output/lycsagnn-7573/data/lycsagnn-7573.json... |
| training_output |
null |
| status |
completed |
| created_at |
1764875628 |
| updated_at |
1764876957 |
| source_adapter_path |
NULL |
| adapter_path |
/home/sid/tuning/finetune/backend/output/lycsagnn- /home/sid/tuning/finetune/backend/output/lycsagnn-7573/adapter... |
| plugged_in |
False |