mrs700 sp04 config_guide

Configuration Guidefor SAPMultiresourceScheduling

Release 7.0 SP04

Public

Document Version 4.0 – 10/01/2010

Configuration Guide

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p,System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,Power Architecture, POWER6+, POWER6, POWER5+, POWER5,POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, SystemStorage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,WebSphere, Netfinity, Tivoli and Informix are trademarks orregistered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. andother countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe Systems Incorporated inthe United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of theOpen Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,ByDesign, SAP Business ByDesign, and other SAP products andservices mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product andservice names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informationalpurposes only. National product specifications may vary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors or omissionswith respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following Internet address:service.sap.com/instguides

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

Typographic ConventionsType Style Represents

Example text Words or characters quoted fromthe screen. These include fieldnames, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation.

Example text Emphasized words or phrasesin body text, graphic titles, andtable titles.

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, table names,and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Example text Output on the screen. Thisincludes file and directorynames and their paths,messages, names of variablesand parameters, source text,and names of installation,upgrade and database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Configuration Guide for SAP Multiresource Scheduling

October 2010 4

Contents

1 Introduction ..................................................................... 101.1 SAP Multiresource Scheduling Functional Overview .. 10

2 Installation ....................................................................... 112.1 SAP Multiresource Scheduling 700 Installation ........... 112.2 Upgrade to SAP Multiresource Scheduling 700 ........... 11

3 Configuration and Customizing: GeneralConfiguration .................................................................. 12

3.1 Configuration of Basic Settings ..................................... 123.1.1 Basic Settings ..................................................................... 123.1.2 Work Center ........................................................................ 133.1.3 Planning Nodes and Evaluation Paths ............................. 143.1.4 HR Integration ..................................................................... 15

3.2 Configuration of Multiple Backend Scenario ................ 163.2.1 Define RFC destinations for logical systems ................... 163.2.2 Define active scenarios...................................................... 173.2.3 HR Data from Remote System ........................................... 173.2.4 Parameters for reprocessing of integration queue ......... 173.2.5 Automatic Activation of SAP Multiresource Scheduling

Integration Queues ............................................................. 183.2.6 New alert for error queues ................................................. 18

3.3 Configuration of PM/CS Integration .............................. 183.4 Configuration of PS Integration ..................................... 19

3.4.1 Process Integration ............................................................ 193.4.2 Field Control in Network Header and Activity .................. 213.4.3 Demand View Integration ................................................... 22

3.5 Configuration of Web-based Resource ManagementIntegration ...................................................................... 23

3.5.1 Status Configuration .......................................................... 233.5.2 RM Master Data Settings Configuration

(/MRSS/V_RM_MDATA) ...................................................... 253.5.3 Authorization Object /MRSS/WRM .................................... 253.5.4 Maintaining Evaluation Paths for Authorization .............. 263.5.5 Workflow Configuration ..................................................... 26

3.6 Configuration of cProjects Integration .......................... 283.6.1 Cutomizing for the integration of cProjects ..................... 283.6.2 Number Ranges .................................................................. 32


July 2010 5

3.6.3 Master Data ......................................................................... 33Define Business Partner ..................................................................... 33Abstract Status Customizing .............................................................. 33Recommendation for cProjects UI settings........................................ 35

3.7 Configuration of CRM Integration .................................. 363.7.1 Define Order Relevance for Resource Planning .............. 363.7.2 Define date types for demand integration ........................ 363.7.3 Define location of service for demand.............................. 373.7.4 Activate resource planning in CRM service order items 37

3.8 Configuration of Persistence Layer ............................... 393.9 Netweaver Demand Settings .......................................... 41

3.9.1 Control assignment processing ........................................ 413.9.2 Allow Stretched assignments ........................................... 413.9.3 Allow capacity Planning .................................................... 413.9.4 Allow abstract assignments .............................................. 413.9.5 Partial concretization of stretched assignments ............. 423.9.6 Site supervisor ................................................................... 42

4 Configuration and Customizing: SpecificConfiguration .................................................................. 43

4.1 Backward Integration ...................................................... 434.1.1 Forward Integration from PM/CS to SAP Multiresource

Scheduling .......................................................................... 444.1.2 Backward Integration from SAP Multiresource

Scheduling to PM/CS ......................................................... 454.1.3 General Settings ................................................................. 46

4.2 Technical Settings for Resource Selection .................. 464.3 Manager Planning Board ................................................ 464.4 SAP Multiresource Scheduling Qualifications ............. 474.5 Supplement Concerning the Static URL to Access

Employee Profiles on Enterprise Portal ...................... 524.6 Smart Forms for Employee and Requirements

Profiles ........................................................................... 524.7 Standard Bar Chart Customizing ................................... 524.8 Capacity View .................................................................. 544.9 Travel Times ..................................................................... 55

4.9.1 Profiles ................................................................................ 56Profile for Geocoding .......................................................................... 56Profile for Distance Calculation .......................................................... 57Profile for Map display in planning board (optional) ......................... 57Travel Profile........................................................................................ 58Assigning Travel Profiles to Resource Planning Nodes .................... 58

4.9.2 Travel Time Calculation and Distribution ......................... 59Assign Travel Time Mode .................................................................... 59


October 2010 6

4.9.3 Activating Travel Time in the Planning Board Profile ..... 594.10 Optimization ..................................................................... 60

4.10.1 Introduction ........................................................................ 60Basic Setting in RCCF ......................................................................... 61

4.10.2 Optimization Profile............................................................ 62Optimization Parameters for Resources ............................................ 62Suitability dependent change to cost rate .......................................... 63Factors for Demand Priority ................................................................ 64Optimization Parameters for Demands .............................................. 65

4.10.3 Logging of Optimization Runs .......................................... 664.10.4 Optimization Scenarios...................................................... 674.10.5 Assigning Profiles to Planning Board Profile .................. 67

5 Master Data Setup .......................................................... 695.1 Personal Resources: HR or not? ................................... 69

5.1.1 Using HR Data .................................................................... 69Creating HR data ................................................................................. 69Using qualifications............................................................................. 71

5.1.2 Using Business Partners ................................................... 73Create Business Partner ..................................................................... 73Using Qualifications ............................................................................ 74Transfer Business Partner .................................................................. 74

5.2 Organizational Structure................................................. 745.2.1 Create Organizational Structure ....................................... 755.2.2 Linking with Work Centers ................................................ 75

5.3 Maintaining SAP Multiresource SchedulingResources ...................................................................... 78

5.3.1 Example: Daily Interval for Time Allocation ..................... 795.3.2 Example: Weekly Interval for Time Allocation ................. 80

6 The First Demand ........................................................... 816.1 Order and Order Operation............................................. 816.2 Production Resource and Tool ...................................... 83

6.2.1 Create Production Resource and Tool ............................. 836.2.2 Assign Production Resource and Tool to Operation ...... 83

6.3 Usage of Several Production Resources and Tools .... 846.3.1 Create Material .................................................................... 856.3.2 Assign Material to Several Production Resources and

Tools .................................................................................... 856.3.3 Assign Production Resource and Tool to Operation ...... 86

6.4 Direct Assignment of Production Resources andTools in the SAP Multiresource Scheduling PlanningBoard .............................................................................. 86

6.5 Definition of HR Qualifications....................................... 866.5.1 Create a HR Qualification Catalog .................................... 86


July 2010 7

6.5.2 Assign HR Qualifications to Order Operation .................. 876.5.3 Assign HR Qualifications to Employee ............................ 87

6.6 Requirements Assignment on Operation Level ........... 887 Enhancing SAP Multiresource Scheduling ................. 90

7.1 Worklist ............................................................................ 907.1.1 Additional Customer Fields in Item Worklist ................... 90

Customizing and Code Example:........................................................ 907.1.2 Highlighting Worklist Items ............................................... 91

Example 1: ........................................................................................... 91Example 2: ........................................................................................... 95

7.1.3 Important Standard Fields ................................................. 987.2 Business Add-Ins (BAdIs) .............................................. 987.3 Further Important Interfaces .......................................... 99

7.3.1 Table /MRSS/C_SGE_SCA ................................................. 99Additional Data for Resource .............................................................. 99Go to Display Order ............................................................................. 99

7.4 Checks and Alerts ......................................................... 1007.5 Additional Information for Customizing ...................... 106

7.5.1 Planning Board Profile ..................................................... 106Time Granularity ................................................................................ 106Splitting .............................................................................................. 106

7.5.2 UI Profile ............................................................................ 106Screens .............................................................................................. 106Additional Menu Buttons .................................................................. 107

7.5.3 Day-based Scheduling ..................................................... 1078 Assignment of Technician Work Centers .................. 108

8.1 How to assign a technician work center to a resource1088.2 How to check what HR work center and logistic work

center is assigned to a resource ............................... 1098.3 How to check whether the assigned work center is a

technician work center................................................ 1108.4 What to do if the assigned work center is not a

technician work center................................................ 1119 Workflow Customizing ................................................. 113

9.1 Basic Workflow Customizing ....................................... 1139.2 Agent Assignment Definition ....................................... 1149.3 Customizing Approval Workflow Settings-Event

Linkage ......................................................................... 1159.4 Setting up the SMTP Mailing for Workflows ............... 116

10 TREX Configuration ..................................................... 11710.1 TREX Integration Requirements .................................. 117


October 2010 8

10.2 TREX Configuration. ..................................................... 11810.3 Testing the TREX Integration. ...................................... 11810.4 TREX Compatibility chart. ............................................ 119

11 Setting up the Employee Profile Web UI .................... 12011.1 Integration ...................................................................... 12011.2 Before You Start ............................................................ 12011.3 SAP Multiresource Scheduling Backend

Configuration ............................................................... 12011.4 Application Check ......................................................... 122

12 Initial Setup Guide for SAP Multiresource SchedulingEmployee Profile Workflows ....................................... 124

12.1 Basic settings ................................................................ 12412.1.1 Customizing Settings ....................................................... 12412.1.2 Agent Assignment ............................................................ 12512.1.3 Event Linkage Activation ................................................. 12512.1.4 Setting up the SMTP mailing for workflows ................... 125

12.2 Organizational settings in PPOME .............................. 12612.2.1 Starting with a blank organizational unit ........................ 12612.2.2 Creation of a position under the organizational unit..... 12712.2.3 Assignment of resources to the newly created position

........................................................................................... 12812.2.4 Creation of the manager position ................................... 13012.2.5 Assignment of a resource to the newly created manager

position ............................................................................. 13112.3 Customer Infotypes for Controlling the Approval

Process ......................................................................... 13112.4 Resource Contact Information ..................................... 135

13 Enhancement of Object Manager Scenario VERIMULT ........................................................................................ 137

14 SAP Multiresource Scheduling BW-Extractors......... 14014.1 Customizing and Package ............................................ 14014.2 Terms for a Better Understanding ............................... 14014.3 BW – Data Extraction: Assignments ........................... 140

14.3.1 Data Dictionary Objects ................................................... 14014.3.2 Business Content: Data Sources .................................... 14114.3.3 Program Units ................................................................... 14114.3.4 General Program Structure ............................................. 142

14.4 BW – Data Extraction: Alerts ........................................ 14214.4.1 Alerts from scheduling .................................................... 142


July 2010 9

Data Dictionary Objects .................................................................... 142Business Content: Data Sources ...................................................... 143Program Units .................................................................................... 143

14.4.2 Alert components of scheduling process ...................... 143Data Dictionary Objects .................................................................... 143Business Content: Data Sources ...................................................... 144Program Units .................................................................................... 144

14.4.3 Alerts: Confirmed Messages per User while SchedulingProcess ............................................................................. 144Data Dictionary Objects .................................................................... 144Business Content: Data Sources ...................................................... 144Program Units .................................................................................... 144

14.5 BW – Data Extraction: Links for the SchedulingEngine ........................................................................... 145


14.6 BW – Data Extraction: Teams in the SchedulingEngine ........................................................................... 146


15 Appendix ....................................................................... 14815.1 Transactions .................................................................. 14815.2 Reports ........................................................................... 14915.3 APIs ................................................................................. 15015.4 Useful Tables ................................................................. 15115.5 Abstract Partner Roles.................................................. 15215.6 Abstract Status .............................................................. 15215.7 Overview of Database Tables ....................................... 154

15.7.1 Customizing Tables.......................................................... 15415.7.2 Data Tables ....................................................................... 158

15.8 External Interfaces ........................................................ 16115.9 Creating Object GUIDs .................................................. 161

Introduction

October 2010 10

1 IntroductionThis document will give a rough overview about the necessary Customizing and master data setupfor the SAP Multiresource Scheduling solution. It focuses on the steps necessary to get SAPMultiresource Scheduling working after an installation. It does not cover other Customizing steps –for example, adapting SAP Multiresource Scheduling to personnel needs. Also it may not addressevery possible situation, as this differs in each case. It represents a common selection of necessarysteps.

For detailed coverage, please see the available Application Help (KW documentation) and theCustomizing documentation in the SAP Multiresource Scheduling system (Transaction/MRSS/IMG).

NoteWe use screenshots throughout this document as a visual aid in betterunderstanding described concepts and procedures. These screenshots may notnecessarily reflect the customer-specific view.

To get SAP Multiresource Scheduling running after installation, you must basically execute thefollowing steps:

1. Configure the SAP Multiresource Scheduling integration with PM/CS or PS.

2. Configure the SAP Multiresource Scheduling Basis.

3. Configure the SAP Multiresource Scheduling.

After completing these steps, you will be able to work with SAP Multiresource Scheduling in itsdefault configuration. This means that you will use the pre-delivered profiles for the workplace. Ofcourse it is possible to change the look of SAP Multiresource Scheduling in many ways. For adescription of these settings, please see the available Application Help.

1.1 SAP Multiresource Scheduling Functional OverviewInformation about the SAP Multiresource Scheduling functionality is contained in the ApplicationHelp, in SAP Help Portal at http://help.sap.com SAP ERP SAP Multiresource Scheduling.

http://help.sap.com/

Installation

July 2010 11

2 Installation2.1 SAP Multiresource Scheduling 700 InstallationThe Master Guide is the central starting point for the technical implementation of SAPMultiresource Scheduling 7.0. You can find the most current information about the technicalimplementation of SAP Multiresource Scheduling 7.0 and the latest installation and configurationguides on SAP Service Marketplace at http://service.sap.com/instguides.

2.2 Upgrade to SAP Multiresource Scheduling 700The Migration Guide provides important information for consultants, partners and customers whoare upgrading from MRS 610 or an earlier release to SAP Multiresource Scheduling 7.0, as well asupgrading from an older release to a newer release of SAP Multiresource Scheduling. You can findthe most current information about the technical implementation of SAP Multiresource Scheduling7.0 and the latest installation and configuration guides on SAP Service Marketplace athttp://service.sap.com/instguides.

Configuration and Customizing: General Configuration

October 2010 12

3 Configuration and Customizing:General Configuration

After installation, SAP Multiresource Scheduling needs to be enabled in your system. This chapterdescribes the mandatory initial configuration of SAP Multiresource Scheduling. Chapter 4 “SpecificConfiguration,” is optional and intended for the initial configuration of some specific SAPMultiresource Scheduling functionalities.

This chapter describes the initial configuration of SAP Multiresource Scheduling. The configurationof basic settings will be described first, in chapter 3.1. In subsequent chapters, the scenarioconfigurations will be described.

If you plan to set up the PM/CS scenario in SAP Multiresource Scheduling, work through chapter 3.3. PS scenario in SAP Multiresource Scheduling, work through chapter 3.4.

3.1 Configuration of Basic SettingsThe following paragraphs give detailed information on configuring the Basic Settings for SAPMultiresource Scheduling.

3.1.1 Basic SettingsLaunch transaction /MRSS/IMG and follow the SAP Multiresource Scheduling Basic Settingspath. In the Configure Basic Settings Customizing activity, you define the general setting for SAPMultiresource Scheduling.

Figure 1


July 2010 13

Team AssignmentsIf set to ‘X,’ an assignment can be created on team level. If initial, theassignments created on team level are distributed to each team member. Anassignment for the resource “Team” is not created in this case.Capacitive assignmentsDefine whether a capacitive planning of assignments is allowed in principle.Activate SAP Multiresource Scheduling BasisDefine that SAP Multiresource Scheduling Basis should be used to manageresources.Resource ClassVia the resource class, you can define if you want to use the HR Integration ornot. If the ‘HR Resource’ option is active, the human resources can be transferredtogether with their availability from HR to SAP Multiresource Scheduling.Furthermore it is possible to set up a back integration from SAP MultiresourceScheduling to HR. If the ‘Business Partner’ option is active, the human resourceshave to be created as Business Partner. In this case the resources get theiravailability via SAP Multiresource Scheduling Reports.SAP Multiresource Scheduling QualificationsHere you can define if you want to use HR Qualifications or the SAPMultiresource Scheduling own qualification concept. Hint: HR Qualifications canbe assigned to Business Partners or Personal Numbers. That means HRQualifications can be used independent of the selected resource class.Activate Authority Check via evaluation pathsDefine whether you want to perform authority checks via evaluation paths. If theflag is set to “X”, evaluation paths will be used to determine user authorizationsfor planning nodes. If the flag is left blank, authorization objects will be used.

3.1.2 Work CenterVia the Customizing node Assign Work Center Types in the sub-folder Assign ERP Objects youassign ‘real’ work center categories to the abstract work center categories that are used within SAPMultiresource Scheduling.

Figure 2

You have to assign the Work Center Categories to the Categories: Work Center of Technician: Work Centers of these Work Center Categories can

be written back into the Order Operation when an assignment gets created.Prerequisite is the 1:1 relation as well as an active back integration.


October 2010 14

Work Center with resource planning node: Work Centers of these Work CenterCategories can be used to find a relevant Planning Node to the Work Center.

3.1.3 Planning Nodes and Evaluation PathsVia the Customizing node: Define resource planning nodes and evaluation paths you can definehow required data can be determined within SAP Multiresource Scheduling in the organizationalmodel.

This is one of the most relevant Customizing activities for certain processes. If this is needed orrelated to other Customizing, it is linked to this chapter.

Figure 3

For more details, refer to the field help documentation.

To get the right objects in the Status Management, an object type has to be defined. This has to bedone in Customizing activity Assign Object Type for Number Range Determination for


July 2010 15

Assignments. The value has to be set to ‘E1’. This is necessary for technical reasons and shouldnot be changed.

Figure 4

NoteIf you have implemented SAP Note 1456178 (2010), you do not have to maintainthe Customizing activity Assign Object Type for Number Range Determination.

3.1.4 HR IntegrationIf you have an active ‘HR Resource’ Resource Class, you have to set up the Configure Settings forHR Integration Customizing activity.


October 2010 16

Figure 5

Here you define how the HR Info Types are mapped against the Time Allocation Types from theSAP Multiresource Scheduling Basis. This Customizing is used for the integration from HR to SAPMultiresource Scheduling (mandatory) and from SAP Multiresource Scheduling to HR (obligatory).

If your SAP Multiresource Scheduling and HR are not running on the same system, SAPMultiresource Scheduling also needs to be installed to the remote HR system. In this case, theCustomizing settings for SAP Multiresource Scheduling do not need to be done in the HR system,since only the HR communication part of the SAP Multiresource Scheduling will be used.

Futhermore you have to customize the RFC Connection from the HCM System to the System SAPMultiresource Scheduling is running in. This can be done in the SAP Multiresource SchedulingCustomizing activity Specify RFC Destination of MRS System. This is used in the‘/MRSS/HCM_RPTWFMIF’ Transfer Report and in the Integration of time allocations to HRObjects.

If the SAP Multiresource Scheduling HCM Part is transferred into the HCM System you have to dothis Customizing via transaction SM30 with in table ‘/MRSS/C_HCM_MRSD’ because in this casethe report ‘/MRSS/HCM_RPTWFMIF’ requires this information which is now in the HCM System.

3.2 Configuration of Multiple Backend ScenarioYou can integrate demands from multiple systems into a single SAP Multiresource Schedulingsystem. To enable this, the multi-backend scenario needs to be configured. This Customizing isdefined in the following location: Basic Settings Configure Multiple Back-End Systems.

3.2.1 Define RFC destinations for logical systemsEach system is identified uniquely by its logical system name. In this customizing, the RFCdestination must be maintained against each logical system.

For the own logical system (where SAP Multiresource Scheduling planning is done) the destinationfield must be left as blank value.

RecommendationAll RFC destinations should be trusted destinations since the user IDs are alsoused for the RFC communication. Via the user ID the authorization checks areperformed.

Some example entries are shown in the figure below:

Figure 6


July 2010 17

3.2.2 Define active scenariosIn this Customizing, you can define the scenarios that are active in each system that is connectedto SAP Multiresource Scheduling. Here you can specify if a system is a R3 system or not. Anexample entry is shown in the figure below:

Figure 7

3.2.3 HR Data from Remote SystemIf you use the HR data from a remote system define the RFC destination for this HR system in theSAP Multiresource Scheduling Customizing via HR Integration -> Specify RFC Destination of HRSystem. Distribute the resource planning structure into all involved systems to ensure that theresource planning structure ID is identical in all systems.

3.2.4 Parameters for reprocessing of integration queueIn this Customizing you can define the wait time (in seconds) and number of attempts forreprocessing of an integration queue. An example entry is shown in the figure below:

Figure 8

ExampleThe wait time is defined as 60 seconds and No. of attempts is defined as 3.In this case, the system will activate the queue after waiting for 60 seconds. If thequeue is errored again, the system will reprocess it again after 60 seconds. This willhappen only 3 times after which the system will stop processing the queueautomatically.After this, the queue must be activated manually.


October 2010 18

