LO815 - Maintenance Processing -- Operational_Functions

8/11/2019 LO815 - Maintenance Processing -- Operational_Functions

1/185


2/185

SAP AG LO815 Preface-2

SAP AG 2001

Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in

any form or for any purpose without the express permission ofSAP AG. The information contained herein may be changedwithout prior notice.

All rights reserved.

Copyright

Trademarks:

Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors.

Microsoft, WINDOWS

, NT

, EXCEL

, Word

, PowerPoint

and SQL Server

are registered

trademarks of Microsoft Corporation.

IBM, DB2

, OS/2

, DB2/6000

, Parallel Sysplex

, MVS/ESA

, RS/6000

, AIX

, S/390

,

AS/400, OS/390

, and OS/400

are registered trademarks of IBM Corporation.

ORACLEis a registered trademark of ORACLE Corporation.

INFORMIX-OnLine for SAP and INFORMIX

Dynamic Server

TMare registered trademarks of

Informix Software Incorporated.

UNIX, X/Open

, OSF/1

, and Motif

are registered trademarks of the Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C

, World WideWeb Consortium, Massachusetts Institute of Technology.

JAVAis a registered trademark of Sun Microsystems, Inc.

JAVASCRIPTis a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,

SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com

are trademarks or registered trademarks of SAP AG in Germany and in several other countries all

over the world. All other products mentioned are trademarks or registered trademarks of their

respective companies.


3/185


SAP AG 2001

Plant Maintenance (PM)

Level 2 Level 3

LO100 5 days

Maintenance Processing:Operational Functions

LO815 3 days

Maintenance Processing:Controlling and Reporting

LO816 3 days

Preventive Maintenanceand Service

LO810 3 days

Document Management

System

LO975 3 days

LO985 3 days

The Cross ApplicationTime Sheet (CATS)

CA500 2 days

Structuring and Managing

Technical Objects

LO805 3 days

InvestmentManagement

AC020 2 days

WCM Work ClearanceManagement

LO820 3 days

Plant Maintenance

Classification


4/185


SAP AG 2001

Course Prerequisites

LO100 - Plant Maintenance

Basic knowledge and experience of PlantMaintenance

Good working knowledge of Windowsenvironment


5/185


SAP AG 2001

Target Group

Audience:

Project team members

Project team leaders

Duration: 3 days

Notes to the user:

The training materials do notconstitute ateach-yourself program.They complement the course

instructors explanations.Your material includes space for noting down this additional information.


6/185

SAP AG LO815 1-1

SAP AG 2001

Course goal

Course content

Course overview diagram

Main business scenario

Course Overview


7/185

SAP AG LO815 1-2

SAP AG 2001

Optimize the configuration and structure of yourmaintenance processing

Understand the application functions withinmaintenance processing in greater detail

This course will prepare you to:

Course Goal


8/185

SAP AG LO815 1-3

SAP AG 2001

Course Objectives

At the conclusion of this course, you will be ableto:

Configure new order and notification types

Set the most important Customizingparameters for orders and notifications

Plan capacity

Use permits

Utilize a standard workflow in PM


9/185

SAP AG LO815 1-4

SAP AG 2001

Unit 4 Planning

Unit 5 Scheduling

Unit 6 Completion

Unit 1 Course Overview

Unit 2 Workplace and Roles

Unit 3 Notification

Preface

Appendix

Contents


10/185

SAP AG LO815 1-5

SAP AG 2001

Course Overview Diagram

Course OverviewCourse Overview

Notification

Workplace and Roles

Completion

Planning

Scheduling


11/185

SAP AG LO815 1-6

SAP AG 2001

Main Business Scenario

At IDES, the maintenance requirementsshould first be collected and then dealtwith during order processing.

This process should contain thefollowing steps: notification,planning, scheduling, executionand completion.


12/185

SAP AG LO815 1-7

SAP AG 2001

Steps in Maintenance Processing

Maintenanceplanner/supervisor

Maintenanceplanner

TechnicianWarehouse clerk

Prodn. employee

Maint. plannerNotification

Completion

History

Material usage, orders, notifications, PMIS, usage list

Work to be performed MaterialResources internal/external Tools

Order release Capacity levelingPrintout Availability check

Planned/unplanned material withdrawalExternal procurement

Time confirmation Tech. completionTech. completion confirmation

4

5

2

3

1

TechnicianSupervisor

Phase Contents Roles

Technical object Date

Description Malfunction

Planning

Scheduling

Execution

The cycle of maintenance processing consists of five steps: Step 1: Notification of a malfunction or request for a particular task (for example, new construction).

Step 2: Creation and planning of an order based on the notification. Typical planning tasks include

creating operations, making reservations for spare parts, and planning execution times.

Step 3: Order scheduling with availability check, provision of capacity, printing of order papers.

Step 4: Actual execution of the work requested, including withdrawal of spare parts from the

warehouse and execution of the order.

Step 5: Completion of the work actually executed, with completion confirmation and technical

findings to record the condition of the technical object and possible damage. The order is settled in

Controlling.


13/185

SAP AG LO815 2-1

SAP AG 2001

Workplace

Roles

Workplace and Roles


14/185

SAP AG LO815 2-2

SAP AG 2001

Using the Workplace to provide a standardizedpoint of entry for all required systems.

Using roles to provide employees with usermenus designed for their specific jobs.

Business Scenario


15/185

SAP AG LO815 2-3

SAP AG 2001

Describe the basic Workplace concept

Create a customer specific role

At the conclusion of this unit, you will be able to:

Workplace and Roles: Topic Objectives


16/185

SAP AG LO815 2-4

SAP AG 2001


Course Overview

Notification

Workplace and RolesWorkplace and Roles

Completion

Planning

Scheduling


17/185

SAP AG LO815 2-5

SAP AG 2001

mySAP.com Workplace

Companyboundary

Web browser access

WorkplaceIndustry specific

Role based

PersonalizedDrag&Relate

Market

place

single

sign-

on

3.1H

R/3 4.6FI LO

HR

CRMKW

Business-to-Business

procurement

SEM

APO

BW

CFM

mySAP.com components

OpenInternetstandards

R/2

non mySAP.com3rdparty

Partners

SAP

internal

external

mySAP.com Internet services

Other Internet services

OtherERP

Systems

Technical info

The mySAP.com Workplace uses a simple, adaptable, and easy-to-use interface. This enablesemployees to access the right information and applications at the click of a mouse. The mySAP.com

Workplace is defined by the following characteristics:

Single point of access - using a Web browser to access applications, content, and services

A personalizedand role-baseduser interface

Easy integration

Open access and flexibility

Universal access at any time


18/185

SAP AG LO815 2-6

SAP AG 2001

Role Functions

SAP user

Harry Meyers

Maintenance engineer

Processing equipment

...

Create equipment

Change equipment

Change list editing

Collective role

Single role

Single role

Harry Meyers user menu

Leave request

Processing equipment

...

Employee

Leave request

Single role

Collective role

When a role is assigned to a user, transactions required for functions appear automatically in the usermenu. This menu appears automatically when the user logs on. Each example role can be easily

copied and then adapted to individual requirements.

The example roles are available in the form of Collective roles. Each collective role includes a

