Preventing Future Time Evaluation Issues While Maintaining Testing Flexibility in QA
- by Imran Sajid, Senior Education Consultant, SAP
- November 17, 2014
Learn how to create an SAP Time Management solution to restrict the running of time evaluation in the future in your production environment, while allowing time evaluation to run in the development and quality environments. With this functionality, you alleviate the risk of running time evaluation into the future in the production environment, and you also never need to manually adjust the schema to allow (or disallow) this functionality when testing changes.
By reading this article, you will learn:
- About SAP ERP HCM Time Management and future time evaluation best practices
- How to create an enhancement spot to add code in an SAP ERP HCM object
- How to create a Time Management custom operation
- How to create a Time Management personnel calculation rule (PCR) that calls a custom operation
- How to insert a PCR into a time schema with standard IF logic
- How to run time evaluation to see the results of the operation
SAP ERP HCM Time Management schema operations and personnel calculation rules (PCRs) are used to determine which environment the user is in and whether time evaluation should be allowed to run into the future (e.g., beyond the current date). Time evaluation uses logic within the time schema to turn future time evaluation on or off depending on the environment.
By creating and implementing an SAP Time Management custom functionality, you can restrict time evaluation from running in the future in your production environment. Using this custom functionality also alleviates the need to manually adjust the schema to allow this functionality when testing changes.
The reason this is a big deal is because when you run time evaluation in the SAP ERP HCM Time Management system to generate quotas, allowing it to run into the future can cause incorrect quota balances, as well as other issues. For example, when employees are clocked in and but don’t clock out, this schema can generate errors that cause confusion. In one scenario, time evaluation was accidentally run for three months into the future for a large population that used clock times and absence quotas, which resulted in risky time-cluster cleanup, which is not recommended in the production system. In this case, this did not result in incorrect or extra pay for the employees, but did create an issue with incorrectly calculated quota balances.
SAP ERP HCM System Best Practices
The SAP ERP HCM system provides the flexibility of testing changes out into the future by allowing time evaluation to be run into the future via the standard schema. This is necessary for testing changes for the upcoming year and each year when updating the holiday calendar or adding new policies. In a production environment you should never run time evaluation in the future because it can add errors to employees’ data.
Would you like to see this full item?