NoteThe parameters for reprocessing of queue is required only if you use the SAPMultiresource Scheduling function module /MRSS/SGE_QUEUE_MONITOR forqueue monitoring and automatic activation of queue.This SAP Multiresource Scheduling function module/MRSS/SGE_QUEUE_MONITOR will monitor and activate SAP MultiresourceScheduling integration only those queues that start with the name: MRSINT*

3.2.5 Automatic Activation of SAP Multiresource SchedulingIntegration Queues

To activate SAP Multiresource Scheduling integration queues automatically, follow the steps:1) Go to transaction SMQE.2) Use the button Event Registration and maintain following values:

a. Queue Name : MRSINT*b. Event Id : 5c. Function Module : /MRSS/SGE_QUEUE_MONITOR

3) Save you entries.

3.2.6 New alert for error queuesYou can configure a new alert in case of multiple back-end scenario. This alert appears if anintegration queue is not processed successfully. To add this new alert, follow the steps:

1) Add the check class: /MRSS/CL_SGE_CHECK_QUEUE_STAT in your check profile.2) Add the alert message: /MRSS/SGE – 411 in your alert profile.

3.3 Configuration of PM/CS IntegrationForward IntegrationThe following paragraphs give detailed information on configuring the PM/CS order integration inthe SAP Multiresource Scheduling Customizing. Launch transaction /MRSS/IMG and follow thepath SAP Multiresource Scheduling ERP Sources of Demand Orders

Figure 9


July 2010 19

In activity Define Order Integration from PM/CS to MRS, you can define which order type should betransferred to SAP Multiresource Scheduling. You can also define whether open orders should alsobe transferred (W. Op. Ord). Otherwise the order will not be transferred if it was not released.

Figure 10The export function defines the function module /MRSS/RSG_MAINTAIN_PM to be used for theback integration into the SAP Multiresource Scheduling order from. If you leave this field empty,there will be no transfer of data from SAP Multiresource Scheduling back into the PM/CS order.The default function module provided by SAP is /MRSS/RSG_MAINTAIN_PM.In the Define resource planning relevance for PM/CS orders activity, you can define which type ofitems from the order you want to be able to see and plan. For planning relevance, tick the Res.Plng field.

Figure 11In the Resource Planning for Production Resources and Tools activity, you can also determinewhether production resources and tools should appear on the planning board.

Figure 12The initial configuration of the PM/CS forward integration is completed. According to your definition,you can create orders in PM/CS, and they become reflected into demands in SAP MultiresourceScheduling. For more details regarding SAP Multiresource Scheduling functionalities please referto chapter 6.

3.4 Configuration of PS Integration

3.4.1 Process IntegrationIn the following paragraphs you find detailed information in order to configure the PS networkintegration in the SAP Multiresource Scheduling Customizing.Launch transaction /MRSS/IMG and follow the path SAP Multiresource Scheduling Sources ofDemand OrdersIn the Define Order Integration from PM/CS to MRS activity, you can define which network typeshould be transferred to SAP Multiresource Scheduling. You can also define whether opennetworks should also be transferred (W. Op. Ord). Otherwise the order will not be transferred if itwas not released.


October 2010 20

Figure 13The export function is not used in the PS integration, so please leave the field initial.In the Define resource planning relevance for PM/CS orders activity, you can define which type ofitems from the network you want to be able to see and plan. For planning relevance, tick the Res.Plng field.

Figure 14Now, follow the path SAP Multiresource Scheduling Sources of Demand Networks and invokeactivity Deactivate Process Variants.Here you can define process variants for the project business, on base of plant, serviceorganization, and network type. The system will determine which process variants the user canchoose in the network header (on the screen enhancement in transaction CJ20N). Moreover youcan deactivate individual process variants by an indicator.

Figure 15For more details concerning the variant meaning see the F1 documentation.In the Define resource planning relevance for networks activity, you specify the network activitiesfrom PS that can be processed with SAP Multiresource Scheduling. For SAP MultiresourceScheduling relevance, the indicator Res. Plng must be active.Additionally, you can configure the system so certain statuses need to set network header oractivity on.

Figure 16


July 2010 21

3.4.2 Field Control in Network Header and ActivityDepending on your individual project business process, you can configure the usage and visibilityof certain fields in the transaction CJ20N.Prerequisite: You have set up the SAP Multiresource Scheduling screen enhancements describedat the beginning of this chapter.The activity Define field control in relation to authorizations allows you to define field groups andspecify the authorizations that a user must have to display or edit certain field groups in networks.You can use the Define field control in relation to process progress Customizing activity to furtherrestrict the authorizations depending on the process phrase. For details see the Customizingdocumentation.

Figure 17In activity Define field control in relation to process progress you can further restrict theauthorizations defined in previous activity depending on the process progress.You specify the combinations of order type, process variant, and status at the network header oractivity level for which certain fields can be displayed only or hidden. For details see theCustomizing documentation.

Figure 18Additional remarks: The field control is based on hard-coded boundary restrictions. According tothese some fields cannot be made input fields because this would not be in line with the programlogic behind these fields. Dependent on the process variant some fields may not be input fields ormay not even be visible.

Example Within the resource planner process, the checkbox for manual

resource confirmation makes no sense and is therefore not visible.You cannot make it visible by changing the field control settings in theCustomizing.

Accept offer function: An offer can only be accepted within the contactperson process with manual resource confirmation. You cannotactivate this function for the resource planner process by means of thefield control.

If a field is defined as an input field by the field control mechanisms, depending on the businessprocess logic this doesn't necessarily mean that it will become an input field on the SAPMultiresource Scheduling screens or that its entries will be processed.The following lists contain restrictions for some fields that cannot be bypassed by the field control.SAP Multiresource Scheduling screen on network header:

All fields: If process variant is "Not planning relevant," all SAP MultiresourceScheduling fields are hidden except the process variant fields. In display mode allfields become display only independent of the field control.Process variant: Cannot be changed if not "Not planning relevant" and alreadysaved.Order probability: If "Posting" is marked, field is display only.


October 2010 22

Manual resource confirmation: Hidden if process variant does not equal"Contact person process".Planning node: In change mode, the field becomes a mandatory input fielddependent on customized user status.

SAP Multiresource Scheduling screen on network activity:All fields: If process variant is "Not planning relevant," all SAP MultiresourceScheduling fields are hidden except the process variant fields. In display mode,all fields become display only independent of the field control.Process variant: Cannot be changed if planning relevant and saved before. Canonly be changed from "not planning relevant" to the process variant defined innetwork header. Disabled if assignments are existing.Network activity number and short text: Display only fields that are hiddenwhen called form CJ20NRequirement profile field: Display only in display modeCreate and change requirement profile buttons Inactive in display modeManual resource confirmation: Hidden, if process variant does not equal"contact person process". Display only, if offer demands are existing or ifassignments are existing.Total work and single work fields: Display only fields.Order probability: Display field, if network refers to a booking.Checkbox "Start planning": Display only, if set and already savedRemaining effort pushbutton: Disabled if not contact person process or timerule exists.Remaining effort delete button: Disabled if not contact person process or timerule exists.Time rule edit button: Disabled if SAP Multiresource Scheduling demand existsand status START_PLAN is set and time rule is not already defined.Time rule delete button: Disabled, if time rule doesn't existToolbar function: Resource by qualification: Disabled if no requirement profilespecified. Disabled if not contact person process.Toolbar function: Resource by planning structure: Disabled if resourceplanner process and one demand already defined.Toolbar function: Delete entry from tree: Disabled if tree is empty.Toolbar functions: Accept/Reject open offers: Disabled if process variant doesnot equal “contact person process” or manual resource confirmation switched off.Toolbar function: Refresh qualification: Disabled if requirement profile notspecified.Toolbar function: Remove offer flag: Disabled if process variant does not equal"Contact person process".

Now, the configuration of the PS integration is complete. According to your definition, you cancreate network activities in PS and they become reflected into demands in SAP MultiresourceScheduling.

3.4.3 Demand View IntegrationAs of SP03 there is an additional SAP Multiresource Scheduling integration in PS to display the PSobjects project, WBS element, network, and activity in the demand view of SAP MultiresourceScheduling. If you want to display this PS objects in the demand view please apply the followingnote.


July 2010 23

The prerequisite is that you have already applied note 1135512. In this case the screenenhancements are not needed that are described in note 1135512.Note 1269800 - MRS 610 SP03 : Integrate Projects and WBS with MRSAfter applying the note you can set up that a specific project profile is relevant for SAPMultiresource Scheduling. For this purpose you have to specify the project profile in activity DefineResource Planning Relevance for Projects.If you set the indicator “Capacitive Planning Relevant” in the activity Define resource planningrelevance for networks, the user can edit and create demands in the demand view, and you canalso call the capacity view for them.

NoteThe indicator takes effect only if you have specified Not Relevant to Planning as theprocess variant in activity Deactivate Process Variants.

3.5 Configuration of Web-based Resource ManagementIntegration

In order to activate the integration of Web-based Resource Management additional Customizingsteps are necessary.

3.5.1 Status ConfigurationThe following implementation steps have to be performed in the same order as mentioned:

1) Creating Status Object Type:a) Go to Transaction BS12.b) Create a new Object type (e.g. ZCD RM Candidate Status Obj ) by entering

object type and object text.2) Maintaining Status Object Type in RM Customizing:

Maintain the status object type created in step (1) in the table /MRSS/C_RM_ST_OB.3) Mapping Candidate Status Profiles to Status Object Types:

a) Go to transaction BS02


October 2010 24

b) Select candidate status profile ‘RM_CAND1’

Figure 19

c) Click on Object types buttond) Select the status object type created in step (1) from the list of allowed object

types.e) Save.f) Repeat the steps (a) to (e) for the status profile RM_CAND2.

4) Maintain Status Object Type Control Parameters:

a) Open Maintenance View TBO00.b) Create a new entry with field values as follows:

Obj .type - First two characters of the status object type created in step (1)Table - /MRSS/D_PARTNERObj.no.fld - Status_obj_keyRef.struc - IonraKey fields - Objnr

c) Save.5) Maintain Number Range Interval for Status Number Range Object:

a) Go to transaction SNROb) Enter Object type as ‘/MRSS/PSTA’ and choose the Number Ranges button.c) Choose Edit Intervals button.d) Enter the data as follows and save:


July 2010 25

Figure 20

3.5.2 RM Master Data Settings Configuration (/MRSS/V_RM_MDATA)The following fields have to be maintained in Customizing for Resource Management under Masterdata settings -> Maintain settings for Resource Management (View /MRSS/V_RM_MDATA).MAX_ COUNT Maximum number of rows to be displayed in worklistsSearch_Max_Hits Maximum number of hits for search resultsEmp_profile The beginning part of the Employee Profile URLPace_field_ch On the Advanced Search selection screen , based on this Parameter, the

PACE fields are made active / InactivePerf_Ustr_Match The SAP Multiresource Scheduling Unstructured Qualification Matching is

performed based on this flagCustomer_Dummy The dummy customer to be used (incase no customer specified on Web

UI, but customer name 2 field is populated)Help_URL The target URL for the Help LinkSp_Cand_Visible This flag is used to switch on /off the candidate level Authorization checksVendor_Dummy Dummy vendor to be used (incase it is desired to add a new external

candidate, but the vendor name is not available yet).R3_SAME_LOGSYS This flag has to be set as “X”. RM Web works in a mode where the SAP

Multiresource Scheduling NW and SAP Multiresource Scheduling ERP add-ons are installed on the same system.

3.5.3 Authorization Object /MRSS/WRMTo perform any demand related operations or candidate related authorizations, users have to beassigned appropriate authorizations to this object. Demand authorizations are tied to ResourceManagement Groups and candidate authorizations are linked to Resource Groups. For moreinformation, see the authorization object documentation in the system.


October 2010 26

/MRSS/OTYP Resource Management Group or Resource Group/MRSS/OBID Object ID of the corresponding RM group or Resource Group/MRSS/ENTYVarious Entity level Authorization check and their possible valuesD Demand (used for auth checks to enable demand management functions)C Candidate (used for auth checks to enable candidate assignment handling functions)O Own Data (Resource) (enables user’s ability to refine own assignments via the My View)P Candidate Profile (for future use)

ACTVTVarious permitted activities are01 Create or generate02 Change03 Display16 Execute - Anonymous Search70 Administer

3.5.4 Maintaining Evaluation Paths for AuthorizationEvaluation path hierarchy for demand and candidate authorizations has to be maintained in theview /MRSS/V_HIER_EVA. For demand authorizations, the evaluation path has to be maintained infield ‘WEGID_DEM_AUTH’ and for candidate authorizations in field ‘WEGID_CAND_AUTH’

3.5.5 Workflow ConfigurationConfigure /MRSS/C_WF_CDPCG for RC_CM_SPN Determination1) Recipient Type RC_CM_SPNSome or all of the below recipients will receive the alert depending on the Resource ManagementGroup as configured in the table /MRSS/C_WF_CDPCG:(a) SP Name(b) Resource Contact(c) Consulting Manager(d) Candidate himself can be included.

2) Configure this table for PCG as shown below

Figure 21


July 2010 27

There are four types of AgentType: RCT (Resource Contact), CMG (Consultant Manager), SPN(SP Name), and CDT (Candidate). The “AlwaysFlag” is the indicator to send the alert to thecorresponding agent type “always”.Example:For the case of PCG 50013304 above, there are three agent types defined in the table and only forSPN the “Always Flag” is selected. This means that the workflow will “always” send an alert to theSPN. If an SPN is found, the workflow won’t send alerts to other agents. However, if the SPNcannot be determined (i.e., there is no SPN for the demand), then the workflow will examine otheragent types by the “Sequence”. In that case, once any recipient is determined by the “Sequence”,only he will get the alert. For example, if RCT (which sequence number is 1) is determined by thesystem, then the workflow won’t consider the next Sequence that is CMG in this case. If RCT doesnot exist for the candidate, then workflow will examine next the Sequence, which is CMG.Linking Custom Status Object Type to Workflow Object:Go to Transaction BSVZ and link the Custom status object type (created in status configurationabove) and the Workflow object /MRSS/CD based on the ‘status_obj_key’.

Figure 22


October 2010 28

Figure 23User parameters:/MRSS/RMS_CMV_ORGID: Default org unit to be populated in the CM View/MRSS/RMS_PRESEL_DEF: Default pre-selection criteria to use/MRSS/RMS_RMV_PLNODE: Default org unit to be populated in the RM View

3.6 Configuration of cProjects IntegrationYou have implemented the following notes for the integracion of SAP Collaboration Projects(cProjects) into the functionality of SAP Multiresource Scheduling:

SAP Note 1391965This note is required to be implemented in case of integration with cProjects 400.

SAP Note 1389664This note is required to be implemented in case of integration with cProjects 500.

SAP Note:1391065This note is required to to activate the integration of code-relevant Business Add-Ins(BAdIs) and exits for cProjects integration.

3.6.1 Cutomizing for the integration of cProjectsIn Customizing for SAP Multiresource Scheduling choose Sources of Demand CollaborationProjects MRS-Relevant Settings for Project Role Type.


July 2010 29

Figure 24

For each role type the process variant and the selection type must be defined. Only resourceplanner process is supported.

For each project role type, you specify:

A description

The process variant

Resource planner process: this means the demand is assigned directly to the resourceplanner from the organizational unit for the cProject.

Whether the resource proposals must be accepted manually, whether they are to bescheduled automatically, or whether they are to be posted automatically and firmly.


October 2010 30

In Customizing for SAP Multiresource Scheduling choose Sources of Demand CollaborationProjects Form for Communicating via E-Mail and Groupware.

You can define different forms for communication via e-mail and groupware, which can be usedwhen integrating demands from cProject roles.

Figure 25


July 2010 31

In Customizing for SAP Multiresource Scheduling choose Sources of Demand CollaborationProjects Configure Interface Elements in cProjects.

You can configure the settings for the cProject interface elements on the MRS tab page.

Figure 26

In Customizing for SAP Multiresource Scheduling choose Sources of Demand CollaborationProjects Define Rejection Reasons for Candidates.

You can define the rejection reasons that are available to the requester in the cProject, if he or sheejects a resource proposal.

Figure 27


October 2010 32

In Customizing for SAP Multiresource Scheduling choose Sources of Demand CollaborationProjects Maintain Status for cProjects.

Maintain the status related to Reason for demand creation and Additional status in assignments inthis table.

Only already defined abstract status must be used here. To do so use the field help.

Figure 28

3.6.2 Number Ranges1. Maintain number ranges using transaction SNUM.

2. Enter object /MRSS/DPRP.

Figure 29

3. Choose Create or Change.

4. Create a number range with the following values:


July 2010 33

Figure 30

3.6.3 Master Data

Define Business Partner

1. Use transaction BP.

2. Create Role General and BUP003.

3. Enter the personnel number in the Employee field.

Figure 31

Abstract Status Customizing

In the Customizing for SAP Multiresource Scheduling choose Basic Settings Assign ERPObjects Status Define Abstract Status.

Maintain the followoing abstract status:

RES_ALLCTD Resource Allocated


October 2010 34

RES_PROPSD Resource proposed

RES_REJECT Resource rejected

RES_SELECT Resource Selected

RES_RESERV Resource reserved

RES_NOTSEL Proposed Resource Not selected

RES_PROPSD Resource Proposed

RES_REJECT Resource Rejected

RES_RESERV Resource Reserved

RES_SELEC Proposed Resource Selected

RES_SELECT Resource Selected

WORK_START Work started

WORK_STOP Work finisked

Time Recording Status Mapping:

Figure 32

In the Customizing for SAP Multiresource Scheduling choose Basic Settings Assign ERPObjects Status Assign Status for Demands(ERP).

In this customizing you assign ERP statuses to the (previously defined) abstract statuses that are usedin Multi Resource Scheduling. Without this assignment, MRS and the ERP systems cannot exchangethe required information.

ERP Abstract Status:

WORK_START = A,B, D, F, H

WORK_STOP = C, E,G, I


July 2010 35

An example mapping is done in the figure below.

Figure 33

Recommendation for cProjects UI settings

If only SAP Multiresource Scheduling is used for staffing within cProjects, we recommend to hidethe staffing process tab in the cProjects Web UI as it should not be used when SAP MultiresourceScheduling staffing is active. To do so, proceed as follows:

1. Launch the cProject Application.

Choose http://<your_hostname>:<port>/sap/bc/webdynpro/ sap/cprojects

2. Open an existing cProject.

3. Choose the Resources tab.

4. Right click on the Staffing Process tab.

5. Choose User Settings.

6. Select Hide tab.

The staffing process tab will be always hidden for the logged in user.

To achieve a value set in the Status field of the MRS tab, the following Customizing is required:

Maintain an abstract status in Customizing for SAP Multiresource Scheduling under Basic Setting Assign ERP Objects Status Define Abstract Status.

For example you can maintain the following values:

Category: DEM_CREATE

Description: Demand newly created

Assign the abstract status in Customizing for SAP Multiresource Scheduling under Basic Settin Assign ERP Objects Status Assign Status.

For example you can maintain the following values:

Category: DEM_CREATE

Plnt:

Sorg:

Type:

Origin: Demand Item (user status)

Stat: DADD

Language: EN

Maintain the abstract status created above for cProjects in Customizing for SAP MultiresourceScheduling under Sources of Demand Collaboration Project Maintain Status for cProjects.

Proceed as follows:


October 2010 36

1. Choose New Entries.

2. Place your cursor in the Category field and choose field help.

3. Choose the abstract status created above.

4. Choose Origin as Demand Item (user status)

5. Choose Save.

With these Customizing activities, drop down values will appear for the Status field in the cPro UI(MRS tab page).

3.7 Configuration of CRM IntegrationIn order to integrate demands from CRM service orders, the CRM BADI: CRM_SRV_SDL must beimplemented. The details of CRM integration is given in the note: 1380854After the BADI implementation, following customizing settings should be maintained.

3.7.1 Define Order Relevance for Resource PlanningYou can define the resource planning relevance of CRM service orders in SAP MultiresourceScheduling IMG. This Customizing is defined in following location:Sources of Demand CRM Service Orders Determine CRM Service Orders for ResourcePlanningAn example entry is shown in the below screen shot.

Figure 34

3.7.2 Define date types for demand integrationYou can define the date types for demand integration. This is defined in following location:Sources of Demand CRM Service Orders Define Date Types for DemandAn example entry is shown in the below screen shot.

Figure 35


July 2010 37

Figure 36

3.7.3 Define location of service for demandYou can define the location of service for demand integration. This is defined in following location:Sources of Demand CRM Service Orders Determine Usage Site of Service OrderAn example entry is shown in the below screen shot.

Figure 37

3.7.4 Activate resource planning in CRM service order itemsThe items in service order must be customized for resource planning relevance. This is to be donein CRM customizing. The customizing is defined in transaction SPRO in following locations:


October 2010 38

Figure 38

Figure 39


July 2010 39

Figure 40

3.8 Configuration of Persistence LayerSAP Multiresource Schedulinghas a persistence layer called SAP Multiresource Scheduling Basis.That means the WFM Core is replaced by the SAP Multiresource Scheduling Basis.

Advantages of SAP Multiresource Scheduling Basis:

Performance

Low effort in Customizing

Optimized solution for SAP Multiresource Scheduling

In order to configure the SAP Multiresource Scheduling Basis you have to do the followingCustomizing:

Time Allocation Types have to be customized via Customizing activity Define Time AllocationTypes.

Time allocation types describe the different time types you want to distinguish in the planningboard. For example, you might want to define a type for working time and a type for overtime work.A good starting point should be the list shown below.