number of Single roles. Each single role contains a group of related transactions.

You assign one or more collective roles to an SAP user. The collective roles assigned to a user form

the user menu.

Example:Harry Meyers works as a maintenance engineer for IDES AG. His role as employee

means that he needs access to general functions, for example, making a leave request. In his role as

maintenance engineer he manages technical objects. The collective rolesEmployeeandMaintenance

engineerare assigned to his SAP user profile, and his user menu is then available.


19/185


20/185

SAP AG LO815 2-8

SAP AG 2001

Create a single role (transaction PFCG)

Create a menu

Enter target system / assign role

Generate authorizations

Create collective role

Assign user

Maintaining Roles

Process:

Creating a single role: Activities that form a logical unit (for example, order processing) are groupedtogether to form a single role. You can use individual transactions, parts of the SAP menu, or area

menus.

Instead of creating single roles, you can copy and adapt SAP example roles

(SAP_WP_MAINTENANCE_*).

Enter target system / assign role: If the transactions for the role are to be performed in another

system, this must be entered as the RFC destination. The roles can be transported to this system in

the same step.

Generate authorizations: You can automatically generate the required authorization profile for each

role. This can be adapted in expert mode.

Create collective role: You can do this either in the component system, or - when the Workplace isimplemented - on the Workplace server. The collective role encompasses several single roles.

Assigning users: Users who perform the same activities are assigned to collective roles. They

automatically receive the corresponding authorization profile.

If you use SAPGUI to operate SAP R/3, the roles are created directly in the corresponding R/3

System. If you use the Workplace to operate R/3, the roles are created on the Workplace server.

The roles are distributed to the R/3 System in which the transactions are to be performed

(Component system).


21/185

SAP AG LO815 2-9

SAP AG 2001

Example: Creating Maintenance TechnicianCustomer Role

Example role: maintenancetechnician

Collective role

Single role

Single role

Single role

Customer role: maintenancetechnician

SAP_WP_MAINTENANCE_TECHNICIAN

SAP_PM_EQM_EQUIPMENT_DISPLAY

SAP_LO_MD_MM_MATERIAL_DISPLAY

...

Z1_PM-Technician

Z1_IH_Equipment_Display

Z1_IH_Material_Display

...

Collective role

Single role

Single role

Single role

Copy/

rename

Process: 1. When maintaining roles (transaction PFCG), search for collective role (for example,

SAP_WP_MAINTENANCE_TECHNICIAN). We recommend you set a filter (for example,

SAP_WP_MAINT*) in the search function (F4).

2. Perform copy function - enter new target role (for example, Z1_PM_Technician) then, for

example: choose Copy all.In the popup, underNew roles, rename the single roles that are offered

according to the chosen naming convention (for example, Z1_PM_Equipment_Display).

3. Assign the required users to the new collective role.

4. Generate authorizations for each single role.

5. Enter the target system for each single role (if the role was created, for example, on the Workplaceserver).

6. UseEnvironment - Overview statusto check the role settings.

Note: You can download the new collective role as an external file, and then upload it to another R/3

system.

You can integrate additional transactions with each single role.


22/185

SAP AG LO815 2-10

SAP AG 2001

Further Information

SAP courses:

MY301 mySAP.com Workplace

CA940 SAP R/3 Application Security Concept

Online help

Basis > Computing Center Management System > Users and

Roles

Web sites:

www.mysap.com

www.sap.com/miniapps


23/185

SAP AG LO815 3-1

SAP AG 2001

Notification category, notification type

Configuration of notification interface

Priorities

Object information

Catalogs and catalog profile

Notification


24/185

SAP AG LO815 3-2

SAP AG 2001

The notification is used withinmaintenance processing to collectmaintenance requirements.

At IDES, the notification type Malfunctionreportshould be configured optimally forentering malfunctions. All the screen areasrequired should be available on a singlescreen if possible. All other screen areasshould be accessible using tab pages.

The entry of malfunctions should also besupported by configuring priorities, anobject information key, and a suitablecatalog profile.

Business Scenario


25/185

SAP AG LO815 3-3

SAP AG 2001

Create a notification type with its mostimportant settings

Configure tab pages

Define an action box

Configure priority types with priorities

Set up an object information key

Define catalogs and catalog profiles Define the field selection for notifications


Notification: Unit Objectives


26/185

SAP AG LO815 3-4

SAP AG 2001


Course Overview

Notification

Workplace and Roles

Completion

Planning

Scheduling


27/185

SAP AG LO815 3-5

SAP AG 2001

Notificationcategory

Notification

category

NotificationtypeNotificationtype

M1 - Maintenance request

M2 - Malfunction report

M3 - Activity report

G0 - General notification

Notification Category, Notification Type

01 - Maintenance notification

02 Quality notification

03 - Service notification

05 - General notification

For entry and further processing of requirements and malfunctions, you can use maintenancenotifications (notification category 01, notification type M1 or M2).

Alternatively, you can create a general notification (notification category 05, notification type (for

example) G0).

General notification uses a simple entry screen for entering the requirement into the system - you do

not have to define the type (for example, malfunction, request, complaint, internal problem

notification).

You first make the decision in the second step by changing the notification type General notification

to the specific notification type (for example,Malfunction report). In the subsequent notification, the

maintenance planner adds all the missing details.

The advantage of using general notifications is that you can make central, coordinated entry for anykind of requirement - the person making the entry does not have to a trained maintenance planner.

You can use Internet Application Components (IACs) in the Workplace to create the notifications

mentioned above. IACs are easy-to-use transactions programmed for Internet use. This means you

can use the transaction QISR and the Workplace (not using the standard GUI) for simple creation of

notifications.


28/185

SAP AG LO815 3-6

SAP AG 2001

Notification typeNotification type

Reference time

Order type

Number assignment

Response profile

Origin indicator

Long text control

Screensequencecontrol

Catalogs

Interval

Partner function

Object information

Field selection

Catalog / catalog profile

Status profile

Classification of defects

Priority / priority type

Settings for Notification Types

Notification

In the R/3 System, notifications are assigned to the individual applications using the notificationtype. In the IMG for PM, your entries are defined automatically for the notification type "PM"

(maintenance notifications).

You can use the individual notification types to define different classes of maintenance notifications

and then use these classes when making selections. You can use the notification type to define the

usage of the maintenance notification for particular business processes. In the standard system,

notification types are structured according to functional criteria (malfunction notification,

maintenance request, activity report).

The origin indicator influences the appearance of the screen, but it does not influence the subsequent

processing.

The reference time specifies the date allocated for the task. The account assignment fields andlocation data for the reference object are defined based on this date.

Example: Equipment E1 is installed at functional location F1

01/09/98 Notification created for E1

> Reference object in notification: F1 - E1

02/09/98 Dismantling of E1 and installation in F2; notification opened again

> Reference object in notification: F2 - E1

03/09/98 Notification completion > Depending on the reference time,

either the data valid on 01/09 or 03.09 is recorded in the history


29/185

SAP AG LO815 3-7

SAP AG 2001

Transaction

start values

Condition

indicator

Field selection List editing

MaintenanceMaintenance

notificationsnotifications

General Settings for Maintenance Notifications

This slide shows several configurations that affect maintenance notifications, although they are notdirectly linked to the notification type. In other words, these settings affect all notifications,

