Common Pitfalls to Avoid
|
Pitfall |
Consequence |
Prevention |
|---|---|---|
|
Enabling Position Control on a job class after pay rate records exist |
System blocks the change |
Enable Position Control on job classes before creating pay rate records |
|
Setting effective dates outside the current/next fiscal year |
Validation error on save |
Verify fiscal year boundaries before entering effective dates |
|
Distributions that do not total exactly 100% |
Position cannot be saved |
Always verify the percentage sum before saving |
|
Running New Year Positions without crosswalk data (specific to TX) |
Distributions may be invalid for the new year |
Populate crosswalk tables before rollover |
|
Enabling workflow without configuring approvers |
Change requests stuck in Open status indefinitely |
Configure approval levels and approvers before enabling workflow |
|
Deleting positions without understanding the impact |
Loss of historical data and occupant records |
Restrict 10555 security; use deletion reports to review before confirming |
|
Posting batch positions without reviewing the pre-posting journal |
Invalid data posted to live tables |
Always review PrePostBatPn.rpt before posting |
|
Turning off Position Control after positions exist |
System blocks the change |
Plan data cleanup if Position Control must be turned off |
|
Not setting calendar cycle effective dates |
Positions may be skipped during the fiscal year rollover |
If a calendar cycle has no effective date set, the effective date becomes 01/01/1900 and is treated as invalid. Explicitly setting the effective date is recommended for predictability. |
|
Running Personnel Budgeting - Post to Position Control with mismatched full account settings |
Unclear validation errors on distributions |
Verify the Fund Accounting profile's full account settings before posting |
Recommended Setup and Configuration Order
Follow this sequence for a clean initial deployment:
-
Configure Full Account Structure (if applicable).
-
Enable Position Control on the Human Resources Profile page.
-
Enable Position Control on each participating job class using Batch Position Control.
-
Set up calendar cycles with effective dates.
-
Configure user-defined fields for positions (if needed).
-
Create positions using Batch Position Control:
-
Import or manually enter positions in batch.
-
Validate using batch reports.
-
Post batch positions to live tables.
-
-
Verify positions on the Position Control page.
-
Assign security resources to all Position Control users.
-
Configure workflow (if using Advanced Workflow):
-
Enable global and Position Change Request workflow settings.
-
Set up approval levels and approvers.
-
Test a change request through the full approval cycle.
-
-
Switch from T - Tracking Mode to Y - Use Position Control when ready for production.
-
Communicate the go-live to end users and provide training on the Position Control, Change Request, Position Requisitions, and Employee Transfer pages.