With the switch button availability, you can define whether this type is valid for presence of theresource or not. Also, you can define a priority for the type. The range reaches from -128 (lowest)to 128 (highest). Use this to define how ‘hard’ this type is. For example, the type HOL for holidaysis defined with priority 128 as the resource is definitely not available. Thus, time allocations withhigher priority overrule those with lower priority. That is useful when you use semi-automated orfully automated scheduling. Thus, the scheduling system knows which times cannot be moved andwhich can.


October 2010 40

Figure 41

NoteIf the EI checkbox is selected, the time allocation appears as a bar in the planningboard. These time allocations can be changed directly in the planning board. If theEI flag is not set, the time allocation appears only in the background as havingavailability or having no availability.Exceptional Time Allocations can only be created in the Planning board and relatedfunctions. Basic Time Allocations (no EI- Flag) can only be created if basisavailability gets transferred e.g. via the HCM SAP Multiresource Scheduling transferreport /MRSS/HCM_RPTWFMIF or the BP Maintenance Report/MRSS/WFM_MASTERDATA_ADMIN.

The next step is assigning the defined time allocation types to the resource types. This can be donevia Customizing activity Assign Time Allocation Categories to Resource Categories. The differentresource types should already be in place by the installation as follows:

Figure 42

You need to assign the defined types to the different resource types. For example, the definedtimes for personnel resources could resemble the following:


July 2010 41

Figure 43

If you create time allocations for resources in SAP Multiresource Scheduling, you can only assignthose time allocation types that are assigned to the corresponding resource type.

3.9 Netweaver Demand SettingsIn this chapter you can configure the additional settings for generic demands. This customizing isrelevant only for netweaver demands (demands that do not originate from SAP ERP). Examples ofnetweaver demands are: CRM Demands, cPRo Demands. Example of R3 Demands are : PM/CS,PS, etc.

3.9.1 Control assignment processingIn this customizing you can define the settings to control assignment processing. In this IMGactivity, you specify the user and system status of the order operation for which creating, editing, ordeleting the associated assignments should no longer be possible. You can define this dependingon demand header type and demand item type.

3.9.2 Allow Stretched assignmentsIn this IMG activity, you define the demand header type and demand item type for which thesystem can create stretched assignments

3.9.3 Allow capacity PlanningIn this customizing, you can define the demans for which system allows capacitive planning.

3.9.4 Allow abstract assignmentsIn this customizing, you can define the demand header type and item type for which the systemallows abstract assignments.


October 2010 42

3.9.5 Partial concretization of stretched assignmentsIn this IMG activity, you define when the system can concretize a stretched assignment as a wholeor in part when it falls within a time of non-availability. You can specify this for combinations of thefollowing data: Demand header type and demand item type.

3.9.6 Site supervisorIn this IMG activity, you can specify that a site supervisor must be assigned for specific demandheader types. This means that for demands of these types, you have to create an assignment forone of the operations, and the site supervisor indicator must be set in this assignment.

Configuration and Customizing: Specific Configuration

July 2010 43

4 Configuration and Customizing:Specific Configuration

This chapter is optional and intended for the initial configuration of some specific SAPMultiresource Scheduling functionalities.

4.1 Backward IntegrationIn this chapter you can configure the backward integration that is responsible for the reflection ofdata from SAP Multiresource Scheduling to the PM/CS order.

Prerequisite: You have set up the export function (function module /MRSS/RSG_MAINTAIN_PM)in Define Order Integration from PM/CS to MRS.

In the Control Integration Between MRS and PM/CS activity, you can activate the backwardintegration for the “C: R/3 PM/CS order” demand type. Note that there is no back integration optionfor other demand types in SAP Multiresource Scheduling.

Figure 44

During the scheduling, demands are assigned to resources. In the Activate 1:1 Relationship ofAssignments and Demands for Demand Categories activity, you can configure the associationbetween demands and assignments.

Figure 45

For each order type, you can activate the 1:1 relationship separately. Therefore follow the pathSAP Multiresource Scheduling Sources of Demand Orders and invoke the Activate 1:1Relationship of Assignments and Demands for Order Types activity.

Figure 46

If you want this for each assignment for which there is a corresponding demand, then activate the1:1 relationship. In particular during the backward integration, the system will create an operation inthe PM/CS order for each new demand.

Since both the forward and backward integration are active now, you can continue with activityControl Integration between MRS und PM/CS. Here you can determine which data should betransferred at all.


October 2010 44

NoteIf you are upgrading from MRS 610 to SAP Multiresource Scheduling 700, then thisCustomizing must be maintained again in transaction: /MRSS/IMG_R3.

Prerequisites: You have configured the work center mapping in chapter 3.1.1.

If you have activated the 1:1 relationship, every technician must be assigned to a separatetechnician work center.

Figure 47

The Customizing activity is separated into three sections, forward integration, backward integrationand general settings.

4.1.1 Forward Integration from PM/CS to SAP MultiresourceScheduling

Splits

With check box Splits you can define that the system should update assignments in SAPMultiresource Scheduling, if the operation splits have been changed in the PM/CS order.

Prerequisite: The 1:1 relationship must be inactive. Only then assignments are reflected into splits(or requirement assignments in the order operation) and vice versa.

If the 1:1 relationship is active, then each assignment will be reflected into an own order operation.In this case the check box Splits must be deactivated.

Travel Times

With the Travel Times check box, you can define that the system should update travel times in SAPMultiresource Scheduling, if travel times are maintained on operation level.

Prerequisite: The 1:1 relationship must be active.


July 2010 45

Hint: Since travel times are not covered by PM/CS, the data base table AFVU was enhanced by acustomer include in order to store travel time information. If you want to use travel time informationon the order operation, you can implement the operation enhancement screen.

Field change Alerts

With check box Fld Chg Alert you can define that the system should update alert messages in theSAP Multiresource Scheduling alert monitor. For example, if the operation start or end datechanges, the system will create corresponding alert messages. For more details please refer to theCustomizing documentation.

4.1.2 Backward Integration from SAP Multiresource Scheduling toPM/CS

Splits

With the Splits check box you can define that the system should create or update operation splits inPM/CS, if assignments have been created or changed in SAP Multiresource Scheduling.

Prerequisite: The 1:1 relationship must be inactive. Only then are assignments reflected into splits(or requirement assignments in the order operation) and vice versa.

If the 1:1 relationship is active, then each assignment will be reflected into a separate orderoperation. In this case the Splits check box must be deactivated.

Work Center

The creation of an assignment in SAP Multiresource Scheduling leads to a transfer of thetechnician work center (assigned to the resource) to the order operation. With the Work Centerdrop down list, you can control the back integration of the technician work center.

Prerequisites: Technician work centers are assigned to resources via evaluation path Customizing.You must ensure that each technician is associated with a separate technician work center. If thisis not the case, the planning will not be allowed. Please refer to chapter 3.1 for more details.

Another prerequisite is that the 1:1 relationship between demand and assignment must be active.

Dates

With check box Dates you can define that the system allows users to change the demand in SAPMultiresource Scheduling planning board. That means the user can change the begin date and enddate of a demand.


Hint: The system will transfer the demand changes into the order operation and will createconstraints on the operation level in Dates tab. Also the system will trigger the PM/CS scheduling.

Demand Follows Assignment

With the Demand Follows Asgmt check box, you can define that assignments dates in SAPMultiresource Scheduling should update the SAP Multiresource Scheduling demand.

Prerequisites: The 1:1 relationship must be active and check box Dates must be active, too.

Travel Times

With check box Travel Times you can define that the system should update travel times in PM/CS,if travel times are maintained for an assignment in SAP Multiresource Scheduling.


Hint: If you want to use travel times, you have to work through Customizing part Optimizer andTravel times Travel times. After configuration, travel times will be displayed in the assignmentdetails screen and represented by bars on the SAP Multiresource Scheduling planning board.


October 2010 46

4.1.3 General SettingsDate Logic

The Date Logic drop-down list controls the determination of demands dates. With the optionPrecise Date Transfer the operation fields “earliest start” and “latest end” will be transferred to thedemand start and end.

If the operation “earliest start” is later than the “latest end,” the system will reverse these values, ifthe option “Automatic Start Adjustment” is set.

Duration Logic

With the Duration Logic drop-down list you can define whether the system should transfer theoperation duration or the operation work to the demand duration.

Now, the configuration of the backward integration for the PM/CS scenario is completed.

4.2 Technical Settings for Resource SelectionIn the Technical Settings for Resource Selection activity, you can adjust the resource buffer of theplanning board resource list. The system buffers resources in the working memory in order toimprove the resource list update.

In the default configuration, the Maximum Number of Resources and Minimum Number ofResources fields are initial and the resource buffer will not become refreshed with each SAPMultiresource Scheduling planning board refresh.

Figure 48

Since the system should not allocate too much working memory, you can enter the maximumnumber of resources that the system may build up. If the maximum number is exceeded, thesystem will try to remove resources from the buffer that are not necessarily needed, based of thelength of time they were not used.

As long as the number of resources is less as the minimum number, the system does not removeany resources from the buffer.

As a result, the system makes sure that the number of buffered resources is between a minimumand a maximum.

If you set the Refresh Buffer check box, the system will delete the resource buffer with each SAPMultiresource Scheduling planning board refresh. The recommandation is not to refresh theresource buffer, since the system then does not need to read existing resources from the databaseagain.

4.3 Manager Planning BoardYou can launch the manager's planning board with transaction /MRSS/PLBOMGR. You can usethis planning board to display the current scheduling situation for the resources of an organizationalunit. However, you cannot change any of the data.

In theDefine Settings for Manager Planning Board activity, you can specify the object type (forexample, organizational unit) for which you can start the manager's planning board.


July 2010 47

When the manager invokes the Manager Planning Board with a certain organizational unit, theevaluation path is used to determine the related personnel resources. The profile is used to specifythe planning board profile, which controls the behavior of the planning board.

Figure 49

4.4 SAP Multiresource Scheduling QualificationsAfter activation of the SAP Multiresource Scheduling qualifications in the basic settings, anenhanced qualification management can be used.

NoteYou can use the enhanced Qualification Management only for resources that arerepresented as HR persons.

In the beginning, the number ranges for all relevant SAP Multiresource Scheduling qualificationobjects have to be defined:

The relevant objects with Customizing activities are:

Qualifications via Customizing activity: Define number ranges for qualifications.

Qualification Catalogs via Customizing activity: Define number ranges forqualification catalogs.

Qualification Matrixes via Customizing activity: Define number ranges forqualification matrixes.

Requirement Profiles: Define Number Ranges for Requirements Profiles

If you create a corresponding object, the object numbers are taken from the corresponding numberrange. The Objects are created via separate Master Data Transactions. For more details pleaserefer to chapter 5.1.1.

If you create Qualification Catalogs, you have to assign a ‘maintenance group’. The MaintenanceGroup is used to group the Qualification Catalogs. Furthermore Authorization is steered via the‘Miantenance Group’. The ‘Maintenance Group’ can be customized via Customizing activity: DefineMaintenance Groups for Qualification Catalogs.


October 2010 48

Figure 50

Via the Define system parameters for qualification catalogs Customizing activity, you define defaultparameters for the creation of qualification catalogs.

The Maximum Number of Hierarchies defines the maximum number of hierarchies. You can lowerthis value in the master data transactions but not raise it.

The other values steer the extended employee and demand search.

Figure 51

Qualifications can be grouped in profiles. There are two kinds of profiles, the requirement profileand the resource profile. The requirement profile is part of the demand; the Resource profile can beassigned to resources.

Via the Define profile settings Customizing activity, you can define the settings for the profiles.


July 2010 49

Figure 52

You define the types of unstructured qualifications.

This is only needed if you want to use unstructured qualifications.

You assign a subtype for HR infotype 0105, in which the users for the portal isdefined.

You specify the URL components for the user interface of the portal. For furtherinformation please refer to chapter 4.5 “Supplement Concerning the Static URL toAccess Employee Profiles on Enterprise Portal”.

You assign Smart Forms to the profile types (resource and requirements profile),which specify how the forms are output for the profile types. For furtherinformation please refer to chapter 4.6 ”Smart Forms for Employee andRequirements Profiles”.

For each plant, you can specify the objects for which the system is to execute thewhere-used list for requirements profiles.

If Resource Profiles are created approval Workflows are triggered. For this purpose the followingCustomizing activities are relevant:

Set up approval workflow (Workflow)

Approval Workflow: Define Infotypes and Fields (Steering of the Worklow)

In principle who has to approve Resource Profile changes can be controlled. The Manager is foundvia the Customizing activity Define resource planning nodes and evaluation paths -> ApprovalWorkflow.

For further details see chapter Workflow Customizing.

Furthermore you have several possibilities to control the Qualification matching.

First you should set up the basic setting in Define basic settings for qualification matchingCustomizing activity. Here you control how the matching is performed.


October 2010 50

Figure 53

To get an overall Matching result, you can define how the matching criteria are weighted againsteach other. This is done in the Define weighting factors for matching criteria Customizing activity.

Figure 54

The Handling of so called ‘On Call Types’ can be defined in the Customizing activity Definefulfillment values for matching on-call types.


July 2010 51

Figure 55

If you want to use unstructured Qualifications, you have to use a TREX. For this purpose you haveto set up an RFC Connection to the TREX. This can be selected via Customizing Activity EnterRFC destination of TREX interface.

You can find further information in the chapter TREX Configuration.

It is possible to optimize performance during the unstructured qualification search. For this purposeyou can define with which language the request is performed via Customizing activity Definelanguage for matching unstructured qualifications.

Figure 56

Via the Define Preselection Modes for Free Employee Search Customizing activity, you can definehow resources are preselected in the free employee search.

The Preselection IDs customized here can be selected in the free employee search. Thepreselection itself is done via an ABAP class.


October 2010 52

Figure 57

How to set up the Web UI where a User can maintain his qualifications is described in chapterSetting up the Employee Profile Web UI.

An ABAP Web Dynpro based Web UI is available via the following URL:

http://<server>:<port>/sap/bc/webdynpro/mrss/dpr_empprf

4.5 Supplement Concerning the Static URL to Access EmployeeProfiles on Enterprise Portal

The portal settings for the Web UI are defined in the SAP Multiresource Scheduling ->Qualifications -> Profiles -> Define profile settings Customizing activity. In this Customizing activityyou enter the Static URL that is part of the complete URL to call an employee profile in theEnterprise Portal. The static URL is a constant value based on portal configuration.

Note the following when you enter the Static URL:

If you use Enterprise Portal 6.0 you have to append the text “DynamicParameter=” tothe end of the static URLExample: “/irj/portal/profile?DynamicParameter=”

If you use Enterprise Portal 7.0 you don’t have to add the text “DynamicParameter=”Example: “irj/portal/profile?”

4.6 Smart Forms for Employee and Requirements ProfilesYou can define smart forms for the print layout of employee profiles and requirements profiles inthe SAP Multiresource Scheduling -> Qualifications -> Profiles -> Define profile settingsCustomizing activity. The following smart forms are delivered:

Smart form for employee profiles:

/MRSS/EMPLOYEE_PROFILE_FORM2

Smart form for requirements profiles:

/MRSS/REQUIREMENT_PROFILE_FM3

4.7 Standard Bar Chart CustomizingIn the Customizing for SAP Multiresource Scheduling under Basic Settings -> Bar chart you will findsome Customizing activities from the SAP Reference IMG (to be found there under SAP


July 2010 53

Customizing Implementation Guide -> SAP NetWeaver -> Application Server -> Frontend Services-> Bar chart).

You can use the following Customizing activities for SAP Multiresource Scheduling as described inthe documentation of the SAP Reference IMG documentation:

Define graphic profiles

Assign colors

Assign shapes

Define colors

Define shapes

Call Example Graphic

For the remaining Customizing activities note the following hints so that you can use the functionsof SAP Multiresource Scheduling as intended:

Define subscreens: To achieve the desired functionality we recommend not changing the entries.Color settings are overridden by the SAP Multiresource Scheduling application.Define graphic elements: Make sure that option R (Rectangle) is always chosen in the fieldElement type. Leave the entries in the fields Index date 1 and index date 2 unchanged.When you create new graphic elements, proceed as described under “Define fields/Text index“.The entry for the drawing level is overridden by the SAP Multiresource Scheduling application soyou do not need to maintain it.The indicator Fix must not be set, because otherwise the functions in the planning board do notwork as desired. The fields under Representation of breaks are not relevant as the break logic ofthe control for the internal calendar is not used.Define option profiles: To achieve the desired functionality, we recommend that you not changethe entries. Some of the entries are overwritten by the SAP Multiresource Scheduling application.Define fields: Leave the entries in the field Text index unchanged, because changes can result ina deficient graphical display. This field is used for the internal communication between the SAPMultiresource Scheduling application and the planning board control. The text index is different forevery used object (for example, for assignments and time allocations). Therefore, if you create ashape definition, use the entry for a similar object (for example assignment or time allocation) fromthe standard as a sample.

The following table shows the values to use if you define new graphic elements for assignments,time allocations, travel times, and concretizations:

ObjectTextindex-Field Value

Assignment Start 1

Assignment End 2

Assignment Text 3

Time Allocation Start 1

Time Allocation End 2

Time Allocation Text 3

Travel to Start 4

Travel to End 5

Travel to Text 6

Travel from Start 7


October 2010 54

Travel from End 8

Travel from Text 9

Concretization Begin Start 10

Concretization Begin End 11

Concretization Begin Text 12

Concretization End Start 13

Concretization End End 14

Concretization End Text 15

4.8 Capacity ViewThere is a capacity view available that can be used to display the current capacity of a work center.

During the work center definition the capacity information must be set up.

Figure 58

In order to use a specific work center in SAP Multiresource Scheduling you have to transfer thework center capacity to SAP Multiresource Scheduling with the report /MRSS/SGE_PN_MNT.


July 2010 55

Figure 59

After that you can create PM/CS orders and PS networks with this work center. The work centercapacity can be displayed in the capacity view.

In order to see the capacity view, you have to change the UI profile. Proceed as follows:

1. In the Customizing for SAP Multiresource Scheduling choose Set Up SchedulerWorkplace Workplace Profiles Define User Interface Profile Container layout name

Screen content items.

2. Select an UI profile, for example STANDARD.

3. Double click on Screen content items.

4. In the popup window select a screen element and a content on screen.

5. Choose Continue.

6. Select the Display checkbox.

Now, you can enter transaction /MRSS/PLBOSRV with the demand and will be able to see thedemand and the capacity view.

4.9 Travel TimesThis chapter describes the initial configuration of the SAP Multiresource Scheduling Travel Timefeature and is intended to give you an overview of the required configuration steps.

The following subchapters will describe the Travel Time configuration that will be done in the SAPMultiresource Scheduling IMG node Optimizer and Travel Times.


October 2010 56

Figure 60

4.9.1 ProfilesThe Travel Time function works based on geographical information that can either come from ageographical information system (GIS), from a postal code table or by using the BAdI/MRSS/OPT_GEOCODE_TRAVEL_TIME. This BAdI can be used for customer-definedimplementations of travel distance, travel time determination and mapping of an address to ageographical position.

For more details see transaction SE18.

Profile for Geocoding

First you have to specify a geocoding profile in the Customizing activity Define Profile forGeocoding of Addresses.

Figure 61

If a GIS is present in your system landscape, you can select the geocoding option GIS and specifythe source ID. The source ID should be assigned to the RFC destination of the GIS service in thestandard Customizing table GEOCD2CLS. This table can be customized in SAP CustomizingImplementation Guide (transaction SPRO) under: SAP Netweaver > General Settings > SetGeocoding > Register Geocoding Program in the System. The GIS System has to support the SAPIGS (Internet Graphics Service) Interface.

You can check if your IGS System works properly with the Test Report GEOCODING_FIRST (tocheck geocoding) and GRAPHICS_GIS_VIEW_DEMO (to check Map Display).


July 2010 57

Technical Info: In case the IGS returns with errors, debugging the Report GEOCODING_FIRST is afast way to find the reason. Within this report you can also view the XML Files which are sent to theGIS-System and returned from them.

Otherwise if a GIS does not exist in your system landscape, you can select the option Postal Code-Based and initialize the field Source. In this case you have to set up the geographical information inthe postal code table /MRSS/D_GEO_ZIP.

As last option BAdI /MRSS/OPT_GEOCODE_TRAVEL_TIME can be used alternatively todetermine these geo coordinates.

Profile for Distance Calculation

In the next step you have to specify a profile for the distance calculation in activity Specify Profilefor Distance Calculation Type.

If you have selected the geocoding option GIS, the SAP Multiresource Scheduling will use thedistance and duration information that is returned by the GIS. For this purpose you have to specifythe determination type GIS in the profile for distance calculation.

Figure 62

Otherwise if a GIS does not exist in your system landscape, you can choose the option Straight-Line Calculation. For this calculation type, the geocodes for the resources and for the demandshave to be available within MRS. This can be done by the different methods described above in theGeocoding Profile (e.g. via a BAdI or via a Postcode Table). If you use the straight-line calculation,you have to select a formula to calculate the distance. The “ARCCOS” formula should be used forthe calculation of short distances only. If location distances are greater than 20 km, you shouldprefer “Haversine”, since the results are more precise.

Figure 63

Also here, the BAdI /MRSS/OPT_GEOCODE_TRAVEL_TIME can be used alternatively todetermine the travel distance.

Profile for Map display in planning board (optional)

As an optional setting, you can define the display of the map in the planning board using IMGactivity Define map profile.

Figure 64


October 2010 58

This step is optional as this is not a prerequisite to run the optimizer or to use travel times. With thisoption set, you can only visualize the resulting tour on the map.

Simply enter a profile name and a short description along with the RFC connection to reach themap server. Afterwards, activate the Map Feature in the MRS Planning Board Profile.

