Você está na página 1de 30

MRS

General Architecture
What is resource management

 Resource management is to have: Right resource at the right time at the right
location for the right work.

 Thereby making the effective utilization of the skilled resource and minimizing
overheads
Resource Management Overview

Demand Dispatching, Scheduling and Supply


Monitoring

Skills &
Availability
Work schedule Skills
Equipment Duration
Org structure Availability

Location On call
Location Skills Assignment

 Order types:  Work center capacity planning  Time specifications


 PM/CS, PS, cPro, DBM  Resource planning  Resource assignments
 Cross-organizational staffing:
 Define:  Assignment types:  Location
 Duration, Capacity,  Capacitive, Concrete,  Qualifications
Qualifications, Location Stretched
 Time specifications
 PRT  Booking types
 Proposal, Softbooked,
Hardbooked
 Scheduling:
 Demand planning
 Demand relationships check
 Monitoring: clocking data
What does MRS do?

 MRS brings the information of demands (resource requirements) and supply


(resource data) into one view for effective planning

MRS can integrate itself into existing order (demand) systems (PM/CS, PS, DBM,
CRM, c-Pro) and resource systems (HCM, BP) in existing SAP solutions.

 Thus MRS fits into the big picture of SAP Enterprise Resource Planning scenario.
MRS Scenario Overview

Demands

PM/CS Order PS Network cProjects Request WebUI


technically based on PS

Planning and Scheduling

Manager View
(Web UI based)

Capacity Management

Graphical Planning Board Employee View


(SAP GUI based) (Web UI based)
Sources of Demands:
Example business scenario

 PM/CS – Plant maintenance and customer service


 The machinery in plant 0001 has broken down and requires immediate repair
 Periodic maintenance of plants / work shops
 My washing machine has got a problem and it needs to be fixed

 PS – Project systems
 Planning of large projects. For example: Construction of new high tension cable
suspended bridge.

 DBM – Dealers business management


 Vehicles to be scheduled

 c-Pro – Collaboration projects (Project Management)


 Project planning of consulting projects. For example: MRS implementation @ Field
Services

 CRM – Customer Relationships Management


 Call customer care for fixing of my broad band connection
General MRS Architecture

ERP
PM/CS PS DBM cProjects
Order Network Order Role

VSR Optimizer
MRS “Vehicle Scheduling and Routing”
(Engine for optimization of technician’s
Assignments schedules)
Demands
(MRS / WFM)

MRS
Resources
Qualifications
GIS System
Geographical Information System
Availability
Qualifications

HR Business HR
Equipments Qualifications*
Persons* Partner

*HR can be in a separate ERP system


How does MRS do it?

 Standard SAP provides BADIs which can be implemented by MRS

 If BADIs are unavailable, then MRS makes modifications into standard SAP

 During the save of orders, the data flows into MRS tables

 Data flow from Orders into MRS is called: Forward Integration

 MRS can also write the resource planning relevant data back to order management
systems. This is called Backward Integration
MRS Architecture inspiration

The MRS architecture has been inspired from other well known (and well architected)
SAP solutions like:

 WFM (Work force management)

 RPA (Resource Planning application) from CRM

 PM/CS order integration


Data Model Diagram

 The demands are created when an order is saved.

 A demand in MRS is modeled as complex demand and single demand

 A complex demand represents the order header information. A complex demand


can have one or more single demands.

 A single demand represents one operation of an order.

 The demand data is stored in following tables:


 DEM_H
 DEM_ADM
 DEM_PLR
 DEM_INFO
 …

 The data model diagram is shown here:


How does data flow in MRS?

 The resource data comes from HCM. This data is transferred by report:
/MRSS/HCM_RPTWFMIF.

 The availability of resources is mapped into time allocations and stored in BASIS.

 The capacity of resources is stored in capacity graph tables.

 The relevant tables and relations are attached in slide: 10


Assignment

 Assignment is the link between demand and a resource.

 Assignments are mainly of 3 types:


 Concrete assignments
 Capacitive assignments
 Stretched assignments.

 Assignments can be hard booked or soft booked.


 Assignment is hard booked when it is confirmed that the work will happen
 Soft booking is performed when a project manager wants to reserve a resource for a work
that might come in future.

 The database tables and relations are shown in slide 10.


Qualifications

 Qualifications represent the skills required to complete a work.


 For example: To repair my washing machine, I need an electrical engineer with 2 years of
experience

Qualifications can be modeled in HR as well as MRS. MRS Qualification object is


more powerful and provides many advantages over HR qualifications.

 MRS engine supports both types of qualifications

 The qualifications of demands are integrated during the save of order

 The qualifications of resources are integrated during the HCM transfer.

 MRS Qualification object:


 Logically similar qualifications are grouped into a qualification catalog.
 A qualification matrix is a combination of a qualification catalog and a rating scale
 A qualification matrix is used to define qualifications of a resource or demnads

 Data model diagram and related tables are shown in slide: 10


PM Integration

MRS Forward
Order creation in Integration
IW31 MRS Planning
• MRS maps the Board
• MRS is called order data from
during save. PM into MRS own • MRS uses the
• MRS is triggered format demand data
via a modification in • FM: from own DB
CO_ZV_ORDER_P /MRSS/RSG_PM_ tables.
OST ORDER_PUSH_T
O_MRS

© SAP 2008 / Page 14


PS Integration

