Você está na página 1de 133

Organisation: Tatra Trucks India Ltd

Project:

Created on 10
March 2006

Page 1 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration Design Document


Plant Maintenance (Project Impact)

Prepared and Compiled by


Nishant Dudha

Nishant Dudha
Page 1

Organisation: Tatra Trucks India Ltd


Project:

Page 2 of
133

Impact

Configuration Design Document

ID: PM 1
Sub-system: Enterprise Structure
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Maintain Maintenance Planning Plant


Transaction code: SPRO
Nishant Dudha

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Enterprise Structure
Definition Plant Maintenance Maintain Maintenance Planning Plant
View Image:

Nishant Dudha
Page 2

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 3 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:
Nil
Configuration pre-requisites:
Maintenance Plants are first created as normal plants in Material Management

Rational for the configuration:

In Customer Service, a distinction is made between the organizational units "planning plant" and
"maintenance plant".

Maintenance plant

In a maintenance plant, you can manage technical objects and main work centers.
Planning plant
In the planning plant, maintenance task lists are defined for the respective maintenance plants, material
planning is carried out on the basis of bills of material in task lists and orders, maintenance plans are
managed and scheduled, maintenance notifications are created and maintenance orders can be handled.
For Tatra, all the branch warehouses are defined as Plants and they are being used in Customer Service as
Maintenance Plants for managing the customer equipments being maintained at sites.

Nishant Dudha
Page 3

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 4 of
133

Impact

Configuration Design Document

Version No: 1.0

ID: PM 2

Title: Assign Maintenance Planning Plant to Maintenance Plant

Sub-system: Technical Objects


Owner:

Transaction code: SPRO


Nishant Dudha

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Enterprise Structure
Assignment Plant Maintenance Assign Maintenance Planning Plant to Maintenance
Plant
View Image:

Nishant Dudha
Page 4

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 5 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:
Maintenance Plants
Configuration pre-requisites:
Maintenance Plants should be created

Rational for the configuration:

In the step "Assign maintenance planning plant to Maintenance Plant one can assign Planning Plants to
maintenance plants. You must assign a planning plant to each maintenance plant.
Tatra follows a centralized planning model for Customer Service and hence the Trading Plant 1110 is defined
as the Maintenance Planning Plant for the branch warehouses defined as plants 1201-1217 and being used as
Maintenance Plants for CS purpose.

Nishant Dudha
Page 5

Organisation: Tatra Trucks India Ltd


Project:

Page 6 of
133

Impact

Configuration Design Document

ID: PM 3
Sub-system: Technical Objects
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Define Location


Transaction code: SPRO
Nishant Dudha

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Enterprise
Definition Logistics General Define Location
View Image:

Nishant Dudha
Page 6

Structure

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Required fields:
Plant
Location
Name
Configuration pre-requisites:
Nil

Nishant Dudha
Page 7

Version No: 1.0

Page 7 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 8 of
133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:


Location has been defined primarily for identifying and demarcating departments and different locations in
plant for which the responsibilities are for various departments. One such example would be when the user
wants to view all PRT equipments in the plant. He simply selects plant code and types in TOOLS in location.
So the list of Tools appears in the plant.

Nishant Dudha
Page 8

Organisation: Tatra Trucks India Ltd


Project:

Page 9 of
133

Impact

Configuration Design Document

ID: PM 4
Sub-system: Technical Objects
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Create Structure Indicator for Functional Loc


Transaction code: OIPK
Nishant Dudha

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects Functional Locations Create Structure Indicator for Reference Functional
Locations/Functional Locations
View Image:

Nishant Dudha
Page 9

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 10 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
The following structure indicator has been finalized for TATRA for both plants by the client (Tatra)
TATRA -

Structure indicator

Edit Mask - NNNN-AAAA-AAAA-XXXX


1

The structure would have four levels.


Required fields:
Structural Indicator
Structural Indicator Description
Edit Mask
Configuration pre-requisites:
Nil

Rational for the configuration:


Nishant Dudha
Page 10

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 11 of
133

Impact

Configuration Design Document

Version No: 1.0

One can define the structure indicators for functional locations and reference functional locations in this step.
The structure indicator determines the edit mask and the number of the hierarchy levels when one create
functional location structures. The edit mask defines:
1. The total length of the functional location number
2. The lengths of the individual blocks of the functional location number
3. The characters allowed
Numbers

Edit mask N
Letters

Edit mask A
Numbers and letters
Edit mask X
Once a functional location has been created for a particular structure indicator, the edit mask can no longer
be changed

Nishant Dudha
Page 11

Organisation: Tatra Trucks India Ltd


Project:

Page 12 of
133

Impact

Configuration Design Document

ID: PM 5
Sub-system: Technical Objects
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Define Category of Functional Location


Transaction code: SPRO
NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects Functional Locations Define Category of Functional Location

View Image:

Nishant Dudha
Page 12

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Configuration design:
Nishant Dudha
Page 13

Version No: 1.0

Page 13 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 14 of
133

Impact

Configuration Design Document

Functional Location Category


Description Technical System
Object Info

Version No: 1.0

M
Standard

Measuring Point Category


View profile

Required fields:
Description
Measuring Point Category
View profile

Configuration pre-requisites:
Measuring Point Category -

Rational for the configuration:


One can create different functional location categories in this step. One can define the following for each
functional location category.
1. Status profile
2. Partner determination procedure
3. Default value for measuring point categories
4. Field selection
5. Whether change documents are created
6. A key defining the appearance of the dialog box for the object information.
Activities
Define your categories of functional locations.
Note for the allocation of the partner determination procedure

Nishant Dudha
Page 14

Organisation: Tatra Trucks India Ltd


Project:

Page 15 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Maintain Equipment Category

Sub-system: Technical Objects

Transaction code: OIET

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects Equipment Equipment Category Maintain Equipment Category
View Image:

Nishant Dudha
Page 15

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Equipment Cat
Ref Category
Description

M for maintenance And Q for Calibration