You can check if your IGS System works properly with the Test Report GEOCODING_FIRST (tocheck geocoding) and GRAPHICS_GIS_VIEW_DEMO (to check Map Display)

Travel Profile

In case of straight-line calculation, you have to specify a travel profile. With the travel profile thesystem performs the travel duration calculation based on the determined distance.

Figure 65

In the activity Define Travel Profiles you have to enter a profile key, a description and the traveltype. The travel types Car, Train, Plane and Ship are available in the dropdown box. The traveltype will be displayed on the assignment details screen of the SAP Multiresource Schedulingplanning board in order to represent the means of transport.

The travel duration is calculated based on the travel type. For this purpose, you have to specify theaverage speed that can be attained with the travel type.

Additionally, you can enter a fix duration that should be added to the travel duration. This allowsyou to include check-in times for flights, for example.

Since in most cases the travel route does not match the straight-line distance, you can adapt thestraight-line calculation by the variance factor.

NoteThe field for the fixed costs is not considered by the optimization function in thecurrent release.

Assigning Travel Profiles to Resource Planning Nodes

In the activity Assign Travel Profiles to Resource Planning Nodes you have to define the relevanceof a travel profile for a resource planning node. Afterwards, the travel profile will be valid for allresources that belong to the resource planning node and will define the maximum distance that anemployee is able to travel a day

The optimization function considers the maximum distance of a resource during travel routedetermination. If the maximum duration becomes exceeded for a particular travel route, theOptimizer will reject the travel route and try to find another solution. For more information about theOptimizer, refer to the Optimizer chapter in this Configuration Guide.

Figure 66

ExampleThe assignments A and B are both located 75 km from the home location ofresource R1, but in opposite directions. Resource R2 lives next to resource R1.


July 2010 59

According to the configuration, the maximum distance for both resources is 200 kmper day. In this example, the travel route for resource R1 would be 300 km in total.Therefore the optimization function will try to include resource R2 to the planningsituation in order find two travel routes of less than 200 km travel distance.

4.9.2 Travel Time Calculation and DistributionAfter you have defined the previously described profiles, you have to specify a geo profile in activityDefine Travel Time Calculation and Distribution. You have to assign the geocoding profile and thetravel profile to the geo profile.

You can also enter distribution factors to define how the travel time should be distributed betweentwo assignments.

Figure 67

ExampleIf you enter 0.5 as factor for the departure time of an assignment and 0.5 for thearrival time of the next assignment, the system will divide the travel time betweenthe first and the second assignment by 50%. If you enter 0 and 1, the system willassign the travel time to the next assignment as arrival time entirely.

NoteWith the distribution factors you can also control how the fix duration (specified inthe travel profile) should be added to the arrival and departure time.

Assign Travel Time Mode

In the activity Assign Travel Time Mode you can define the travel time mode that should be valid fora particular assignment. For this purpose you have to specify a combination of assignment type,plant, order type etc. and select a travel time mode. The travel time mode determines whether thetravel time is active and whether a gap between travel time and assignment is allowed. With thecheckboxes Arrival and Departure you can specify that the system should display or hide the arrivaland departure bars in the SAP Multiresource Scheduling planning board.

Figure 68

NoteFor optimization you have to use the mode Travel Times without Gaps.

4.9.3 Activating Travel Time in the Planning Board ProfileIn the last step you have to set the geo profile in your planning board profile. Select the checkboxTravel Times Active and specify the geo profile you have customized in the previous steps. If youwant to use the map display, select this checkbox and specify the map profile.


October 2010 60

Figure 69

4.10 OptimizationThis chapter describes the initial configuration of the SAP Multiresource Scheduling optimizationfunction and is intended to give you an overview of the required configuration steps.

4.10.1 IntroductionThere are three possible application use cases for the SAP Multiresource Scheduling Optimizer:

Initial planning of daily schedule

The resource planner creates an optimized daily schedule at beginning of workday or previous day. All orders will be considered and will be planned by the SAPMultiresource Scheduling Optimizer. The result is an optimized schedule.

Planning of emergency orders

In case an emergency order needs to be scheduled urgently, the Optimizerassigns this order to the technician so that the total “cost” is minimized. Duringthe optimization a new daily schedule will be created, potentially also withinfluence on other technicians.

Optimization of existing schedules

In case there are already daily schedules (e.g. manually created), the SAPMultiresource Scheduling Optimizer will create new schedules. Afterwards, thetotal “cost” will become reduced.

For the installation of the SAP Multiresource Scheduling Optimizer, refer to the installation note1138787.

The SAP Multiresource Scheduling Optimizer works as a cost-based optimizer. This means that theoptimizer will take all parameters, conditions and restrictions into account to find the best solution.

The Optimizer has to consider:

Locations of resources and demands

Travel between locations (speed and distance)

Conditions (SLA-Dates, resource availability)

Costs (non-fulfillment costs, resource costs, etc.)

One important parameter is the travel time for a resource to travel from one location to another.Therefore it is recommended to customize the travel time together with the Optimizer Customizing.However, it is also possible to use the Optimizer without travel times. In this case deactivate thetravel times in the planning board profile. For more information on how to customize the rravel rime,please refer to the previous chapter in this Configuration Guide.


July 2010 61

The following subchapters will describe the Optimizer configuration that will be done in theCustomizing for SAP Multiresource Scheduling under Optimizer and Travel Times.

Figure 70

Basic Setting in RCCF

In activity Define External Engines in RCCF, you have to enter the external engine for the SAPMultiresource Scheduling Optimizer. The Remote Control and Communication Framework (RCCF)supports the call as well as the control and logging of engines in external destinations. You have tospecify an application ID, a description and, in the remaining fields, the log, input and outfilenames.

Figure 71

In activity Process Destinations of RCCF Engines, you have to enter the destination of the externalengine in the RCCF. In case of communication method RFC, the RFC destination of the Optimizermust be set up in transaction SM59. You can test the connection directly within this customizingview.

Figure 72

You will find more details related to this activity in the IMG documentation.


October 2010 62

You can skip the activity Configure Advanced Settings, since there are no mandatory settingsneeded in the initial configuration of the optimization function. If you need more details related tothis activity, please consult the IMG documentation.

4.10.2 Optimization ProfileAfter the configuration of the basic settings, you must define an optimization profile in the activityDefine Optimization Profile. Here you have to enter the application ID that you have specified in theprevious step.

In the Runtime field you have to specify the maximum runtime of the Optimizer in seconds, whenthe user invokes the optimization function in the SAP Multiresource Scheduling planning board or ifthe optimizer is triggeed from a batch job (e.g. from /MRSS/OPTIMIZE).

In the field Cancel after you can enter the runtime in seconds to terminate the optimization, whenno improvement has been found by the Optimizer.

The field Lead time specifies a time range in hours that should not be considered in an optimizationrun. By this, you can specify a buffer based on the actual time in which no more optimization ispossible.

The next two fields Maximum Travel and Assignment Break can be used to define the amount ofallowed time in minutes the optimizer can break the corresponding activities.

If you want to log the input data and output data of the Optimizer processing for analysis, you haveto select the checkbox Data Dump. For the input and output parameters the system will createseparate files. The Optimizer processing will be logged in a logging file independently of thecheckbox. You can display and download the files with transaction /MRSS/MRS_LOG.

With the Aut.ResCr checkbox, you can specify that the system should use the Optimizer, if theuser performs the automatic assignment creation functions in the SAP Multiresource Schedulingplanning board. If you select the checkbox, the Optimizer will be responsible for the assignmentdetermination.

During the automatic assignment creation, the optimization function considers additionalparameters (e.g. travel routes) than the original automatic scheduling. The optimization parameterswill be defined in the IMG activities under the node Optimizer.

Figure 73

The other settings are not necessary to get the optimizer working. Check the IMG documentationand field help for more information about how to use these settings.

Optimization Parameters for Resources

In activity Define RP-Node-Based Optimization Parameters for Resources, you can specify foreach resource planning node certain parameters that are relevant for the Optimizer. Theparameters will be outlined in the following paragraphs.

The optimization function tries to find a solution for the planning situation with the shortest travelroute and the minimal costs. Costs incur for example if the Optimizer assigns a demand to aresource, if the assignment starts later than the demand was planned or if a demand cannot bescheduled in the specified planning period at all.

Figure 74


July 2010 63

The parameter Fix costs per day describes, how much a resource costs per day, if the Optimizerassigns a demand to the resource.

ExampleIf you want the optimization to take only one resource into account to execute threeshort assignments, you can configure a high value for the parameter Fix costs perday. Note that the demand start/end dates and the travel routes are crucial for anoptimized planning situation.

The parameter Fixed costs per assignment describes, how much a resource costs per each singleassignment.

Variable costs per hour can be used to specify the costs based on time dimension.

By using the Variable costs for each distance unit parameter, you can model the costs that wouldapply per each distance unit, e.g. kilometer. Note that you need to fill also the corresponding fieldholding the unit to ensure proper results.

With the parameter Factor to increase duration/Extension factor you can specify how theoptimization modifies the assignment duration in case the resource qualification does not match therequired qualification. In fact, you can modify the time scale of an assignment with this parameter.

ExampleThe demand “Check Network Module” is planned with 30 minutes duration andrequires advanced experience in setting up network modules. The optimizationparameter Factor to increase duration is 2. The Optimizer tries to assign thedemand to a resource with basic experience in setting up network modules. Sincethe resource experience does not meet the required qualification, the assignmentwill be scheduled with 60 minutes duration by the Optimizer.

If you apply a Cost profile you can specify how the optimization modifies the assignment costs incase the resource qualification does not match the required qualification. See also next chapter.

ExampleBy using this parameter (or profile) you can define that resources without a perfectqualification for a job will be cheaper to do the job and thus get some training on thejob.

If you select the Travel time checkbox, the travel time for a resource to reach the demand locationmay fall into non-availability. With the parameter Maximum travel time in non-availability you canspecify how many minutes of travel time are allowed in non-availability. Here the travel time in themorning and in the evening are considered separately by the optimization.

ExampleThe configuration allows 120 minutes travel time in non-availability. Since theresource availability begins at 8:00, the optimization tries to create assignments at8:00 and can include up to 2 hours arrival time before the assignment. If the arrivaltime is more than 2 hours the assignment must start after 8:00.

Suitability dependent change to cost rate

With this profile it is possible to increase the assignment costs based on the qualifications of aresource by a given amount.


October 2010 64

Figure 75

ExampleAssuming we would have a resource which has a ranking of 75% based on thequalification matching and the fix costs for this assignment is 1.000. So based onthe above shown customizing settings, the resulting costs for this resource and thissingle assignment would be 2.100.In the above shown table the entry for qualification 73 would be taken as theresource has a matching of 75%. So the logic for this is, take the entry which hitsperfect or ly in the the range between the this an the next one (so the entry 73would be valid for matching results from 73,00% to 79,99%). As the base costs are1.000 for this assignment, the customized 1.100 would be added.

Factors for Demand Priority

The priority factor influences the non-fulfillment costs for the demand depending on the demandpriority. You can specify the priority factor in activity Define Factors for Demand Priority.

Figure 76


July 2010 65

ExampleIn the configuration, the demand priority is specified according to the figure above.In case of an availability bottleneck in the planning period, the Optimizer prefersdemands with higher priority in the solution. This does not mean that the demandsare scheduled first in timeline, since this is influenced by other criteria like thedemand date period or the travel route.

Optimization Parameters for Demands

In activity Define RP-Node-Based Optimization Parameters for Demands, you can set up demandspecific cost factors.

Figure 77

The cost factors can be set up separately for different order types. Only the demand item category“SERV” is considered in the current release.

In the Non-fulfillment costs field you can enter the non-fulfillment costs that arise, if no assignmentscan be planned for a demand. As a rule, the higher the non-fulfillment costs for each demand, themore definitely the demand is planned to reduce the costs for a solution or keep them as low aspossible.

The Function checkbox controls how the non-fulfillment costs are calculated for a specific demand.There are two calculation formulas available. If the Function checkbox is not active, the costs areaccepted linearly:

If the Function checkbox is active, the costs are calculated non-linearly:

The parameters Counter and Number of remaining days to fulfill demand (Customizing field Period)are used in the nonlinear calculation and are aimed to adapt the non-fulfillment costs of a solution.

If a demand is to be fulfilled by a certain date (must end on a certain date), but it has not beenpossible to plan it previously, the Optimizer attempts to plan the demand for a further number ofdays. However, higher non-fulfillment costs are incurred in this period to further increase theplanning probability.

Example

Demand validity 10.01.2008 to 20.01.2008

Date Days Left CalculatedCosts

Customizing settings

10.01.2008 10 150.000 Counter 5

11.01.2008 9 166.667 Priority Factor 10

12.01.2008 8 187.500 Non-fulfillment costs 30.000

13.01.2008 7 214.286 Normal Non-fulfillment costs 300.000


October 2010 66

14.01.2008 6 250.000

15.01.2008 5 300.000

16.01.2008 4 375.000

17.01.2008 3 500.000

18.01.2008 2 750.000

19.01.2008 1 1.500.000

20.01.2008 0 1.500.000

Demand vality timeframe

Non fulfilment costMonday

Non fulfilment costTuesday

Non fulfilment costTuesday

Nonfulfilment

costs

Vality extension

Figure 78

With the remaining fields Direction, Penalty Costs: Late and Penalty Costs: Early you can specifycosts that are incurred in case the Optimizer assigns a demand outside the planned start and endtime.

If the calculation is based on start, fix costs for an early start or a late start are taken into account.Otherwise if the calculation is based on end, costs for an early end or a late end are incurred.

4.10.3 Logging of Optimization RunsWith IMG activity Define Logging of Optimization Runs it is possible to define how the SAPMultiresource Scheduling part of the optimization will be tracked.

Figure 79

In fact, an optimization run contains of 3 basic steps:

1) Reading the data to be optimized from SAP Multiresource Scheduling

2) Call optimizer / execute optimization


July 2010 67

3) Read result and put into SAP Multiresource Scheduling

With this log functionality you can keep track of steps 1 and 3 whereas step 2 can be tracked by theoptimizer log (available via transaction /MRSS/RCCF_LOG). All logs can be displayed in the MRSOptimizer log transaction /MRSS/OPT_LOG)

The Level defines the list of messages that should be included in the the log. You can set the rangefrom MUTE (nothing will be tracked) up to DEBUG 2 which will dump every message into the logfile.

The logical path defines the location where the file should be written. These locations can bedefined using transaction FILE.

Use the last flag Active to activate or deactivate the logging. With this, you can deactivate thewriting of the log file without completely deleting the customizing entry.

NoteBe aware that using the log functionality may have slight impacts on performance.

4.10.4 Optimization ScenariosThis IMG activity groups the different profiles for the optimizer, travel times and logging together.

Figure 80

As the default scenario can be changed during runtime, use this functionality to define differentscenarious for different needs.

ExampleDefine one scenario Fine Planning to optimize the next 5 days into future as this isthe fine planning. Here you want to use a longer runtime for the optimizer along witha GIS system. For optimization of up to 2 weeks in future you might want to define ascenario called Rough Planning and use only half of the runtime for the optimizer asthe result will anyway still change. Also using direct line calculation might be OK atthis point in time.

4.10.5 Assigning Profiles to Planning Board ProfileIn the final step you carry out the activity Define Planning Board Profile. Here you have to assignthe scenario, the geo profile and the optimizer profile to the planning board profile. By selecting thecorresponding checkboxes, you activate the functions map display, travel times and optimization.

Figure 81

The here defined scenario and profiles will be taken as defaults. Where the Scenario will define theoptimizer profile and the geo profile. You can oversteer the log profile and optimizer profile whenyou are about to invoke the optimizer.


October 2010 68

Figure 82

Master Data Setup

July 2010 69

5 Master Data SetupBefore SAP Multiresource Scheduling setup is complete, a few other things must be done, althoughthey are not part of Customizing.

5.1 Personal Resources: HR or not?You must determine if you want to maintain your personal resources using an HR system or if youwant to use business partners who have the role ‘employee’. In this case, ‘maintaining’ meansdealing with the qualifications and working times for an employee.As mentioned, you have two choices: Use the data from an HR system Use the business partners with the role ‘employee’

It is beyond the scope of this document to discuss here the advantages and disadvantages of eachalternative. Depending on your choice you have to perform different setup steps.

5.1.1 Using HR DataIf you want to use HR, you need to tell SAP Multiresource Scheduling. Use the Configure BasicSettings (view /MRSS/V_SGE_PROC) Customizing activity to choose the option HR Resource.

Figure 83

Creating HR dataYou can create new HR persons with transaction PA40 or use existing ones. In both cases youmust create or maintain the following info types in transaction PA30:

Action (info type 0000)For hiring an employee.

Personal Data (info type 0002)For the employee’s name.

Organizational assignment (info type 0001)The HR person must be assigned to an organizational unit (or indirectly assignedto it by a position).

Master Data Setup

October 2010 70

Figure 84 Planned working schedule (info type 0007)

The planned working schedule (PWS) of the HR person is defined by a workschedule rule. For example an employee works two shifts (day shift and nightshift). In info type 0007 you can assign the work schedule rule, the daily workinghours, and the weekly workday.

Figure 85

Master Data Setup

July 2010 71

Optional: Addresses (info type 0006)If you want to use the geographical information system in order to locate an HRperson you have to define a home address.

Using qualificationsYou can use either standard qualifications or specific SAP Multiresource Scheduling qualificationsfor your resource planning. If you use specific SAP Multiresource Scheduling qualifications you cancombine qualifications in qualification matrices.Use the Configure Basic Settings (view /MRSS/V_SGE_PROC) Customizing activity to activateSAP Multiresource Scheduling qualifications:

Figure 86If you use standard qualifications you can assign qualifications to persons using transaction PPPM.If you use specific SAP Multiresource Scheduling qualifications you can create the following data:

qualification catalogs using the transaction /MRSS/SQM_CAT qualification matrices using the transaction /MSRS/SQM_MAT employee profiles using the transaction /MRSS/PPPM requirements profiles using the transaction /MRSS/REQM

For more information about the functions for qualifications, see the Application Help.Transferring HR data to SAP Multiresource Scheduling BasisAfter telling SAP Multiresource Scheduling you will use HR data, you need to transfer the HR datainto the SAP Multiresource Scheduling Basis. You need to do this every time the HR data haschanged, so it’s a good idea to use a batch job running e.g. every night.The transfer is done using the report /MRSS/HCM_RPTWFMIF. This report will transfer theresources itself, their HR qualifications, and their availability times into the SAP MultiresourceScheduling Basis for usage by SAP Multiresource Scheduling.

Figure 87In the example, the HR availability times assigned to the profile ‘WORK’ are transferred as workingtimes, and the profile ‘WORK_BREAK’ is transferred as break times. For a detailed description, seethe online documentation of the report.

Master Data Setup

October 2010 72

Figure 88You can check if the resources are created by using the ‘read availability’ option only. The resultinglist will look like this:

Figure 89

Master Data Setup

July 2010 73

5.1.2 Using Business PartnersWhen using the business partners as employees, you need to create them using the BPtransaction.

Create Business PartnerRemember that you also have to maintain the partner in the ‘BUP003 Employee’ role.

Figure 90

NoteIf a business partner has been created by mistake and is not used in the system, itcan be deleted with BUPA_DEL.

NoteTo use the standard back-integration of the order, the personal number must bemaintained on the business partner. Role Employee, Tab Identification.

NoteIn the organizational management it is not possible to search for business partnersin the tree search function. Business partners can only be found with the transactionBP.

Master Data Setup

October 2010 74

Using QualificationsIf you want to use HR qualifications with your business partner, you can maintain them usingtransaction PPPM.

Transfer Business PartnerOnce they are created, you can use the transaction /MRSS/WFM_ADMIN to transfer the businesspartners.It is possible to select the partners either by organizational units or directly. In any case you need tospecify which times you want to transfer. In the example, the working times defined by the profileWORK will be transferred.For a more detailed description of each field, refer to the documentation or use the F1 helpfunctionality.

Figure 91

5.2 Organizational StructureThe next important thing to set up (if it does not already exist) is the organizational structure. Youneed to set up a structure where you can assign your workplaces and employees (from HR orbusiness partners) to positions.

Master Data Setup

July 2010 75

5.2.1 Create Organizational StructureUsing the PPOME transaction will bring you to the maintenance screen where you can do all thework.

Figure 92You need to build up the structure matching your organizational model, then assign your used workcenters to the corresponding organizational unit. Also, you need to create positions and assignemployees.

5.2.2 Linking with Work CentersAfter creating the organizational structure and adding positions and employees, you need to attachthe units to your work centers. The orders created for a specific work center (of category workcenter with resource planning node) will then appear under the assigned organizational unit in theSAP Multiresource Scheduling.For example, use transaction CR02 to do this. After selection of the work center (of category workcenter with resource planning node), press the HR Assignment button available in the menu bar.

Figure 93This will bring you to a dialog to select the object you want to attach. Select the corresponding unit.

Figure 94

Master Data Setup

October 2010 76

Remember that you also need to set up the capacity times for your work center. You can also getthere by entering the transaction CR02 and switching to Capacities tab. Press the Capacity button.If you do not see the tab for capacities, please see the end of this chapter.

Figure 95

In the following dialog, you can enter the necessary values.

Master Data Setup

July 2010 77

Figure 96

Enabling the capacity tab: if you are not able to see the capacity tab, you might need to enable itfirst in the Customizing Configure screen sequence for Work Center. Please go to transactionSPRO and follow the path:

Figure 97

Here you need to enable the Capacities and Scheduling tabs.

Master Data Setup

October 2010 78

NoteThe capacity information maintained in the work center is not used in SAPMultiresource Scheduling directly. But it is used in the order during scheduling. Inthis way, the planned start and planned end of the operation are influenced by thestart and finish date maintained above.