irrespective of notification type or category.

The field selectionfor notifications enables certain fields to be controlled together for all notification

types (for example, light color for the fields "Notification from" and "Notification date").

List editing reportsfor notifications can be set in Customizing so that they have defaults for

selection screens (default data on the initial screen of the report), field selection (which fields can be

selected, suppressed, and so on) and the display order of the fields.

The system condition indicatordefines the conditions that a technical system can have (operational,

out of order, and so on). These settings are not dependent on the notification type; they are defined at

client level. The transaction start valuesfor a notification transaction define whether an initial screen should be

shown and which notification type should be preset. "Initial screen" must be selected if you want to

access the initial screen with the fields for notification number and notification type. You can also

define which screen should be the first detail screen. The notification header screen is the initial

screen in the standard system, but this can be changed.


30/185

SAP AG LO815 3-8

SAP AG 2001

Configuring Tab Pages

Create PM Notification: Malfunction Report

Notification 100123 M2

Status MOFN

Order

Items Causes Tasks Activities

Reference object

Notification Malfunction data Location data Activities Dates

You can configure tab pages for each notification type. There are 20 different tab pages available intotal (16 notification-based, 4 item-based).

You can define a simple view or an enhanced view for each notification type. This means that the

screen is very simple for the person entering the notification, but contains all details for the person

processing it. Different transactions enable you to use the two notification type views:

- the Plant Maintenance transactions IW24 (Malfunction Report) IW26 (Maintenance Request), and

IW25 (Activity Report) for access to the enhanced view- the transaction IQS21 - Simplified Viewto

obtain the basic view

Screen areas (subscreens) can be defined for each tab page. There are 16 different screen areas

available.

You can assign the tab pages their own internal heading and a graphical symbol, if required.

Tab pages already defined can be switched easily on and off.

Within a notification type, it is still possible to specify different layouts for the notification screen,

for example, to distinguish between display mode and change mode: You might want only core data

to be visible in display mode, whereas all data should be seen in changed mode. This is controlled

using activity categories (create, change and display).


31/185

SAP AG LO815 3-9

SAP AG 2001

Priority typePriority type

PM....

PrioritiesPriorities

12...

Relevant

startand unit

Relevant

endand unitNotification

sequence

StartPM notification

Priorities

A priority can be assigned to each maintenance notification and order. This priority defines therequired start and end dates for the notification or order, relative to the creation date.

During maintenance processing, you can work with internal priority types for notifications and

orders. Since you can define an unlimited number of priorities for each priority type, it is easier for

the user to utilize the same priority types for notifications and orders; the same priority keys have the

same meaning.


32/185

SAP AG LO815 3-10

SAP AG 2001

Create PM Notification: Malfunction Report


Status MOFN

Order

Items

Notification

Activity category

Notification type

Origin indicator

Catalog profile

Priority

Application

component

Fields are controlled

usingField selection

Field Selection for Notifications: Influences

Field selection determines what features the different fields in a master record or transaction have:Ready for input (optional), required entry field, cannot be displayed, highlighted.

For example, if you want the "Priority" field in the notification to be a required entry field instead of

an optional one, you can use field selection to define this. In this example, "Priority" would be a

modifiable field. Only notifications of notification type "NB" should have the priority as a required

entry. In this case, the notification type is an influencing factor. Several fields that influence

notifications are listed above. Each time a notification is created with notification type "NB", the

"Priority" field is a required entry field. It is also possible to define these rules for a field without

including specific influencing factors.

All fields that can be modified are assigned to one screen group. Some objects, for example, work

centers are linked to several screen groups. Double-click on the screen group that contains the fields

you require and change the field selection.


33/185

SAP AG LO815 3-11

SAP AG 2001

++

+

+

+*

** * *

-

-

-

-

-

- - - -

*

*

.

..

-

*

+

.

= Hide field

= Display field

= Required entry field

= Normal input field

Field Selection: Link Rules

Sometimes, field selection for a single field is influenced by several factors. For example, thenotification type may define that a particular field is a required entry field, but the activity category

determines that this field is not displayed at all. In such cases, you can use the link table above to

determine what sort of field it should be.


34/185

SAP AG LO815 3-12

SAP AG 2001

Automatic display of

object information

Reference to object information

Number of days in past

for search for PMIS

information and notifications

Display characteristics for

reference object

ControlControl

Object Information Key

The object information key defines how the object information is displayed in notifications andorders.

If the indicator "Automatically" is set, the system displays the object information automatically in

the notification as soon as the reference object is entered or changed.

The reference specifies whether the object information should relate only to the reference object, the

reference object and the superior objects in the technical hierarchy, or all the objects in the structure

of the reference object.

You can specify how many days in the past (from the time of the inquiry) the system should search

for the statistics from the information system (breakdowns reported, notifications created, and so on).

You can also enter such a search period for finding notifications. You can also define whether the

system should display completed or outstanding notifications, and not only notifications with thestatus "In processing" or "Outstanding".

If the indicator for characteristics is set, the characteristics of the reference object are displayed if it

is assigned to a class.


35/185

SAP AG LO815 3-13

SAP AG 2001

Electrical work

Mechanical tasks

.

.

.

Code groups

Replace cable

Replace fuse

Replace starter

Codes

Tasks

Causes of damage

Activities

Object parts

Damage

Catalog types

Selection sets of

Codes

Mandatory evaluation

Administrative data

Catalogs

A cross-application catalog system is used for reporting maintenance notifications. This catalogsystem has a hierarchical structure.

The first level of the catalog system is the catalog type. Each PM catalog type represents a certain

directory.

Each catalog type can be further subdivided using code groups.

You can define individual codes within each group.

The following catalog types are provided as standard for Plant Maintenance:

Catalog 2 for tasks

Catalog 5 for causes of damage

Catalog A for activities

Catalog B for object parts

Catalog C for damage

If you want to define your own catalog types and assign them to PM-relevant catalogs, use catalog

types R to Z.

You can define corresponding key words for standard catalogs for damage and problem codes. The

key words appear in the notification item as key words for the displayed catalog.


36/185

SAP AG LO815 3-14

SAP AG 2001

Problems: CCauses: 5Tasks: 2Activities: A

Object parts: B

Notification type M2

C

Catalogs

Assigning Catalogs to Notification Types

2

5

In Customizing, catalogs are assigned to each notification type for the predefined areas: Problems,causes, tasks, activities and object parts.

Only after catalogs have been assigned to the notification type are the corresponding fields for cause

of damage, object part and so on, provided in the notification item.


37/185

SAP AG LO815 3-15

SAP AG 2001

Catalog C: Damage

........

........

PM catalog type

Damage

Task

Object part

Catalog profile

Code group

001 1000002 5400

M*

GEN

Group 5400: Pumps1000 Unbalanced rotor blade

1100 Tear in motor casing

1200 Smouldered cable

1300 Cracked ring seal

1400 .......

Group 1000: General damage1000 Corrosion

1100 Breakage

1200 Dirt

1300 Leakage

1400 .......

Catalogs and Catalog Profile

The catalog profile combines a selection of code groups from different catalogs for a particular topic(for example, findings procedure for pumps).

