PTMW inconsistent processing of substitutions and breaks

[former_member291090]

In PTMW a normal schedule is overwritten with a substitution in the time data part of the screen. When you enter (overwrite) a substitution with the same working times as the original schedule the break is not applied. If you overwrite the schedule with a substitution with a different starttime then the break does appear.

We do not want the break to show up. Where do we solve this issue. In the BADI PT_BLP_USER? In time evaluation?

We have SAP 4.6c with support package C1.

-

---

Problem in detail

If you overwrite the regular working schedule there are a few

scenarios, which seem inconsistent to us:

1. The working schedule (23:00 - 7:00) is overwritten with a

substitution (23:00 - 7:00), so new working times are the same: the

break disappears. Why? The break (03:00 - 04:00) should be applied.

2. The working schedule (23:00 - 7:00) is overwritten with a

substitution (14:00 - 22:00) which has working times that end before

the original working schedule would start, the break (03:00 - 04:00) is

applied, while working times are outside the breaking time.

3. The working schedule (23:00 - 7:00) is overwritten with a

substitution (21:00 - 05:00), which has working times that begin before

the original working schedule would start, the break (03:00 - 04:00) is

applied.

What we do not understand is that if you do not change working times

with a substitution the breaks disappears completely (case 1) but if

you change it a little bit (case 3) breaks are applied? In both cases

the break is within the time of the substitution, why then a different

reaction?

Secondly if a break is outside substitution times the break is still

copied (case 2) while a break within working times of a substitution

(case 1) disappears. It seems to be inconsistent.

[Former Member]

I did try your test and in case 1, you are right the break disapear but only if you check in the field in the detail part (on the bottom). Break is still there in the column (in the data part). If you run time eval, the break is taken into consideration anyway. Do you confirm it reacts the same for you?