If the requirement assignment tab on the order operation should be visible – for example, if back-integration is activated – then you must enter a formula under Other formula:

Figure 98

5.3 Maintaining SAP Multiresource Scheduling ResourcesUsing transaction /MRSS/WFM_ADMIN_HR you can access the report/MRSS/WFM_MASTERDATA_ADMIN_HR. This report gives you the opportunity to create, changeor delete time allocations for SAP Multiresource Scheduling resources that reiterate periodically.You can specify a period for the time allocation by defining the start and end date as well as therepetition interval.You can maintain time allocations for SAP Multiresource Scheduling resources by using thepersonnel number. Apart from that, you can maintain time allocations for all resources assigned tothe same resource planning node.A distinction is made between daily and weekly intervals for time allocations.

Master Data Setup

July 2010 79

5.3.1 Example: Daily Interval for Time AllocationYou use daily intervals for time allocations for maintaining the annual leave (HOLIDAY) of an SAPMultiresource Scheduling resource.For this purpose, you choose the desired SAP Multiresource Scheduling resource and maintain thetime allocation. Choose the factory calendar and select the time allocation type HOLIDAY. Specifythe period for the time allocation, for example the first quarter of the year by selecting the start andend date. Select the daily radio button.Specify the interval for the first time allocation that will be repeated. Define start and end date andtime. If you want to delete old time allocations check the checkbox.Then specify the repetition interval. This way you determine on which day the time allocation will berepeated. If the time allocation should be repeated every day during the specified period, choose 1.

Figure 99

Master Data Setup

October 2010 80

5.3.2 Example: Weekly Interval for Time AllocationYou use weekly intervals for time allocations for maintaining on call services (ONCA) of an SAPMultiresource Scheduling resource.For this purpose, you choose the desired SAP Multiresource Scheduling resource and maintain thetime allocation. Choose the factory calendar and select the time allocation type ONCA. Specify theperiod for the time allocation, for example the first quarter of the year by selecting the start and enddate. Select the weekly radio button.Specify the interval for the first time allocation that will be repeated and if needed a delay. Definestart and end date and time. If you want to delete old time allocations check the checkbox.Then specify the repetition interval. This way you determine the week in which the time allocationwill be repeated. If the time allocation should be repeated every week during the specified period,choose 1.

Figure 100

The First Demand

July 2010 81

6 The First DemandIn this chapter you will create the first demand (coming from PM/CS integration) that will bedisplayed in the worklist of SAP Multiresource Scheduling.

6.1 Order and Order OperationUsing the IW31 transaction you can create an order and maintain the order operations. In the initialscreen you have to provide the order type and the planning plant at least.

Figure 101

In the order header you have assign the order to the responsible work center and choose the basicstart and finish date.In this example the ‘Maintenance order’ was assigned to work center DE_SC_01/0001 andscheduled on 4th October at 8:00.

Figure 102

The First Demand

October 2010 82

In the order operation you have to choose the control key, assign the operation to the executingwork center, and choose the duration and the number of necessary employees.In this example, the ‘Maintain machine’ operation with control key PM01 was assigned to workcenter DE_SC_01/0001. The operation takes two hours and needs to be performed by one person.

Figure 103

Afterwards you can press the schedule button in order to determine the scheduled start time andrelease the order. Finally when you can save the order, the corresponding demand will be createdin the SAP Multiresource Scheduling worklist.

NoteIn the SAP Multiresource Scheduling Customizing you can define whether the orderneeds to be released before the demand becomes created in the SAPMultiresource Scheduling worklist for each order type.

Using the transaction /MRSS/PLBOORG you can invoke the SAP Multiresource Schedulingplanning board and choose the organizational unit that is assigned to the executing work center ofthe created order operation. The result is your first demand in the SAP Multiresource Schedulingworklist.

Figure 104

Now you can go on with scheduling of this demand by looking for an available human resource.Therefore you can create an assignment by dragging the demand from the worklist to the SAPMultiresource Scheduling planning board.

Figure 105

In the next paragraphs you will find additional information regarding the demand definition.

The First Demand

July 2010 83

6.2 Production Resource and ToolIn certain situations a tool resource is necessary in order to execute the order operation. First, themaster data for the tool resource must be defined by creating an equipment with the type‘production resource/tool’ (PRT).

6.2.1 Create Production Resource and ToolThis paragraph describes the creation of the equipment first, which will be used as tool resource inthe SAP Multiresource Scheduling resource list later. Using transactions IE01 and IE02, you cancreate and maintain equipments.The equipment has to be created with type ‘P’. The basic data of the equipment is the planningplant and organizational unit the equipment belongs to.

Figure 106In this example the equipment will be assigned to work center DE_SC_03/0001.

6.2.2 Assign Production Resource and Tool to OperationIn order to define the need for a certain tool resource, you can assign a production resource/tool(PRT) to an order operation.

The First Demand

October 2010 84

Figure 107

Therefore select the operation in the operation tab and press the PRT button.

Figure 108

In the next dialog, you can assign the necessary PRT. In this example the required equipment is10000017 and the control key is 1.

Figure 109

6.3 Usage of Several Production Resources and ToolsIn most cases the need for one particular tool resource is not feasible, because the service advisorwho creates the order operation does not know which tool resource might be available at a workcenter. In this case, the scheduler in the SAP Multiresource Scheduling planning board shouldselect an available tool resource among others.

The First Demand

July 2010 85

For this purpose you can assign a material to the order operation and define the need for a groupof possible tool resources.

6.3.1 Create MaterialUsing the transaction MM01 and MM02 you can create and maintain a material. The material hasto be created with the ‘production resource/tool’ material type.

Figure 110

On the PRT tab you must maintain the task list usage. With this key you can control in which tasklists the PRT may be used.

In this example, the material 341 was created using control key 009 (usage in all task lists). Thismaterial defines a group of tools for checking uninterruptable power supply.

Figure 111

6.3.2 Assign Material to Several Production Resources and ToolsNow you can assign the material as construction type to several equipments by using the tabstructure.

The equipment 10000207 is one voltameter among others at the work center and part of the groupof tools for checking uninterruptable power supply.

The First Demand

October 2010 86

Figure 112

6.3.3 Assign Production Resource and Tool to OperationDuring the creation of an order operation, you can assign the material 341 to the operation. In thisway you define the need for a group of possible production resources and tools.

Figure 113

6.4 Direct Assignment of Production Resources and Tools in theSAP Multiresource Scheduling Planning Board

If no production resource was assigned to the operation you can also later on assign a tool demandin the planning board and thus plan a tool resource. You can define a default value for the controlkey of the production resource In the Customizing activity Sources of Demand -> Orders -> DefineDefault Values for Production Resources and Tools or in the material master data. For moreinformation, refer to the Application Help.

6.5 Definition of HR QualificationsOn one hand, qualifications are used to define the need for certain skills for executing an orderoperation. On the other hand, employees possess qualifications in order to execute a certain task.Before assigning them, a qualification catalog must be defined.

6.5.1 Create a HR Qualification CatalogUsing the OOQA transaction you can define a qualification catalog.

The First Demand

July 2010 87

6.5.2 Assign HR Qualifications to Order OperationWhen creating an order with transaction IW31 you can assign the necessary qualifications to eachoperation.

First create a requirement profile.

Figure 114

NoteYou can also maintain requirement profiles with transaction PO17.

Afterwards maintain the necessary qualifications.

Figure 115

6.5.3 Assign HR Qualifications to EmployeeUsing the PPPM transaction you can assign qualifications to an employee who can be either an HRPerson or a business partner.

The First Demand

October 2010 88

Figure 116

6.6 Requirements Assignment on Operation LevelDuring the back-integration into the order from SAP Multiresource Scheduling, the assignmentreflected by capacity splits on the operation level.

Figure 117

If the Requirements Assignment tab is not visible on the operation level, please check the followingpreconditions:

The work center possess a capacity category

The First Demand

July 2010 89

The work center possess a distribution formula

Figure 118

In the order header the Capacity requirements check box must be set

Figure 119

A duration must be defined on the operation level

Enhancing SAP Multiresource Scheduling

October 2010 90

7 Enhancing SAP MultiresourceScheduling

In this chapter you become familiar with some possibilities for enhance SAP MultiresourceScheduling.

CautionAll examples and code fragments must be used for learning purposes only.

7.1 Worklist

7.1.1 Additional Customer Fields in Item WorklistThe customer may define additional fields in the item worklist in order to enable a scheduler to seeimportant information when working with the planning board.

Customizing and Code Example:

In this example the worklist will be extended by a customer’s address information fields that arecoming from the customer service order.

1. In structure /MRSS/T_DEM_INFO and create append structure ZCUSTOMER_FIELDSwith the following fields:

Component Component Type

ZZSTREET AD_STREET

ZZPOSTAL_CODE AD_PSTCD1

ZZCITY AD_CITY1

2. In /MRSS/IMG invoke activity Define the Fields in the Worklist and define the fields withaccording data elements.Invoke activity Assign Fields from Generic Demand and assign the worklist fields to theappend structure fields of subobject INFO (corresponds with /MRSS/T_DEM_INFO).

Figure 120: Assign Fields from Generic Demand3. Invoke activity Create Worklist Profile and assign the worklist fields to a worklist profile.

When creating a new worklist profile, please note that this profile has to be used in theplanning board profile (activity Define Planning Board Profile).In order to pass the address information fields, the method PUSH_TO_MRS of BAdI/MRSS/RSG_PM_INT has to be implemented.


July 2010 91

METHOD /mrss/if_ex_rsg_pm_int~push_to_mrs.

***********************************************************************

* Demo implementation: customer address information

***********************************************************************

DATA: s_diadr_wa TYPE diadr,

l_ihpa_tab TYPE TABLE OF ihpavb.

FIELD-SYMBOLS <fs_info> TYPE /mrss/t_dem_info_ext.

CALL FUNCTION 'PM_PARTNER_GET'

EXPORTING

objnr = is_header-object_no

IMPORTING

diadr_wa = s_diadr_wa

TABLES

ihpa_tab = l_ihpa_tab.

* update customer address information in ct_info

LOOP AT ct_info ASSIGNING <fs_info>.

<fs_info>-zzstreet = s_diadr_wa-street.

<fs_info>-zzpostal_code = s_diadr_wa-post_code1.

<fs_info>-zzcity = s_diadr_wa-city1.

ENDLOOP.

ENDMETHOD.

7.1.2 Highlighting Worklist ItemsIn order to focus the scheduler’s attention on particular worklist items the color of each item can bechanged. There are two possible ways described in the examples below. In the first example theworklist item color depends on a static parameter (for example order priority; this might change onlyduring order save). In the second example the system will determine the color while working withthe planning board, so that the worklist item color might change.

Example 1:

In this example, the color of worklist items will be set depending on the service order operationpriority.

1. Go to transaction SE11 and create a new data element ZMRS_LINECOLOR. Choose theData Element type and confirm. Enter a description and choose Predefined Type. Enter thedata type CHAR with a length of 4.


October 2010 92

2. Enter the following field labels.

3. Save and activate the new data element.

4. Go to transaction SE11 and create the customer include structure CI_INFO (if it does notexist yet). Choose the Structure type and confirm. Enter a description and a component asfollows.

5. Save and activate the new data element. If the system asks for an enhancement category,we recommend to choose Can be enhanced (character-type).


July 2010 93

NoteThe new component of the customer include structure will be added to the database table/MRSS/D_DEM_INFO.

6. In the Customizing for SAP Multiresource Scheduling choose Multiresource PlanningSet Up Scheduler Workplace Workplace Profiles Worklist Profile.

Choose Customizing activity Define the Fields in the Worklist and define the LINECOLORfield. Do not assign any class name or data element. Only the LINECOLOR field name istechnically important.

7. Choose Customizing activity Assign Fields from Generic Demand and assign the worklistfield LINECOLOR to the structure field LINECOLOR of sub object INFO (corresponds with/MRSS/T_DEM_INFO).

8. Choose Customizing activity Create Worklist Profile and assign the worklist fieldLINECOLOR to a worklist profile. When creating a new worklist profile, note that this profilehas to be used in the planning board profile (see Customizing activity Define PlanningBoard Profile).

As shown in the screenshot below, you can also use the standard worklist profile ST_R3.


October 2010 94

9. In order to set the appropriate color of a worklist item, the method PUSH_TO_MRS of BAdI/MRSS/RSG_PM_INT has to be implemented. Remember to activate the BAdI.

In this example, when the user saves the PM/CS order the order priority is taken intoaccount for the worklist item color.

METHOD /mrss/if_ex_rsg_pm_int~push_to_mrs.

************************************************************************ Demo implementation: set color of worklist items***********************************************************************DATA: ls_info TYPE /mrss/t_dem_info_ext,

ls_plrs TYPE /mrss/t_dem_plrs_ext, lv_tabix TYPE sy-tabix.

* Set color on service order levelLOOP AT ct_info INTO ls_info.

lv_tabix = sy-tabix.

READ TABLE ct_plrsINTO ls_plrsWITH KEY key_ext = ls_info-key_ext.

IF sy-subrc EQ 0 AND ls_plrs-priority <> 0.CASE ls_plrs-priority.WHEN 1. "Very High

ls_info-linecolor = 'C610'. "Bright redWHEN 2. "High

ls_info-linecolor = 'C710'. "Bright orangeWHEN 3. "Medium

ls_info-linecolor = 'C300'. "YellowWHEN 4. "Low

ls_info-linecolor = 'C100'. "BlueWHEN 5. "Very Low

ls_info-linecolor = 'C100'. "BlueENDCASE.

MODIFY ct_infoFROM ls_infoINDEX lv_tabixTRANSPORTING linecolor.

ENDIF.ENDLOOP.

ENDMETHOD.

NoteThe color code is defined as follows: Cxyz


July 2010 95

Color Code (x) Brighter colors (y) Inverse coloring (z)

1 = Gray-Blue

2 = Light Gray

3 = Yellow

4 = Blue-Green

5 = Green

6 = Red

7 = Orange

1 indicates that thecolor is brighter.

0 indicates that thecolor is displayed asnormal.

1 indicates that the colorsare displayed inversely.

0 indicates that the color isdisplayed as normal.

Example 2:

In this example, the system will perform a check during the worklist initialization and will set thecolor of worklist items depending on the item plan status. As opposed to the previous example, theparameter is not static (like the order priority). That means if the parameter becomes differentduring working with the planning board, the system will change the worklist item color.

1. Go to transaction SE24 and create a new class (for example ZMRS_CL_WL_COLOR).Choose the Class object type. Enter a description and specify the instantiation as Public.

On the Interfaces tab enter the interface /MRSS/IF_SGE_WL_ATT.

On the Methods tab double-click the method ATTRIBUTES_DETERMINE and enter thefollowing example implementation:


October 2010 96

METHOD /mrss/if_sge_wl_att~attributes_determine.

INCLUDE /mrss/constants.

DATA: ls_demand LIKE LINE OF it_items, lref_item TYPE REF TO /mrss/cl_sgd_single_demand, lv_plan_status TYPE /mrss/t_wl_plan_status, ls_value TYPE /mrss/t_guid_field_value, ls_attribute TYPE /mrss/t_fieldname_value.

LOOP AT it_items INTO ls_demand.

lref_item ?= ls_demand-object. ls_attribute-fieldname = 'LINECOLOR'.

CALL METHOD lref_item->plan_status_get RECEIVING rv_plan_status = lv_plan_status.

CASE lv_plan_status.

WHEN gc_plan_status-planned. " TP ls_attribute-value = 'C500'.

WHEN gc_plan_status-part_planned. " PP ls_attribute-value = 'C300'.

WHEN gc_plan_status-not_planned. " NP ls_attribute-value = 'C600'.

WHEN gc_plan_status-tech_completed. " TC ls_attribute-value = 'C100'.

WHEN OTHERS.

ENDCASE.

INSERT ls_attribute INTO TABLE ls_value-attributes. ls_value-guid = ls_demand-guid.

INSERT ls_value INTO TABLE et_values.

ENDLOOP.

ENDMETHOD.

2. In the Customizing for SAP Multiresource Scheduling choose Multiresource PlanningSet Up Scheduler Workplace Workplace Profiles Worklist Profile.

Choose Customizing activity Define Classes for Determining Worklist Fields and specifythe new class (for example ZMRS_CL_WL_COLOR).


July 2010 97

3. Choose Customizing activity Define the Fields in the Worklist and define the LINECOLORfield. Assign the new class (for example ZMRS_CL_WL_COLOR). In addition select theValue Is Determined Dynamically checkbox.

Do not assign any data element here.

4. Invoke activity Create Worklist Profile and assign the worklist field LINECOLOR to aworklist profile. When creating a new worklist profile, note that this profile has to be used inthe planning board profile (see Customizing activity Define Planning Board Profile).

As shown in the screenshot below, you can also use the standard worklist profile ST_R3.

When the user enters the planning board or creates assignments in this example, the item planstatus is taken into account for the worklist item color.


October 2010 98

7.1.3 Important Standard FieldsWhen Customizing worklist profiles, the following fields must always be in the profile; otherwise theworklist will dump:

Object_id Number_int Duration Duration_unit Utilization

7.2 Business Add-Ins (BAdIs)The table below lists BAdIs with their technical names and short descriptions. For furtherinformation see the BAdI documentation in the system. For some BAdIs, there are also exampleimplementations available in the system.

BAdI Description/MRSS/SQL_CAT_MIGR Transfer of Qualification Catalogs/MRSS/SQL_QUAL_MIGR Transfer of Qualifications/MRSS/SQM_CAT_EXIT Enhance Catalog Options/MRSS/SQM_MAT_EXIT Enhance Matrix Options/MRSS/SQP_DEM_EXIT Extend requirements profiles/MRSS/SQP_EMP_EXIT Extend employee profiles/MRSS/SQE_MATCHING Qualification matching/MRSS/SQE_QUALRESULT Adjust field catalog of qualification

matching results list/MRSS/RSG_PM_INT Integration of Maintenance/Service Order

with SAP Multiresource Scheduling/MRSS/RAC_ASSGN_ELEM Determine material number for access to

material master/MRSS/RAC_SEARCH_ALG Search algorithm for access to SAP

Multiresource Scheduling Customizingtables

/MRSS/RAC_CHECK_DURA Comparison of duration between demandand assignment

/MRSS/RAC_NOTIF Tasks for Notification/MRSS/SGE_AUTO_ASG_RES_AVAIL Change Resource During Automatic

Assignment Creation/MRSS/RSG_TECH_FIELD_DET Determination of Technical Field Names/MRSS/RSG_DEMAND_ADRESS_GET Determination of Address Data for

Demands/MRSS/RAP_PS_INT Integration of network with SAP

Multiresource Scheduling/MRSS/RAP_BACK Back intergration to network/MRSS/SGE_RESOURCE Anonymize resources/MRSS/SGE_MOBILE_PS Sending Assignments to Mobile Devices/MRSS/INTER_COMPANY Control of cross-functional resource

processing/MRSS/HCM_INT Filter Infotype Records for HR Integration/MRSS/HCM_TZONES Alternative Determination of Time Zone for


July 2010 99

Specific Resources/MRSS/HCM_TIMESPECS Description for Time Allocations/MRSS/ROUND_OFF_TIMESPECS Rounding of Time Allocations/MRSS/SGU_ASSGN_ELEM Determine Graphical Element for

Assignments/MRSS/SGU_DESC_DETER Determine Description and Quick Info for

Assignments/MRSS/SGU_WORKLIST Change field catalog for operation worklist/MRSS/SGU_CAPA_ASSIGNMENT_LIST Enhancement of capacitive assignments

list/MRSS/MESSAGES Message Creation/MRSS/SGU_RES_FILTER Resource filter - selection screen/MRSS/SGE_AUTH_CHECK Authorization Check for Resource Planners/MRSS/SGU_EQUI_AUTH Equipment Check/MRSS/SGE_ASGN_RELAT Determine Related Assignments and

Demands/MRSS/SGU_RES_MESSAG Send Messages to Resources/MRSS/ALERT_FUNCTION User functions for alerts/MRSS/SGU_RESFLT_MGR Filter Resources in Manager Planning

Board/MRSS/SGE_GET_TEAM_WC Determine Work Center for Team/MRSS/SGE_SCHEDAUTO Automatic Assignment Creation

7.3 Further Important Interfaces

7.3.1 Table /MRSS/C_SGE_SCAThe table /MRSS/C_SGE_SCA contains all attributes that are used for scenario R/3. Please referto the transaction SE16, enter table /MRSS/C_SGE_SCA and search for all attributes with SCENequal to “R3”.

Additional Data for Resource

On the context menu of a resource, a popup with additional data can be called. This popup is calledwith a function module: parameter attribute = RES_DET. This function module can be a customerfunction module in its own function group.

Go to Display Order

From the demand the user can jump to an order. This is done with a function module: parameterattribute DISP_ORDER. This function module can be a customer function module in an ownfunction group.


October 2010 100

7.4 Checks and AlertsAs mentioned above, the check and alerts for the planning board are fully customizable. Here’s anexample of how to do it:

First implement a new class (e.g. Z_CL_MRS_CHECK_DEMO) that should handle the check. Thisclass needs to implement interface /MRSS/IF_SGE_CHECK. In the example, we also added oneprivate method that does the check and raises a message (to trigger the alert):

Method Type Description

/MRSS/IF_SGE_CHECK~CHECK_PERFORM Public Perform Check forResource

/MRSS/IF_SGE_CHECK~INITIALIZE Public Initialization

/MRSS/IF_SGE_CHECK~IS_TIME_DEPENDENT Public Time-DependentCheck?

/MRSS/IF_SGE_CHECK~CHECK_PERFORM_CHANGE