One or more code groups can be selected from each catalog. Code groups can be specified by writing

them out in full or several code groups can be selected within an entry using wildcards (for example,

PUMP*).


38/185

SAP AG LO815 3-16

SAP AG 2001

PM catalog type

Damage

Task

Object part

Catalog profile

Code group

001 1000

002 5400M*GEN

Assigning Catalog Profiles to Notification Types

Maintenance

Notification

Notification typeNotification typeNotification type

You can assign the catalog profile to the master record for the technical object and notification type. If the technical object and notification type both have a catalog profile, the profile from the technical

object is always read first when a notification is created, and copied depending on availability.


39/185

SAP AG LO815 3-17

SAP AG 2001

Action Box for Notifications

Create Maintenance Notification: Malfunction Report


Status MOFN

Order

Action box

Automatic creation of a

task or activity

Call up a

function module

Note

Phone

message

You can use the Action Box function when creating or processing a notification. The Action Boxcontains follow-up activities that were set as defaults for each notification type in Customizing. You

can execute these follow-up activities simply by pressing the relevant pushbutton. The follow-up

activity is documented either as an activity or an task in the notification header once it has been

successfully executed.

The technology used for follow-up functions differs from that for the existing task-based follow-up

actions as follows:

The function is executed immediately after the follow-up function has been selected, not when

the notification is saved.

A task or activity is only created after the follow-up activity has been successfully executed.

You can use a follow-up activity to start a workflow task.

The function group QM06 contains useful standard follow-up activities.

The function group QM10 contains copy models for creating own follow-up activities.


40/185

SAP AG LO815 3-18

SAP AG 2001

Customizing Check List (I)

Notification type

Number range

Screen layout

Long text control

Object info keys

Priority type

Order type

Partners

Catalogs

Catalog profile

Action box

General notification


41/185

SAP AG LO815 3-19

SAP AG 2001

Customizing Check List (II)

General settings

Condition indicator

Transaction start values

Field selection

List editing

Workflows


42/185

SAP AG LO815 3-20

SAP AG 2001

You are now able to:

Create a notification type with its most importantsettings

Configure tab pages

Define an action box

Configure priority types with priorities

Set up an object information key

Define catalogs and catalog profiles Define the field selection for notifications

Notification: Unit Summary


43/185

SAP AG LO815 3-21

Exercises

Unit: Notifications

Topic: Notification Category, Notification Type

At the conclusion of these exercises, you will be able to:

Create notification types

Define notification parameters

Configure the notification interface

At IDES, a new notification type should be created for the entryof malfunctions.

All the notification parameters and notification interface should

be configured optimally for this purpose.

Data Used in the PM Courses:

Description Training System IDES

General

Controlling area 1000 1000

Company code 1000 1000

Plant 1000 1000

Storage location 0001 0001

Purchasing organization 1000 1000

G/L account 417000 417000

Vendors 1000, 1101, 1102

SRV-1

1000


44/185

SAP AG LO815 3-22

Technical Objects

Equipment TEQ-## P-1000-N001

Inspection equipment 10003540,10003541

10003540,10003541

Equipment with equipment

BOM

T-SM0100 T-SM0120

Configurable equipment P-6000-N001 P-6000-N001

Functional locations K1

## (*)

SERV-PRO-RZ-##

K1

SERV-PRO-RZ-##

Operating hours counter for

FL ->K1-M01-2, K1-M01-

3, K1-M02-2, K1-M02-3

Created in course

Status profile for equipment PMSTAT


45/185

SAP AG LO815 3-23

Materials and Bills of Material

Materials:

Pump without serial

number standard price

batches

Pump with serial number

standard price batches

Pump with serial number

moving average price

batches. Moving average

price

Pump without serial

number moving average

price batches. Moving

average price

T-FP1##

T-FP2##

T-FP3##

T-FP9##

P-2001

P-2002

P-2003

P-2009

Material with condition-

based valuation (standard

price valuation)

P-2001 P-2001

Serial number profile

(stock check = 1 > warning)

PM1 PM1

Configurable material P-6000 Not available

Bill of material for material

P-6000

P-6000 Not available

Materials for material BOM

P-1000

(plant 1000, resp. 4)

100-100

100-400

DG-1000

100-600100-431

KR117185

WL-1000

G-1000

M-1000

100-100

100-400

DG-1000

100-600100-431

KR117185

WL-1000

G-1000

M-1000


46/185

SAP AG LO815 3-24

Materials for equipment

BOM

T-SM0100 T-SM0120

(plant 1200, resp. 4)

DPC9021

C-1112

R-1120

R-1131R-1160

DPC9021

C-1112

R-1120

R-1131R-1160

Configurable material (service) INSPECTION_SERVI

CE

Work centers

Work centers T-ME##

T-EL##

T-EX##

Mechanics

Electrics

Task Lists and Maintenance Planning

Task lists PUMP_WTG

PUMP_REP

MM-CALIB

PUMP_WTG

PUMP_REP

MM-CALIB

Profile 0000001 0000001

Maintenance plans

Service procurement

PM/QM link

50

600000000000

51, 52

50

600000000000

51, 52

Maintenance strategy

(performance-based)

DFL DFL

Cycle set CS CS

Configurable general task

list for maintenance

planning in conjunction

with configurable

equipment

PUMP_WTG 6 PUMP_WTG 6

(old status)

Maintenance plan with

configurable equipment and

general task list

Maintenance plan 80


47/185

SAP AG LO815 3-25

Notification and Order Processing

Service masters 100131, 100132 100131, 100132

Order type for generating

inspection lots

PM06 PM06

Control key for internal

service processing

PM05 PM05

Standard text keys PM00001 PM00008 PM00001 PM00008

Settlement profile for

refurbishment (for order

type PM04)

PM_AWA

Order type for investment

orders

PM07

Service masters for internalservice processing (control

key PM05)

100020, 100021

Cost Centers and Activity Types

Cost centers

Installed

Technical systems

External company

4300

4110

4350

4300

4110

4350

Activity types 1410 (repair)

1610 (external)

1410 (repair)

1610 (external)

Allocation cost element for

activity type 1610

Outline Agreements / Framework Orders

Outline agreements:

Pipe laying work (vendor

1102)Services (vendor 1101)

4600000023

4600000024

4600000024 (pipe laying,

vendor 1101)

Framework order for

services

4500007351


48/185

SAP AG LO815 3-26

Service

Maintenance contract 40000077

Configurable material (service) INSPECTION_SERVI

CE

Sold-to-party 1171

Classes

Variant class (used in

configurable equipment and

general task list)

CL_P600 CL_P600

Project and Investment Program

Project I/5001 I/5001

Project profile PM00001 PM00001

Investment program PM2000 Not available


49/185

SAP AG LO815 3-27

1-1 Displaying an Existing Notification Type:

Display the existing notification type N1. Which Customizing function do you

choose?

__________________________________________________________________

____________________________________________________________________________________________________________________________________

Answer the following questions:

1-1-1 To which notification category is notification type N1 assigned, and which

other notification categories exist?

____________________________________________________________

________________________________________________________________________________________________________________________

1-1-2 What is defined by the origin indicator?

____________________________________________________________

____________________________________________________________

____________________________________________________________

