Mrs700 sp04 config_guide

6,329 views

Published on

MRS Config Guide

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
6,329
On SlideShare
0
From Embeds
0
Number of Embeds
41
Actions
Shares
0
Downloads
685
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Mrs700 sp04 config_guide

  1. 1. Configuration GuideConfiguration Guidefor SAPMultiresourceSchedulingRelease 7.0 SP04PublicDocument Version 4.0 – 10/01/2010
  2. 2. SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com© Copyright 2009 SAP AG. All rights reserved. Java is a registered trademark of Sun Microsystems, IncNo part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG. JavaScript is a registered trademark of Sun Microsystems, Inc., usedThe information contained herein may be changed without prior under license for technology invented and implemented by Netscape.notice. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,Some software products marketed by SAP AG and its distributors ByDesign, SAP Business ByDesign, and other SAP products andcontain proprietary software components of other software vendors. services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and inMicrosoft, Windows, Excel, Outlook, and PowerPoint are registered several other countries all over the world. All other product andtrademarks of Microsoft Corporation. service names mentioned are the trademarks of their respective companies. Data contained in this document serves informationalIBM, DB2, DB2 Universal Database, System i, System i5, System p, purposes only. National product specifications may vary.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, These materials are subject to change without notice. These materialsOS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, are provided by SAP AG and its affiliated companies ("SAP Group")Power Architecture, POWER6+, POWER6, POWER5+, POWER5, for informational purposes only, without representation or warranty ofPOWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System any kind, and SAP Group shall not be liable for errors or omissionsStorage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, with respect to the materials. The only warranties for SAP GroupOS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, products and services are those that are set forth in the expressWebSphere, Netfinity, Tivoli and Informix are trademarks or warranty statements accompanying such products and services, if any.registered trademarks of IBM Corporation. Nothing herein should be construed as constituting an additional warranty.Linux is the registered trademark of Linus Torvalds in the U.S. andother countries. DisclaimerAdobe, the Adobe logo, Acrobat, PostScript, and Reader are either Some components of this product are based on Java™. Any codetrademarks or registered trademarks of Adobe Systems Incorporated in change in these components may cause unpredictable and severethe United States and/or other countries. malfunctions and is therefore expressively prohibited, as is any decompilation of these components.Oracle is a registered trademark of Oracle Corporation. Any Java™ Source Code delivered with this product is only to be usedUNIX, X/Open, OSF/1, and Motif are registered trademarks of the by SAP’s Support Services and may not be modified or altered in anyOpen Group. way.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks of Documentation in the SAP Service MarketplaceCitrix Systems, Inc. You can find this documentation at the following Internet address: service.sap.com/instguidesHTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.
  3. 3. Typographic Conventions IconsType Style RepresentsExample text Words or characters quoted from Icon Meaning the screen. These include field Caution names, screen titles, pushbuttons labels, menu Example names, menu paths, and menu options. Note Cross-references to other Recommendation documentation. SyntaxExample text Emphasized words or phrases in body text, graphic titles, and table titles.EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.
  4. 4. Configuration Guide for SAP Multiresource SchedulingContents1 Introduction ..................................................................... 10 1.1 SAP Multiresource Scheduling Functional Overview ..102 Installation ....................................................................... 11 2.1 SAP Multiresource Scheduling 700 Installation ...........11 2.2 Upgrade to SAP Multiresource Scheduling 700 ...........113 Configuration and Customizing: General Configuration .................................................................. 12 3.1 Configuration of Basic Settings .....................................12 3.1.1 Basic Settings.....................................................................12 3.1.2 Work Center ........................................................................13 3.1.3 Planning Nodes and Evaluation Paths .............................14 3.1.4 HR Integration.....................................................................15 3.2 Configuration of Multiple Backend Scenario ................16 3.2.1 Define RFC destinations for logical systems...................16 3.2.2 Define active scenarios......................................................17 3.2.3 HR Data from Remote System...........................................17 3.2.4 Parameters for reprocessing of integration queue .........17 3.2.5 Automatic Activation of SAP Multiresource Scheduling Integration Queues .............................................................18 3.2.6 New alert for error queues .................................................18 3.3 Configuration of PM/CS Integration ..............................18 3.4 Configuration of PS Integration .....................................19 3.4.1 Process Integration ............................................................19 3.4.2 Field Control in Network Header and Activity..................21 3.4.3 Demand View Integration...................................................22 3.5 Configuration of Web-based Resource Management Integration ......................................................................23 3.5.1 Status Configuration ..........................................................23 3.5.2 RM Master Data Settings Configuration (/MRSS/V_RM_MDATA) ......................................................25 3.5.3 Authorization Object /MRSS/WRM ....................................25 3.5.4 Maintaining Evaluation Paths for Authorization ..............26 3.5.5 Workflow Configuration .....................................................26 3.6 Configuration of cProjects Integration ..........................28 3.6.1 Cutomizing for the integration of cProjects .....................28 3.6.2 Number Ranges ..................................................................32October 2010 4
  5. 5. Configuration Guide for SAP Multiresource Scheduling 3.6.3 Master Data .........................................................................33 Define Business Partner ..................................................................... 33 Abstract Status Customizing .............................................................. 33 Recommendation for cProjects UI settings........................................ 35 3.7 Configuration of CRM Integration ..................................36 3.7.1 Define Order Relevance for Resource Planning ..............36 3.7.2 Define date types for demand integration ........................36 3.7.3 Define location of service for demand..............................37 3.7.4 Activate resource planning in CRM service order items 37 3.8 Configuration of Persistence Layer ...............................39 3.9 Netweaver Demand Settings ..........................................41 3.9.1 Control assignment processing........................................41 3.9.2 Allow Stretched assignments ...........................................41 3.9.3 Allow capacity Planning ....................................................41 3.9.4 Allow abstract assignments ..............................................41 3.9.5 Partial concretization of stretched assignments .............42 3.9.6 Site supervisor ...................................................................424 Configuration and Customizing: Specific Configuration .................................................................. 43 4.1 Backward Integration ......................................................43 4.1.1 Forward Integration from PM/CS to SAP Multiresource Scheduling ..........................................................................44 4.1.2 Backward Integration from SAP Multiresource Scheduling to PM/CS .........................................................45 4.1.3 General Settings .................................................................46 4.2 Technical Settings for Resource Selection ..................46 4.3 Manager Planning Board ................................................46 4.4 SAP Multiresource Scheduling Qualifications .............47 4.5 Supplement Concerning the Static URL to Access Employee Profiles on Enterprise Portal ......................52 4.6 Smart Forms for Employee and Requirements Profiles ...........................................................................52 4.7 Standard Bar Chart Customizing ...................................52 4.8 Capacity View ..................................................................54 4.9 Travel Times .....................................................................55 4.9.1 Profiles ................................................................................56 Profile for Geocoding .......................................................................... 56 Profile for Distance Calculation .......................................................... 57 Profile for Map display in planning board (optional) ......................... 57 Travel Profile........................................................................................ 58 Assigning Travel Profiles to Resource Planning Nodes.................... 58 4.9.2 Travel Time Calculation and Distribution .........................59 Assign Travel Time Mode.................................................................... 59July 2010 5
  6. 6. Configuration Guide for SAP Multiresource Scheduling 4.9.3 Activating Travel Time in the Planning Board Profile .....59 4.10 Optimization .....................................................................60 4.10.1 Introduction ........................................................................60 Basic Setting in RCCF ......................................................................... 61 4.10.2 Optimization Profile............................................................62 Optimization Parameters for Resources ............................................ 62 Suitability dependent change to cost rate.......................................... 63 Factors for Demand Priority................................................................ 64 Optimization Parameters for Demands .............................................. 65 4.10.3 Logging of Optimization Runs ..........................................66 4.10.4 Optimization Scenarios......................................................67 4.10.5 Assigning Profiles to Planning Board Profile ..................675 Master Data Setup .......................................................... 69 5.1 Personal Resources: HR or not? ...................................69 5.1.1 Using HR Data ....................................................................69 Creating HR data ................................................................................. 69 Using qualifications............................................................................. 71 5.1.2 Using Business Partners ...................................................73 Create Business Partner ..................................................................... 73 Using Qualifications ............................................................................ 74 Transfer Business Partner .................................................................. 74 5.2 Organizational Structure.................................................74 5.2.1 Create Organizational Structure .......................................75 5.2.2 Linking with Work Centers ................................................75 5.3 Maintaining SAP Multiresource Scheduling Resources ......................................................................78 5.3.1 Example: Daily Interval for Time Allocation .....................79 5.3.2 Example: Weekly Interval for Time Allocation .................806 The First Demand ........................................................... 81 6.1 Order and Order Operation.............................................81 6.2 Production Resource and Tool ......................................83 6.2.1 Create Production Resource and Tool .............................83 6.2.2 Assign Production Resource and Tool to Operation ......83 6.3 Usage of Several Production Resources and Tools ....84 6.3.1 Create Material....................................................................85 6.3.2 Assign Material to Several Production Resources and Tools ....................................................................................85 6.3.3 Assign Production Resource and Tool to Operation ......86 6.4 Direct Assignment of Production Resources and Tools in the SAP Multiresource Scheduling Planning Board ..............................................................................86 6.5 Definition of HR Qualifications.......................................86 6.5.1 Create a HR Qualification Catalog ....................................86October 2010 6
  7. 7. Configuration Guide for SAP Multiresource Scheduling 6.5.2 Assign HR Qualifications to Order Operation..................87 6.5.3 Assign HR Qualifications to Employee ............................87 6.6 Requirements Assignment on Operation Level ...........887 Enhancing SAP Multiresource Scheduling ................. 90 7.1 Worklist ............................................................................90 7.1.1 Additional Customer Fields in Item Worklist ...................90 Customizing and Code Example:........................................................ 90 7.1.2 Highlighting Worklist Items ...............................................91 Example 1: ........................................................................................... 91 Example 2: ........................................................................................... 95 7.1.3 Important Standard Fields .................................................98 7.2 Business Add-Ins (BAdIs) ..............................................98 7.3 Further Important Interfaces ..........................................99 7.3.1 Table /MRSS/C_SGE_SCA .................................................99 Additional Data for Resource.............................................................. 99 Go to Display Order ............................................................................. 99 7.4 Checks and Alerts .........................................................100 7.5 Additional Information for Customizing ......................106 7.5.1 Planning Board Profile ..................................................... 106 Time Granularity ................................................................................ 106 Splitting.............................................................................................. 106 7.5.2 UI Profile............................................................................ 106 Screens .............................................................................................. 106 Additional 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 resource108 8.2 How to check what HR work center and logistic work center is assigned to a resource ...............................109 8.3 How to check whether the assigned work center is a technician work center................................................110 8.4 What to do if the assigned work center is not a technician work center................................................1119 Workflow Customizing ................................................. 113 9.1 Basic Workflow Customizing .......................................113 9.2 Agent Assignment Definition .......................................114 9.3 Customizing Approval Workflow Settings-Event Linkage .........................................................................115 9.4 Setting up the SMTP Mailing for Workflows ...............11610 TREX Configuration ..................................................... 117 10.1 TREX Integration Requirements ..................................117July 2010 7
  8. 8. Configuration Guide for SAP Multiresource Scheduling 10.2 TREX Configuration. .....................................................118 10.3 Testing the TREX Integration. ......................................118 10.4 TREX Compatibility chart. ............................................11911 Setting up the Employee Profile Web UI .................... 120 11.1 Integration ......................................................................120 11.2 Before You Start ............................................................120 11.3 SAP Multiresource Scheduling Backend Configuration ...............................................................120 11.4 Application Check .........................................................12212 Initial Setup Guide for SAP Multiresource Scheduling Employee Profile Workflows ....................................... 124 12.1 Basic settings ................................................................124 12.1.1 Customizing Settings ....................................................... 124 12.1.2 Agent Assignment ............................................................ 125 12.1.3 Event Linkage Activation ................................................. 125 12.1.4 Setting up the SMTP mailing for workflows ................... 125 12.2 Organizational settings in PPOME ..............................126 12.2.1 Starting with a blank organizational unit........................ 126 12.2.2 Creation of a position under the organizational unit..... 127 12.2.3 Assignment of resources to the newly created position ........................................................................................... 128 12.2.4 Creation of the manager position ................................... 130 12.2.5 Assignment of a resource to the newly created manager position ............................................................................. 131 12.3 Customer Infotypes for Controlling the Approval Process .........................................................................131 12.4 Resource Contact Information .....................................13513 Enhancement of Object Manager Scenario VERIMULT ........................................................................................ 13714 SAP Multiresource Scheduling BW-Extractors......... 140 14.1 Customizing and Package ............................................140 14.2 Terms for a Better Understanding ...............................140 14.3 BW – Data Extraction: Assignments ...........................140 14.3.1 Data Dictionary Objects ................................................... 140 14.3.2 Business Content: Data Sources ....................................141 14.3.3 Program Units ................................................................... 141 14.3.4 General Program Structure ............................................. 142 14.4 BW – Data Extraction: Alerts ........................................142 14.4.1 Alerts from scheduling .................................................... 142October 2010 8
  9. 9. Configuration Guide for SAP Multiresource Scheduling Data Dictionary Objects .................................................................... 142 Business Content: Data Sources ...................................................... 143 Program Units.................................................................................... 143 14.4.2 Alert components of scheduling process ...................... 143 Data Dictionary Objects .................................................................... 143 Business Content: Data Sources ...................................................... 144 Program Units.................................................................................... 144 14.4.3 Alerts: Confirmed Messages per User while Scheduling Process ............................................................................. 144 Data Dictionary Objects .................................................................... 144 Business Content: Data Sources ...................................................... 144 Program Units.................................................................................... 144 14.5 BW – Data Extraction: Links for the Scheduling Engine ...........................................................................145 Data Dictionary Objects .................................................................... 145 Business Content: Data Sources ...................................................... 146 Program Units.................................................................................... 146 14.6 BW – Data Extraction: Teams in the Scheduling Engine ...........................................................................146 Data Dictionary Objects .................................................................... 146 Business Content: Data Sources ...................................................... 147 Program Units.................................................................................... 14715 Appendix ....................................................................... 148 15.1 Transactions ..................................................................148 15.2 Reports ...........................................................................149 15.3 APIs .................................................................................150 15.4 Useful Tables .................................................................151 15.5 Abstract Partner Roles..................................................152 15.6 Abstract Status ..............................................................152 15.7 Overview of Database Tables .......................................154 15.7.1 Customizing Tables.......................................................... 154 15.7.2 Data Tables ....................................................................... 158 15.8 External Interfaces ........................................................161 15.9 Creating Object GUIDs ..................................................161July 2010 9
  10. 10. Introduction1 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). Note We use screenshots throughout this document as a visual aid in better understanding described concepts and procedures. These screenshots may not necessarily 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.October 2010 10
  11. 11. Installation2 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.July 2010 11
  12. 12. Configuration and Customizing: General Configuration3 Configuration and Customizing: General ConfigurationAfter 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 1October 2010 12
  13. 13. Configuration and Customizing: General Configuration Team Assignments If set to ‘X,’ an assignment can be created on team level. If initial, the assignments created on team level are distributed to each team member. An assignment for the resource “Team” is not created in this case. Capacitive assignments Define whether a capacitive planning of assignments is allowed in principle. Activate SAP Multiresource Scheduling Basis Define that SAP Multiresource Scheduling Basis should be used to manage resources. Resource Class Via the resource class, you can define if you want to use the HR Integration or not. If the ‘HR Resource’ option is active, the human resources can be transferred together with their availability from HR to SAP Multiresource Scheduling. Furthermore it is possible to set up a back integration from SAP Multiresource Scheduling to HR. If the ‘Business Partner’ option is active, the human resources have to be created as Business Partner. In this case the resources get their availability via SAP Multiresource Scheduling Reports. SAP Multiresource Scheduling Qualifications Here you can define if you want to use HR Qualifications or the SAP Multiresource Scheduling own qualification concept. Hint: HR Qualifications can be assigned to Business Partners or Personal Numbers. That means HR Qualifications can be used independent of the selected resource class. Activate Authority Check via evaluation paths Define whether you want to perform authority checks via evaluation paths. If the flag is set to “X”, evaluation paths will be used to determine user authorizations for 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 2You 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.July 2010 13
  14. 14. Configuration and Customizing: General Configuration Work Center with resource planning node: Work Centers of these Work Center Categories 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 3For 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 forOctober 2010 14
  15. 15. Configuration and Customizing: General ConfigurationAssignments. The value has to be set to ‘E1’. This is necessary for technical reasons and shouldnot be changed.Figure 4 Note If you have implemented SAP Note 1456178 (2010), you do not have to maintain the 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.July 2010 15
  16. 16. Configuration and Customizing: General ConfigurationFigure 5Here 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. Recommendation All RFC destinations should be trusted destinations since the user IDs are also used for the RFC communication. Via the user ID the authorization checks are performed.Some example entries are shown in the figure below:Figure 6October 2010 16
  17. 17. Configuration and Customizing: General Configuration 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 Example The 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 the queue is errored again, the system will reprocess it again after 60 seconds. This will happen only 3 times after which the system will stop processing the queue automatically. After this, the queue must be activated manually.July 2010 17
  18. 18. Configuration and Customizing: General Configuration Note The parameters for reprocessing of queue is required only if you use the SAP Multiresource Scheduling function module /MRSS/SGE_QUEUE_MONITOR for queue monitoring and automatic activation of queue. This SAP Multiresource Scheduling function module /MRSS/SGE_QUEUE_MONITOR will monitor and activate SAP Multiresource Scheduling integration only those queues that start with the name: MRSINT* 3.2.5 Automatic Activation of SAP Multiresource Scheduling Integration QueuesTo 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 : 5 c. 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 OrdersFigure 9October 2010 18
  19. 19. Configuration and Customizing: General ConfigurationIn 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.July 2010 19
  20. 20. Configuration and Customizing: General ConfigurationFigure 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 16October 2010 20
  21. 21. Configuration and Customizing: General Configuration 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 the Customizing. Accept offer function: An offer can only be accepted within the contact person process with manual resource confirmation. You cannot activate this function for the resource planner process by means of the field control.If a field is defined as an input field by the field control mechanisms, depending on the businessprocess logic this doesnt 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 Multiresource Scheduling 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 not "Not planning relevant" and already saved. Order probability: If "Posting" is marked, field is display only.July 2010 21
  22. 22. Configuration and Customizing: General Configuration Manual resource confirmation: Hidden if process variant does not equal "Contact person process". Planning node: In change mode, the field becomes a mandatory input field dependent on customized user status.SAP Multiresource Scheduling screen on network activity: All fields: If process variant is "Not planning relevant," all SAP Multiresource Scheduling 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. Can only be changed from "not planning relevant" to the process variant defined in network header. Disabled if assignments are existing. Network activity number and short text: Display only fields that are hidden when called form CJ20N Requirement profile field: Display only in display mode Create and change requirement profile buttons Inactive in display mode Manual resource confirmation: Hidden, if process variant does not equal "contact person process". Display only, if offer demands are existing or if assignments 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 saved Remaining effort pushbutton: Disabled if not contact person process or time rule exists. Remaining effort delete button: Disabled if not contact person process or time rule exists. Time rule edit button: Disabled if SAP Multiresource Scheduling demand exists and status START_PLAN is set and time rule is not already defined. Time rule delete button: Disabled, if time rule doesnt exist Toolbar function: Resource by qualification: Disabled if no requirement profile specified. Disabled if not contact person process. Toolbar function: Resource by planning structure: Disabled if resource planner 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 does not equal “contact person process” or manual resource confirmation switched off. Toolbar function: Refresh qualification: Disabled if requirement profile not specified. 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.October 2010 22
  23. 23. Configuration and Customizing: General ConfigurationThe 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. Note The indicator takes effect only if you have specified Not Relevant to Planning as the process variant in activity Deactivate Process Variants.3.5 Configuration of Web-based Resource Management IntegrationIn 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 BS02July 2010 23
  24. 24. Configuration and Customizing: General Configuration b) Select candidate status profile ‘RM_CAND1’ Figure 19 c) Click on Object types button d) 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_PARTNER Obj.no.fld - Status_obj_key Ref.struc - Ionra Key fields - Objnr c) Save. 5) Maintain Number Range Interval for Status Number Range Object: a) Go to transaction SNRO b) 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:October 2010 24
  25. 25. Configuration and Customizing: General Configuration 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.July 2010 25
  26. 26. Configuration and Customizing: General Configuration/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 21October 2010 26
  27. 27. Configuration and Customizing: General ConfigurationThere 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 22July 2010 27
  28. 28. Configuration and Customizing: General ConfigurationFigure 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 View3.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 1391965 This note is required to be implemented in case of integration with cProjects 400. SAP Note 1389664 This note is required to be implemented in case of integration with cProjects 500. SAP Note:1391065 This 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.October 2010 28
  29. 29. Configuration and Customizing: General ConfigurationFigure 24For 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 resource planner from the organizational unit for the cProject. Whether the resource proposals must be accepted manually, whether they are to be scheduled automatically, or whether they are to be posted automatically and firmly.July 2010 29
  30. 30. Configuration and Customizing: General ConfigurationIn 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 25October 2010 30
  31. 31. Configuration and Customizing: General ConfigurationIn 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 26In 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 27July 2010 31
  32. 32. Configuration and Customizing: General ConfigurationIn 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 293. Choose Create or Change.4. Create a number range with the following values:October 2010 32
  33. 33. Configuration and Customizing: General Configuration Figure 30 3.6.3 Master DataDefine Business Partner1. Use transaction BP.2. Create Role General and BUP003.3. Enter the personnel number in the Employee field.Figure 31Abstract Status CustomizingIn the Customizing for SAP Multiresource Scheduling choose Basic Settings Assign ERPObjects Status Define Abstract Status.Maintain the followoing abstract status: RES_ALLCTD Resource AllocatedJuly 2010 33
  34. 34. Configuration and Customizing: General Configuration 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 finiskedTime Recording Status Mapping: ERP Abstract Status: WORK_START = A, B, D, F, H WORK_STOP = C, E, G, I Figure 32In 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.October 2010 34
  35. 35. Configuration and Customizing: General ConfigurationAn example mapping is done in the figure below. Figure 33Recommendation for cProjects UI settingsIf 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/cprojects2. 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 createdAssign the abstract status in Customizing for SAP Multiresource Scheduling under Basic SettinAssign 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: ENMaintain 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:July 2010 35
  36. 36. Configuration and Customizing: General Configuration1. 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 35October 2010 36
  37. 37. Configuration and Customizing: General ConfigurationFigure 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:July 2010 37
  38. 38. Configuration and Customizing: General ConfigurationFigure 38Figure 39October 2010 38
  39. 39. Configuration and Customizing: General ConfigurationFigure 403.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 SchedulingIn 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.July 2010 39
  40. 40. Configuration and Customizing: General ConfigurationFigure 41 Note If the EI checkbox is selected, the time allocation appears as a bar in the planning board. These time allocations can be changed directly in the planning board. If the EI flag is not set, the time allocation appears only in the background as having availability or having no availability. Exceptional Time Allocations can only be created in the Planning board and related functions. Basic Time Allocations (no EI- Flag) can only be created if basis availability gets transferred e.g. via the HCM SAP Multiresource Scheduling transfer report /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 42You need to assign the defined types to the different resource types. For example, the definedtimes for personnel resources could resemble the following:October 2010 40
  41. 41. Configuration and Customizing: General ConfigurationFigure 43If 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.July 2010 41
  42. 42. Configuration and Customizing: General Configuration 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.October 2010 42
  43. 43. Configuration and Customizing: Specific Configuration4 Configuration and Customizing: Specific ConfigurationThis 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 44During 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 45For 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 46If 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.July 2010 43
  44. 44. Configuration and Customizing: Specific Configuration Note If you are upgrading from MRS 610 to SAP Multiresource Scheduling 700, then this Customizing 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 47The Customizing activity is separated into three sections, forward integration, backward integrationand general settings. 4.1.1 Forward Integration from PM/CS to SAP Multiresource SchedulingSplitsWith 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 TimesWith 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.October 2010 44
  45. 45. Configuration and Customizing: Specific ConfigurationHint: 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 AlertsWith 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 to PM/CSSplitsWith 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 CenterThe 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.DatesWith 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.Prerequisite: The 1:1 relationship must be active.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 AssignmentWith 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 TimesWith 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.Prerequisite: The 1:1 relationship must be active.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.July 2010 45
  46. 46. Configuration and Customizing: Specific Configuration 4.1.3 General SettingsDate LogicThe 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 LogicWith 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 48Since 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 managers 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 managers planning board.October 2010 46
  47. 47. Configuration and Customizing: Specific ConfigurationWhen 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 494.4 SAP Multiresource Scheduling QualificationsAfter activation of the SAP Multiresource Scheduling qualifications in the basic settings, anenhanced qualification management can be used. Note You can use the enhanced Qualification Management only for resources that are represented 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 for qualification catalogs. Qualification Matrixes via Customizing activity: Define number ranges for qualification matrixes. Requirement Profiles: Define Number Ranges for Requirements ProfilesIf 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.July 2010 47
  48. 48. Configuration and Customizing: Specific ConfigurationFigure 50Via 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 51Qualifications 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.October 2010 48
  49. 49. Configuration and Customizing: Specific ConfigurationFigure 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 is defined. You specify the URL components for the user interface of the portal. For further information please refer to chapter 4.5 “Supplement Concerning the Static URL to Access 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 further information please refer to chapter 4.6 ”Smart Forms for Employee and Requirements Profiles”. For each plant, you can specify the objects for which the system is to execute the where-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.July 2010 49
  50. 50. Configuration and Customizing: Specific ConfigurationFigure 53To 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 54The Handling of so called ‘On Call Types’ can be defined in the Customizing activity Definefulfillment values for matching on-call types.October 2010 50
  51. 51. Configuration and Customizing: Specific ConfigurationFigure 55If 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 56Via 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.July 2010 51
  52. 52. Configuration and Customizing: Specific ConfigurationFigure 57How 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_empprf4.5 Supplement Concerning the Static URL to Access Employee Profiles on Enterprise PortalThe 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=” to the end of the static URL Example: “/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_FM34.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 SAPOctober 2010 52

×