Public Perform Check AfterChange (Assignment,Time Specification)

CREATE_ALERT Private Creates a single dummyalert for demo purposes

We also added the following attributes for the demo-class. For a real working class, you might needeven more.

Attribute Type Type Description

GREF_RESOURCE_MGR Protected Ref To/MRSS/CL_SGE_RESOURCE_MGR

Scheduling Engine:Resource Manager

GREF_ALERT Protected Ref To/MRSS/IF_SGA_ALERT_INT

Alert MonitorInterface

GREF_WORKLIST Protected Ref To/MRSS/IF_SGE_WORKLIST

Worklist Interface

GREF_CLOCKING Protected Ref To/MRSS/IF_SGE_CLOCKING

Interface for TimeRecording

GV_CHECK_ENABLE Protected /MRSS/T_BOOLEAN Checks enabled?

GT_CHECK_SINGLE_RES_MSGNR

Protected /MRSS/T_ALERT_MESSAGE_TAB

Messages

For a simple demo, we need to implement two of the interface’s public methods for the incomingcalls on runtime (beside the initialization method when the planning board starts):

/MRSS/IF_SGE_CHECK~CHECK_PERFORM( ) and

/MRSS/IF_SGE_CHECK~CHECK_PERFORM_CHANGE( ).

These methods will be called when the planning board executes the registered checks. Withinthese methods you can do your checks or perform some private methods for further checks.


July 2010 101

In the example, we have an additional private method for the checks, so we simply implement anadditional perform to hand over the given data from the planning board.

METHOD /mrss/if_sge_check~check_perform.

* check something and raise a demo-message (/MRSS/SGE 100)

*=====================================================================

INCLUDE: /mrss/constants_all.

* ---------------------------------------------------------------------

DATA: ls_assignment TYPE /mrss/t_assignment.

*=====================================================================

* Simply loop over all assignments and raise a message

LOOP AT it_assignments INTO ls_assignment.

create_alert( is_assignment = ls_assignment ).

ENDLOOP.

ENDMETHOD.

METHOD /mrss/if_sge_check~check_perform_change.

* check something and raise a demo-message (/MRSS/SGE 100)

*=====================================================================


* ---------------------------------------------------------------------

DATA: lref_assignment TYPE REF TO/mrss/cl_sge_data_changed_ass,

ls_assignment TYPE /mrss/t_assignment.

*=====================================================================

* Simply take the assignment and raise a message

CASE iref_data_changed->gv_object_type.

* Do assignment-changes


October 2010 102

WHEN gc_obj_type-assignment.

* Do a cast

lref_assignment ?= iref_data_changed.

CALL METHOD create_alert

EXPORTING

iref_assignment = lref_assignment.

ENDCASE.

ENDMETHOD.

In the CREATE_ALERT method the ‘real’ check would take place. In this demo for eachassignment a simple message will be raised.

METHOD create_alert.

*=====================================================================

* Importing:

* IS_ASSIGNMENT (TYPE /MRSS/T_ASSIGNMENT)

* Assignment ID with Object

* IREF_ASSIGNMENT (TYPE REF TO /MRSS/CL_SGE_DATA_CHANGED_ASS)

* Changed Assignment Specification in Scheduling

* Engine Application.

*=====================================================================


* ---------------------------------------------------------------------

DATA: ls_interval TYPE /mrss/t_timestamp_interval,

lref_demand TYPE REF TO /mrss/if_sge_single_demand,

lref_resource TYPE REF TO/mrss/cl_sge_single_resource,

ls_assignment_data TYPE /mrss/t_assignment_int,

lt_alert TYPE /mrss/t_alertdata_tab,

ls_alert TYPE /mrss/t_alertdata,

l_res_text TYPE text80,

l_timestmp_char(14) TYPE c,

lv_mess TYPE c,

ls_object TYPE /mrss/t_guid_w_type,


July 2010 103

lt_object TYPE /mrss/t_guid_w_type_tab.

* ---------------------------------------------------------------------

* Replace with your message and package

CONSTANTS: lc_msgnr_demo TYPE msgnr VALUE '199',

lc_msgid_demo TYPE msgid VALUE '/MRSS/SGE'.

*=====================================================================

* Check only, if alert-nr is enabled in alert-monitor

CHECK gv_check_enable = true.

* Depending on how we were called, fill the needed data

IF iref_assignment IS NOT INITIAL.

lref_resource = iref_assignment->gref_assignment->resource_get().

lref_demand = iref_assignment->gref_assignment->demand_get( ).

ls_assignment_data = iref_assignment->gref_assignment->data_get( ).

ELSE.

* Get demand for assignment

CALL METHOD is_assignment-object->demand_get

RECEIVING

rref_demand = lref_demand.

* Get resource of assignment

CALL METHOD is_assignment-object->resource_get

RECEIVING

rref_resource = lref_resource.

* Get assignment data

ls_assignment_data = is_assignment-object->data_get( ).

ENDIF.

* Perepare a dummy alert. Use e.g. parameters to this method for amore

* "usefull" creation of alerts

CLEAR ls_alert.

* Replace with your package


October 2010 104

ls_alert-msgid = lc_msgid_demo.

ls_alert-msgnr = lc_msgnr_demo.

ls_alert-msgtype = 'W'.

ls_alert-valid_from = ls_assignment_data-beg_tstmp.

ls_alert-valid_to = ls_assignment_data-end_tstmp.

CALL METHOD lref_resource->text_get

EXPORTING

iv_langu = sy-langu

RECEIVING

rv_text = l_res_text.

MOVE l_res_text TO ls_alert-msgvar1.

MOVE ls_assignment_data-beg_tstmp TO l_timestmp_char.

ls_alert-msgvar2 = l_timestmp_char.

ls_alert-msgvar2_is_tstmp = true.

MOVE ls_assignment_data-end_tstmp TO l_timestmp_char.

ls_alert-msgvar3 = l_timestmp_char.

ls_alert-msgvar3_is_tstmp = true.

* Prepare object-table

REFRESH lt_object.

ls_object-guid = ls_assignment_data-assignment_key.

ls_object-obj_type = gc_obj_type-assignment.

INSERT ls_object INTO TABLE lt_object.

ls_object-guid = lref_resource->gv_id.

ls_object-obj_type = gc_obj_type-resource.

INSERT ls_object INTO TABLE lt_object.

ls_alert-components = lt_object.

APPEND ls_alert TO lt_alert.

* Finished preparing table with alerts to raise=======================

IF lt_alert IS INITIAL.

* Delete old alerts of this resource/time-period

CALL METHOD gref_alert->alert_del_for_component


July 2010 105

EXPORTING

iv_component_guid = lref_resource->gv_id

iv_component_type = gc_obj_type-assignment

iv_valid_from = ls_assignment_data-beg_tstmp

iv_valid_to = ls_assignment_data-end_tstmp

it_messages = gt_check_single_res_msgnr.

ELSE.

* Start: internal usage to keep the "where-used list" working

MESSAGE i199(/mrss/sge) INTO lv_mess.

* End: internal usage to keep the "where-used list" working

* Delete old alerts of this resource/time-period and create newalerts

CALL METHOD gref_alert->alert_mod_for_component

EXPORTING

iv_component_guid = lref_resource->gv_id

iv_component_type = gc_obj_type-assignment

iv_valid_from = ls_assignment_data-beg_tstmp

iv_valid_to = ls_assignment_data-end_tstmp

it_messages = gt_check_single_res_msgnr

it_alerts = lt_alert.

ENDIF.

ENDMETHOD.

The new class needs then to be registered as a new check class. You can do this within the SAPMultiresource Scheduling Customizing. Specifically, you need to enter the new class in two places.

First register the class itself as a new check class, then add the class to a check profile.

Figure 121 Customizing activities for checks

You then need to register your used message to an alert profile. That is, you must link yourmessage and the alert type you want to belong the message to. In the screenshot below you cansee for example message 100 which belongs to alert type 1 which deals with capacities.


October 2010 106

Figure 122 Alert profile

After that configuration, your message should appear in the alert monitor.

7.5 Additional Information for Customizing

7.5.1 Planning Board Profile

Time Granularity

If the time granularity is not fine enough, the default time values of order operations might not fit tothe planning board grid. Planning via drag-and-drop is not possible then.

Example: Time granularity of one hour, order duration of 20 minutes beginning at 9:07 to 9:27.

Figure 123 Time granularity

Splitting

Instructions for Customizing splitting are given in the Customizing of the planning board profile. Ifsplitting should be deactivated, a very high value should be inserted in the field minimum duration.

Figure 124 Minimal duration

7.5.2 UI Profile

Screens

In the UI Profile you can customize which screens should be visible. For example, if the alertmonitor and the order tree structure are not needed, they can be deactivated in the profile.Furthermore the container in which the element should be displayed can be defined in thisCustomizing.

The following container composition is often used to show the most important information at aglance.


July 2010 107

Figure 125 Container composition

Additional Menu Buttons

If further transactions should be reachable from the planning board, it is possible to create up tofive buttons in the UI profile that later appear in the menu.

7.5.3 Day-based SchedulingYou can use day-based scheduling to schedule assignments based on the day. Day-basedscheduling supports resource planning based on entire days. This enables you to display resourceplanning more clearly. You can also specify only the working hours of one day as entire day anduse this specification for day-based scheduling. This function is available for the followingassignment types:

Concrete assignments

Stretched assignments

Capacitive assignments

Team assignments

To use day-based scheduling, make the following settings in Customizing for SAP MultiresourceScheduling under Set Up Scheduler Workplace Workplace Profiles Define Planning BoardProfile :

1. Select Day-Based Sched. checkbox the in Maintenance of Scheduling Engine Profile.

2. In Time Unit for Planning Board Profile, you have to specify a time unit for day-basedscheduling, for example, a time unit for a working day.

3. If you want assignments that are created using drag&drop in the planning board to be day-based, select the checkbox Create New Assignments Day-Based in the Customizingactivity Define User Interface Profile under Set Up Scheduler Workplace WorkplaceProfiles

RecommendationTo optimize the display of day-based scheduling in the planning board, werecommend to select the following checkboxes in the Customizing activity DefineUser Interface Profiles:.

1. Hide Non-Working Times to disable the display of night and break times2. Show Capacitive Assignments in Planning Row to hide the capacitive line

and enable collisions of capacitive assignments

Assignment of Technician Work Centers

October 2010 108

NoteThe recommended Customizing settings are independent of day-based scheduling.You can also use them in different planning situations.

For more information, see the available Application Help.

8 Assignment of Technician WorkCenters

In context of PM/CS it needs to be made sure, that a technician work center is assigned to aresource. If the technician work center is not assigned to the resource, planning of this assignmentis not allowed.

8.1 How to assign a technician work center to a resourceYou need a logistic work center (transaction IR01/IR02) of a work center category that is configuredas technician work center. (To find out what categories are considered to be technician workcenters see SAP Multiresource Scheduling Customizing: Basic Settings Assign ERP ObjectsAssign Work Center Types).

NoteThe category of a work center cannot be changed after the work center has beencreated.

The second step is the creation of HR work center (transaction PO01). Once the HR work centerobject is created you have to create two relationships for this work center (also in transactionPO01). The first one is the relation between HR work center and logistic work center (type A 061,see example). The second relation is the relation between HR work center and the resource (typeA 008, see example).

ExampleResource with pers.no. 11691. Logistic work center WC_1169

Create a logistic work center (Transaction IR01)2. HR Work center HR_1169

Create a HR work center (Transaction PO01)3. Relationships of HR_1169

Create the following relations: A 008 Holder P 00001169 A 061 Equals LA 10000033 (= object ID of WC_1169 to be found

using F4-help)


July 2010 109

Figure 126

8.2 How to check what HR work center and logistic work centeris assigned to a resource

Call transaction PPOSE (or PPOME) and locate the resource under its respective planning node. Inthe view Assignment of personal resource you will find the HR and the logistic work center of theresources.


October 2010 110

Figure 127

The fact that work centers are displayed in PPOSE is achieved by the following customizing ofevaluation paths (Tx. OOAW). Please do not change these settings.

Figure 128

8.3 How to check whether the assigned work center is atechnician work center

Call transaction IR03 and display the basic data to your work center.


July 2010 111

Figure 129

Compare the work center category with SAP Multiresource Scheduling Customizing:Basic Settings Assign ERP Objects Assign Work Center Types

Figure 130

In our example, the work center category 0005 of work center WC_1169 is defined as workcenter of technician.

8.4 What to do if the assigned work center is not a technicianwork center

The category of an existing work center can not be changed. The assigned work center is thereforeto be replaced with a technician work center.

Steps:

1. Create a new work center (transaction IR01) with work center category as “Work center oftechnician”. See above how to find the appropriate category in SAP MultiresourceScheduling Customizing.


October 2010 112

2. Locate the HR work center of your resource (see above how to find it using tx. PPOSE).Change the relationship of this HR work center using transaction PO01. Locate existingrelation of type A 061 and change the logistic work center to the newly created one.

Figure 131

Figure 132

Workflow Customizing

July 2010 113

9 Workflow Customizing9.1 Basic Workflow CustomizingIt is absolutely necessary that the Basic Workflow Customizing is correct to run the workflow.The Runtime Environment part is necessary to execute the standard workflow. The DefinitionEnvironment is necessary to develop specific workflows. This second part is only required on thedevelopment environment.

Figure 133

Start with Automatic customizing. If several points remain red or yellow, it might be necessary toprocess them one by one.

- Active plan version 01 should be customized on the system. The active plan version allowsyou to manage several simulations of your enterprise organization and compare them.Generally only one active plan (01) is used.

- The Workflow administrator is the user who receives messages when an error occurs on awork item. It can be any object of the organizationnal structure (position, function,organizationnal unit…)

- RFC Destination WORKFLOW_LOCAL_<MANDANT> should be created in SM59(connection type : L logical) and associated to user WF-BATCH (background) who shouldhave SAP_ALL profile. It can be necessary to synchronize passwords (then save) to havethis user at the workflow level.


October 2010 114

For more information on this point please review OSS notes:

0357742 - Maintaining RFC destination via Transaction SWUB(no authorization)

0073160 - Authorization profile for WORKFLOW_LOCAL

- Jobs SWWDHEX (triggering deadline handling) and SWWERRE (restarting of workitemswith temporary errors) should be scheduled. Periodicity for each check is generally setbetween 20 and 30 minutes. The SWWDHEX job is only required if workflows using thedeadline monitoring feature have been activated on the system.

This customization should be done in each client (you cannot transport everything). It is aprerequisite for any workflow development or processing of workflows.

9.2 Agent Assignment DefinitionAgent assignment (also called Task profile) defines agents who can execute work items linked todialog tasks. It should be maintained for tasks belonging to Task group TG 00209101.

Use transaction PFTG, enter task group id (here00209101). In the menu choose Extra Agentassignment Maintain.

For each task belonging to this group, select thecorresponding line by click on then click onAttributes.Carry out this activity for general tasksonly.Background task not needed.

Choose General Task. Click on Refresh index. Repeat this operation foreach tasks.

Figure 134

NoteAgent assignment is important when an error occurs on a workflow. According tothe agent determination type developed, the work item can be sent to all agents


July 2010 115

attached to the Task profile. The work item can also be transferred to all agentsassigned to tasks (depending on the customizing made above).

9.3 Customizing Approval Workflow Settings-Event LinkageThe second step is the event linkage activation. The customization setting required for the approvalworkflow is as follows.

Go to transaction /MRSS/IMG. Go to SAPMultiresource Scheduling

->Qualification->profile->setup approvalworkflow.

The event linkage should be activated.click on activate event linking

Click on details icon . Enable the checkbox for event linkage and presssave button and attach it to a customizingrequest.

The event linkage is activated. Agent assignment process can be carried outfrom the link here also.

Figure 135


October 2010 116

9.4 Setting up the SMTP Mailing for WorkflowsSending SMTP messages from R/3 requires three things:

1. SAP Connect customizing to send messages from R/3 to SMTP server

2. Customizing from users’ SAP Business Workplace of forwarding to SMTP address(transaction SBWP, menu Settings Office settings then create mail address).

3. Schedule of background job running report RSWUWFML (or new RSWUWFML2, seeOSS note 991764.) with a variant for the following options :

- Job suffix : 1

- Tasks: All that tasks that generate the notification

- Send granularity: one message for work item

- Attachment type: Workflow entry

- Log : Errors only

For more information please refer to OSS note 131795 - e-mail notification of workflow work items.

TREX Configuration

July 2010 117

10 TREX Configuration10.1 TREX Integration RequirementsThe two requirements To setup the TREX integration are as follows

A compatible TREX server (Refer to Product availability matrix for Details).

The RFC destination of the TREX server to be maintained in the ABAP server.

The RFC destination has to be created and connection test should be Succesful.

RFC destination should be of Type TCP/IP .the details of configurationare shown below

Use SM59 for RFC destination Maintenance The connection test should be confirmed

Figure 136

TREX Configuration

October 2010 118

10.2 TREX Configuration.The Primary requirement is a compatible TREX server Whose RFC destination has to bemaintained .the details of configurationare shown below

Use transaction /MRSS/IMG, navigate to the settingbelow

Enter the Name of the TREX destination here andsave. This has to be a previously maintained RFCdestibnation.The corresponding table is/MRSS/C_SQE_TREX

Figure 137

10.3 Testing the TREX Integration.The Report TREX_RFC_AE_EXAMPLE is used for testing the connection between the ABAPserver and the TREX server .it can be used to test creation, searching and deletion of an index inthe TREX server via the ABAP server. This can be helpful to find incompatibilities between theTREX and TREX ABAP client.

Run the report. Enter the RFC destination of the TREX Server andstart testing the creation deletion and updating ofan index.

Figure 138

TREX Configuration

July 2010 119

10.4 TREX Compatibility chart.The compatibility chart for the TREX versions is shown below.

TREX 7.00:

SAP Basis TREX Version

7.00 SP08 7.00.08.00

7.00 SP09 7.00.24.00

7.00 SP10 7.00.26.00

7.00 SP11 7.00.30.00

Setting up the Employee Profile Web UI

October 2010 120

11 Setting up the Employee Profile WebUI

This chapter describes the process of configuring the SAP Multiresource Scheduling employeeprofile maintenance component as configurations required in the SAP Multiresource Schedulingbackend system.

11.1 IntegrationThe complete SAP Multiresource Scheduling landscape consists of:

1. An SAP backend system (called SAP Multiresource Scheduling Backend in the document)where the SAP Multiresource Scheduling application is available.

2. ABAP Web Dynpro based UI component that enables maintenance of employee profile onthe web.This component is RFC enabled (communication between the Web Dynpro UI layer andthe SAP backend system)

11.2 Before You StartThe administrator is expected to have functional knowledge of SAP HR Master Data Management.

For any queries related to the standard SAP products refer to the standard documentation in SAPHelp Portal at http://help.sap.com:

1. SAP HR Master Data Management

2. SAP J2EE Administration

3. SAP EP Administration

11.3 SAP Multiresource Scheduling Backend ConfigurationThis step is needed to map the HR personnel number created in HR master data to the userslogging in to the application.

NoteTo create and administer HR personnel data in preparation for this step refer to theapplication help on Personnel Administration.

The users login to the application through the Web Interface with a user/password (called as webuser). This user has to be mapped to the actual HR personnel number in the transaction PA30.

1. Launch transaction PA30.


July 2010 121

Figure 139

2. Provide the HR personnnal number to be mapped (use search help if personnel number isnot known). Provide info type as 105 and subtype 0002.


October 2010 122

Figure 140

3. Enter the user name (Web user name)

This same “Web user name” is then added to the Web AS (section 3.3 of this guide).

NoteThe Web user name must not be more than 12 characters long.

Figure 141

4. Save your changes.

11.4 Application CheckOnce the installation is completed successfully the application can be accessed directly or via theportal.

Direct Link

Once the above steps are done, the application can be launched standalone by using the URL:

http://<server>:<port>/sap/bc/webdynpro/mrss/dpr_empprf

The logon screen should appear.

Log on using a user ID that is mapped to the corresponding HR Personal No. in SAP MultiresourceScheduling.


July 2010 123

Figure 142

The profile of the mapped user in the SAP Multiresource Scheduling system should come up.

Initial Setup Guide for SAP Multiresource Scheduling Employee Profile Workflows

October 2010 124

12 Initial Setup Guide for SAPMultiresource Scheduling EmployeeProfile Workflows

This chapter describes the basic settings that need to be maintained in order to use the workflowfunctionality in SAP Multiresource Scheduling employee profiles.

12.1 Basic settings

12.1.1 Customizing SettingsWorkflow ID: WS00209101

Choose Tools Business Workflow Development Utilities Automatic WorkflowCustomizing (Transaction: SWU3). Automatic Customizing covers all the activities that concern thetechnical basic settings.

Active plan version 01 should be customized on the system. Active plan version allowsyou to manage several simulations of your enterprise organization and compare them.Generally only one active plan (01) is used.

The workflow administrator is the user who receives messages when an error occurson a work item. It can be any object of the organizationnal structure (position, function,organizationnal unit…).

RFC Destination WORKFLOW_LOCAL_<MANDANT> should be created in SM59(connection type : L logical) and associated to user WF-BATCH (background) who shouldhave SAP_ALL profile. It can be necessary to synchronize passwords (then save) to havethis user at the workflow level.

This customizing should be done in each client. It is a prerequisite for any workflow development orprocessing of workflows.


July 2010 125

12.1.2 Agent AssignmentAgent assignment (also called task profile) defines agents who can execute work items linked todialog task. It should be maintained for tasks belonging to task group TG 00209101.

Use transaction PFTG, enter task group ID(here 00209101).