1-1-3 When is the catalog profile, which is assigned to the notification type,

proposed in a notification?

____________________________________________________________

____________________________________________________________

____________________________________________________________

1-1-4 Which update group is supported for the PM Information System?

____________________________________________________________

1-1-5 What is defined by the reference date/time?____________________________________________________________

____________________________________________________________

____________________________________________________________

1-1-6 What effect does the Early number assignment indicator have?

____________________________________________________________

____________________________________________________________

____________________________________________________________


50/185

SAP AG LO815 3-28

1-2 Creating a New Notification Type

1-2-1 Control Parameters

Create a new notification type ## as a copy of notification type N1. This

notification type should have the following properties:

It should have the character of a general maintenance notification. The reference date/time should be the notification completion.

The catalog profile for pumps should be assigned.

The update group is 26.

The number assignment should take place when you save.

Which control parameters do you set?

Origin indicator

Reference time

Catalog profile

Update group

Early number assignment

1-2-2 Screen area notification header

The screen type for the notification header should beMaintenance

notification. The screen type for the reference object should beEquipment

only.

In which Customizing option can you enter these settings?

____________________________________________________________

____________________________________________________________

____________________________________________________________

1-2-3 Long Text Control

For notifications created for your notification type ##, it should be logged

who entered the long text. It should not be possible to change the long text

later. How do you do this?

____________________________________________________________

____________________________________________________________

____________________________________________________________


51/185

SAP AG LO815 3-29

1-2-4 Number Range

Your notification type ## should be assigned to the number range of the

group of maintenance notifications. How do you do this?

____________________________________________________________

____________________________________________________________

____________________________________________________________

1-2-5 Create four tab pages with the screen areas specified below for your

notification type ##. How do you proceed?

____________________________________________________________

____________________________________________________________

____________________________________________________________

Notification - Reference object

- Subject and long text

(Windows 32bit)

- Basic dates

- Areas of responsibility

- Item + cause

Item overview - Overview of all notification

items with activities, causes,

tasks

System availability - System availability

- Effect on system

Activities - Activities for notificationheader


52/185

SAP AG LO815 3-30

Unit: Notifications

Topic: Priorities

1-3

1-3-1 Define a new priority type ##. Which Customizing path do you choose?

____________________________________________________________

____________________________________________________________

____________________________________________________________

1-3-2 Define three priorities A, B and C for your priority type. The proposed start

dates should each be set to today, and the required end dates should be set to

today (A), a week today (B), and two weeks today (C). Which entries do

you make?

Priority Rel. start Rel. End Unit Start Unit End

A

B

C

1-3-3 Assign your notification type ## to your priority type ##. How do youproceed?

____________________________________________________________

____________________________________________________________

____________________________________________________________


53/185


54/185

SAP AG LO815 3-32

Unit: Notifications

Topic: Object Information Key

1-5

1-5-1 Defining an Object Information Key

Define a new object information key ##; this should appear automatically

when you create a notification. The analysis data should only relate to the

object entered. The evaluation should take the past two years into

consideration. All notifications should be considered, but no contracts. The

characteristic information should be displayed.

Which parameters do you set?

Automatically

Reference for notification and class selection

Selection of days

Contract

Classification

1-5-2 Assigning an Object Information Key

Assign your object information key ## to your notification type ##. How do

you proceed?

____________________________________________________________

____________________________________________________________

____________________________________________________________


55/185

SAP AG LO815 3-33

1-5-3 Creating a Notification

Create a maintenance notification with notification type ## for equipment

P-1000-N001.

What information is derived from the object information?

From which date onwards is the selection made?

How many completed orders are there?

What is the diameter of the running wheel?

Which documents are assigned?

Save the maintenance request. Which number is assigned to it?

___________________________________________________


56/185

SAP AG LO815 3-34

Unit: Notifications

Topic: Catalogs and catalog profile

1-6

1-6-1 Which catalogs are normally used in PM?

Assign these to your notification type ##.

How do you proceed?

____________________________________________________________

____________________________________________________________

____________________________________________________________

1-6-2 Code Groups and Codes

Create a new code group ## with 5 codes for the damage catalog. Which

codes have you created?

Code Description

1-6-3 Catalog Profile

Create a catalog profile ##, that accesses your code group ## for the damage

catalog, but displays all entries for the other catalogs. What entries do you

make in the catalog profile?


57/185

SAP AG LO815 3-35

1-6-4 Catalog Profile and Notification Type

Assign your catalog profile ## to your notification type ##. Which entries do

you make?

1-6-5 Creating a Notification

Create a notification with notification type ## for your equipment TEQ-##.Check whether the required code groups and codes are proposed. Which

notification number was assigned by the system?

____________________________________________________________

____________________________________________________________

____________________________________________________________


58/185

SAP AG LO815 3-36

Solutions

Unit: Notifications

Topic: Notification Category, Notification Type

1-1 SAP menu Tools Accelerated SAP Customizing Edit Project

SAP Reference IMGbutton

Plant Maintenance and Customer ServiceMaintenance and Service

ProcessingMaintenance and Service Notifications Notification Creation

Notification Types Define Notification Types

Answer the following questions:

1-1-1 M1 has notification category 01 (= Plant maintenance). Other notification

categories available are 02 (= Quality notification) and 03 (= Service

notification).

1-1-2 The origin indicator specifies the screen sequence upon which the

notification type is based.

1-1-3 If a catalog profile has not been entered for a piece of equipment orfunctional location, or if a notification is created without a reference object.

1-1-4 Update group 26

1-1-5 Date and time that are proposed when you complete the maintenance

notification. The location and account assignment data for updating the

history are determined using the reference time.

1-1-6 The indicator causes the notification to be assigned a number when the

Create function is called up, and not just when it is saved.


59/185

SAP AG LO815 3-37

1-2

1-2-1 Plant Maintenance and Customer ServiceMaintenance and Service

ProcessingMaintenance and Service Notifications Notification

Creation Notification Types Define Notification Types

Control Parameters

Field Name or Data Type Values

Origin indicator General notification

Reference time B

Catalog profile 2000

Update group 26

Early number assignment Not active


ProcessingMaintenance and Service Notifications Overview ofNotification Type

Select the line containing the notification type.

In the dialog structure, double click on the option Screen Areas in

Notification Header.


Screen type hdr H100

Screen category object O150


ProcessingMaintenance and Service Notifications Overview of

Notification Type

Select the notification type, and in the dialog structure click on the line

Format Long Text.

Check the boxesLog lineandNo text change.



Creation Notification Types Define Number Ranges

Select pushbuttonMaintain groups, double click on notification type ##,

and then assign the notification type to the interval using the pushbuttonAssign element/group.


60/185

SAP AG LO815 3-38



Notification Type


Screen Structure for Extended View.

ButtonNew entriesand make the following entries:

Notification tab page


Tab 10\TAB01

Tab heading Notification

Tab ; Data release

Screen area 1 005

Screen area 2 032

Screen area 3 040

Screen area 4 010

Screen area 5 015

Save, Back

New entriesbutton

Item overview tab page: 5 entries necessary:

Items main tab


Tab 10\TAB10

Tab heading Items

Tab ; Data release

Screen areas None

Save, Back


61/185

SAP AG LO815 3-39

