• No results found

Resource Planning in the Service

As part of the service offering, work packages are planned at operation level of the order in the areas of Plant Maintenance (PM) and Customer Service (CS). The process models the collaboration between the requester and the resource planner in the system.

During the process, the system transfers planning-relevant demand information to resource planning, and can also update information in the order once the assignment has been created. An overview of the fields that are significant for integration to SAP Multiresource Scheduling and backwards integration to PM/CS is provided as a table at Integrating Operation Data into SAP Multiresource Scheduling.

Backward Integrating SAP Multiresource Scheduling Data to PM/CS

Prerequisites

In Customizing, you have carried out the IMG activities under SAP Multiresource Scheduling Sources of Demand Orders .

Process

The process can run as follows, for example:

It starts with the responsible person creating a service order that is relevant for resource planning in accordance with the current Customizing settings (IMG activity Define Resource Planning Relevance for PM/CS Orders):

1. So that the system creates a demand with suitable requirements, you can enter a requirements profile directly in the order operation under General Operation Data. The system specifies the requirements profile defined in the equipment or material master by default, provided that this requirements profile exists. If you have changed the requirements profile manually, automatic determination is deactivated. To determine the default requirements profile again, choose (Activate auto. determination). The system then determines the requirements profile from the equipment or material master again.

2. So that the system can assign the operation to a resource planner, you have to enter a work center that is assigned to a resource planning node. You can use the input help to select a work center from the resource planning structure.

3. As soon as you save or release the order (based on the Customizing settings under Sources of Demand Orders Define Order Integration from PM/CS to MRS ), the system creates a demand for each planning-relevant operation and transfers the following information to SAP Multiresource Scheduling. (the information that the resource planner sees in the Scheduler Workplace depends on the Customizing settings under Set Up Scheduler Workplace Workplace Profiles Worklist Profile Create Worklist Profile ):

o Start and end date (from operation dates)

o Duration of the demand (from work of operation)

If no value is specified for the work in the operation, the system copies the default value defined in Customizing for SAP Multiresource Scheduling under Sources of Demand Orders Set Default Values for Work .

o Number of resources

o Requirements profile

o Resource planning node of demand (from work center)

o Operation user status:

Fixed date

Date agreement required

Required date

o Capacitive planning

The system sets the Capacitive? indicator if capacitive planning is to be used for the operation in accordance with the Customizing settings under Sources of Demand Orders Allow Capacitive Planning . If a fixed date is set, the system excludes capacitive planning from the outset.

o SLA dates

The SLA dates are taken from the header notification of the order (planned start and end date). To ensure that the system uses the correct header task, the task code for the task relevant to SAP Multiresource Scheduling is defined in Customizing for SAP Multiresource Scheduling under Basic Settings Assign ERP Objects .

o Status

o Partner

4. As soon as the resource planner has created one or more assignments for the demand, the system can update the following data in the order or order operation (prerequisite: you have activated backwards integration for PM/CS orders in Customizing under Sources of Demand Activate Backward Integration of Data ):

o Status (for example, order contains assignments, assignment is capacitive) if a corresponding ERP status is assigned

For more information about the transferred status, see Backward Integrating SAP Multiresource Scheduling Data to PM/CS.

o Work center of the employee or original work center for the resource planning node if an assignment has been deleted

o Work (determined based on Customizing settings)

o Header notification if an item task for assignments is defined for the affected notification type.

For each assignment that belongs to the demand of an order, the system creates an item with an item task in the relevant header notification, or deletes it if assignments have been deleted. The item number is

determined through a BAdI. If this BAdI has not been implemented, the system uses the operation task that belongs to the assignment as the default. The task in which the assignment is written depends on your Customizing settings. The planned start and end dates of the task are determined using the corresponding assignment information (date and time).

o Site Supervisor indicator on the Enhancements tab page if this has been set for the demand. The field name is determined with the BAdI

Determination of Technical Field Names /MRSS/RSG_TECH_FIELD_DET.

o Changed dates and work (determined based on Customizing settings) These changes also cause the order to be rescheduled.

Other Cases

Automatic Assignment Creation

For more information, see Automatic Assignment Creation.

1:1 Relationship Between Assignment and Demand

You can activate the following system behavior in Customizing by choosing Sources of Demand Activate 1:1 Relationship of Assignments and Demands for Order Types

: If assignments are created for several resources, for example, the system

automatically creates new demands for these assignments to ensure a 1:1 relationship between demand and assignment. It also deletes demands if assignments are deleted. If a demand is created automatically, the system creates the corresponding operation in the service order as part of backwards integration. If a demand is deleted automatically, the system deletes the corresponding operation in the service order. The system does not delete the operation if it is already confirmed or if the operation status prevents the deletion action.

Assignment Transfer from Existing Demand

With cross-functional resource processing, it may be necessary to transfer assignments from existing demands. Using the BAdI Control of Cross-Functional Resource

Processing (/MRSS/INTER_COMPANY), the system decides whether cross-functional resource processing is required. If so, it takes the following steps:

1. It determines an “original operation” based on the operation information.

2. It assigns the assignments of the original demand to the new demand.

3. It closes the original demand.

This function is executed only when a demand is created for the corresponding operation for the first time.