In the menu choose Extra Agentassignment Maintain.

For each task belonging to this group, select thecorresponding line, then choose Attributes.

Carry out this activity for general tasks only.Background task is not needed.

Choose General Task. Click on Refresh index. Repeat this operation foreach task.

Agent assignment is important when an error occurs on a workflow. According to the agentdetermination type developed, a work item can be sent to all agents attached to a task profile. AWork item can also be transferred to all agents assigned to a task (depending on the customizingmade above).

12.1.3 Event Linkage ActivationGo to transaction /MRSS/IMG. Go to Multiresource scheduling ->Qualification->Profile->Setup approval workflow.

The event linkage should be activated. ChooseActivate event linking.

Choose the details icon.

The event linkage is activated. The agent assignment process can be also carriedout from the link.

12.1.4 Setting up the SMTP mailing for workflowsSending SMTP messages from R/3 requires three things:

1. SAP Connect customizing to send messages from R/3 to SMTP server2. Customizing from users’ SAP Business Workplace of forwarding to SMTP address

(transaction SBWP, menu Settings Office settings then create mail address).3. Schedule of background job running report RSWUWFML (or new RSWUWFML2, see OSS

note 991764.) with a variant for following options:Job suffix: 1

Tasks: All that tasks that generate the notification

Send granularity: One message for work item

Attachment type: Workflow entry

Log: Errors only

For more information please refer to OSS note 131795 - E-mail notification of workflow work items.


October 2010 126

12.2 Organizational settings in PPOMEWhen an employee updates his/her profile and saves it, SAP Multiresource Scheduling allows forthe changes to be approved by the employee’s manager. The following is a step-by-step guide ofhow the manager of the employee is assigned / determined in HR.

12.2.1 Starting with a blank organizational unit

Figure 143


July 2010 127

12.2.2 Creation of a position under the organizational unit

Figure 144


October 2010 128

Figure 145

12.2.3 Assignment of resources to the newly created position

Figure 146


July 2010 129

Figure 147


October 2010 130

12.2.4 Creation of the manager positionThis is the same as creating a normal position. The only difference is that the indicator Head ofown organizational unit has to be checked.

Figure 148


July 2010 131

12.2.5 Assignment of a resource to the newly created managerposition

Figure 149

12.3 Customer Infotypes for Controlling the Approval ProcessThis following sub-topic describes the maintenance of the two custom infotypes required tocontrol the employee profile approval process (i.e. one infotype to control the managerapproval scenario and one infotype to control the employee approval scenario).1. The infotypes for controlling employee approval and manager approval are maintained in

SAP Multiresource Scheduling Customizing.

Figure 150


October 2010 132

Figure 151

2. Before these infotypes can be used they need to be created in SAP HR. The followingsteps outline the process for doing so.

3. Execute PM01 transaction (i.e. transaction for the creation of infotypes).

4. Maintain the infotype number 9222 (i.e. the same infotype which has been maintained inSAP Multiresource Scheduling Customizing for employee approval) as shown below.

Figure 152

5. Choose the Generate Objects button.

6. A pop-up will be displayed as shown below. Choose the Create button.


July 2010 133

Figure 153

7. Create the PS9222 structure. Enter the fields as shown below. The name of the field hasto be the same as what is maintained in SAP Multiresource Scheduling Customizing.

Figure 154

8. Activate the structure using the local object package.

9. The next screen which is displayed will show all the existing custom infotypes. Choose theNew Entries button to create an entry for the newly created infotype.


October 2010 134

Info type characteristics:

Figure 155

10. Enter the following entries.

Figure 156

11. Save the screen and save it as a local object.

12. As a result, a new custom infotype will be created.

13. This new infotype can be maintained for resources in the PA30 transaction (i.e. thetransaction to maintain HR master data).

14. Repeat the same procedure for the second infotype 9223 (i.e. the same infotype which hasbeen maintained in SAP Multiresource Scheduling Customizing for manager approval).


July 2010 135

15. In this case, when the generated structure PS9223 is to be maintained, the name of thefield has to be the same as what is maintained in SAP Multiresource SchedulingCustomizing for manager approval.

Figure 157

12.4 Resource Contact InformationWhen an employee submits his/her profile for approval, an e-mail is sent to the respectivemanager. Similarly when the manager approves / rejects a profile, an e-mail is sent to theconcerned employee.

In this process, the contact information (i.e. e-mail IDs) for the resources involved is picked up fromSAP HR data. The infotype containing the contact information must be maintained in SAPMultiresource Scheduling Customizing.

Figure 158


October 2010 136

Figure 159

Enhancement of Object Manager Scenario VERIMULT

July 2010 137

13 Enhancement of Object ManagerScenario VERIMULT

Search configuration in Transaction: OOOBJMANCUST

Configuration of search is done for both scenarios as shown in the following. Scenario OMEOO0represents search in transaction PPOME and scenario VERIMULT represents search in SAPMultiresource Scheduling transactions.

NoteFor the implementation of MRS 610 only the description for the scenarioVERIMULT is relevant. Carry out the described configuration for the scenarioVERIMULT only.

Figure 160

First define search node keys for planning node (object type used for resource planning nodes),and assign the according object types .


October 2010 138

Figure 161

Afterwards the search nodes can be defined.

Figure 162

NoteColumn group and header type can be defined and maintained in the ColumnFramework (transaction OOCOLFRAMCUST).

Figure 163


July 2010 139

Figure 164

SAP Multiresource Scheduling BW-Extractors

October 2010 140

14 SAP Multiresource Scheduling BW-Extractors

This chapter gives an overview to the implementation team responsible for BW integration of theSAP Multiresource Scheduling system.

14.1 Customizing and PackageBW Customizing: use transaction SBIW to get information or change settings in this area.

The development is located in development class /MRSS/GBW.

14.2 Terms for a Better UnderstandingTerm Definition

Assignment An assignment links a resource to a requirement. It containsspecifications about the time and duration of the planned execution

Demand Demands are planned in SAP Multiresource Scheduling withresources. The data for the demand is synchronized from the serviceorder operation or the network operation in SAP MultiresourceScheduling.

Operation This refers to a service order operation or a network operation.

DataSource Object that makes data for a business unit available to SAP BW.From a technical perspective the DataSource contains a number oflogically-related fields that are provided in a flat structure for datatransfer to SAP BW.

BW Extractor Program to export data to a BW system. Data will be selected in asource system, stored into a transfer structure using filters or datamapping and exported to a BW system.

BW service API Technology package in SAP source systems that facilitates a highlevel of integration for data transfer from source systems toconnected SAP BW systems.

14.3 BW – Data Extraction: Assignments

14.3.1 Data Dictionary ObjectsExtract structure: /MRSS/CBW_ASSGN_ATTR:

Component Component type Datatype/Len Description

ORDER_TYPE AUFART CHAR 4 ORDER TYPE

ORDER_NUMBER AUFNR CHAR 12 ORDER_NUMBER

ACTIVITY VORNR CHAR 4 OPERATION / ACITIVITYNUMBER


July 2010 141

ASSGN_DATE DATS DATS 8DATE (AS SELECT-OPTION FOR DATAEXTRACTION)

DEM_TYPE /MRSS/T_DEM_TYPE TYPE OF DEMAND

L_TIMEZONE TZNZONE CHAR 6 TIMEZONE

ASSINGMENT_KEY CHAR32 CHAR 32 ASSIGNEMENT-GUID

DEMAND_KEY CHAR32 CHAR 32 DEMAND-GUID

RESOURCE_KEY CHAR32 CHAR 32 RESOURCE-GUID

BEG_TSTMP TIMESTAMP DEC 15 UTC TIME STAMP

END_TSTMP TIMESTAMP DEC 15 UTC TIME STAMP

DURATION INT4 INT 4 NATURAL NUMBER

UTIL /MRSS/T_UTILIZATION DEC 3 RESOURCE UTILIZATION

APPL_STATUS J_ISTAT CHAR 5 SYSTEM STATUS

DESCRIPTION TEXT120 CHAR120 TEXT

IS_CAPACITIVE /MRSS/T_DEM_IS_CAPACTIVE CHAR 1 CAPACITIVE PLANNING

ALLOWED FOR DEMAND?

ASS_PROB /MRSS/T_ASS_PROB NUMC 3 ASSIGNMENTPROBABILITY

14.3.2 Business Content: Data SourcesData Source /MRSS/ASSIGNMENT_ATTR has been created for extraction of assignments andassignment related data. It is available as delivered version.

Selection field is:

ASSGN_DATE (= begin of an assignment)

No delta extraction is in scope.

14.3.3 Program UnitsExtractor function module: /MRSS/CBW_BW_GET_ASSIGNMENT located in function group:/MRSS/CBW_BW_EXTRACTORS.


October 2010 142

14.3.4 General Program StructureThe extractor program created for data source maintenance has SAP standard outlook.

Data transfer is processed by customized number of calls, which are performed by S-API dedicatedfor BW. In the first step of the extractor API, selection ranges are created and selection ofassignments and related data takes place. For each extractor’s call, a separate data package isfetched and processed. At the end of the processing, data is mapped into complex structure andstored in output table.

14.4 BW – Data Extraction: Alerts

14.4.1 Alerts from scheduling

Data Dictionary Objects

This is an existing database table for alerts from scheduling:

Extract structure: /MRSS/D_ALERTS:


ALERT_GUID GUID_32 CHAR 32 GUID in 'CHAR' Format inUpper Case

.INCLUDE /MRSS/T_ALERT_EXT STRU Work Area: Alert Data(External Structure)

MSGID MSGID CHAR 20 Message identification

MSGNR MSGNR CHAR 3 Message number

MSGTYPE MSGTY CHAR 1 Message Type

VALID_FROM TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

VALID_TO TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

MSGVAR1 SYMSGV CHAR 50 Messages, messagevariables

MSGVAR1_IS_TSTMP

XFELD CHAR 1 Checkbox

…

.INCLUDE /MRSS/T_ALERT_INT STRU Work Area: Alert InternalData


July 2010 143

CREATED_AT TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

CREATED_BY SYUNAME CHAR 12 SAP System, User LogonName

CHANGED_AT TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

CHANGED_BY SYUNAME CHAR 12 SAP System, User LogonName

CONFIRMD /MRSS/T_ALERT_CONFRIMD

CHAR 1 Confirmation

ALERT_TYPE /MRSS/T_ALERTTYPE NUMC 3 Alert Type

DEL_FLG /MRSS/T_BOOLEAN CHAR 1 Boolean Variable

Business Content: Data Sources

Data Source /MRSS/ALERTS_ATTR has been created for extraction of alerts from scheduling.

Selection fields are:

ALERT_TYPE (alert type)

CONFIRMD (alert confirmed?)

DEL_FLG (alert deleted?)


Program Units

Extractor function module: /MRSS/CBW_ALERTS_GET_DATA located in function group:/MRSS/CBW_ALERTS_MAP.

14.4.2 Alert components of scheduling process


This is an existing database table for alert components:

Extract structure: /MRSS/D_COMPO:


ALERT_GUID GUID_32 CHAR32

GUID in 'CHAR' Format inUpper Case

GUID GUID_32 CHAR32



October 2010 144

OBJ_TYPE /MRSS/T_SGE_OBJECT_TYPE

CHAR 1 Object Type in PlanningBoard


Data Source /MRSS/ALERT_COMPO_ATTR has been created for extraction of alert componentsfrom scheduling process.

Selection fields: None.


Program Units

Extractor function module: /MRSS/CBW_ALERT_COMPO_GET_DATA located in function group:/MRSS/CBW_ALERTS_MAP.

14.4.3 Alerts: Confirmed Messages per User while SchedulingProcess


This is an existing database table for alert components:

Extract structure: /MRSS/D_USER_CON:


ALERT_GUID GUID_32 CHAR32


USER_NAME SYUNAME CHAR12

SAP System, User LogonName


Data Source /MRSS/USER_CON_ATTR has been created for extraction of the confirmedmessages per user while scheduling process.

Selection fields: None.


Program Units

Extractor function module: /MRSS/CBW_USER_CON_GET_DATA located in function group:/MRSS/CBW_ALERTS_MAP.


July 2010 145

14.5 BW – Data Extraction: Links for the Scheduling Engine


This is an existing database table for links for the Scheduling Engine:

Extract structure: /MRSS/D_LINK:


.INCLUDE /MRSS/T_SGE_KEY STRU Key Fields

CLIENT MANDT CLNT 3 Client

GUID CHAR32 CHAR 32 Character field, length 32

.INCLUDE /MRSS/T_LINK_EXT STRU External Fields in Link Table

ID1 CHAR32 CHAR 32 Character field, length 32

ID2 CHAR32 CHAR 32 Character field, length 32

BEG_TSTMP TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

END_TSTMP TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

REL_TYPE /MRSS/T_REL_TYPE CHAR 2 Relationship Type

.INCLUDE /MRSS/T_SGE_ADM STRU Administrative Data forEntry


CREATED_BY UNAME CHAR 12 User Name


CHANGED_BY UNAME CHAR 12 User Name

DEL_FLG CRMT_BOOLEAN CHAR 1 Logical Variable


October 2010 146


Data Source /MRSS/LINKS_ATTR has been created for extraction from links for the SchedulingEngine.

Selection fields:

DEL_FLG (Link deleted?)

REL_TYPE (Relationship Type)


Program Units

Extractor function module: /MRSS/CBW_LINKS_GET_DATA located in function group:/MRSS/CBW_LINKS_MAP.

14.6 BW – Data Extraction: Teams in the Scheduling Engine


This is an existing database table for links for the Scheduling Engine:

Extract structure: /MRSS/D_TEAM:


.INCLUDE /MRSS/T_SGE_KEY STRU Key Fields

CLIENT MANDT CLNT 3 Client

GUID CHAR32 CHAR 32 Character field, length 32

.INCLUDE /MRSS/T_TEAM_DATA STRU Team Data

BEG_TSTMP TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

END_TSTMP TIMESTAMP DEC 15 UTC Time Stamp in ShortForm(YYYYMMDDhhmmss)

SERV_GROUP PD_OBJID_R NUMC 8 Object ID

DESCRIPTION TEXT40 CHAR 40 Text, 40 Characters Long

CAP_PLAN /MRSS/T_CAP_PLAN CHAR 1 Capacity Planning

.INCLUDE /MRSS/T_SGE_ADM STRU Administrative Data forEntry



July 2010 147

CREATED_BY UNAME CHAR 12 User Name


CHANGED_BY UNAME CHAR 12 User Name

DEL_FLG CRMT_BOOLEAN CHAR 1 Logical Variable


Data Source /MRSS/TEAMS_ATTR has been created for extraction of Teams in the SchedulingEngine

Selection fields:

CAP_PLAN (Capacity Planning)

DEL_FLG (Link deleted?)

SERV_GROUP (Object ID)


Program Units

Extractor function module: /MRSS/CBW_TEAMS_GET_DATA located in function group:/MRSS/CBW_TEAMS_MAP.

Appendix

October 2010 148

15 Appendix15.1 TransactionsThe following table lists the most important transactions needed for Customizing and master datasetup.

Transaction Description

/MRSS/PLBOORG Enter the SAP Multiresource Scheduling planningboard using organizational units for selection

/MRSS/PLBOORGM Enter the SAP Multiresource Scheduling planningboard using multiple organizational units for selection

/MRSS/PLBOTIME Enter the SAP Multiresource Scheduling planningboard using the current user as assigned planner.

/MRSS/PLBOSRV Enter the SAP Multiresource Scheduling planningboard using a specified order

/MRSS/PLBOMGR Manager’s Planning Board

/MRSS/PLBOORGSRV Planning Board (General)

/MRSS/UTILREP Enter the utilization report for organizational units

/MRSS/BACKLOG Unplanned Demands

/MRSS/IMG Customizing for the SAP Multiresource Scheduling

/MRSS/RM_IMG Customizing for Resource Management

SPRO Standard customizing transaction for R/3

SIMGH Maintenance for IMG structures; can be used if the/MRSS/IMG transaction is not available

BP Maintain business partner

PPOCE or PPOME Create or maintain organizational units and positions

PA40 or PA30 Create or maintain personal resources (based onHR)

CR01 or CR02 Create or maintain work centers (assignorganizational units to work centers)

IW31 or IW32 Create or change orders

PPPM Maintain business partner profiles (e.g.qualifications)

SCOT SAPconnect Administration; maintain thefunctionality to send short messages

/MRSS/DEMAND_SEARCH Global demand search

/MRSS/EMPL_SEARCH Free employee search

/MRSS/PPPA Manager’s Approval Screen

/MRSS/PPPM Employee Profile Maintenance

/MRSS/PPPT SAP Multiresource Scheduling Profile Maintenance

Appendix

July 2010 149

/MRSS/RAP_CP Worklist: Contact Person

/MRSS/RAP_CP_GEN Worklist: Contact Person (General)

/MRSS/RAP_NPAU Field control by authorization

/MRSS/RAP_NPPR Field control by progress

/MRSS/RCCF_CUST RCCF: Process Destinations

/MRSS/RCCF_LOG RCCF: Log Display

/MRSS/RCCF_PARAM RCCF: Advanced Settings

/MRSS/RCCF_SESSION RCCF: Display Active Sessions

/MRSS/RCCF_VERSION RCCF: Version Display

/MRSS/REQM Requirement Profile Maintenance

/MRSS/SQM_CAT Qualification Catalogs

/MRSS/SQM_CAT_FILTER Filter Information

/MRSS/SQM_CAT_NUM Number ranges for Catalogs

/MRSS/SQM_MAT Qualification Matrixes

/MRSS/SQM_MAT_NUM Number ranges for matrixes

/MRSS/SQM_PARAM System parameters for qualifications

/MRSS/SQM_QUAL_NUM Number ranges for qualifications

/MRSS/SQPP_NUM Profile Key Number Range

/MRSS/SQW_OOCUPAR Set up workflow

/MRSS/SQW_WF_LIST All Workflows for Employee Profiles

/MRSS/WFM_ADMIN Maintain WFM Core Resources

/MRSS/WFM_ADMIN_HR WFM Administration HR

/MRSS/WFM_IMG_R3 WFM Core Customizing

/MRSS/WFM_STAT Transfer assignment status

15.2 ReportsThe following table lists some reports needed for Customizing and master data setup.

Report Description

/MRSS/HCM_RPTWFMIF Transfers the HR data (availability times,qualifications and the resources itself)into the SAP Multiresource SchedulingBasis

/MRSS/WFM_MASTERDATA_ADMIN Maintain Business Partner resources andperiodic time allocations

/MRSS/WFM_MASTERDATA_ADMIN_HR Maintain HR resources and periodic timeallocations

/MRSS/TLS_ASSIGNMENTS_DEL Delete assignments

/MRSS/TLS_RESOURCES_DEL Delete resources

Appendix

October 2010 150

Report Description

/MRSS/TLS_TIMESPECS_DEL Delete time allocations

15.3 APIsThe following API function modules can be used for creating, changing, deleting or reading of SAPMultiresource Scheduling data.

Function module Description

/MRSS/SGE_API_ASSIGNMENT_CRE API to create assignments

/MRSS/SGE_API_ASSIGNMENT_DEL API to delete assignments

/MRSS/SGE_API_ASSIGNMENT_GET API to read assignments

/MRSS/SGE_API_ASSIGNMENT_UPD API to update assignments

/MRSS/SGE_API_ASSMT_MOB_ST_ADDSet Assignment Status from MobileDevice

/MRSS/SGE_API_COMMIT Function for Commiting API Changes

/MRSS/SGE_API_DEMANDS_GET API to get the demand details

/MRSS/SGE_API_GUID_EQUNRConversion of Equipment number from/toGUID

/MRSS/SGE_API_GUID_PERNRConversion of Personnel number from/toGUID

/MRSS/SGE_API_ROLLBACK Function for Commiting API Changes

/MRSS/SGE_API_SUBS_CRE API for creation of irregular work time

/MRSS/SGE_API_SUBS_DEL API for deletion of irregular work time

/MRSS/SGE_API_SUBS_GETAPI to get irregular work times forresources

/MRSS/SGE_API_TIMESPEC_CRE API to create time allocations

/MRSS/SGE_API_TIMESPEC_DEL API to delete the time allocations

/MRSS/SGE_API_TIMESPEC_GETAPI to get the time allocations for theresource

/MRSS/SGE_API_TIMESPEC_UPD API to update tIme allocations

/MRSS/SGE_API_TOOL_LINKS_CRE API to create tool links

/MRSS/SGE_API_TOOL_LINKS_DEL API to delete the tool links

/MRSS/SGE_API_TOOL_LINKS_GET API to read tool links

/MRSS/SQM_API_CAT_CHANGE Change Qualification Catalog

/MRSS/SQM_API_CAT_CREATE Create Qualification Catalog

/MRSS/SQM_API_CAT_DELETE Delete Qualification Catalog

/MRSS/SQM_API_CAT_GET Read Qualification Catalog

/MRSS/SQM_API_MAT_CHANGE Change Qualification Matrix

Appendix

July 2010 151

/MRSS/SQM_API_MAT_CREATE Create Qualification Matrix

/MRSS/SQM_API_MAT_DELETE Delete Qualification Matrix

/MRSS/SQM_API_MAT_GET Read Qualification Matrix

/MRSS/SQP_EMP_PROF_CRE_API To save employee profile data from legacy

/MRSS/SQP_EMP_PROF_DEL_APITo delete employee profile data receivedfrom legacy

/MRSS/SQP_EMP_PROF_GET_API To get employee profile data

/MRSS/SQP_EMP_PROF_UPD_APITo update employee profile data fromlegacy

/MRSS/SQP_EMP_START_WF_API To start the approval workflow of a profile