Machines
Machines

Object Info
View Profile

PM
Standard

Required fields:
Ref Category
Description
Object Info
View Profile

Configuration pre-requisites:
Object Info - OIMD
View Profile menu path defined in FL view profile

Nishant Dudha
Page 16

Page 16 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 17 of
133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:


In this step you define the description for an equipment category and assign a reference category to this
equipment category. You use the equipment category to define the characteristics for an equipment master
record. Using the control characteristics, you can decide how many and which equipment categories you
require. The following control characteristics are available:
1. View profile for master data maintenance
2. Number interval and number assignment (you can choose between numerical and alphanumerical
numbers)
3. Update of a usage history
4. Installation options at functional locations
5. Verification documents for master data changes
6. Usage as production resources/tools
7. Status profile
8. Equipment texts in several languages

Nishant Dudha
Page 17

Organisation: Tatra Trucks India Ltd


Project:

Page 18 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Number Ranges

Sub-system: Technical Objects

Transaction code: OIEN

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects Equipment Equipment Category Maintain Equipment Category Define
Number Ranges
View Image:

Nishant Dudha
Page 18

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Configuration design:
Insert Group
Select equipment type
Assign eqpt type M and Q to group

PM Eqpt no range grp ext


M P and Q
PM Eqpt no range grp ext

From Number
To Number

1000
99999

Nishant Dudha
Page 19

Version No: 1.0

Page 19 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 20 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:
Equipment Type
From Number
To Number

Configuration pre-requisites:
Equipment Categories

Rational for the configuration:


In this step you can define the number assignment category in the step equipment categories. You must
allocate a unique number for each equipment master record. You have the following options:
1. Internal number assignment
In this case, the SAP System assigns the numbers.
2. External number assignment
In this case, the user assigns the numbers.
You can define both an internal and an external number range for each equipment category. The same
number ranges can be shared by several equipment categories

Nishant Dudha
Page 20

Organisation: Tatra Trucks India Ltd


Project:

Page 21 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Installation at Functional Location

Sub-system: Technical Objects

Transaction code: OIEP

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects Equipment Equipment Usage Period Define Installation at Functional
Location
View Image:

Nishant Dudha
Page 21

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 22 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:

Equipment Category Description

M is allowed for installation and Q is not allowed for installation


at Functional Location
Machines

Ref Cat
Inst al Functional Loc

M
YES

Category

Required fields:
Category
Equipment Category Description
Ref Cat
Inst al Funct Loc.
Configuration pre-requisites:
Nishant Dudha
Page 22

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 23 of
133

Impact

Configuration Design Document

Version No: 1.0

Equipment Category
Rational for the configuration:
In this step one define for each equipment category, whether the installation of a piece of equipment is
allowed at a functional location.

Nishant Dudha
Page 23

Organisation: Tatra Trucks India Ltd


Project:

Page 24 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Planner Group

Sub-system: Technical Objects

Transaction code: OIAI

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects General Data Define Planner Group
View Image:

Nishant Dudha
Page 24

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Planning Plant
1010

Name

Planner Grp

Plant Maintenance

PM

The same will be applicable for all plants ie. 1020, 1030,1040,1050,1060,1070,1080

Required fields:
Planning Plant
Planner Group
Name
Configuration pre-requisites:
Planning Plant

Nishant Dudha
Page 25

Page 25 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 26 of
133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:


1. Group of employees responsible for the planning and processing of maintenance tasks in a particular
plant.
2. Planner groups must be defined separately for each planning plant.
3. Maintenance planning groups are used for evaluation purposes.
4. Every piece of equipment and functional location can be allocated to a maintenance-planning group.
Planner groups or maintenance planning groups must be defined separately for each planning plant.
Every piece of equipment and functional location can be allocated to a maintenance-planning group.
Maintenance planning groups can also be used for evaluation purposes.

Nishant Dudha
Page 26

Organisation: Tatra Trucks India Ltd


Project:

10

Page 27 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define ABC Indicators

Sub-system: Technical Objects

Transaction code: OIAA

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects General Data Define ABC Indicators

View Image:

Nishant Dudha
Page 27

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 28 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
ABC Indicator

ABC Indicator Text

Very Critical object

Critical Object

Non Critical Object

Required fields:
ABC Indicator
ABC Indicator Text

Configuration pre-requisites:
Nil

Rational for the configuration:


The characteristics of the ABC indicator can be used as a selection criterion in evaluations.

This defines the degree of criticality of an object or activity. You can determine which
particular values are to be valid as ABC indicators and the meaning that is given to these
values. The ABC indicator can be entered in equipment as well as functional locations.
Nishant Dudha
Page 28

Organisation: Tatra Trucks India Ltd


Project:

11

Page 29 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define types of Technical Objects

Sub-system: Technical Objects

Transaction code: SPRO

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Technical
Objects General Data Define types of Technical Objects
View Image:

Nishant Dudha
Page 29

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Equipment Type Code

Description

COMM

Communication

CIVIL

Civil Works

HANDTOOLS

Hand Tools

ITES

IT Services

MATHANDLG

Material Handling

MECH

Mechanical

Required fields:
Equipment Type Code
Description

Nishant Dudha
Page 30

Page 30 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 31 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration pre-requisites:
Nil

Rational for the configuration:


We have categorized the utility type of Equipments into different equipment types. The Equipment type
code is as asked by the client. The classification has been done primarily to uniquely identify these
equipments and generate reports for all its corresponding measurement parameters.

Nishant Dudha
Page 31

Organisation: Tatra Trucks India Ltd


Project:

12

Page 32 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Employees Responsible for Work Centers

Sub-system: Technical Objects

Transaction code: OIZ3

Owner:

NISHANT DUDHA

00nu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Master Data in Plant Maintenance and Customer Service Work
Centers General Data Define Employees Responsible for Work Centers
View Image:

Nishant Dudha
Page 32

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Plant
1010

Pers Responsible
PWC

Pers Responsible for Work Center