MRS Forward
Create project in Integration
CJ20N MRS Planning
• MRS maps the Board
• MRS is called order data from
during save. PS into MRS own • MRS uses the
• MRS is triggered format demand data
via a modification in • FM: from own DB
CO_ZV_ORDER_P /MRSS/RAP_PS_ tables.
OST ORDER_SAVE_P
REP

© SAP 2008 / Page 15


C-Pro Integration

MRS Forward
Create project in Integration
cPro Web UI MRS Planning
• MRS maps the Board
• MRS is called order data from
during save. PM into MRS own • MRS uses the
• MRS is triggered format demand data
via a DPR BADI. from own DB
• BADI: tables.
/MRSS/DPR_SUBS
YSTEM

© SAP 2008 / Page 16


Scenario Variants

 MRS offers 2 variants in resource planning process. These process variants are
valid only for project planning (cPro and PS)

 Resource Planner Process


 The project manager directly assigns the demand request to a resource manager
 The resource manager assigns resource and process is complete.

 Contact Person Process


 The project manager can assign the demand request to central person responsible for
staffing.
 The contact person can search for resources and find our their resource managers.
 Then the demand request is sent to these resource manger.
 Here the project manager has option to accept or reject a resource proposal.

© SAP 2008 / Page 17


High level Technical architecture

UI Layer
• Enables user Interaction
• Communicates to the engine layer.
• This layer gives commands to engine to perform any type
of tasks

Object Layer (Engine Layer)


• Interacts with the UI (external world)
• Takes care of performing main tasks and manages:
Assignment , capacity, demands, resources, history, alerts,
integration, etc
• Interacts with the DB layer. Executes read and write
operations on DB

DB Layer
• Responsible for DB operations like read and write to data
DB
base.
UI Layer

UI Layer: /MRSS/CL_SGU_UI_MAIN

UI Gantt UI Hotlist UI Work List UI Alerts UI Details

IL Layer: /MRSS/CL_SGU_IL_MAIN

IL Gantt IL Hotlist IL Work List IL Alerts IL Details

Access to MRS Engine via Façade


Main parts of MRS Engine

Command Qualifications
Manager Engine

Worklist
Basis
Checks Resource
& Alerts Manager
Resource Manager

• Responsible for all assignment


operations like: creation, maintenance
Assignment
Manager

• Responsible for maintaining links like:


HH, TH links
Link
Manager
Resource manager
manages all resource
related data
• Responsible for initialization and
managing all tool resources
Tool
Manager

• Resource manager keeps a list of


Single resources in abstract form. This could be
Resources human resource, BP, Team or Tool…
Single Resource

/MRSS/CL_SGE_SINGLE_RESOURCE
• This abstract class models a resource in MRS engine.
• At run time, the concrete object is of one of the below types:

/MRSS/CL_SGE_HUMAN_RES_PERS
• This class models a Human Resource Person (from HCM)

/MRSS/CL_SGE_HUMAN_RESOURCE
• This class models a Business Partner (BP)

/MRSS/CL_RSG_TOOL_RESOURCE
• This class models a tool resource

/MRSS/CL_SGE_TEAM
• This class models a team resource
Work List

Worklist :
/MRSS/CL_SGD_WORKLIST_GEN

1:n
GT_ORDERS: /MRSS/CL_SGD_COMPLEX_DEMAND

1:n
GT_ITEMS: /MRSS/CL_SGD_SINGLE_DEMAND
Commands

 Commands are the core of MRS engine.

 Commands enable Undo-Redo functionality.

Command Patterns and Undo-Redo


functionality

Varun Verma
Checks and Alerts

 Check classes perform various business checks and create alerts.

 MRS engine provides a framework such that customers can enhance / extend
checks and alerts

 MRS engine provides an interface: /MRSS/IF_SGE_CHECK which is implemented


by all check classes
MRS 610 vs. MRS 700

MRS
700 NW
Add on

MRS
610
MRS
700 ERP
Add on
System Boundaries

MRS NW MRS ERP

• Can be installed • Can be installed on


separately on any ECC
NW. • Needs MRS NW as
• Does not need ERP prerequisite
Add on • SHOULD NOT
• CAN NOT access access MRS NW
MRS ERP objects objects directly.
• Use ROUTER to • Use APIs to access
access ERP NW
Interaction with other add on

 Each add on provides an interaction layer that can be used by the external
systems to read / write data.
 The main objects of interaction layer are listed below.

• FUGR:
MRS 700 NW Add
on

on
MRS 700 ERP Add
• FUGR: /MRSS/R3_BO_INTERACTION
/MRSS/NW_SGE_INTERACTION • FUGR:
• FUGR: /MRSS/R3_MRS_INTERACTION
/MRSS/NW_MRS_INTERACTION • FUGR:
• FUGR: /MRSS/R3_UI_INTERACTION
/MRSS/NW_BO_INTERACTION • CLASS:
• CLASS: /MRSS/CL_NW_ROUTER /MRSS/CL_R3_OBJECT_LAYER
• CLASS:
/MRSS/CL_NW_OBJECT_LAYER
Limitations of MRS

 MRS does not take into account the resource costs.

 MRS is only a planning tool. The downstream process of time booking and billing
are out of scope of MRS.
Q/A

 What are main parts of MRS Engine

 What are main components of Resource Manager

 What should you use to access ERP from NW?

 What should you use to access NW from ERP?