/MRSS/SQP_REQ_PROF_CRE_APITo save requirement profile data fromlegacy

/MRSS/SQP_REQ_PROF_DEL_APITo delete requirement profile datareceived from legacy

/MRSS/SQP_REQ_PROF_GET_API To get requirement profile data

/MRSS/SQP_REQ_PROF_UPD_APITo update requirement profile data fromlegacy

15.4 Useful TablesThe following table lists important tables. For a more detailed overview refer to section 0.

Table Description

/MRSS/D_DEM_H This table contains the demand header information.If you want to check whether your orders arecorrectly transferred to the SAP MultiresourceScheduling system, you can have a look in this tableto verify it was successfully transferred.

/MRSS/D_BAS_RES This table contains the resource information in SAPMultiresource Scheduling Basis. Here you can verifywhether your HR persons or SAP Business Partnersare correctly transferred to the SAP MultiresourceScheduling system.

/MRSS/D_CAG_CG_G This table contains the resource basic availabilityinformation without on-call times.

/MRSS/D_CAG_CG_H This table contains the resource basic availabilityinformation.

/MRSS/D_CLOCK This table contains the clocking information that isused to display the actual working time in the SAPMultiresource Scheduling planning board.

/MRSS/D_GEO_GPS This table contains the actual GPS coordinates of aresource.

/MRSS/D_GEO_ZIP This table contains the zip codes needed for GEOreferencing.

Appendix

October 2010 152

15.5 Abstract Partner RolesThe following table lists the abstract partner roles that are used in connection with the PM/CS andPS integration. Abstract partner roles are delivered in Customizing table /MRSS/VC_ABROLE.

Status Status Description Meaning

CUST_R3NW Customer in PS Network Represents the customer inalert check. The check foridentical assignments is donebased on these partners.

CUST_R3OR Customer in Service Order See above

RESC_FOUND Resource Found Names the found resources tobe displayed in the worklist. Thepartners assigned to this roleare not considered elsewhere inSAP Multiresource Scheduling.

TECH_1ST First Technician Preferred technician. Names aresource that will be preferred incase of automatic resourceplanning (includingoptimization). However, it is notmandatory that this resource isassigned.

15.6 Abstract StatusThe following table lists the abstract status that are used in connection with the PM/CS and PSintegration. Abstract status are delivered in Customizing table /MRSS/C_ABSTAT.

Statuses for PM/CS integration:


ARRAN_DATE Date agreement required Can be set in the order and istransferred to SAPMultiresource Scheduling

DESIR_DATE Required date Can be set in the order and istransferred to SAPMultiresource Scheduling

FIXED_DATE Fixed date Can be set in the order and istransferred to SAPMultiresource Scheduling

IRDA_RELEV IRDA Relevant Is set from BAdI

HAS_CAPA Capacitive Assignmentsavailable

Is set on operation level if atleast one capacitive assignmentexists

OR_HAS_ASG Order contains at least oneassignment

Back integration to the order

Appendix

July 2010 153


PLAN_FULL Demands fully planned Demand is fully planned

PLAN_OVER Demand overplanned Demand is overplanned

PLAN_UNDR Demand underplanned Demand is underplanned

Statuses for PS integration:

The following abstract statuses are currently visible in the status schema, but they cannot bechanged by a modification:


NW_BOOKED Network booked Network is booked

NW_RESERVD Network reserved Network is reserved

IRDA_RELEV IRDA relevant IRDA relevant

REM_EFFORT Remaining demand has beenprocessed

Remaining demand has beenprocessed

PLAN_START Start of planning Demand is visible in SAPMultiresource Scheduling

PLAN_FULL Demands fully planned Demands is fully planned

PLAN_UNDR Demand underplanned Demand is underplanned

WITH_MAN_ACCP With manual acceptance With manual confirmation ofresources

HAS_NO_ASG Has no assignment See note 1090641 for moredetails

NoteThe threshold value for the differentiation partly planned vs. completely planned canbe maintained in the Customizing.

The following abstract statuses are maintained internally and are currently not visible in the statusschema:


OFFER This is an offer demand Demand is an offer demand

OFFER_ASSG This is an offer assignment Assignment is an offer

OFFREJ Request for offer has beenrejected

Offer submission was rejected

Appendix

October 2010 154

15.7 Overview of Database TablesThis chapter lists Customizing and data tables in the context of SAP Multiresource Scheduling.

15.7.1 Customizing TablesName Description

/MRSS/C_1TO1_REL 1:1 Releation Demand Assignment

/MRSS/C_ABROLE Abstract Partner Role

/MRSS/C_ABROLET Abstract Partner Role: Texts

/MRSS/C_ABSTAT Abstract Status

/MRSS/C_ABSTAT_T Abstract Status: Texts

/MRSS/C_ALERTS Assignment of Alert Types and Messages

/MRSS/C_AL_PROF Scheduling Alert Profiles

/MRSS/C_AL_PROFT Text Table of Alert Profiles

/MRSS/C_AL_TYPE Alert types

/MRSS/C_AL_TYPET Texts for Alert Types

/MRSS/C_AL_TYP_N Non-Relevant Alert Types

/MRSS/C_AUT_ASGN Control table for automatic assignment creation

/MRSS/C_AVAIL_CR Control creation of concretization attributes

/MRSS/C_BACK_INT Back integraton Active ?

/MRSS/C_BAS_TA Time allocation Types

/MRSS/C_BAS_TAT Texts for Time allocation types

/MRSS/C_BUT_NAVI Navigation buttons to launch transactions

/MRSS/C_BUT_NAVT Maintain texts for pushbuttons

/MRSS/C_BUT_PARA Parameters for navigation pushbuttons

/MRSS/C_CAG_CUST Include Capacitive Assignments During Slot-BasedAvail. Det.

/MRSS/C_CAP_PLAN SAP Multiresource Scheduling: capacitive planning

/MRSS/C_CHECK_AC Scheduling Engine: Active Checks

/MRSS/C_CHECK_CL Definition of Check Classes

/MRSS/C_CHECK_OR SAP Multiresource Scheduling Checks While SavingOrder

/MRSS/C_CHECK_P Profile for Checks in the Planning Board

/MRSS/C_CHECK_PO Parameters for Checking the Percentage ofCompletion

/MRSS/C_CHECK_PT Text Table for Check Profiles

/MRSS/C_CHECK_T Parameters for Checking the Time Differences

/MRSS/C_CUSTPARM RCCF: Experteneinstellungen

Appendix

July 2010 155

Name Description

/MRSS/C_DBM_STAT This Table maps DBM order status to graphicalelement type

/MRSS/C_DEF_DUR SAP Multiresource Scheduling: work of operation(default value for integration)

/MRSS/C_DEM_AS Assignment of the Demand Item Categories toSubobjects

/MRSS/C_DEM_SO Subobjects of a Demand Item

/MRSS/C_DEM_TY Demand Types

/MRSS/C_DEM_TYI Demand Item Categories

/MRSS/C_DEM_TYIT Texts for Demand Item Types

/MRSS/C_DEM_TYT Texts for Demand Types

/MRSS/C_DPR_ROLE Customizing: SAP Multiresource Scheduling relevantsetting for the project role type

/MRSS/C_DSG_CLR Hold the color details of the properties of the graph

/MRSS/C_DSG_EXCE Defining exceptions for each team

/MRSS/C_DSG_TBUF Table to store the buffer properties of a team

/MRSS/C_DSG_TCOL Table to store the team colour properties

/MRSS/C_DSG_TEAM Table to hold the Organizal unit ID for DBMcustomizing

/MRSS/C_DSG_TWAR Table specifying the warning factor of the teams

/MRSS/C_DWS_VAR Display Daily Work Schedule Variant in substitutiondetails

/MRSS/C_EMP_PRNT Smartform customizing for Employee Profiles

/MRSS/C_ENGINES Externe Engines im RCCF

/MRSS/C_ENG_DEST RCCF: Destinationen für Engines

/MRSS/C_FCHG_FLD Checks During Field Changes

/MRSS/C_FCHG_GRP Groupings for Field Checks

/MRSS/C_FCHG_GRT Text Table: Groupings for Field Checks

/MRSS/C_FCHG_OBJ Objects for Checking Field Changes

/MRSS/C_GEOLOC Settings for Connection to Geographical Information

/MRSS/C_GEO_CODE Define settings for GEO coding

/MRSS/C_GEO_CODT Description of Geo coding profile

/MRSS/C_GEO_SYS Define settings for Geo Information System

/MRSS/C_GEO_SYST Description of Geo profile

/MRSS/C_HCMPTLRP Mapping HR Time Data to WFM Time Allocations

/MRSS/C_HCMTZONE Assignment: Personnel (Sub)Area - SAPMultiresource Scheduling Time Zone

Appendix

October 2010 156

Name Description

/MRSS/C_HCM_INFT Mapping HR Time Data to WFM Time Allocations

/MRSS/C_HCM_MRSD RFC Destination of SAP Multiresource Scheduling

/MRSS/C_HRES_CTY HR communication methods to be displayed inadditional data

/MRSS/C_HRES_DAT Communication Data

/MRSS/C_MAPASTXT Status texts for assignments

/MRSS/C_MAPNPOS Code Groups for Notification Items

/MRSS/C_MAPROLE Mapping of R/3 partner roles

/MRSS/C_MAPSTAT Mapping of R/3 status

/MRSS/C_MAPTASK Mapping of R/3 task

/MRSS/C_MAPWC Mapping of R/3 work center types

/MRSS/C_MATCHING Customizing table for general qualification matching

/MRSS/C_MOB_ABS Abstract Assignment Statuses: Mobile Integration

/MRSS/C_MOB_ABST Texts for Abstract Status (Integration of MobileDevices)

/MRSS/C_MOB_STAT Assignment of Abstract Status to Plants (MobileIntegration)

/MRSS/C_M_WEIGHT Rating factors for matching criteria

/MRSS/C_ONCALL Describes the On Call Types

/MRSS/C_ONCALL_D Describes the On Call Type Determination

/MRSS/C_ONCALL_T Describes the On Call Type

/MRSS/C_ONCL_TSP On call types for particular time allocations

/MRSS/C_OPT_DBG Optimization Server: Debugging/Log Indicator

/MRSS/C_OPT_RES Customizing table to define optimizer relevantparameters

/MRSS/C_OPT_SCOM Optimization Server: Communication Pckgs - TypeDefinition

/MRSS/C_OPT_SYS Customizing table to define optimizer relevantparameters

/MRSS/C_OPT_SYST Text Table for Optimizer System Settings

/MRSS/C_PARAM RCCF: Generelle Einstellungen

/MRSS/C_PLBOMGR Settings for Planning Board Manager

/MRSS/C_PREV_DEL Prevent Deletion of Operations

/MRSS/C_RAP_ASG Degree of Coverage of Demands

/MRSS/C_RAP_NPAU Field control in connection with authorizations

/MRSS/C_RAP_NPPR Field control in connection with process progress

/MRSS/C_RAP_PAR Parameters for PS Integration

Appendix

July 2010 157

Name Description

/MRSS/C_RAP_PV Settings for Process Variants

/MRSS/C_RAP_TREE Layouts for Resource Overview

/MRSS/C_RCT_NPRV Determination of SAP Multiresource Schedulingrelevance

/MRSS/C_REQ_PRNT Smartform customizing for Requirement Profiles

/MRSS/C_REQ_WUSD Whereused customizing for notification purposes

/MRSS/C_RESSTAT Possible Resource Status

/MRSS/C_RESSTATT Short and Longtexts for Resource Status

/MRSS/C_RES_PLAN Base Resources from Explicit Planning Node

/MRSS/C_RES_TA Assignment of Resource Types and Time AllocationTypes

/MRSS/C_RES_TYP SAP Multiresource Scheduling Basis ResourceTypes

/MRSS/C_RES_TYPT SAP Multiresource Scheduling Basis Resource typetexts

/MRSS/C_RMI_PS Project System data required for creating Request

/MRSS/C_RSG_CTRL SAP Multiresource Scheduling: resource planningrelevance of operations

/MRSS/C_RSG_DEAS Control: one own demand for each assignment

/MRSS/C_RSG_OITG Control of PM/CS Order Integration

/MRSS/C_RSG_PAR Parameters for Multiresource Planning

/MRSS/C_RSG_SA Extended assignments

/MRSS/C_RSG_STAT SAP Multiresource Scheduling Customizing forStatus Object Type (Release 46C)

/MRSS/C_RSG_STEF Control Keys for Production Resources/Tools inResource Plng

/MRSS/C_RSG_STEU Multiresource Planning Control Keys

/MRSS/C_RSG_ST_V Control-Key Default Values for Production Resources& Tools

/MRSS/C_SGE_BPR Business process Customizing

/MRSS/C_SGE_CD Collision definition

/MRSS/C_SGE_CD_T Collision definition

/MRSS/C_SGE_CH Activate Change Documents

/MRSS/C_SGE_EXBL Check classes for external business logic

/MRSS/C_SGE_HCMD RFC Destination of HCM

/MRSS/C_SGE_HCMI Function Modules for Transferring SAP MultiresourceScheduling to HR

/MRSS/C_SGE_OS Collision profile

Appendix

October 2010 158

Name Description

/MRSS/C_SGE_OS_T Collision profile texts

/MRSS/C_SGE_PR Scheduling Engine Profile

/MRSS/C_SGE_PROC Business process Customizing

/MRSS/C_SGE_PR_D Determination of Scheduling Engine Profile

/MRSS/C_SGE_PR_T Text for Scheduling Engine Profile

/MRSS/C_SGE_SCA Scenario Attributes for Multiresource Planning

/MRSS/C_SGE_SCAC Customer-scenario attribute of SAP MultiresourceScheduling

/MRSS/C_SGE_SC_A Active Scenario for Multiresource Planning

/MRSS/C_SGE_SIND Demand status individualization for assignments

/MRSS/C_SGE_TECH Technical Settings for Resource Selection

/MRSS/C_SGU_CON Define layout: container item

/MRSS/C_SGU_DEF Default Settings for the Planning Board

/MRSS/C_SGU_ENH Customer menu entries

/MRSS/C_SGU_ENHT Text table for customer menu entries

/MRSS/C_SGU_GRPH Graphical element for time specifications

/MRSS/C_SGU_LTS Graphical element for time specifications

/MRSS/C_SGU_PRO UI Planning Profile

/MRSS/C_SGU_PROT UI Planning Profile

/MRSS/C_SGU_SGL Used Language for Status Checks

/MRSS/C_SGU_SGR Status groups

15.7.2 Data TablesName Description

/MRSS/D_ADDRESS Stores Primary/Secondary address

/MRSS/D_ALERTS Alerts

/MRSS/D_ASGN_INF Additional Info for Assignment

/MRSS/D_ASG_INFX Add. attributes of partial concretization of strechedassign

/MRSS/D_BAS_REQQ Required Qualifications for Demands

/MRSS/D_BAS_RES Resource Master Data

/MRSS/D_CAG_CG_A Type A Capacity Graphs: W/ Cap. Assignments &Reservations

/MRSS/D_CAG_CG_B Type B Capacity Graphs: W/o Cap. Assgmnts, w/Reservations

/MRSS/D_CAG_CG_C Type C Capacity Graphs: with Cap. Assgmnts, w/oReservations

Appendix

July 2010 159

Name Description

/MRSS/D_CAG_CG_D Type D Capacity Graphs: w/o Cap. Assgmnts, w/Reservations

/MRSS/D_CAG_CG_G Type G Capacity Graphs: Basic Availability w/o On-Call Times

/MRSS/D_CHG_HISM Change Documents (Text Attributes)

/MRSS/D_CHG_HIST Change Documents (Field Changes)

/MRSS/D_CH_ORD Time of Last Change for Assignments for an Order

/MRSS/D_CH_RES Time of Last Change for Resources

/MRSS/D_CLOCK Time Recording Information for the Scheduling Engine

/MRSS/D_COMPO Alert Components

/MRSS/D_DEM_ADM Administrative Demand Item Data

/MRSS/D_DEM_DATA Demand Master Data

/MRSS/D_DEM_H Complex Demand

/MRSS/D_DEM_INFO Informative Fields for Demand Items

/MRSS/D_DEM_MAP Mapping External Keys

/MRSS/D_DEM_MATE Data for Spare Part Items

/MRSS/D_DEM_PLR Data required for planning-relevant items

/MRSS/D_DEM_PLRS Data for Service Items

/MRSS/D_DEM_PS Rejected and/or deleted requirements

/MRSS/D_DEM_REL Relationships Between Demand Items

/MRSS/D_DEM_SPLI Split Information of Demands

/MRSS/D_DEM_STAT Status of demand items

/MRSS/D_DEM_TOOL Data for Tool Items

/MRSS/D_DESTSLOT Übersicht über belegte Zieladressen im RCCF

/MRSS/D_DPR_MAP Mapping of external keys of project and role guid incpro

/MRSS/D_ENG_LOG Protokolltabelle für Engineläufe

/MRSS/D_GEO_GPS Data table to hold actual GPS coordinates of aresource

/MRSS/D_LINK Link Table for the Scheduling Engine

/MRSS/D_ORD_H_UI Header Table

/MRSS/D_PARTNER Partner for demands

/MRSS/D_REPL_CAR Vehicle Data

/MRSS/D_RES_H Resource Data (Status)

/MRSS/D_RES_QUAL Resource Qualifications

/MRSS/D_RES_TA Time allocations for resources

Appendix

October 2010 160

Name Description

/MRSS/D_RSBUFADM Resource Buffering Admin Data

/MRSS/D_RSBUFDAT Resource Buffering Data

/MRSS/D_SGE_RI Resources - Integration of Transfer Status, TimeStamp

/MRSS/D_SHIFTS Standard Shift Schedule for Organizational Unit

/MRSS/D_SQM_KH Qualification Catalog: Header Data

/MRSS/D_SQM_KHT Qualification Catalog: Header Data Texts

/MRSS/D_SQM_KP Qualification Catalog: Items

/MRSS/D_SQM_KPF Qualification Catalog: Person-Specific Filter

/MRSS/D_SQM_KPO Qualification Catalog: Organization-Specific Filter

/MRSS/D_SQM_KPT Qualification Catalog: Item Texts

/MRSS/D_SQM_MEG Association of Matrices to Employee Groups

/MRSS/D_SQM_MH Qualification Matrix

/MRSS/D_SQM_MHT Qualification matrix: texts

/MRSS/D_SQM_MPL Association of Matrices to Plants

/MRSS/D_SQP_EAPP Employee Profile : Approval details

/MRSS/D_SQP_EHDR Employee Profile : Header Attributes

/MRSS/D_SQP_EHIS Employee Profile : History of changes

/MRSS/D_SQP_ESTR Employee Profile - Structured Qualifications

/MRSS/D_SQP_EUST Employee Profile : Unstructured Qualifications

/MRSS/D_SQP_HDTX Profile/structured qualifications: text table

/MRSS/D_SQP_PROF Profile Master Table : Contains all Profile Guids

/MRSS/D_SQP_RADT Requirements Profile: Information of Additionalattributes

/MRSS/D_SQP_RHDR Requirements Profile: Header Attributes

/MRSS/D_SQP_ROCS Requirement Profie on call types with search types

/MRSS/D_SQP_ROCS_DATA On Call type and search type Key

/MRSS/D_SQP_ROCS_KEY On Call type and search type Key

/MRSS/D_SQP_ROCT Requirement Profie on call types

/MRSS/D_SQP_ROCT_KEY On Call type key

/MRSS/D_SQP_RSTR Requirements Profile : Structured Qualifications

/MRSS/D_SQP_RUSR Requirements Profile: Unstructured Qualifications

/MRSS/D_SQP_RUST Requirements Profile: Unstruct Qualif. - Languagedepend.

/MRSS/D_TA_INT Complex time allocations intervals

/MRSS/D_TEAM Team in Scheduling Engine

Appendix

July 2010 161

Name Description

/MRSS/D_TRAVEL Travel Times

/MRSS/D_TS_INFO Time Spec Additional Info

/MRSS/D_USER_CON Confirmed Messages for Each User

/MRSS/D_WORKTIME Pers. Resource: HCM - Base Normal and PlanningWorking Time

15.8 External InterfacesThe following table represents important classes and function modules that are used for externalinterfaces of SAP Multiresource Scheduling.

Name Description

Function module/MRSS/SGD_DEMANDS_MAINTAIN

Maintain demands

Class/MRSS/CL_SGE_APPLICATION_MNT

Assignments and time specificationsHint: never call this class inside the SAPMultiresource Scheduling application.otherwise the worklist will have initializationproblems and display wrong results

Function module/MRSS/SGE_CLOCK_MAINTAIN

Maintain clocking data

Function module/MRSS/SGA_ALERTS_CREATE

Create alerts

15.9 Creating Object GUIDsThis appendix offers further information about the creation of Object GUIDs, which is relevant forthe programming of user exits or interfaces.

Requirements

The GUIDs (Globally Unique Identifiers) of requirements are unique identifiers that are determinedaccording to the GUID procedure. The class /MRSS/CL_RSG_DEM_EXT_KEY enables you toconvert the external keys into the SAP R/3 document number and vice versa.

Time Allocation

The GUIDs of time allocation are unique identifiers that are determined according to the GUIDprocedure.

Resources

The GUIDs of resources are unique pseudo GUIDs in the system that are created according to thefollowing scheme:

[Personnel number][22 digits with “0“]

Assignment

[2 digits status object][20 digits internal number][10 digits “0“]

The status object in Customizing can be adjusted:

Appendix

October 2010 162

Basic Settings Assign Object Type for Number Range Determination for Assignments

NoteIf you have implemented SAP Note 1456178 (2010), you do not have to maintainthe Customizing activity Assign Object Type for Number Range Determination.