New entriesbutton

Item overview lower-level tab


Tab 20\TAB01

Tab heading Item overview

Tab ; Data release

Screen areas None

Save, Back

New entriesbutton

Activities lower-level tab


Tab 20\TAB04

Tab heading Activities

Tab ; Data release

Screen areas None

Save, Back

New entriesbutton

Causes lower-level tab


Tab 20\TAB02

Tab heading Causes

Tab ; Data release

Screen areas None

Save, Back

New entriesbutton

Tasks lower-level tab


Tab 20\TAB03

Tab heading Tasks

Tab ; Data release

Screen areas None

Save, Back

New entriesbutton


62/185

SAP AG LO815 3-40

System availability tab page


Tab 10\TAB04

Tab heading System availability

Tab ; Data release

Screen areas None

Activities main tab page


Tab 10\TAB12

Tab heading Activities

Tab ; Data release

Screen areas None

Save, Back


63/185

SAP AG LO815 3-41

Unit: Notifications

Topic: Priorities

1-3

1-3-1 SAP menu Tools Accelerated SAP Customizing Edit Project



ProcessingMaintenance and Service Notifications NotificationProcessingResponse Time Monitoring Define Priorities

In the popup Choose Activity, place the cursor in the lineDefine Priorities

and then Choose. Enter the priority type ##, save, and return.

1-3-2 In the popup Choose Activity, place the cursor in the lineDefine Priorities

for Each Priority Type, then click Choose.

Priority Rel. start Rel. end Unit Start Unit End

A

B 7 DAY

C 14 DAY

Save and return

1-3-3 In the popup Choose Activity, place the cursor in the lineAssign Priority

Types to Notification Types, then click Choose.

Assign priority type to notification type


64/185

SAP AG LO815 3-42

1-4

1-4-1 SAP menu Logistics Plant Maintenance Maintenance Processing

Notification Create (General)

Enter notification type ##

1-4-2 Which reference object can you enter?

Equipment only

1-4-3 Choose priority C. Which dates are set by the system?

Required start: Current date

Required end: Current date + 14 days

1-4-4 Enter a long text. What entry is made?

User, date, time

1-4-5 Save the notification. Which number is assigned to it?

10000xxx


65/185

SAP AG LO815 3-43

Unit: Notifications

Topic: Object Information Key

1-5




Processing

Maintenance and Service Notifications

NotificationProcessingObject Information Define Object Information Keys


Automatically Yes

Reference for notification and

class selectionObject

Selection of days 730

Contract None

Classification Characteristics





ProcessingObject Information Assign Object Information Keys to

Notification Types

1-5-3 From which date onwards is the selection made? Current date 2 years

How many completed orders are there? 72

What is the diameter of the running wheel? 130 mm

Which documents are assigned? H-1000, P-1000


66/185

SAP AG LO815 3-44

Unit: Notifications

Topic: Catalogs and catalog profile

1-6

1-6-1 PM Catalogs


Damages C

Causes 5

Tasks 2

Object parts B

Activities A

Choose PM catalogs:



Notification Type


Catalogs and Catalog Profiles.





Creation Notification ContentMaintain Catalogs

In the popup, select the lineEdit Catalogs, enter catalog type C, code group

##

Short text and set statusReleased, release data

then select line and double click on folder Codeson the left hand side in the

Dialog Structurecolumn.


67/185

SAP AG LO815 3-45

Code Description

1000

2000

3000

4000

5000



Plant Maintenance and Customer ServiceMaintenance and ServiceProcessingMaintenance and Service Notifications Notification

Creation Notification Content Define Catalog Profile

Button New entries, enter ## as number of catalog profile, release data

then double click on folder Catalogs/code groups in the Dialog

Structure

Button New entries

Catalog Code group

2 *

5 *

A *

B *

C ##


68/185


69/185

SAP AG LO815 4-1

SAP AG 2001

Setting up an order type

Additional functions

Work center

Capacity planning

Planning


70/185

SAP AG LO815 4-2

SAP AG 2001

Business Scenario

In the planning phase, the maintenancerequirements reported are assigned to orders.The work to be performed is planned in detailin the order.

At IDES, different order types are used for theareas of routine maintenance, preventivemaintenance and refurbishment.

The order type contains the parameters criticalfor an optimized process flow.

Capacity planning is performed based on themaintenance work centers, with the option ofutilizing the integration with Human Resourcesand Production Planning.


71/185

SAP AG LO815 4-3

SAP AG 2001

Planning: Unit Objectives

Create an order type with its most importantparameters

Create a control key for internal and externalprocessing

Create external profiles

Create a maintenance work center

Plan capacity



72/185

SAP AG LO815 4-4

SAP AG 2001


Course Overview

Notification

Workplace and Roles

Completion

PlanningPlanning

Scheduling


73/185

SAP AG LO815 4-5

SAP AG 2001

Order Category, Order Type

Order categoryOrder category 10 - Production order

... ...

30 - Maintenance order

... ...

Order typeOrder type PM01 - Maintenance order

PM02 - Preventive maintenance order

PM04 - Refurbishment order

Orders are a type of business process. Order categories differentiate orders because there are orders in different applications.

The order categories are fixed in the system for the respective applications.

You can freely define the order types within an order category for each application.


74/185


75/185

SAP AG LO815 4-7

SAP AG 2001

Maintenance Activity Types

PM activity types

- Inspection

- Maintenance

- Repair

- Revision

- Cleaning

- Warranty

- Insurance

. . .

- Function for grouping

the actual costs in theobject history

- Warranty/insuranceindicator

- Selection criteria

PM order types

- PM01

- PM02

The maintenance activity type is the key for the type of maintenance activity executed (repair,shutdown, periodic tasks and so on).

In cost evaluations (total costs, number of orders per technical object), you can classify the data

using the maintenance activity type (distinction made between maintenance activities and costs).

The permitted activity types are assigned to each order type.


76/185

SAP AG LO815 4-8

SAP AG 2001

Order typeOrder type

Order typeOrder type

andand

Planning plantPlanning plant

Setting Up an Order Type: (II)

15. Default control key

12. Step-by-step operations, change documents, MRP relevance

13. Priorities

14. Object information

11. Default Value Profiles

16. Determination of address data

Parameters for order type: Object information

Priority type with priorities

Parameters for order type and planning plant:

Default Value Profiles

Default control key

Step-by-step operations / change documents / MRP relevance

Determination of address data

Special indicator for specific order types:

To set up an order type for integrated processing with a notification, an additional indicator

must be set in Customizing along with the corresponding notification category.

To set up an order type for refurbishment, an additional indicator must be set in Customizing.


77/185

SAP AG LO815 4-9

SAP AG 2001

External Processing Profiles

Default values for:- Cost element

- Purchasing organization- Purchasing group- Material type

Default values for:- Cost element- Purchasing organization- Purchasing group- Material type

Two profiles can be assigned:

External procurement

of material components

External procurementof material components

External processing

of operations

External processingof operations

During external processing, a distinction is made between the external procurement of material andthe assignment of complete operations to external companies.

Since both of the procurement processes generally require different data for purchasing (different

purchasing groups or different cost elements), you should define different profiles.

The profiles can be defined centrally for each order type in Customizing.

