SAP Knowledge Base Article - Preview

3360430 - Standard Scheduling: Updates to Schedules

Symptom

Standard scheduling has a number of different ways for the schedule at the timesheet to be updated. When multiple of these are used, there is a priority order.

All of these methods have similar behavior when working with a new timesheet. When a timesheet that has never been saved before is pulled up, the system will populate the Schedule tab with appropriate information based on the assigned Schedule Template, Cycle, or similar. If the timesheet is still not saved while viewing it, the schedule information is released when navigating away, and will once again be repopulated when the timesheet is pulled up, accounting for any changes. Thus, future timesheets which have never been saved before will reflect the current state of the specific assignment and related schedule.

However, the system behavior can differ with existing timesheets that have already been saved at some point. Timesheets could have been saved manually, or may have been created for a script, a Time Off Request, or even a specialized calculate job that includes future periods. Regardless of the reason, if the timesheet has been saved, the related information has been stored in the database including the schedule at the time it was saved. That schedule at the time of the save is now associated with the period, and may not update automatically to reflect later changes.

The easiest way to see the periods that have already been saved for an employee are through direct database access or reports. The SQL query below will return all periods that have been saved at least once. Reports will only be able to return data about periods that have been saved, so using a schedule report is a useful check.

select e.display_employee, am.description, ep.pp_begin, ep.pp_end
from employee e, employee_periods ep, asgnmt_master am
where e.employee = ep.employee
and ep.asgnmt = am.asgnmt
and e.end_eff_dt = to_date('3000-12-31', 'yyyy-mm-dd') -- Oracle date format
-- and e.end_eff_dt = '3000-12-31' -- SQL Server date format
and e.display_employee in ('?')
order by e.display_employee, ep.pp_begin, am.description;

 


Read more...

Environment

SAP Time and Attendance Management by WorkForce Software (All versions)

Keywords

Demand Scheduling, Forecasting, Scheduling, Assign schedule , KBA , XX-PART-WFR-TAM , SAP Time and Attendance Management by Workforce Software , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.