Manager maintenance

Required fields:
Plant
Pers Responsible
Pers Responsible for Work Center
Configuration pre-requisites:
Plant

Nishant Dudha
Page 33

Page 33 of
133

Organisation: Tatra Trucks India Ltd


Project:

13

Page 34 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Profiles with Default Values

Sub-system: Technical Objects

Transaction code: OIL6

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance Plans, Work Centers, Task Lists and PRTs Task List
General Data Define Profiles with Default Values
View Image:

Nishant Dudha
Page 34

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 35

Version No: 1.0

Page 35 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Profile PM
Description - Int. proc. profile for Plant Maintenance
General
Operation / act increment 0010
Group PM
Name Network
Internal Processing
Calculation key 1
Normal Duration unit H
Unit for Work H
Header data
Usage - 4
Status - 4
Required fields:
Description
Operation / act increment
Group
Name
Calculation key
Normal Duration unit
Unit for Work
Usage
Status
Configuration pre-requisites:
Task list usage OIL2

Rational for the configuration:

You can simplify data entry in the Task Lists creation by defining this profile.

Nishant Dudha
Page 36

Page 36 of
133

Organisation: Tatra Trucks India Ltd


Project:

14

Page 37 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Maintain Settlement Profiles (PREV, PLND &BDN)

Sub-system: Technical Objects

Transaction code: OKO7

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Basic Setting General Order
Settlement Maintain Settlement Profiles
View Image:

Nishant Dudha
Page 37

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 38

Version No: 1.0

Page 38 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Configuration design:
Receiver end defined as cost center as per CAI requirement.
Default Object Type is cost center and Allocation Structure A3
Settlement Profile 40 - Maintenance Measure
Actual Cost / Cost of Sales To be settled in full
Cost Center 1 (To be settled)

Nishant Dudha
Page 39

Version No: 1.0

Page 39 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 40 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:
Settlement Profile
Text
Actual Cost / Cost of Sales
Default Values
Indicators
Valid Receivers
Other Parameters
Configuration pre-requisites:
Allocation structure
Rational for the configuration:

In the settlement profile, you define a range of control parameters for settlement. You must define
the settlement profile before you can enter a settlement rule for a sender. If you want to settle the
costs each time to just one cost center or just one G/L account, you need a settlement profile. As you cannot
maintain the settlement parameters during settlement to a receiver, you must save the settlement profile
either in the order type or in the model order or reference order.
The settlement profile includes, among other things, the retention period for the settlement
documents. You should bear in mind the following when you determine the retention period.
The settlement documents take up additional storage capacity. When a posting period is finally locked
against further postings in Financial. Accounting and Controlling, you can clear the settlement documents.
However, you should build in a safety margin, as you will need the settlement documents if you have to
cancel any settlements or repeat the period end close.
Activities
1. Create a settlement profile.
2. Save the profile in the order type

Nishant Dudha
Page 40

Organisation: Tatra Trucks India Ltd


Project:

15

Page 41 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Maintain Allocation Structure

Sub-system: Technical Objects

Transaction code: SPRO

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Basic Setting General Order
Settlement Maintain Allocation Structures
View Image:

Nishant Dudha
Page 41

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 42 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Allocation Structure A6
Text - CAI Network Settlement
Controlling area - 1000
Assnmt

Text

SOURCE
From
Cost
Element

001
002

Internal
Material
External
Service

SETTLEMENT COST ELEMENT


To Cost
Element

Cost
Element
Group
RM

50657

Nishant Dudha
Page 42

Receiver
Category

By Cost
Element

Settleme
nt Cost
Element

Name

CTR

PM Cost

CTR

PM Cost

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 43 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:
Allocation Structure
Text
Controlling area
Assnmt
Text
SOURCE ( From cost element, to cost element, Cost element Group)
SETTLEMENT COST ELEMENT (Receiver Category, by cost element, settlement cost element, name )

Configuration pre-requisites:
Controlling Area
Cost Element (Master Data)
Cost Element Group (Master Data)

Rational for the configuration:


During settlement, costs incurred under the primary and secondary cost elements by a sender are allocated to
one or more receivers. When you settle by cost element, you settle using the appropriate original cost
element. An allocation structure comprises one or several settlement assignments. An assignment shows
which costs (origin: cost element groups from debit cost elements) are to be settled to which receiver type
(for example, cost center, order, and so on.
You have two alternatives in settlement assignment:
1. You assign the debit cost element groups to a settlement cost element.
2. You settle by cost element - that is, the debit cost element is the settlement cost element.
This is a good idea, for example, if the required capital spending for an asset you are
building yourself is to be monitored. These costs are settled by cost element to an inventory
account in Asset. Accounting at the end of the year, or when the measure is complete.
Each allocation structure must fulfill the following criteria:
- Completeness
An allocation structure is assigned to each object to be settled. All cost elements in which
costs are incurred, must be represented in the appropriate allocation structure.
- Uniqueness
Each cost element in which costs are incurred may only appear once in an allocation structure. Only one
settlement cost element may be assigned to a source within a particular allocation structure.

Nishant Dudha
Page 43

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 44 of
133

Impact

Configuration Design Document

Version No: 1.0

ID: PM 16

Title: Maintain Value Categories

Sub-system: Technical Objects

Transaction code: OIKI

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Basic Settings Settings for
Display of Costs Maintain Value Categories
View Image:

Nishant Dudha
Page 44

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 45 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Value Category KEY

450

Value Category Text


Material Consumed Internal /
External (Stock / Non Stock)
AMC Service - PM

460

Sublet Repair - CS

Yes

470

Internal Labour

Yes

440

Required fields:
Value Category
Text
Costs
Revenues

Configuration pre-requisites:

NIL

Nishant Dudha
Page 45

UM

Costs
Yes
Yes

Revenues

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 46 of
133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:

In this step, you define value categories. Value categories are intervals for cost elements.
These are required to update the Plant Maintenance Information System
Activities

Define a key and description for the value category.


If you want to evaluate quantities in the order, assign a unit of measure to the value category.
Enter the load category for the value category:
Costs and outgoing payments
Revenues and incoming payments

Nishant Dudha
Page 46

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 47 of
133

Impact

Configuration Design Document

Version No: 1.0

ID: PM 17

Title: Assign Cost Elements to Value Categories

Sub-system: Technical Objects

Transaction code: OIK2

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Basic Settings Settings for
Display of Costs Assign Cost Elements to Value Categories
View Image:

Nishant Dudha
Page 47

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 48

Version No: 1.0

Page 48 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 49

Version No: 1.0

Page 49 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 50 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:

Component PM
Value Category

Text

1000

440

Material Consumed Int./ Ext

1000

450

External Services

CO Area

Cost
Element

Required fields:
CO Area
Value Category
Cost Element
Cost Element Group

Configuration pre-requisites:
CO Area
Value Category
Cost Element (Master Data)
Cost Element Group (Master Data)
Nishant Dudha
Page 50

50657

Cost Element
Group
RM

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 51 of
133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:

In this section, you define a cost element, a cost element interval or a cost element group as a value
category.
Activities:
1. Choose a value category and call up the detail screen.
2. Define a cost element, a cost element interval or a cost element group as a value category.

Nishant Dudha
Page 51

Organisation: Tatra Trucks India Ltd


Project:

18

Page 52 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Notification Types

Sub-system: Maintenance Process

Transaction code: OQN0

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Notification Notification
types Define Notification Types
View Image:

Nishant Dudha
Page 52

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Notification Type

Description

Notification Cat

M1

General Maintenance

PM Notification

M2

Breakdown Maintenance

PM Notification

M3

Preventive Maintenance

PM Notification

M4

Refurbishment Request

PM Notification

M5

Calibration Request

PM Notification

M6

Modification Request

PM Notification

M7

External/AMC Service

PM Notification

Required fields:
Notification Type
Description
Nishant Dudha
Page 53

Page 53 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 54 of
133

Impact

Configuration Design Document

Version No: 1.0

Notification Cat
Parameters

Person to Process Task


Sub screens
Configuration pre-requisites:
NIL

Rational for the configuration:

The purpose defining the notification type is to define the nature maintenance activity in your
company.
General Maintenance
Breakdown Maintenance
Preventive Maintenance
Calibration Maintenance
AMC/Service Maintenance
Installation/Dismantling
Miscellaneous Breakdown Maintenance
This will be update in the PM Information Structure for evaluation purpose like History reports (MTTR,
MTBR ect.,)

Nishant Dudha
Page 54

Organisation: Tatra Trucks India Ltd


Project:

Page 55 of
133

Impact

Configuration Design Document

ID: PM 19
Sub-system: Maintenance and Service
Processing
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Overview of Notification Type


Transaction code: SPRO
NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and Service
Notification Overview of Notification Type
View Image:

Nishant Dudha
Page 55

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

For M1 screen areas in Notification is shown below

Nishant Dudha
Page 56

Version No: 1.0

Page 56 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document


For M1 Screen structure for Notification is shown below

Individual screens are as follows

Nishant Dudha
Page 57

Version No: 1.0

Page 57 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 58

Version No: 1.0

Page 58 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 59

Version No: 1.0

Page 59 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 60

Version No: 1.0

Page 60 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 61

Version No: 1.0

Page 61 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 62

Version No: 1.0

Page 62 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 63

Version No: 1.0

Page 63 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document


For M1 Screen structure for Simplified View is shown below

For M1 Catalog and Catalog Profile is shown below.

Nishant Dudha
Page 64

Version No: 1.0

Page 64 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document


For M1 Priority Type is shown below.

For M1 Partner Determination Procedure is shown below.

Nishant Dudha
Page 65

Version No: 1.0

Page 65 of
133

Organisation: Tatra Trucks India Ltd


Project:

20

Page 66 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Assign Notification Types to Order Types

Sub-system: Maintenance Process

Transaction code: OIM3

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Notification Notification
types Assign Notification Types to Order Types
View Image:

Nishant Dudha
Page 66

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Notification Type

Description

Order Type

M1

General Maintenance

PM 01

M2

Breakdown Maintenance

PM 02

M3

Preventive Maintenance

PM 03

M4

Refurbishment Request

PM 04

M5

Calibration Request

PM 05

M6

Modification Request

PM 06

M7

External/AMC Service

PM 07

Required fields:
Notification Type
Notification Type Text
Type
Nishant Dudha
Page 67

Page 67 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 68 of
133

Impact

Configuration Design Document

Version No: 1.0

Order Type Text

Configuration pre-requisites:
Notification Type
Order Type
Rational for the configuration:

In this step, you can define which order type is created from which maintenance notification.
Note
You can work with different notification types and order types. In this step, you can allocate a
single order type to a single notification type in each case

Nishant Dudha
Page 68

Organisation: Tatra Trucks India Ltd


Project:

21

Page 69 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Catalog Profile

Sub-system: Technical Objects

Transaction code: OQN6

Owner:

NISHANT DUDHA

IMG
Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and Customer
Service Maintenance and Service Notification Notification Creation Notification Content Define
Catalog Profile
View Image

Nishant Dudha
Page 69

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Catalog Profile

Catalog Profile Text

PM

PM Catalog Profile

Nishant Dudha
Page 70

Page 70 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 71 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:

Catalog Profile
Catalog Profile Text

Configuration pre-requisites:
Nil
Rational for the configuration:
Create Catlog Profile for PM activities.
Catalog profile can be added to respective equipments which will only allow see the catalog list
attached in the catalog profile.

Nishant Dudha
Page 71

Organisation: Tatra Trucks India Ltd


Project:

22

Page 72 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Priority Type

Sub-system: Technical Objects

Transaction code: OIMP

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Notification Notification Processing
Response Time Monitoring Define Priorities
View Image:

Nishant Dudha
Page 72

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 73

Version No: 1.0

Page 73 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Priority type

Priority Type Text

PM

PM Priorities

Nishant Dudha
Page 74

Page 74 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 75 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:
Priority type
Priority Type Text

Configuration pre-requisites:
Nil

Rational for the configuration:


In this step you define the possible priority types.
For every priority type you can define your own priorities

In this step, you define the priorities for every priority type. The start date and the end date are
calculated automatically for the maintenance order or notification based on the chosen priority.
The date determination is calculated based on the current system date and the time when the
maintenance order or notification is created.
Note

The start/end dates are pure default values and can be overwritten by the user.

Nishant Dudha
Page 75

Organisation: Tatra Trucks India Ltd


Project:

23

Page 76 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Configure Order Types

Sub-system: Technical Objects

Transaction code: OIOA

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Configure Order Types
View Image:

Nishant Dudha
Page 76

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 77

Version No: 1.0

Page 77 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 78 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:

As per client requirements 6 order types defined for maintenance


Order type

Text

Settlement Profile

Release Immediately

PM01

General Maintenance Order

40

YES

PM02

Breakdown Maintenance order

40

YES

PM03

Preventive Maintenance Order

40

YES

PM04

Refurbishment Order

40

YES

PM05

Calibration Order

40

YES

PM06

Equipment modification Order

40

YES

PM07

AMC/External Service

40

YES

Required fields:

Order type
Text
Settlement Profile
Residence Time 1
Release Immediately
Configuration pre-requisites:

Order type
Settlement Profile

Rational for the configuration:


Nishant Dudha
Page 78

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 79 of
133

Impact

Configuration Design Document

Version No: 1.0

Nature Maintenance activities can be categories with Order types. The maintenance order
contains data regarding the planning and execution (Actual). The maintenance order would
capture the activity costs, material cost and External service cost. With this order type we can
retrieve required reports and it would be ease to do the analysis.

General Maintenance Order


Breakdown Order
Preventive Maintenance Order
Calibration Order
AMC/Service Order
Installation/dismantling Order

Nishant Dudha
Page 79

Organisation: Tatra Trucks India Ltd


Project:

24

Page 80 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Configure Number Ranges

Sub-system: Maintenance process

Transaction code: OION

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Configure Number Ranges
View Image:

Nishant Dudha
Page 80

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 81

Version No: 1.0

Page 81 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 82 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:

For Maintenance Order Internal Number ranges defined as given below


From number

To Number

Current Number

External Numbering

000400000000

000499999999

400000899

NO

Required fields:
Number Range Object
Group
Order Type

From number
To Number
Current Number
External Numbering
Configuration pre-requisites:
Order type

Rational for the configuration:


We can defined each order type will have the individual numbering system. This will be useful to easy
identification. Generally this scenario comes if different functional department using Maintenance Order.

Nishant Dudha
Page 82

Organisation: Tatra Trucks India Ltd


Project:

25

Page 83 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Assign Order Types to Maintenance Plants

Sub-system: Maintenance Process

Transaction code: OIOD

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Assign Order Types to Maintenance Plants
View Image:

Nishant Dudha
Page 83

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 84 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
PIPI

Name 1
Type
Manufacturing
1010
PM01
Plant, TTIL
Manufacturing
1010
PM02
Plant, TTIL
Manufacturing
1010
PM03
Plant, TTIL
Manufacturing
1010
PM04
Plant, TTIL
Manufacturing
1010
PM05
Plant, TTIL
Manufacturing
1010
PM06
Plant, TTIL
Manufacturing
1010
PM07
Plant, TTIL
Same is applicable for all remaining plants 1110

Nishant Dudha
Page 84

Order type text


General Maintenance Order
Breakdown Maintenance order
Preventive Maintenance Order
Refurbishment Order
Calibration Order
Equipment modification Order
AMC/External Service

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 85 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:

Planning Plant
Text
Order Type
Order type text
Configuration pre-requisites:

Planning Plant
Order Type
Rational for the configuration:
In this step, you can determine the allowed maintenance order types for the individual maintenance plants
Note
If you want to allow all order types for all maintenance plants, you must enter all order types per plant.

Nishant Dudha
Page 85

Organisation: Tatra Trucks India Ltd


Project:

26

Page 86 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Assign Inspection Types to Maintenance Order Types

Sub-system: Technical Objects

Transaction code: SPRO

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Assign Inspection Types to Maintenance Order
Types
View Image:

Nishant Dudha
Page 86

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 87 of
133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Plant
1010
1110

Type
PM05
PM05

Required fields:

Plant
Type
Inspection Type

Configuration pre-requisites:
Nishant Dudha
Page 87

Inspection Type
14
14

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 88 of
133

Impact

Configuration Design Document

Version No: 1.0

Plant
Type
Inspection Type
Rational for the configuration:
In this work step, assign the QM inspection types to the PM/SM types.
These settings result in an inspection lot being generated automatically for the corresponding order when a
PM/SM order is released. This inspection lot can then be processed further in the QM System, within the
framework of results recording and of a usage decision.
Example
You create a maintenance order that should result in the inspection several pieces of inspection or
measurement equipment. These pieces of test or measurement equipment are usually created a pieces of
equipment. In a maintenance task list, you have previously assigned inspection characteristics to one or more
operations. This can concern qualitative or also quantitative inspection characteristics.
During order release an inspection lot is created. This inspection refers to the inspection
characteristics and the test equipment of maintenance order.
Possible follow-up actions include:
1. Change of equipment status (Prerequisite: equipment is a PRT),
2. Measurement document recording in Plant Maintenance (Prerequisite:
Master inspection characteristics in the QM System and measuring points in the PM System
refer to the same, general class characteristic),
Change of inspection frequency or to the inspection interval if maintenance plans are used. (Change of cycle
modification factor in the maintenance plan).

Nishant Dudha
Page 88

Organisation: Tatra Trucks India Ltd


Project:

Page 89 of
133

Impact

Configuration Design Document

ID: PM 27
Sub-system: Maintenance
Process
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Define Default Value for Planning Indicator for Each Order Type
Transaction code: SPRO
NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Define Default Value for Planning Indicator for
Each Order Type
View Image:

Nishant Dudha
Page 89

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Configuration design:
Order type

Order planning Indicator

PM01

Unplanned Order

PM02

Unplanned Order

PM03

Planned Order

PM04

Planned Order

PM05

Planned Order

PM06

Unplanned Order

PM07

Planned Order

Required fields:

Order type
Nishant Dudha
Page 90

Version No: 1.0

Page 90 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 91 of
133

Impact

Configuration Design Document

Version No: 1.0

Select Planning Indicator


Configuration pre-requisites:

Order type
Rational for the configuration:
The order-planning indicator is used for selection and statistical analyses in the Plant Maintenance.
In this section, you can define a default value for each order type for the order-planning indicator.
Three order planning indicators are predefined by SAP:
Planned order: You should use this indicator for order types, for
which tasks can be anticipated.
Unplanned order: You should use this indicator for order types, for
which the necessity of the task cannot be anticipated, but where the
task must be performed immediately

Nishant Dudha
Page 91

Organisation: Tatra Trucks India Ltd


Project:

28

Page 92 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Create Default Value Profiles for External Procurement

Sub-system: Technical Objects

Transaction code: SPRO

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Create Default Value Profiles for External
Procurement
View Image:

Nishant Dudha
Page 92

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 93

Version No: 1.0

Page 93 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Configuration design:
Prof.

Profile Description

0000001

External Material

0000002

Procured Services

Nishant Dudha
Page 94

Version No: 1.0

Page 94 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 95 of
133

Impact

Configuration Design Document

Version No: 1.0

Required fields:
Profile
Cost Element
Purch. Org.
Purch Group

50657
1010-1080
depending upon
plant
Depending upon
plant
101,102,103,104

Material Group

Rational for the configuration:


In this step, you define the profiles for external procurement of services and materials. In the external
processing profile, you can store default values to generate purchase requisitions from maintenance orders.
In each profile, you can store a default value for:
1. Cost element account
2. Purchasing organization
3. Purchasing group
4. Material group
During external processing, a distinction is made between the external procurement of materials and the
allocation of complete order operation to vendors. Since both of these procurement processes generally
require different data for purchasing, for example, different purchasing groups or different cost element
accounts, you should also define different profiles for them. One should therefore define different profiles
for:
1. External processing or external assignment of complete order operations
2. Procurement of materials (material profile)
In a further step, one can assign two profiles to each user. The assignment of profiles can, of course, also be
made dependent on other parameters, such as plant or order type.

Nishant Dudha
Page 95

Organisation: Tatra Trucks India Ltd


Project:

Page 96 of
133

Impact

Configuration Design Document

ID: PM 29
Sub-system: Maintenance
Orders
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Create Default Value Profiles for General Order Data


Transaction code: SPRO
NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Create Default Value Profiles for General Order
Data
View Image:

Nishant Dudha
Page 96

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Configuration design:
Network Profile

0000001

Description

PM: Standard profile

Calculation key

Relationship View

Group

PM

Name

Network

Required fields:
Nishant Dudha
Page 97

Version No: 1.0

Page 97 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 98 of
133

Impact

Configuration Design Document

Version No: 1.0

Network Profile
Description
Calculation key
Relationship View
Group
Name
Configuration pre-requisites:
Group
Rational for the configuration:
In this step, one defines default values for further order data.
Recommendation
When making these settings, you should check carefully to see whether you have to maintain all parameters.
For order processing in the case of maintenance orders, you should:
1. Define a key word ID to select the user-defined fields from the task list and
2. Allocate a calculation key to calculate the capacity of the operation
For further settings
1. Define the view for the graphic display of the relationships
2. Define a key for the required graphics profile
3. Define a key for the explosion level for the graphic maintenance of standard networks
4. Allocate a key for the scheduling of orders which are allocated to WBS elements

Nishant Dudha
Page 98

Organisation: Tatra Trucks India Ltd


Project:

30

Page 99 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Settlement Rule: Define Time and Distribution Rule

Sub-system: Technical Objects

Transaction code: SPRO

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Settlement Rule: Define Time and Distribution
Rule
View Image:

Nishant Dudha
Page 99

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 100
of 133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Order type

Settlement rule type

Distribution rule sub order

PM01

Mandatory for Completion

No special handling of sub Orders

PM02

Mandatory for Completion

No special handling of sub Orders

PM03

Mandatory for Completion

No special handling of sub Orders

PM04

Mandatory for Completion

No special handling of sub Orders

PM05

Mandatory for Completion

No special handling of sub Orders

PM06

Mandatory for Completion

No special handling of sub Orders

PM07

Mandatory for Completion

No special handling of sub Orders

Required fields:
Nishant Dudha
Page 100

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 101
of 133

Impact

Configuration Design Document

Version No: 1.0

Order Type
Settlement Rule Type
Distribution Rule sub Order

Configuration pre-requisites:
Order Type
Rational for the configuration:
In this step, one defines default values for further order data.
Recommendation
When making these settings, one should check carefully to see whether one has to maintain all parameters.
For order processing in the case of maintenance orders, you should
1. Define a key word ID to select the user-defined fields from the task list and
2. Allocate a calculation key to calculate the capacity of the operation.
For operations and their graphic display.
1. Define the view for the graphic display of the relationships
2. Define a key for the required graphics profile
3. Define a key for the explosion level for the graphic maintenance of standard networks
Allocate a key for the scheduling of orders which are allocated to WBS elements

Nishant Dudha
Page 101

Organisation: Tatra Trucks India Ltd


Project:

31

Page 102
of 133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Default Order Types for Maintenance Items

Sub-system: Maintenance Processing

Transaction code: OIVA

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Define Default Order Types for Maintenance Items
View Image:

Nishant Dudha
Page 102

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 103
of 133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
PIPI
1010

Planner group
PM

PM Planner Gr Name
Plant Mnt Planner

Required fields:
Planning Plant
Planner group
PM Planner Group Name
Order type
Default order type text

Configuration pre-requisites:
Planning Plant
Planner group
Order type

Nishant Dudha
Page 103

Order type
PM03

Default order type text


Preventive Maintenance order

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 104
of 133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:


In this step you can specify default values for the creation of maintenance items for the maintenance order
types. Several maintenance-planning groups are active in a planning plant. Every maintenance-planning
group uses its own order types within regular maintenance. Allocate the order type to each maintenanceplanning group, which is most frequently used for maintenance items.
Requirements

The maintenance planning groups for the individual maintenance planning plants must be defined.
The individual maintenance order types must be defined.

Nishant Dudha
Page 104

Organisation: Tatra Trucks India Ltd


Project:

32

Page 105
of 133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Maintenance Activity Types

Sub-system: Maintenance Processing

Transaction code: OIO3

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Maintenance Activity type Define Maintenance
Activity Types
View Image:

Nishant Dudha
Page 105

Organisation: Tatra Trucks India Ltd


Project:

Page 106
of 133

Impact

Configuration Design Document

Configuration design:
Maint Act M Act Descrp

Created on 10
March 2006
Version No: 1.0

Warranty Case

Insurance Case

Not Selected
Not Selected

Not Selected

Not Selected

Not Selected

004

Inspection
Preventive
Maintenance
Repair
Refurbished Material

Not Selected

Not Selected

006

Investment

Not Selected

Not Selected

010

Warranty Case

Selected

Selected

011

Insurance case

Not Selected

Not Selected

012

Repair service

Not Selected

Not Selected

001
002
003

Required fields:
Nishant Dudha
Page 106

Not Selected

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 107
of 133

Impact

Configuration Design Document

Version No: 1.0

Maint Act
Maint Act Description
Warranty Case
Insurance Case

Configuration pre-requisites:
Maint Act

Rational for the configuration:


In this step, you determine the allowed maintenance activity types.
Recommendation
Define the level of detail of your maintenance tasks from the point of view of task processing and from

the point of view of cost follow-up for the maintenance history. The maintenance activity types are
stored in the header of each maintenance order.
The maintenance activity types are used in the PM Information System as a grouping
element for maintenance orders. Cost evaluations in the PM Information System can be performed
using maintenance activity types. The maintenance activity types should not be confused with activities in
the CO system (Activity type eg. ELC, MEC)
.

Nishant Dudha
Page 107

Organisation: Tatra Trucks India Ltd


Project:

Page 108
of 133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Assign Valid Maintenance Activity Types to Maintenance Order


Types

33

Sub-system: Maintenance
Processing
Owner:

Transaction code: OIO5


NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Function and setting for order types Maintenance Activity type Assign Valid
Maintenance Activity Types to Maintenance Order Types
View Image:

Nishant Dudha
Page 108

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 109
of 133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Order

Order Type Text

Maintenance Act

PM01

General Maintenance Order

001,003,005,007,008,013

PM02

Breakdown Maintenance Order

001,003,005,007,008,013

PM03
PM04

Preventive Maintenance Order


Refurbishment Order

001,003,005,007,008,013
001,003,005,007,008,013

PM05

Calibration Order

001,003,005,007,008,013

PM06

Equipment Modification

001,003,005,007,008,013

Amc /External Service

001,003,005,007,008,013

PM07

Required fields:
Order Type
Text
Maint Activity

Configuration pre-requisites:

Order Type
Maint Activity

Rational for the configuration:


In this step, you can determine which maintenance activities are allowed with which order types. Say, you
created an order type for replacements. You can now determine that only the maintenance activity 'UMBAU'
is allowed for replacements, all other activities should not be allowed for this special order type.

Nishant Dudha
Page 109

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 110

Version No: 1.0

Page 110 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 111 of
133

Impact

Configuration Design Document

Version No: 1.0

Sub-system: Maintenance Process

Title: Define Account Assignment Category/Document Type for


Purch Req Types
Transaction code: SPRO

Owner:

NISHANT DUDHA

ID: PM

34

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
General Data Define Account Assignment Category/Document Type for Purchase
Requisition
View Image:

Nishant Dudha
Page 111

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Version No: 1.0

Configuration design:

TEXT
30

Maint Order

Acc assgn type

Order

Acc Assgmt. Cat. Proj.

Proj. make-to order

Acc Assgmt. Cat. S. Order

Ind.cust w. KD-CO

Sales Doc. - Project

Indiv. Cust/project

Order Cat
Doc Type

Required fields:
Order Cat
Doc Type
Acc assgn type

Configuration pre-requisites:

Nishant Dudha
Page 112

Page 112 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 113 of
133

Impact

Configuration Design Document

Version No: 1.0

Doc Type
Acc assgn type

Rational for the configuration:


In this step you can define the account assignment category and purchasing document type for purchase
requisitions for maintenance and service orders.

For the document type, you can choose whether you always want to generate purchase requisitions
for standard purchase orders, contracts or other document types of the purchasing system.
Remember that this setting applies to all PM/SM order types.

Nishant Dudha
Page 113

Organisation: Tatra Trucks India Ltd


Project:

35

Page 114 of
133

Impact

Configuration Design Document

ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Define Control Parameters for Completion Confirmations

Sub-system: Technical Objects

Transaction code: SPRO

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
completion Confirmation Define Control Parameters for Completion Confirmations
View Image:

Nishant Dudha
Page 114

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 115

Version No: 1.0

Page 115 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 116

Version No: 1.0

Page 116 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 117

Version No: 1.0

Page 117 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 118

Version No: 1.0

Page 118 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 119

Version No: 1.0

Page 119 of
133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 120
of 133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:

Order Cat - 30
Plant
PM01

PM02

PM03

Order Type

Default Val

General
Maintenance
Order
Breakdown
Maintenance
Order
Preventive
Maintenance
Order

Final confir, Post


open doc, Propose
Dates & activity
Final confir, Post
open doc, Propose
Dates & activity
Final confir, Post
open doc, Propose
Dates & activity
Final confir, Post
open doc, Propose
Dates & activity
Final confir, Post
open doc, Propose
Dates & activity
Final confir, Post
open doc, Propose
Dates & activity
Final confir, Post
open doc, Propose
Dates & activity

PM04

Refurbishment
Order

PM05

Caliberation
Order

PM06

Equipment
modification
Order

PM07

AMC/External
Service Order

Required fields:
Plant
Order Type
Default Val
Mat movement
Logs / Work flow
Configuration pre-requisites:

Plant
Order Type
Nishant Dudha
Page 120

Mat mvmnt

Logs / Work flow

For all
components

Goods Movement

For all
components

Goods Movement

For all
components

Goods Movement

For all
components

Goods Movement

For all
components

Goods Movement

For all
components

Goods Movement

For all
components

Goods Movement

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 121
of 133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:

You can set control parameters for each order type. Using the completion parameters, you define:
Proposed data Goods Movement
All Components
The completion confirmation processes are controlled

Nishant Dudha
Page 121

Organisation: Tatra Trucks India Ltd


Project:

Page 122
of 133

Impact

Configuration Design Document

ID: PM 36
Sub-system: Maintenance
Process
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Maintain Scheduling Types


Transaction code: OIOT
NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Scheduling Maintain Scheduling Types
View Image:

Nishant Dudha
Page 122

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 123
of 133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
S No

Description

Forwards

Backwards
Only Cap
Reqrmnt
Current
Date
Forwards in
Time
Backwards
in Time

3
4
5
6

Forward

Backward

Cap. Rq

Current Date

Date/Time

YES
YES
YES
YES
YES

YES
YES

Required fields:
Description
Assignments

Nishant Dudha
Page 123

YES

Organisation: Tatra Trucks India Ltd


Project:

37

Page 124
of 133

Impact

Configuration Design Document


ID: PM

Created on 10
March 2006
Version No: 1.0

Title: Set Scheduling Parameters

Sub-system: Maintenance Process

Transaction code: OPU7

Owner:

NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Maintenance and service orders
Scheduling Set Scheduling Parameters
View Image:

Nishant Dudha
Page 124

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 125

Version No: 1.0

Page 125
of 133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 126

Version No: 1.0

Page 126
of 133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 127

Version No: 1.0

Page 127
of 133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Impact

Configuration Design Document

Nishant Dudha
Page 128

Version No: 1.0

Page 128
of 133

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 129
of 133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Plant

Order
Type

1010

PM01

1010

PM02

1010

PM03

1010

PM04

1010

PM05

1010

PM06

1010

PM07

Prod
Scheler

*
*
*
*
*
*
*

Adjust Dates

Adjust Dates, adjust dep reqmts


to operation dates
Do not adjust basic dates, dep
reqmts to operation dates
Do not adjust basic dates, dep
reqmts to operation dates
Do not adjust basic dates, dep
reqmts to operation dates
Do not adjust basic dates, dep
reqmts to operation dates
Adjust Dates, adjust dep reqmts
to operation dates
Adjust Dates, adjust dep reqmts
to operation dates

Scheduling type

Forward, Auto
scheduling
Forward, Auto
scheduling
Forward, Auto
scheduling
Forward, Auto
scheduling
Forward, Auto
scheduling
Forward, Auto
scheduling
Forward, Auto
scheduling

Start in
past

Required fields:
Plant
Order Type
Prod Scheduler
Adjust dates
Scheduling Type
Start in Past

Configuration pre-requisites:
Plant
Order Type
Scheduling Type
Rational for the configuration:

In this step, you can set scheduling parameters for every maintenance order type and every
Nishant Dudha
Page 129

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 130
of 133

Impact

Configuration Design Document

Version No: 1.0

maintenance plant.
In addition to the scheduling type, you can determine further scheduling parameters:
Automatic scheduling
Display scheduling log automatically after scheduling
Maximum number of days for start in the past
Automatic adjustment of the start/finish dates
Shift order indicator
Scheduling to incorporate breaks (breaks at the work center are taken into account when
scheduling is created

Nishant Dudha
Page 130

Organisation: Tatra Trucks India Ltd


Project:

Page 131
of 133

Impact

Configuration Design Document

ID: PM 38
Sub-system: Maintenance and Service
Processing
Owner:

Created on 10
March 2006
Version No: 1.0

Title: Assign Value categories to Maintenance Cost key figure


Transaction code: SPRO
NISHANT DUDHA

Menu path:
IMG Implementation guide for R / 3 Customisation (IMG) Plant Maintenance and
Customer Service Maintenance and Service Processing Completion Confirmations
Assign Value categories to Maintenance Cost key figure
View Image:

Nishant Dudha
Page 131

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 132
of 133

Impact

Configuration Design Document

Version No: 1.0

Configuration design:
Cost Key Figures

Value Category

Key figure Desc.

Value Category Discription

IAMATKOSE

440

Internal Material

Material Consumed Int / Ext

IADIENKOS

450

Services

AMC Service - PM

IADIENKOS

460

Services

Sublet Repair - CS

IAPERKOSE

470

Internal employees

Internal Labour

Required fields:
Cost Key Figures
Value Category

Configuration pre-requisites:
Defining Value category
Assigning Cost element w.r.t Value category

Nishant Dudha
Page 132

Organisation: Tatra Trucks India Ltd


Project:

Created on 10
March 2006

Page 133
of 133

Impact

Configuration Design Document

Version No: 1.0

Rational for the configuration:

In this section, you can allocate value categories to PM cost key figures predefined by SAP. The value
category generally groups several cost element accounts together. Which value categories are grouped
together under which key figure depends on your chart of accounts.
Recommendation
You should make sure that the correct allocations are made when starting your production system, since
subsequent changes to the allocation influence the updating of the key figures, which may possibly require
you to spend time setting up the key figure system again

Nishant Dudha
Page 133