on 08-19-2015 5:34 AM
I have been having discussions with SAP where critical processes like time evaluation and payroll have ABAP during processing.
The majority of these instances are where incorrect master data has existed (or been created) for an employee, however the consequence of these dumps is that all employees after the one with the issue are not run. This is a painful occurrence to recover from for payroll processing as payroll / time eval is often run overnight and therefore the issue is not discovered until the morning. At which point the employee needs to be identified (reasonably simple to do), excluded and payroll / time eval run for the remaining employees.
This then has an impact on the business as payroll needs to remain locked during business hours while the processing is completed.
Has anyone else had similar problems? If so have you established any overall solution?
Given the basic premise of SAP's payroll solution is that data is calculated and validated during processing (rather than when it is input) I believe it should ensure that any exception that occurs during payroll or time eval processing is caught and an error given so the process can move on to the next employee, rather than ABAP dumping with an uncaught exception which kills the job.
Examples I've had of this are:
1. Time evaluation creating an IT2006 record (in function QUOTA) where one already exists with the same key fields
2. Negative record causing error in a calculation, resulting in an ABAP dump
3. Incorrect field definition in a SAP standard program that is called for employees who are passed retirement age
4. Field overflow
5. Greater than (SAP standard) coded for number of positions for an employee
It could just be the complexity and size of some of my customers, but I was wondering if anyone else was experiencing the same and if so I may request an overall enhancement (as part of SAP's customer influence program) to the payroll / time solution to catch uncaught exceptions.
I don't have a problem with the payroll not completing for employees with issues, it's the consequence of how it fails that I believe should be addressed.
Hello
We have had a ABAP dump while processing Time evaluation.
Due to incorrect PCR Field overflow error caused ABAP Dump and thereby stopping whole of the job which was set in sequence to follow next one.
Regards
Ajay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
99 | |
11 | |
11 | |
6 | |
6 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.