Hi,
Situation is that a few -, very few - of times that should be approved manager in process through catex-BADI_cats_approval and TS31000007 is slipping through and ends up in catsdb being approved, but not by the manager, instead approved by the employee, In the same second as entered. It may be identical times, saved in the same second by same employee that goes two ways - one to manager for approval, the other directly approved. I. e it seems to be performance related somehow. We have done a report that corrects them, by setting value to zero, then approve, then set back the value and it ends up by a repeat of the approval process. But before implementing this rather complicated correcting process, it would be good to make an attempt to simplify the process. There are two ways in this case. One is to shorten up feature Catex. Now it has entries for all times that should be approved (the vast majority) and - else -> approval is not neccessary - feature would be considerably shorter the other way around. Otherwise badi_CATS_Approval could be inactivated - as of now it is identifying managers position, which could be moved to a rule in the task itself. As other customes seems to have similar problems - (there is a note for this which is implemented but gave no effect) - maybe someone could contribute with comment on this matter? B rgds, Marianne