The resource planner checks the alerts and can change the resource planning as required.
Since the conditions for resource planning are constantly changing and each change to assignments can generate new alerts, alert monitoring is a continuous process.
Prerequisites
In Customizing for SAP Multiresource Scheduling, under Set Up Scheduler Workplace Workplace Profiles , you have:
• Defined the check classes and profile under Check Profile
• Defined the alert types and profile under Alert Profile
Features
Alerts• There are a number of different alert types that can refer to dates, capacities, or availabilities, for example. The way in which the alerts are generated and displayed depends on how the alert type is configured.
• There are different types of alert, which are indicated by the following icons:
o ( Information) Information
o (Warning) Warning
o (Error) Error
• Alerts are displayed in a list in the Alert Monitor. Each alert row contains the category and type of alert, the object (for example, the assignment) associated with the alert, as well as other contextual information. For more information, see Alert Monitor.
• You can call the reference object (such as the assignment) or data about the reference object directly by double-clicking the alert row.
• You can confirm alerts in your personal profile or globally for the entire organization. The alert is then no longer displayed.
Checks
For more information, see Checks.
Activities
• The system carries out checks when the resource planner makes changes in the planning board.
• The system displays all alerts that are generated in the Alert Monitor.
• The resource planner checks the alerts and makes any necessary changes to resource planning.
• If the alerts affect the order data, the resource planner can display the order to check the data.
• If dates are moved, the resource planner informs the relevant personnel resources and, where necessary, the customer.
Checks
Checks are combined in a check class that refers to a specific data area (for example, resource utilization). The role of a check class is to carry out the check using attributes and methods, and to communicate with the Alert Monitor (that is, to create or remove corresponding alerts).
In Customizing for the alert profiles, you can specify that the planning board is not saved if specific alerts are generated.
Prerequisites
• You have created and defined the required check classes in the Class Builder (transaction SE24).
Check Class Meaning
/MRSS/CL_SGE_CHECK_RESCAP Checks for resource utilization /MRSS/CL_SGE_CHECK_RELAT Checks relationships between
assignments
/MRSS/CL_SGE_CHECK_ASG Checks for assignment data /MRSS/CL_SGE_CHECK_ASG_TIME Checks for time-dependent alerts /MRSS/CL_SGE_CHECK_ASG_TR Checks for demands with date rule /MRSS/CL_SGE_CHECK_OVER Checks for collisions
/MRSS/CL_SGE_CHECK_QUAL Checks for qualifications of resources /MRSS/CL_SGE_CHECK_LINK Checks for tool links
/MRSS/CL_SGE_CHECK_CLOCK Checks related to time recording data
/MRSS/CL_SGE_CHECK_DEM Checks for demands
/MRSS/CL_SGE_CHECK_DEMAND Checks for demands
/MRSS/CL_SGE_CHECK_DEM_T Checks whether demand was planned on time
/MRSS/CL_SGE_CHECK_INTEGRATION Checks whether assignments are to be created automatically for assignments
• In Customizing for SAP Multiresource Scheduling, you have assigned the existing check classes and defined the check profile under Check Profile.
Features
• Resource Utilization
The availability is calculated using the basis availability and the time allocations. The utilization data is calculated from the planned assignments.
o Alerts are generated if the resource planner creates an assignment for an operation before the production resources and tools are available or if no availability date is determined.
o Alerts are generated if a personnel resource is overloaded in a specific period. The same applies to teams. The utilization of teams is calculated from the team assignments and the assignment total at individual resource level.
• Capacities
The system checks the resource capacity.
o Teams
The capacity of a team is calculated from the total capacities of the team members. The utilization is calculated from the team assignments and the assignment total at individual resource level.
• Relationships Between Assignments
The system checks for condition violations between assignments for demands from Plant Maintenance (PM), Customer Service (CS), and Project System (PS). The conditions are taken from the underlying order. They are assigned explicitly (for relationships) or implicitly (for production resource and tool items).
The check is usually carried out for assignments. If there is no assignment for a demand, the demand data is taken from the order.
The system carries out the following checks:
o Relationships between assignments or demands
o Availability of tools
o Concurrency between assignments of several personnel resources for a demand if more than one person is required for the demand
• Assignment Data
o The system checks whether the assignments are within the order
operation dates. For example, it checks whether an assignment is within the period between the earliest start and latest end date. It also compares the duration of all assignments of a demand with the planned duration of the order operation.
o Assignment not yet started: The system generates this alert if an assignment has not yet been started although the time of the planned start (plus a duration defined in Customizing) has been reached. To
determine whether the assignment has been started, the system evaluates its status, which is determined from the time data.
o Assignment not yet finished The system generates this alert if an assignment has not yet finished even though the planned end time has expired. To determine whether the assignment has finished, the system evaluates its status, which is determined from the time data.
o If travel times are active, the system also checks whether there are conflicts with travel times (for example, overlaps with other travel times, assignments, or absences). This check is not available for demands from cProjects.
o The system checks whether capacitive assignments overlap with absences or other assignments. It also generates alerts if capacitive assignments are not provided on time. This is the case if the capacitive assignment is not started on time before the scheduled end date minus the planned duration and buffer defined in Customizing.
• Planned Working Time Frame
The system checks whether an assignment starts between the normal working time and the planned working time, and whether the duration of the assignment is longer than the normal working time. It also checks whether the start of the first assignment and the end of the last assignment within the planned working time frame are further apart than the duration of the normal working time.
• Date Rules
The system checks demands with date rules from Project System to determine whether the assignments correspond to the date rule defined in the network activity.
• Qualifications
When you create an assignment for a personnel resource, the system checks whether the resource's qualifications meet the mandatory requirements of the corresponding order operation.
• Links
If a tool is linked to a personnel resource, the system automatically creates assignments for the tool if it is required to execute the assignment that the personnel resource is to carry out.
The system checks whether there is an assignment for the tool in the link period but there is no corresponding assignment of the personnel resource. This check is available for demands from Plant Maintenance (PM) and Customer Service (CS).
• Time Recording
The system compares the time recording data of the personnel resources with the planned times of the assignments.
It carries out the following checks:
o Delayed start of work
o Delayed end of work
o Early end of work
o Degree of completion
• Demands
o Orders for the same customer: The system generates this alert if there are unplanned demands in the current worklist of the planning board when you create an assignment, these demands belong to the same customer, and are within a period defined in Customizing. The system also generates an alert if there are assignments for the same customer in this period or if the resource for the assignment belongs to the same resource planning node as the resource for the new assignment. To check the customer to which a demand belongs, the system evaluates a partner role of the order.
o SLA violation: The system generates this alert if no assignment has been created in a specific period before the latest start of a demand. You can specify this period in Customizing.
o Site supervisor indicator: The system checks whether an order meets the necessary site supervisor assignment as specified in the Customizing settings for demands from Plant Maintenance (PM), Customer Service (CS), and Project System (PS). This is the case only if there is exactly one assignment for the demands of the order and the site supervisor indicator has been selected for this assignment.
• Dates (date-based planning)
This check is carried out at demand level from the order. The system checks whether an assignment is planned for a demand in good time before the planned start.