Alternatively, these settings can be set as user-specific with the user default values. The user values

override the Customizing settings.


78/185

SAP AG LO815 4-10

SAP AG 2001

Control Keys for Operations

Capacity planning

Scheduling operations

Capacity requirement

Costing

Service

Printing time tickets

Printing confirmation slipsPrinting operations

Completion confirmations

External processing

ControlControl

The system controls the processing of individual operations using the operation control key. You use the capacity planning indicator to ensure that the operation is scheduled and capacity load

records are created for it.

By setting the costing indicator, you ensure that the operation is taken into account during costing.

You use the external processing key to define that the operation is executed by an external company.

You use the completion confirmation indicator to specify whether the operation can be confirmed

and what type of completion confirmation applies.

The print parameters specify whether time tickets, confirmation slips, and so on should be printed for

this operation.


79/185

SAP AG LO815 4-11

SAP AG 2001

Internal Service Item

Operation 10 Lay house connection 6.5 hours

Service Quantity Unit Working time

Dig trenches 3 m 3 h (calculated)

Lay pipes 3 m 1.5 h (calculated)

Weld pipes 2 PC 2 h (direct entry)

Working time

calculated from

services

You can now use service masters to process internal operations. This standardizes the planningprocess for internally and externally processed operations. Individual steps can be described in

greater detail in a service master, where units are no longer restricted to the dimension "time".

The service master is maintained in Materials Management and enables you to plan work to be

performed in a simple, standardized way. This type of planning is used primarily if services should

also be processed internally using fixed prices. However, services are not currently entered for each

service master, instead all the services are calculated in work hours at operation level.

You must create a control key in your system for internal processing, for which the "Service"

indicator has been flagged. Once you have entered this control key, one or more service numbers can

be assigned on the operation detail screen.

You cannot make an entry in the field "Work" for operations to be processed internally, which allowthe assignment of a service master. The system fills this field automatically with the cumulated

values from the times it has calculated, based on the services planned for this operation. You can also

enter a value in the field "Work" in each service line.

When a service master is used for the operation, the execution factor can no longer be maintained. If

a factor had already been set, the system automatically resets it to 1 again.


80/185

SAP AG LO815 4-12

SAP AG 2001

Equipment -location data

Notification/order -

location data

Location and account assignment data is copied when

you create an order or notification You can then change it

Function Update reference object data

Defining Location and Account Assignment Data

When you create an order or notification, the technical object location and account assignment datais immediately copied from the master data and saved in the notification or order.

You can then change it there.

This prevents automatic changes to notifications or orders when you change technical object master

data (for example, dismantling, installing, or modifying equipment).

This ensures that data for PM-IS evaluation remains stable.

The function Update reference object dataenables you copy current data from the technical object

master data (the reference object for the notification or order) to the notification or order. Clicking

the right mouse buttonin the order header is the only way to access this function.


81/185

SAP AG LO815 4-13

SAP AG 2001

Order Hierarchies

Sub-order 1

Sub-order 2.1 Sub-order 2.2

Sub-order 2 Sub-order 3

Main order

If a maintenance task consists of several independent steps, whose costs should be separated, thistask can be represented using an order hierarchy.

A series of sub-orders (all of which are autonomous maintenance orders) are created here for an

existing main order.

The aim of an object hierarchy is to summarize costs at every level.

All the sub-orders must be completed before the main order can be completed.


82/185

SAP AG LO815 4-14

SAP AG 2001

The work center is an organizational unit that

can perform work.

It specifies where and by whom the operations can be

performed. Machines, people, groups of people and soon, can be defined as work centers.

The work center is an organizational unit that

can perform work.

It specifies where and by whom the operations can be

performed. Machines, people, groups of people and soon, can be defined as work centers.

DefinitionDefinition

The work center data forms the basis for:

Calculation of costs, capacities, dates

The work center data forms the basis for:

Calculation of costs, capacities, dates

FunctionFunction

Work Center

You use work centers to execute operations in task lists and orders. You can use the work center data to:

Define which machines or people should be used for the operations

Calculate costs, capacities and dates for the operations


83/185

SAP AG LO815 4-15

SAP AG 2001

Basic dataBasic data

Default valuesDefault values

CapacitiesCapacities

SchedulingScheduling

CostingCosting

Name and description

Standard value keyEfficiency key

Control key

Standard text keys

Wage data

Available capacity

Formula key

Individual capacities

Scheduling basis

Transport / queue time

Formula key

Cost center

Activity types

Personnel dataPersonnel data

Positions

Persons

Work Center Data

Work center data is used for the following business functions: Basic data - contains the description, work center category (for example, Plant Maintenance) and

planned usage (in which task lists can the work center be used).

Default values- contain, for example, a default control key.

Capacities - the available capacity is usually the standard available capacity with the

specifications - factory calendar, work start and end, number of individual capacities (= number of

people) and shift time per capita. The available capacity can be restricted according to time, or

organized in shifts different from the standard available capacity.

Scheduling- the operation dates are calculated based on the lead times (duration of operation),

starting from the basic start and end dates.

Costing - the internal personnel costs are made based on the activity types defined in Controlling.

The activity types contain the assignment to an hourly rate. The activity types are not assigned

directly to the work center, but indirectly using a cost center.

Personnel data - in addition to defining available capacity, people (= personnel numbers from

Human Resources) or positions can be assigned in the work center.


84/185

SAP AG LO815 4-16

SAP AG 2001

The available capacity is the work that can be providedby a unit of capacity at a work center for each working day.

The available capacity is defined using the start and finish ofwork, duration of the breaks, capacity utilization andnumber of individual capacity units.

The available capacity is the work that can be provided

by a unit of capacity at a work center for each working day.

The available capacity is defined using the start and finish of

work, duration of the breaks, capacity utilization andnumber of individual capacity units.


The available capacity forms the basis for:

Capacity planning

The available capacity forms the basis for:

Capacity planning

FunctionFunction

Available Capacity

The available capacity refers to the capacity available within a certain period. The available capacityis determined by:

Work start and finish times

Break lengths

Capacity utilization level of the capacity units

Number of individual capacity units that constitute the capacity

The system stores the working time and the daily available capacity for each work center.

The available capacity can be defined for one work center or for all work centers.


85/185

SAP AG LO815 4-17

SAP AG 2001

Interval duration

StandardStandardavailableavailablecapacitycapacity

Time

h

h

Interval 1

Interval 1 Interval 2 Interval 3

Not a workday according

to factory calendar

Time

Cycle durationFrom To

AA

BB

Available Capacity at Work Center

The standard available capacity is valid if no interval of available capacity is defined. The standardavailable capacity is defined using the start/finish times of the shift, break lengths, and number of

individual capacities.

The system uses the above data to calculate the working time of the capacity units. The validity

period of the standard available capacity is unlimited.

If you have specified validity periods for the available capacity, these are referred to as intervals of

available capacity. This is the capacity available within a specific validity period.

To define an interval of available capacity, you can determine shift sequences that can be valid for all

work centers for a certain period.

Start, finish and break times are specified for work centers in a shift.


86/185

SAP AG LO815 4-18

SAP AG 2001

Required work which results from an operation in an

order and should be performed by a particular workcenter within a particular period of time.

