This release note provides information on the following changes:
To control the checks on the working time (time evaluation simulation), you previously stored one report variant of RPTIME00 for the evaluation of the actual plan and another report variant for the evaluation of the target plan. The disadvantage of this procedure was that you had to duplicate the processing steps that were identical for regular time evaluation and for target and actual planning, in three different schemas.
As of Release 4.6C, you can use one schema for all three applications. This is made possible by time evaluation function IF TPLN, which you can use to query whether a completed target plan exists on the day being evaluated.
In the course of this change, the switch PEINS SCEMI, which you previously used for determining the report variant for the actual plan in the Set Report Variant for Time Evaluation step, was deleted.
Previously, the standard system did not take
account of the Time Management status from the
Planned Working Time infotype when it checked working times (simulation
run of time evaluation). In the simulation run, the system treated all
employees as if they had Time Management status
9 - Time evaluation of planned times.
You had the option of using the
Set
Employee Status for Simulation step to change the standard
setting from BLANK (Time Management status not taken into account) to
X (Time Management status taken into account).
In Release 4.6C, the switch is set to X in the standard system. This means that you always have access to the most realistic evaluation results possible for your planning, such as the current status on overtime worked. This is particularly important in the following cases:
If you have activated the automatic
assignment option in the shift plan, any employee shift or working
times that are changed in the shift plan are automatically assigned to the
requirement with corresponding requirement times in Requirements Matchup.
The assignment is made on the basis of the options specified in the strategy
for automatic assignments. You can determine which strategy
is valid in the IMG for Shift Planning. For this reason, the
Define Strategy for Automatic Assignment for Shift Changes activity has
been added to the IMG for Shift Planning, under Info Columns and Proposal
Determination -> Set Up Automatic Proposal Determination.
Previously, you could only save the Microsoft Excel macro in the installation path of the SAP GUI . The link between macro and GUI meant that if a new SAP GUI was installed, any Microsoft Excel macros that a customer had modified could be overwritten.
To reduce the resulting workload for system
administrators, PEINS EXCME has been entered in
table T77S0.
This new entry allows you to specify whether the system searches for the
Microsoft Excel macro in the SAP GUI installation path, or in
the path defined in the environment variable.
If a customer-specific macro is saved in the path of the environment variable,
any new SAP GUI installations do not overwrite the macro.
System administrators can maintain Microsoft Excel macros by saving them on a file server.
Switch PEINS PZTEF is set to X in the standard system, which means that the employee's Time Management status is now taken into account. Time evaluation runs from the date of the PDC recalculation in the Payroll Status infotype (0003) or from the start of the planning interval.
The standard SAP system contains SAP_2 as the default strategy.
The PEINS EXCME switch has
been added to the Specify Control Parameters for Printout
function under Connecting to Microsoft Excel.
The standard SAP system contains the Blank switch.