Required work which results from an operation in anorder and should be performed by a particular workcenter within a particular period of time.


Maintenance order

Preventive maintenance orderRefurbishment order

Maintenance order

Preventive maintenance orderRefurbishment order

Capacity requirements generated by:Capacity requirements generated by:

Capacity Requirement

Orders are the focal point of capacity planning. Orders generate requirements and thereby a capacityload for the resources that should execute the orders.

The requirement in an order is calculated from the sum of work times scheduled in the operations

(field: Resources required).


87/185

SAP AG LO815 4-19

SAP AG 2001

Areas of Capacity Planning

Available - Required = Free

Capacity evaluation

Determination of:

Available capacity

Capacity requirements

Comparison: Available -Required

Capacity leveling

Leveling overloads andunder-use of capacity

Optimum scheduling

Selection of suitable

resources

From work center

master

From

order operations

Capacity planning can be divided into two areas: Capacity evaluation

Capacity leveling

When evaluating the capacity situation, the capacity requirements are compared with the available

capacity. The available capacity specifies the available capacity per workday. The capacity

requirements specify the capacity required for the orders at a particular time.

Capacity leveling is used to adjust capacity overloads or under-use at work centers. It also helps to

optimize the use of labor and machinery and the selection of suitable resources.


88/185

SAP AG LO815 4-20

SAP AG 2001

Assignment of Personnel

Plant Maintenance

Production

IDES AG

Finances/Administration

Personnel

HR organizational units

Scott Weiland

Installed plant New York

Production/Sales

Craig Armstrong

John Squires

Work center - Plant Maintenance

Basic data

CapacitiesCapacities

HR links

Craig Armstrong

John Squires

You can only assign people, qualifications and positions to work centers if you use HumanResources (HR).

When using HR, individual people, who are stored in HR as a personnel master record with a

personnel number, can be assigned to a maintenance work center.


89/185

SAP AG LO815 4-21

SAP AG 2001

Assignment of Employee to Order

Order

Employee responsibleEmployee responsible

0010 Mechanics - Change seals0010 Mechanics - Change seals

0020 Mechanics - Check shaft0020 Mechanics - Check shaft

0030 Mechanics - Check motor0030 Mechanics - Check motor

Craig ArmstrongCraig Armstrong

John SquiresJohn Squires

Work center - Mechanics

Craig Armstrong 1 hourCraig Armstrong 1 hour

John Squires 2 hoursJohn Squires 2 hours

Craig ArmstrongCraig Armstrong

1

2

3

If people are assigned in the maintenance work center, these can be assigned at different places in themaintenance order:

1. Assignment of employee responsible in order header

To do this, the order type must contain a partner determination procedure with a function "Employee

responsible" and the field must have been activated in the order header.

2. Assignment of employee in operation

3. Assignment of several employees in requirements assignment for operation

Splits can be generated here manually or automatically - this means the work in the operation is

divided between several people.

Automatic creation of splits:

Several partners are assigned to the order (from the partner determination procedure for the ordertype). Work due is distributed automatically and evenly among these partners (partner type person).

This takes place in the form of automatically created requirement assignments (splits) for the

operation.

For automatic split creation to take place, a partner role must be assigned to the order type.

Note: Automatic creation of splits is only possible when you create an order. If you subsequently

change the order, this does not enable you to adapt the splits.


90/185

SAP AG LO815 4-22

SAP AG 2001

Graphical Monitor

Graphical Monitor for Resource Planning

Technician

MartinSmith

ReevesJones

Mortimer

Employees

assigned to a

work center

Day Time

Current time

Overdue

operation

Current

operation

Future

operation

Processing toolbar

You can use the graphical monitor to obtain an up-to-date overview of the work that has beenassigned to individual techniciansin a work center. The graphical monitor is updated automatically

by the system at specified time intervals. This provides you with a current overview of several

employees and, if required, several orders.

The capacity load records for all technicians asigned to a work center are displayed.

The following HR datais integrated:

Shift schedules

Attendances and absences (these are displayed differently from the work times)

On-call availability

In order to use the graphical monitor, personnel must be assigned for the specified work center in theTime Management(PT) application component.

Note: The graphical monitor only shows capacity loads for people who have been assigned in the

order operation as a capacity split (Requirements assignmenttab page in the operation).


91/185

SAP AG LO815 4-23

SAP AG 2001

PM-PP Integration

Master data

Technical object(equipment, functional location)

PP work center

Movement data

PM ordersOperation status indicator

PP orders

Available capacity Capacity requirement

If a maintenance order is executed for a machine, which is used as a production work center, theproduction planner should be able to see the production orders and also the maintenance orders that

arise for this work center on his planning board.

To display maintenance orders for a production work center, the number of the PP work center

must be entered in the location datafor the technical object.

The maintenance order must also contain a system conditionat header level.


92/185

SAP AG LO815 4-24

SAP AG 2001

Customizing Check List (I)

Order type

Number range

Maintenance planning plant

Planning indicator

Maintenance activity type

Object info keys

Priority type

External profiles

Special order types

Order combined with notification

Refurbishment order

You can find the Customizing paths for the individual options in the appendix.


93/185

SAP AG LO815 4-25

SAP AG 2001

Customizing Check List (II)

Control key

Customer exits and business add-ins

Customer exit definition:

Customer exits allow customers to add customer-specific functions to enhance the standard SAP

applications. Customer exits do not contain functions themselves - they are program exits that enable

connection to customer-specific programs.

Customer exits have two main advantages:

Customer exits do not affect the SAP standard source code

Customer exits are not effected by

software updates

Business add-in definition:

Similar to a customer exit, the business add-in is a program exit. Customer exits are based on a two

layer (SAP, customer) system landscape. Business add-ins are not - they are based instead on a

multi-layer system landscape (for example, SAP, country version, Industry Solutions, partners,

customer). You can define and implement business add-ins at any level of the system landscape.

For further information about business add-ins, use transaction SE19 and then the menu pathHelp >

Application help.


94/185

SAP AG LO815 4-26

SAP AG 2001

Create an order type with its most importantparameters

Create control keys for internal and external

processing

Create external profiles


Plan capacity

You are now able to:

Planning: Unit Summary


95/185

SAP AG LO815 4-27

Exercises

Unit: Planning

Topic: Setting up an order type

At the conclusion of these exercises, you will be able to:

Create a new order type

Assign all the required parameters to the order type


Plan and monitor available capacity and capacity requirements

At IDES, a new order type should be created for processing

routine maintenance tasks.

All the parameters for the order type should be configured

optimally for this purpose.

2-1 Create a new order type LO##. Assign the settlement profile for maintenance

orders, general budget profile, and entry mask for functional location, equipmentand assembly for the reference object.

How do you proceed?

Settlement profile:

Budget profile:

Reference object:

2-1-1 Number Range

Assign this order type to the number range group for maintenance orders.

How do you proceed?

____________________________________________________________

____________________________________________________________

____________________________________________________________

2-1-2 Order Type and Planning Plant

Assign this order type to the maintenance planning plant 1000. Which

Customizing function do you choose for this?

________

LO815 - Maintenance Processing -- Operational_Functions

Documents

Transcript of LO815 - Maintenance Processing -- Operational_Functions