aapl plant maintenance

8/10/2019 AAPL Plant Maintenance

http://slidepdf.com/reader/full/aapl-plant-maintenance 1/161

Configuration Manual

AAPL Plant Maintenance

vCentric Technologies & Adhunik Group

Plant Maintenance

Configuration Guide

Presented To

Adhunik Alloys & Power Limited

Adhunik Group Of Companies

By

43/A, Road No. 12, M.L.A. Colony, Banjara Hills, Hyderabad – 500034, INDIA

Tel: +91 40 4455 9999, Fax: +91 40 4455 9900, Website: www.vcentric.com

http://www.vcentric.com/









Introduction

PurposeThis document describes the Configuration settings of SAP Plant Maintenance Module

Implementation for AAPL (Adhunik Alloys & Power Limited). The purpose of this

configuration document is to document the final configuration settings made for L SAP

R/3 system as per their business requirements.

Scope

This document covers the configuration of SAP-Plant Maintenance module for Adhunik

Alloys & Power Limited.






Configuration Settings

1. Enterprise Structure 1.1 Maintenance Plant

T.Code SPRO

Menu Path IMG Enterprise StructureDefinitionLogistics

GeneralDefine Copy, Delete, Check plant Define Plant

General Explanation:

In Logistics a plant is an organizational unit for dividing an enterprise according to

production, procurement, maintenance, and materials planning.

A Plant can be defined as a maintenance planning plant

Requirement:

Maintenance plant is required for Orissa Manganese & Minerals Limited organization,

to incorporate maintenance equipments and their activities.

Configuration:






1.2 Define Location

T.Code SPROMenu Path IMG Enterprise StructureDefinitionLogistics General

Define Location


A location allows a plant to be classified according to spatial or situation criteria.

Locations are used for informative assignment only. User can only use locations to

structure a match code or as parameter criteria in reporting.

You cannot derive any functionality from locations in terms of hierarchies, etc.

Requirement:

Locations are mainly required to get information and reports to specifically for that

area. This is also required to monitor different history, installations, cost, break downs,Preventive schedule etc location wise. It can be used to track information for Assets

also.Configuration:






1.3 Maintain Maintenance Planning Plant

T.Code SPROMenu Path IMGEnterprise Structure Definition Plant Maintenance

Maintain Maintenance Planning Plant


The Maintenance planning plants must first have been created as normal Plants. If the

maintenance planning is carried out centrally for several plants in one plant if from a

PM Perspective each plant stands alone, then each plant is also its own planning plant.

A plant in which maintenance tasks are planned & prepared.

Requirement:

Maintenance plants that do not plan their maintenance tasks are assigned to planning

plants. Planning is performed for the maintenance plants in the planning plants.

Configuration:






1.4 Assign Maintenance planning Plant

T.Code SPROMenu Path IMG Enterprise Structure Assignment Plant Maintenance

Assign Maintenance planning plant to Maintenance plant


User must assign a planning plant to each maintenance plant.

A maintenance plant, to which an alternative planning plant is assigned, can not be a

planning plant.

Requirement:

Maintenance plant can not make maintenance plans and its not prepare maintenancetask lists. To prepare Maintenance tasks, plans and activities maintenance planning

plant must assign to maintenance plant.

Configuration:






2.0 Master data in Plant Maintenance & Customer Service

2.1 Basic Settings

2.1.1 Define Permit Categories

T.Code SPRO

Menu Path IMG Plant Maintenance & Customer Service Master data in

Plant Maintenance & Customer service Basic Settings

Permits


In this customizing activity we can define the permit categories. These permit

categories are used to group the permits together. Every permit must be assigned to a

permit category.

Requirement:

In AAPL, they are using different types of permit categories and different types of

permits. Based on their requirement permit categories are defined.

Configuration:






2.1.2 Measuring points, Counters & Measurement Documents

2.1.2. A Make System Settings for Measuring points & M. Documents

T.Code SPRO



Measuring points, Counters & Measurement Documents Make

system settings for measuring points & M.documents.


In this IMG activity user can make global system settings for measuring points, counters

and measurement documents. At the moment there is just one system setting in this

IMG activity:Generation of interval documents for the counter reading transfer.

Requirement:

Generation of interval documents for the counter reading transfer. The counter reading

transfer does not generate any more individual documents.

Configuration:






2.1.2. B Define Measuring point categories

T.Code SPROMenu Path IMG Plant Maintenance & Customer Service Master data in


Measuring points, Counters & Measurement Documents Define

Measuring point categories


User always need measuring point categories if you want to record measurement or

counter readings for equipment or functional location measurement point categories

define whether a measurement item is unique.

Requirement:To identify the measuring points and counters at different equipments and functional

location.

Configuration:






2.1.2. C Create number ranges for Measuring Points

T.Code IK09Menu Path IMG Plant Maintenance & Customer Service Master data in


Measuring points, Counters & Measurement Documents Create

number ranges for measuring points


A range of numbers that you can assign to business objects (or their sub-objects) of the

same type.

Each number range has one or more number range intervals and a number assignment

type.

There are the following types of number assignment: Internal -

When storing a data record, the R/3 System assigns a sequential number, which

lies in the relevant number range interval.

External -

The number is assigned by the user or by an external system, both of which must

ensure that the number lies in the relevant number range interval.

Requirement:

To creates sequential measuring points on equipment or functional location for

measuring the measurement readings or counter readings.

Configuration:






2.2.0 Technical Objects

2.2.1 General Data

2.2.1.A Define Types of Technical Objects

T.Code SPRO


Plant Maintenance & Customer service Technical Objects

General data Define Types of Technical Objects


A division of a technical object for precise descriptions.

Example

Category of technical object: "Fleet objects" Type of technical object: "Heavy goods vehicle," "Automobile," "Fork-lift

truck"

Requirement:

This allows pieces of equipment that have the same use. Its helps to group instruments

and equipments. Assign a key and a description for each type of technical object.

Configuration:






2.2.1.B Define Plant sections

T.Code SPRO

Menu Path IMG

Plant Maintenance & Customer Service

Master data inPlant Maintenance & Customer service Technical Objects

General data Define Plant Sections


The plant section enables you to subdivide the maintenance plant from the point of

view of production responsibility. The person responsible for the plant section is the

contact for coordination between production and plant maintenance.The plant section can be used for evaluation purposes.

Every piece of equipment and functional location can be assigned to a plant section.

Requirement:

To identify or install Machines or sets of machines those are represented in the system

as pieces of equipment or functional locations in plant sections. To indicate the place for

which a maintenance task was requested with the plant section






Configuration:






2.2.1.CDefine Planner groups



General data Define Planner Groups


A group of employees responsible for planning and processing maintenance tasks in a

plant. Depending on the size and structure of your company, a maintenance planning

group may be an individual department (for central work preparation), a group of

skilled craftsmen or a workshop.

Every piece of equipment and functional location can be allocated to a maintenanceplanning group.

Maintenance planning groups can also be used for evaluation purposes.

Requirement:

Maintenance planner groups are required for processing maintenance tasks

Configuration:






2.2.1.D Define ABC Indicators



General data Define ABC Indicators


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

evaluations.

The ABC indicator can be entered in equipment as well as functional locations.

Requirement:These ABC indicators will help the user to easily sort out the equipments and functional

location by the form of categories. These are help in selection criterion.

Configuration:






2.2.1.E Define Object Information Keys

T.Code SPRO



General data Define Object Information Keys


In this step we can define the object information keys an object information key can be

assigned to the following object types.

Functional location categories

Equipment categories

Maintenance & Service notification types

Maintenance & Service order types

Via the parameterization of the object information key, you determine the data of a

technical object (equipment, functional location, structure) that is shown in a special

information window.

The object information also contains history data from the PM Information System and

data from the notifications and orders executed.

Requirement:

To get the earlier instances of damage and number of days required to process theproblem, earlier notifications and / or orders created or completed for the technical

object. Maintenance plans for the technical object.

Configuration:






2.2.2 Functional Location

2.2.2.A Create Structure Indicator For Functional Location

T.Code OIPK



Functional Locations Create Structure indicator for Functional

Location


Structure indicator is a key for the edit mask.

The characters allowed

Numbers Edit mask N Letters Edit mask A

Numbers and letters Edit mask X

Special characters and numbers and letters Edit mask S

Once a functional location already exists for a particular structure indicator,

you receive a warning when you change the edit mask.

Requirement:

To determine the generic structure of the location number & Make the hierarchy levels

in the location structure visible in the location number

Configuration:






2.2.2.B Define Category of Functional Location

T.Code SPRO



Functional Location Define category of Functional Location


In this step we can define “N“number functional location categories.An indicator that lets we differentiate functional locations according to how they are

used.

Each location category required in the system is described using parameters. The

number of functional location categories in a system depends on the number of

parameter constellations required.

Requirement:

To define the following parameters.

Status Profile

Measuring point Categories

Field Selection

Whether change documents are created

Configuration:






2.2.3.B Define Number Ranges

T.Code OIEN


Plant Maintenance & Customer service Technical Objects EquipmentEquipment CategoriesDefine Number Ranges


In this step, define the number assignment category in the step equipment categories.

Must be allocating a unique number for each equipment master record.

We have the following options:

internal number assignment

In this case, the SAP System assigns the numbers.

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.

Requirement:

Based on AAPL requirement External number is assigned to Equipment category “B” “C”

and “Q”. They like to give their own numbering style. Different number ranges have






been allotted to the equipment categories. For “Q” & “E” category internal number

ranges also assigned. When users receipt the material system creates internal

equipment number based on customization as per requirement.

Configuration:

2.2.3.C Usage History Update

T.Code SPRO



Equipment

Equipment usage period

Usage History Update


A period of time during which, no changes have occurred to location, maintenance, or

sales data for a piece of equipment. Changes to certain master data fields will be logged

in the usage history.






Using the usage history define that changes to the account assignment data (e.g. cost

center) are always documented in the system via the usage history. This means that a

change to the cost center in the equipment master record will always be documented bythe system in such a way that you can display the equipment master record with the

data contents at the time of the change to the cost center at any time.

Requirement:

This is required for storing the usage times of equipments at different functional

locations.

Configuration:

2.2.3.D Define Installation at Functional Location

T.Code SPRO



Equipment Equipment usage period Define Installation at

Functional Location


In this step we define for each equipment category, whether the installation of a piece of

equipment is allowed at a functional location. We have the option of defining for each






equipment category whether the installation of equipment at a functional location is

allowed.

Requirement:

All the above equipment categories are allowed to install on functional locations

Configuration:

2.2.3.E Assign User Status Profile To Equipment Categories

T.Code SPRO



Equipment Assign User Status Profile to Equipment Categories


Here we can allocate a status profile to each equipment category. We should only usedifferent status profiles for the individual equipment categories when this is necessary

from the view point of our processes.

Requirement:

For AAPL no more user status profiles are customized. Only standard User status

profiles are used.






Configuration:

2.2.3.F Assign Partner Determination Procedure to Equipment Category

T.Code OIEV


Plant Maintenance & Customer service Technical Objects Equipment Assign Partner Determination Procedure to

Equipment Category.


A plan that specifies how, when, and from what sources the system determines partners

in a business transaction, what partner functions are mandatory or suggested in this

transaction, and what rules apply to these partner functions.

Requirement:

For sub equipments purpose different equipment categories are defined based on theAAPL requirement.

Configuration:






2.2.3.G Allow Multilingual Text Maintenance for Each Equipment Category

T.Code OIEV

Menu Path IMG Plant Maintenance & Customer Service Master data inPlant Maintenance & Customer service Technical Objects

Equipment Allow Multilingual Text Maintenance for Each

Equipment Category.


In this step we can define for each equipment category whether the maintenance of

equipment texts is allowed in several languages.

Requirement:

SAP Standard settings are adopted.

Configuration:






2.2.3.H Define Field Selection for the Equipment Master Record.

T.Code OIAD / OIAFMenu Path IMG Plant Maintenance & Customer Service Master data in


Equipment Define Field Selections for The Equipment master

record.


In this step, you can define the field selection for the equipment master record.

The fields offered here are common data fields for functional locations and equipment.

For this reason you should always take account of the affected values.

These fields are found in the following objects:

Equipment Functional location

Reference functional location

In the second setting, you can define the field selection for the fields which are only

found in the equipment master record.

Requirement:

To search out the equipments from the data base system in different way by using

different master data information which are given by the users.

Configuration:






All the standard SAP fields are taken as input fields. Equipment category code as

mandatory field.






2.2.3.I Define Field Selection for Multi-Level List Displays of Equipment

T.CodeMenu Path IMG Plant Maintenance & Customer Service Master data in


Equipment Define Field Selection for Multi-Level List Displays

of Equipment


In this step you maintain the default settings for the multi-level list display for

equipment.

In the subordinate menu options you can determine the field selection for all objects

which are displayed via the list display of a piece of equipment.

The field selection that you define here determines the standard field selection for yourclient.

Requirement:

Standard settings are adopted. These settings are help to view the master data

information at different levels with sequential steps. For all the below settings standard

SAP settings are used.

Configuration:






2.2.4 Serial Number Management

2.2.4.A Define Serial Number Profile

T.Code OIS2



Serial Number Management Define Serial Number Profile


A serial number profile must be assigned to each material that is to be serialized. This

assignment is made at plant level in the material master record. This means that youcan assign a separate serial number profile to a material for each plant. However, a

material can have a mandatory serial number in one plant but not in others.

Requirement:

In AAPL, Electrical & Instrumentation department maintain the serial numbers for their

Motors, Gearboxes, thermocouples & instruments for this purpose serial number

management was activated.






Configuration:






2.2.4.B Define Default Equipment Categories for Serial Numbers



Serial Number Management Define Default Equipment

categories for Serial Numbers


In this step, we define a central default equipment category for the serial number

management.

This equipment category is proposed by the system if the system cannot find an

equipment category in the serial number profile for a serialization operation.

Requirement:

As per the AAPL requirement, Production Resource Tools (Equipment Category “P” )

defined. All the Production resource tools are defined under equipment category “P”.

Configuration:






2.3.0 Bill of Material

2.3.1 Control Data for Bills of Material

2.3.1.A Set Modification Parameters

T.Code OICB


Plant Maintenance & Customer service Bills Of Materials

Control Data for Bills Of Materials Set Modification Parameters


The modification parameters set here are valid both for material BOMs and equipment

BOMs. This is, as a rule, a one-time setting which should not be changed once the

system is productive.The following settings are supplied in the standard system:

validity maintenance and EC management are active

the current date is proposed

Requirement:

As per the AAPL requirement, for maintaining the material BOM and equipment BOM,

these BOM configurations are done.

All Standard SAP settings are adopted.

Configuration:






2.3.1.B Define BOM Status

T.Code OICH



Control Data for Bills Of Materials Define BOM Status


A tool used to control processing of a BOM in different application areas.

SAP recommends that you accept the settings defined in the standard system. In this

case, no action is required on your part. The BOM status controls other activities indifferent areas (for example, engineering, costing, material requirements planning).

Requirement:


Configuration:






2.3.1.C Define Default Values

T.Code OICCMenu Path IMG Plant Maintenance & Customer Service Master data in


Control Data for Bills Of Materials Define Default Values


This menu option allows you to define the following default values for the maintenance

of BOMs:

Base quantity

BOM status

Size unit Unit of measure for variable-size part

The default values that you enter here are valid both for material BOMs and for

equipment BOMs.

Requirement:


Configuration:






2.3.2

General Data

2.3.2.A BOM Usage / Define BOM Usage

T.Code OICD



General Data BOM Usage Define BOM Usages


When you maintain BOM usage, you define the user departments (production, plant

maintenance, engineering and so on) by which a BOM of a particular usage can be used.

Note

BOM components that are needed by several user departments (for example,

production and plant maintenance) can also be used jointly in material

BOMs.

Once BOMs exist for a BOM usage, the usage can no longer be deleted.

Furthermore, the usage can also only be changed to a limited extent.

The indicator that shows the usage is relevant to plant maintenance shouldonly be used when this is the case.

Requirement:

Standard settings are adopted.






Configuration:

2.3.2.B

Define Default Values for Item Status

T.Code OICE



General Data BOM Usage Define Default values for Item

Status


The item status is proposed in BOM maintenance when you create new BOM items.

Bear in mind that the status spare part indicator refers to the production BOMS and not

to the maintenance BOMs. This means that you may not use the item status spare part

indicator in maintenance BOMs.

In the case of maintenance BOMs, you should always check the indicator maintenance

relevant.

Configure the default values as necessary for the item status of the individual BOM

usages.

Requirement:


Configuration:






2.3.2.C

Define Copy Default values for Item Status

T.Code OICF



General Data BOM Usage Define Copy Default Values for

Item Status


If you want to use the BOMs of other user departments as a reference when creating

maintenance BOMs, you can specify in this menu option that the item status of the

copied item is to take on certain features for maintenance BOMs.

If you only use the item status 'PM' for maintenance BOMs, you do not need to maintain

default copy values, as the system copies all the item statuses that can be copied on the

basis of the BOM usage, which in this case is simply only the item status 'PM'.

Requirement:

As per SAP Recommendation Standard settings are adopted with out changing any

thing.

Configuration:






2.3.2.D Define Valid Material Types for BOM Header

T.Code OICG



General Data BOM Usage Define Valid Material Types for

BOM Header


We can define whether BOMs can be created for materials of a particular type for each

BOM usage in this menu option.

We have the option of making the material type entry.

When we create a new BOM, the material type is checked as follows:

The entries that are fully qualified (those not masked) are checked first. The

masked entries are checked last.

Our choice of control indicator determines whether the entry is allowed or

not

Requirement:

SAP Standard Settings are adopted as per sap recommendation.

Configuration:






Remaining Item Data settings and Determination of Alternative bills of Material aremaintained with standard SAP settings only. Nothing is changed in these customization

areas.

3.0 Maintenance Plans, WorkCenters, Task Lists and PRTs

3.1 Maintenance Plans

3.1.1 Set Maintenance Plan Categories

T.Code SPRO

Menu Path IMG Plant Maintenance & Customer Service Maintenance

Plans, WorkCenters, Task Lists and PRT’s Maintenance Plans

Set Maintenance Plans Categories


In this IMG activity, we can make the settings for maintenance plan categories.

We can use the maintenance plan categories to control different business processes for

maintenance planning.

The functions for maintenance plans can be used, for example, for generating:

Maintenance- and service notifications

Maintenance- and service orders

Service entry sheets (purchasing) Service procurement

Inspection lots

Since this involves different business processes, different screens are also required.

We recommend that the screen numbers should not be changed.

Reference object is understood to cover the material, equipment, functional location or

other objects, for which you create the maintenance plan.






Requirement:

IN AAPL, they are having different plans as per their business processes. Accordingbusiness process they required different reference objects in maintenance plans with

different call objects.

Configuration:

3.1.2 Define NumberRanges for Maintenance Plans

T.Code IP20



Define Number Ranges for Maintenance Plans


In this step, we define the type of number assignment for the maintenance plans. Every maintenance plan must be identified by a unique number.

We can define a number range for both external and internal number assignment for

maintenance plans.

For this, we have the following options:

Internal number assignment

In this case, numbers are assigned by the SAP System. A number range must be

selected for internal number assignment.






External number assignment

In this case, the user assigns the numbers manually. A number range must be

selected for external number assignment

Requirement:

A unique number must identify every maintenance plan. Here Internal Number ranges

are assigned for all the maintenance plan categories with different number intervals for

easy identification by seeing the number series.

Configuration:

3.1.3 DefineNumberRanges for Maintenance items

T.Code IP21

Menu Path IMG Plant Maintenance & Customer Service MaintenancePlans, WorkCenters, Task Lists and PRT’s Maintenance Plans

Define Number Ranges for Maintenance Items


A description of the maintenance and inspection tasks required at regular intervals for

maintenance objects.






We can specify the reference objects directly in the maintenance item or by using an

object list.

We can describe the required activities in a maintenance task list that you assign to themaintenance item.

In the standard SAP R/3 System, the number range is defined with internal number

assignment.

In the standard system, there are two number ranges:

01 for internal number assignment

02 for external number assignment

Requirement:

A Unique number must identify every maintenance item. Here Internal number ranges

are assigned for maintenance items.Configuration:

3.1.4 Define Sort Fields for Maintenance Plan

T.Code SPRO


Plans, Work Centers, Task Lists and PRT’s Maintenance Plans

Define Sort fields for Maintenance Plan


In this step, you can define sort fields for the maintenance plan.

We can assign the sort field in the maintenance plan, which facilitates the selection and

grouping of maintenance plans.

We should consider and assign this sort field from the point of view of grouping and

selection, particularly for maintenance plan scheduling.






Requirement:

For sort out the required maintenance plan from the “N” number of maintenance plans

list.

Configuration:AAPL Pending

3.1.5 Define Field Selection for Maintenance Plan

T.Code OIW0

Menu Path IMG

Plant Maintenance & Customer Service

MaintenancePlans, WorkCenters, Task Lists and PRT’s Maintenance Plans

Define field selection for Maintenance Plan


We can define the field selection for maintenance schedule overview lists for the

maintenance plan data in this step.






The fields that you choose at this point are used for the field selection. Here we can

define the layout of maintenance lists or the structure display by numbering the fields

which should appear in the lists or by marking them as 'suppressed'.Numbering fields defines the sequence in the list, so that the field with the number '1'

appears first in the list, the field with the number '2' second, and so on.

Requirement:

Standard SAP settings are adopted. Nothing changed in standard settings.

Configuration:






3.1.6 Configure Special Functions for Maintenance Planning

T.Code SPROMenu Path IMG Plant Maintenance & Customer Service Maintenance


Configure Special Functions for Maintenance Planning


In this IMG activity we can configure special functions for maintenance plans. We can

use this indicator to activate additional functions in the multiple counter plans. The

additional functions are also available to pre-existing multiple counter plans after

saving. Without this enhancement, only one "cycle set" (that is, a combination of various

cycles) can be defined in a plan. This is used to calculate all the schedules, and generatesa corresponding maintenance call object for all the maintenance items for each

schedule.

The enhancement allows the maintenance of multiple cycle sets in one plan. Thus you

can define different cycle sets, and thus cycles, for calculating the dates within a plan.

You can use the assignment between cycle sets and the maintenance item to control

that only certain maintenance items generate a call object for certain dates.

Requirement:

As per the AAPL requirement, some of the equipments required maintenance plans at

different intervals with different cycle sets. That type of cycle sets are customized by

using this type of customization.

Configuration:






3.3.0 Work Centers

3.3.1 General Data

3.3.1.A Define WorkCenter Types and Link to Task List Application

T.Code OIZA


Plans, Work Centers, Task Lists and PRT’s Work Centers

General Data Define Work Center Types and Link to Task List

Application


In this IMG activity we define the work center types. Every work center is assigned to a

work center type during creation, which determines the following: The allowed task list application (for example, plant maintenance,

production)

The screen sequence (for example, basic data, capacity data)

The field selection

Whether changes to the work center should be documented with change

documents.

In the standard system, task list application I is used for task lists in plant maintenance.

Requirement:

Standard SAP settings are adopted.

Configuration:






3.3.1.B Define Field Selection

T.Code OPFA


Plans, Work Centers, Task Lists and PRT’s Work Centers

General Data Define Work Center Types and Link to Task List

Application


In this step, we can select fields for the following screens:

Task lists

Header screens

Sequence screens

Operation screens

PRT overview

PRT details

For each screen group we define the modifiable and influencing fields: For modifiable

fields, we use an indicator to determine how the individual fields are displayed on the

screen:

Field is ready for input (standard setting)

Field requires an entry (required entry)

Field is display only

Field is hidden

Field is highlighted

If, for example, we determine for the list and detail screens for confirmation within the

network that "work center" is a required entry, we must maintain the work center in all

confirmations. For the influencing fields, you determine how the modifiable field is






displayed on the screen, depending on a value (for example, "work center" is a required

entry for a certain order type).

Requirement:

As per requirement standard settings are adopted. Nothing changed in standard

settings.

Configuration:

3.3.1.C Set Parameters

T.Code OP7B


Plans, WorkCenters, Task Lists and PRT’s Work Centers

General Data Set Parameters


In this menu option, we define the parameters. We assign these parameters to thedefault value key.

The most commonly used default value in Plant Maintenance is the "duration of

internal processing".

Under certain circumstances, you must also be able to plan other default values such as

"personnel times" and/or "cleaning times".






Requirement:

As per requirement standard parameters are used for AAPL.

Configuration:

3.3.1.D Define Standard Value Keys

T.Code OIZ2


Plans, WorkCenters, Task Lists and PRT’s Work Centers General Data Define Standard Value Keys


The standard values are planned values for calculating the execution time maintenance

task list and service task list. Maintenance processing and service processing only take

into account the duration of an operation for the scheduling of the orders. For work






centers that are used by maintenance or service only, use the standard value key for

which no standard values are defined.

Requirement:

Standard settings are adopted.

Configuration:

3.3.1.E Define Employees Responsible for Work Centers

T.Code SPRO



General Data Define Employees Responsible for Work Centers


In this key, we can store the person or the group of people responsible for maintaining

the master data of a particular work center.

This area of responsibility does not refer to possible planning activities but to the

management of the work center in the sense of parameter maintenance instead.

Requirement:






To define responsible person for each work center to handle all the activities which are

related to maintenance?

Configuration:

3.3.2 Task List Data

3.3.2.A Define Task list Usage Keys

T.Code OIZD



Task list Data Define Task List Usage Keys


In this IMG activity, we can specify the task lists in which a work center or production

resource/tool may be used. For example, we can categorize work centers into

maintenance work centers or inspection work centers according to their relevance and

their usage in maintenance plans or inspection plans.

We can also allow multiple, cross-application uses in any combination.

Requirement:

SAP Standard settings are adoptedas per the business requirement.






Configuration:






3.3.2.B Maintain Control Keys



Task list Data Maintain Control Keys


Control keys are assigned to every work center in the master data screen "Default

values".

Use the control key of the operation to determine

the business functions we want to carry out

How we want to deal with the operation.

Requirement:

For calculating capacity planning, costing, external processing, completion confirmation

& general activity of all operations which are done in maintenance orders.

Configuration:






Plant Maintenance Internal Control Keys:

The following settings are adopted in Internal Control keys (Standard SAP Settings)

Plant Maintenance External Services Control Keys:






3.3.2.C Configure Screen Sequence for Work Center

T.Code OIZUMenu Path IMG Plant Maintenance & Customer Service Maintenance


Task list Data Configure Screen Sequence for WorkCenter


In this step, we determine the screen selection for each work center category.

We can control the following parameters the sequence of the screens by means of the

consecutive number, for example:

Basic data

Default values

Capacities

Scheduling data

Cost center allocation

Technology, etc.

The need to maintain data when creating for example, allocation of a cost center is

mandatory

Requirement:

SAP standard settings are adopted.

Configuration:






3.4 Task Lists

3.4.1 General Data

3.4.1.A Maintain Task List Status

T.Code OIL1


Plans, WorkCenters, Task Lists and PRT’s Task List General

Data Maintain Task List Status


In this step we define the possible status of a task list. The status of the task list

determines in which other application areas the respective task list may be used. The

status controls the following functions: Release for costing

Release for use in the order

Requirement:


Configuration:






3.4.1.B Define Task List Usage

T.Code OIL1Menu Path IMG Plant Maintenance & Customer Service Maintenance


Data Define Task List Usage


We can define your task list usages in this step. With the task list usage we can define

different categories of task lists for Plant Maintenance. We can use the different task list

usages for analysis purposes.In the standard SAP R/3 System, task list usage '4' is

supplied for Plant Maintenance. This task list usage covers all maintenance

requirements.

Requirement:


Configuration:






3.4.1.C Configure Planner Group

T.Code SPRO



Data Configure Planner Group


In this step, we can determine the planner groups for each plant. A planner group is

responsible for maintaining task list data.Key which identifies the planner group

responsible for maintaining the task list.

Requirement:

As per the AAPL requirement different task list planner groups are defined.

Configuration:






3.4.2 Control Data

3.4.2.A Define NumberRanges for General Maintenance Task Lists

T.Code OIL4


Plans, WorkCenters, Task Lists and PRT’s Task List Control

Data Define Number Ranges for General Maintenance Task

Lists


We can determine the type of number assignment for the general maintenance task lists

in menu option "General maintenance task list number ranges". Here we have two

options: Internal number assignment

In this case, the SAP System assigns the numbers.

External number assignment

In this case, the user assigns the numbers.

In each case, we can set up an internal and external number range for the general

maintenance task lists.

Requirement:

Internal Number ranges are assigned to general maintenance task lists.

Configuration:






3.4.2.B Define NumberRanges for Equipment Task Lists



Data Define Number Ranges for Equipment Task Lists


In this step, we can define the type of number assignment for equipment task lists.

The numbers are assigned internally.

Requirement:


Configuration:






3.4.2.C Define NumberRanges for Task Lists for Functional Locations


Plans, Work Centers, Task Lists and PRT’s Task List Control

Data Define Number Ranges for Task Lists for Functional

Locations


In this step we determine the type of number assignment for task lists for functional

locations.

The numbers are assigned internally.

Requirement:


Configuration:






3.4.2.D Define Profiles with Default Values



Data Define Profiles with Default Values


We can simplify data entry as follows in task list maintenance:

Data is proposed or used as a reference from the work center

Data is proposed from the profile

When maintaining a task list, we can enter a profile ID. When creating a new task list or

a task list object (for example, header, and operation), the values from this profile ID isproposed. We can overwrite this data if necessary.

Maintenance of default values for header data, the values of the fields "Use" and "Task

list status" are also used for task list maintenance. The header data in the task list is

automatically filled out with the settings defined here.

1. Check which useful default values can minimize the required input in your

company.

2. Define several different profiles if necessary.

3. Maintain the default values in task list management.

Requirement:

For simplifying the data entry in maintenance task lists. To save the users from re-enter

default values in maintenance task list data from the maintenance transaction.

Configuration:






3.4.2.E Define Presetting for Free Assignment of Material

T.Code SPRO


Plans, Work Centers, Task Lists and PRT’s Task List Control

Data Define Presetting for Free Assignment of Material


In this section you determine the BOM usage for materials which are allocated freely

(they are not a component of a bill of material) in the task list. SAP recommends that

you use the BOM usage which is primarily used in the Plant Maintenance area. The

usage is an important selection criterion in the BOM application, which controls theautomatic explosion of BOMs.

With the free material allocation, you can allocate materials at any time to general task

lists, equipment task lists or task lists for functional locations. This means that you can

create a task list for a PM object and allocate materials to it without the material being a

component of the object BOM (for example, equipment bill of material). For these 'free'

materials that are not allocated to the object BOM, the system creates a bill of material






in the background. Here you can only define the BOM usage of the internal bill of

material.

In all cases, only one entry is valid per client. The standard BOM usage for PlantMaintenance is '4'.

Requirement:


Configuration:

3.4.2.F Define Field Selection

T.Code SPRO



Data Define Field Selection


In this IMG activity, we can define the field selection for the screens of the task lists.

Note that you cannot hide fields which are mandatory fields in the standard or lock

them for entry.All screens, for which a field selection is possible, are summarized into individual

screen modification groups (e.g. all detail screens for the confirmation of a maintenance

order).

Requirement:







Configuration:






3.5 Production Resources/Tools

3.5.1 General Data

3.5.1.A Define PRT Status

T.Code SPRO


Plans, WorkCenters, Task Lists and PRT’s Production Resource

tools General Data Define PRT Status


We can define the PRT status in this step. The status controls the usage of a production

resource/tool in the functional application.

The status allows you to release production resource/tools for different tasks whenmaintaining master data.

The PRT status is only relevant for the PRT master record (others).

Requirement:


Configuration:






3.5.1.B Define PRT Group Keys



tools General Data Define PRT Group Keys


In this menu option, we define production resource / tool group keys. With this key, we

can combine production resources/tools into groups. We can use the PRT group key to

set up match codes or use it for informational purposes in printing.

The group key is only relevant for the following PRT categories:

PRTs with material master records (material PRTs) PRTs with PRT master records (miscellaneous PRTs)

The PRT group key does not have as large a range of functional uses as the PRT

category.

Requirement:

As per AAPL requirement PRT Group keys are customized.

Configuration:

Pending






3.5.2. Production Resource/Tool Assignments

3.5.2.A Define PRT Control Keys

T.Code SPRO



tools Production resource tools assignment Define PRT

Control keys


The PRT control key determines whether PRTs that are allocated to a task list or an

order are included in the following business functions:

scheduling costing

printing production order printing

completion confirmation

Requirement:


Configuration:






4.0 Maintenance and Service Processing

4.1 Basic Settings

4.1.1 General Order Settlement

4.1.1.A Maintain Settlement Profiles

T.Code SPRO


and Service Processing Basic Settings General Order

Settlement Maintain Settlement Profiles


A requirement for creating a settlement rule allowed settlement receivers (such as cost

center or asset) settlement rule that determines which portions of a sender's costs are

allocated to which receivers.

A settlement rule contains distribution rules, one or more of which are assigned to eachsender. In most cases, there will be one distribution rule for each receiver. 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 we

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.






Requirement:

As per the AAPL requirement, settlement profile created for settle the incurred cost ofmaintenance orders.

Configuration:






4.1.2 Settings for Display of Costs

4.1.2.A Maintain Value Categories


and Service Processing Basic Settings Settings for Display of

Costs Maintain Value Categories


In this step, we define value categories. Value categories are intervals for cost elements.

These are required to update the:

Plant Maintenance Information System

1. Define a key and description for the value category.

2. If we want to evaluate quantities in the order, assign a unit of measure

to the value category.

3. Enter the load category for the value category:

Costs and outgoing payments

Revenues and incoming payments

Requirement:






As per AAPL requirement, different types of value categories are created for capture the

cost of maintenance orders.

Configuration:

4.1.2.B Assign Cost Elements to Value Categories

T.Code OIK2



Costs Assign Cost Elements to Value Categories


In this section, we define a cost element, a cost element interval or a cost element group

as a value category.

Choose a value category and call up the detail screen.

Define a cost element, a cost element interval or a cost element group as avalue category.

Requirement:

As per AAPL, requirement cost elements are assigned to value categories.






Configuration:






4.1.2.C Define Default Values for Value Categories



Costs Define Default Values for Value Categories


In this step, we can define default values for the value categories for the entry of costs.

This setting applies to the creation of historical orders and cost estimates in normal

orders. we can choose from the same value categories as for the cost display of non-

historical orders.

Requirement:

As per the AAPL, requirement default value categories are defined.

Configuration:






4.2 Maintenance and Service Notifications

4.2.1 Notification Creation

4.2.1.A Notification Types / Define Notification Types

T.Code SPRO


and Service Processing Maintenance and Service Notifications

Notification Creation Notification Types / Define

Notification Types


In this step, we define notification types. Each notification type references a notification

category and an origin. Notifications have the category predefined on the basis of theorigin. We can define notification types for the following origins:

Maintenance Notification

General maintenance notification

Malfunction report

Activity report

The origin requires a suitable screen control in the notification transactions.

Comprehensive controls are linked to the notification type. Due to the wide range of

functions that are

Requirement:

As per the AAPL, requirement notification types and notification settings are

customized.

Configuration:






A1: AAPL: Gen Maint Request

A2: AAPL: Malfunction:-

A3: AAPL: Activity Report:-






A4: AAPL: Conditional Notification:-

Set Screen Templates for the Notification Type






Define Long Text Control for Notification Types






4.2.1.A Notification Types / Define Number Ranges

T.Code IW20



Notification Creation Notification Types / Define

NumberRanges


In this work step, we define the accompanying number range interval for each

notification type.

We can define a number range interval for each notification type, whereby we can

choose between internal and external number assignment.

Note the following for our settings.

We can also enter a notification from the maintenance order processing. This means

that a notification is created automatically in the background. To guarantee the use of

these functions, we must allow internal number assignment for these notification types

because you want to create a notification automatically from the order. If you create all

your notifications in the SAP System, SAP recommends always using an internal

number

Requirement:







Configuration:

Pending






4.2.1.A Notification Types / Assign Notification Types to Order Types



Notification Creation Notification Types / Assign

Notification Types to Order Types


In this step, we can define which order type is generated from which notification type.

we can work with different notification types and order types. In this step, we can

assign a single order type to a single notification type in each case. Check the activities

that you have performed in this step after processing the "Maintenance and ServiceOrders" section in Customizing.

If you want orders to be generated automatically from notifications, internal number

assignment must be defined for the order type concerned.

Requirement:

As per the AAPL, requirement notification types are assigned to order types.

Configuration:






4.2.1.B Notification Content / Define Catalog Profile

T.Code OQN6



Notification Creation Notification Content / Define Catalog

Profile


In this step, we define the catalog profiles for notifications. we define:

Which catalogs and code groups from the individual catalogs are to be

accessed by the system for notifications? We can make a selection of code

groups from the catalog by entering a generic key for these code groups. The

catalogs that are to be used for the notifications have already been defined.






Define that the system displays a warning (type W) if the catalog profile is

not followed.

Requirement:

As per AAPL requirement catalog profile is defined and assigned to notification types.

Configuration:






4.2.1.B Notification Content / Change Catalog and Catalog Profile for

Notification Type

T.Code SPRO



Notification Creation Notification Content / Change Catalogs

and Catalog Profile for Notification Type


Define the information that is to be entered for the notification item and

choose the most appropriate catalog.

Define the catalog profile for the notification type, if this did not alreadytake place when the notification type was created.

Requirement:

As per AAPL requirement catalogs and catalog profiles are assigned to notification

types

Configuration:






4.2.2 Notification Processing

4.2.2.A Response Time Monitoring

4.2.2.A Response Time Monitoring / Define Priorities

T.Code SPRO



Notification ProcessingResponse time monitoring / Define

Priorities


In this step, we define the priorities for the notifications. We can define different

priority types and assign a priority type to each notification type. For each priority type,

we define:

Which priority (rank) a notification warrants

Which start date and finish date (based on the creation date) the

notifications should have

Determine which priorities and target basic dates will be valid for the notification types

used in your company.1. First define the different priority types.

2. For each priority type, define its priority (rank) and basic dates.

3. Assign a suitable priority type to each notification type.

Notes

The system finds the basic dates for the notification header with the help of the priority;

the system automatically suggests tasks to be included in the notification header using






the response profile and specifies the processing deadlines. These two scheduling

functions work independently of one another.

If you choose the unit "day" for the relative start and end time of the notification, thesystem takes the factory calendar into account. If you choose other units, for example,

"hour" or "week", non-working hours are not considered.

Requirement:


Configuration:






4.2.2.A Response Time Monitoring / Define Response Monitoring

T.Code SPRO



Notification Processing Response time monitoring / Define

Response Monitoring


In this step, we define the response time monitoring functions for notifications. For this

purpose, we must first define response profiles and service profiles. we must thenassign these profiles to the notification types.

In the response profile, we define a sequence of standard tasks (based on the priority of

the notification) that can be proposed in the notification and which must be carried out

within a predefined period of time.

When the system processes a notification, it always assigns the tasks that have been

selected on the basis of a response profile to the notification header.






Requirement:


Configuration:






4.2.2.B Object Information

4.2.2.B Object Information / Define Object Information Keys

T.Code OIMD



Notification Processing Object Information / Define Object

Information Keys


In this step we can define different object information keys.

An object information key can be assigned to the following object types:

functional location categories equipment categories

maintenance and service notification types

maintenance and service order types

Via the parameterization of the object information key, you determine the data of a

technical object (equipment, functional location, structure) that is shown in a special

information window.

The object information also contains history data from the PM Information System and

data from the notifications and orders executed.

Requirement:


Configuration:






4.2.2.B Object Information / Assign Object Information Keys to Notification

Types

T.Code SPRO



Notification Processing Object Information / Assign Object

Information Keys to Notification Types


In this step we can assign an object information key to each notification type.

Requirement:


Configuration:






4.3 Maintenance and Service Orders4.3.1 Functions and Settings for Order Types

4.3.1.A Configure Order Types

T.Code OIOA


and Service Processing Maintenance and Service Orders

Functions and Settings for Order Types Configure Order Types


In this step, we set up our order types for Plant Maintenance.In addition to the business reasons for configuring several order types, there are also

technical controls which depend on the order type and may require the creation of

different order types. A tool that categorizes orders according to business purpose.

The order type contains information which is necessary for managing orders. Order

types are client-specific. The same order type can be used in all controlling areas in one

client.

Example

Maintenance orders

Capital investment orders

Requirement:

As per the AAPL, requirement 7 types of orders are configured.

Configuration:






ZA02 AAPL: Breakdown Maint. Order

ZA03 AAPL: Preventive Maintenance Order






ZA04 AAPL:Refurbishment Maint Order

ZA05 AAPL: Calibration Maint. Order






ZA06 AAPL: Capital Investment Order

ZA07 AAPL: Shutdown Maintenance Order






4.3.1.C Assign Order Types to Maintenance Plants

T.Code OIODMenu Path IMG Plant Maintenance & Customer Service Maintenance


Functions and Settings for Order Types Assign Order Types to

Maintenance Plants


In this Customizing activity, we determine the order types allowed for the individual

planning plants.

Note

If we want to allow all order types for all planning plants, we must enter all the ordertypes for each plant.

Requirement:


Configuration:






4.3.1.D Assign Inspection Types to Maintenance/Service Order Types



Functions and Settings for Order Types Assign Inspection

Types to Maintenance/Service Order Types


In this work step, we assign the QM inspection types to the PM/CS order types. These

settings result in an inspection lot being generated automatically for the corresponding

order when a PM / CS order is released. This inspection lot can then be processed

further in QM, within the framework of results recording and of a usage decision.

Requirement:

As per AAPL, requirement Inspection types are assigned to ZA05 order type.

Configuration:






4.3.1.E Define Default Value for Planning Indicator for Each Order Type

T.Code OIOSMenu Path IMG Plant Maintenance & Customer Service Maintenance


Functions and Settings for Order Types Define Default Value for

Planning Indicator for Each Order Type


In this section, we can define a default value for each order type for the order planning

indicator.

The order planning indicator is used for selection and statistical analyses in the Plant

Maintenance and Customer Service Information System.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

task cannot be anticipated, but also need not be performed immediately.

Immediate 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.

Requirement:


Configuration:






4.3.1.F Create Default Value Profiles for External Procurement



Functions and Settings for Order Types Create Default Value

Profiles for External Procurement


In this step, we define the profiles for external procurement of services and materials.

In the external processing profile, we can store default values to generate purchase

requisitions from maintenance- or service orders.

In each profile, we can store a default value for the following values:

Cost element account Purchasing organization

Purchasing group

Material group

During external processing, a distinction is made between the external procurement of

materials and the allocation of complete order operations 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.

You should therefore define different profiles for:

External processing or external assignment of complete order operations

Procurement of materials (material profile)In a further step, you can assign two profiles to each user.

Requirement:

To reduce the data entry work at maintenance order creation time and task list creation

time, these default value profiles are customized.

Configuration:






4.3.1.G Create Default Value Profiles for General Order Data



Functions and Settings for Order Types Create Default Value

Profiles for General Order Data


In this Customizing Activity, we define default values for further order data. When

making these settings, we should check carefully to see whether you have to maintain

all parameters.

For order processing for maintenance- or service orders, we should Define a key word ID to select the user-defined fields from the task list and

Allocate a calculation key to calculate the capacity of the operation.

Requirement:

As per AAPL, requirement to reduce the data entry work in maintenance order and task

list.

Configuration:






4.3.1.H Default Values for Task List Data and Profile Assignments

T.Code SPRO



Functions and Settings for Order Types Default Values for TaskList Data and Profile Assignments


In this IMG activity we define which default values should be copied to the order data

for order processing.

In previous IMG activities, we maintained the profile for procuring material, external

processing profile and general order profile which you now assign here:

we can define the profile assignment individually for each plant and each

order type.

If the profile should be independent of the order type, only make oneassignment for the plant.

If we want the assignment to be cross-company for all plants, only define one

entry without plant and without order type.

we can perform the masking of the entries by entering the value **** in the

entry field.






Requirement:


Configuration:






4.3.1.I Settlement Rule: Define Time and Creation of Distribution Rule



Functions and Settings for Order Types Settlement Rule: Define

Time and Creation of Distribution Rule


In this step, we can define for each order type the time by which the settlement rule

must be maintained during order processing. We can also define a default value for the

distribution rule for each order type, according to which the settlement rule should be

calculated, if an order of this order type has a superior order.Example

To settle an order, a settlement rule must be defined. This settlement rule can either be

generated by the system based on the default value for the distribution rule, or it must

be maintained manually.

To settle a sub-order, you can define here, for example, that the main order is a

settlement receiver of the sub-order.

If you enter a settlement receiver manually in a sub-order, this is not changed by the

default value for the distribution rule.

Requirement:


Configuration:






4.3.1.J Define Notification and Order Integration



Functions and Settings for Order TypesDefine Notification and

Order Integration


In this Customizing activity,we can define

Whether you want to maintain notification- and order data in one screen.

This means that you can create another notification automatically when

entering the order. Whether the long text of the notification header should be automatically

copied to the order header

Whether and in what range you allow the assignment of operations to object

list entries of the order

Note that for all notification types which you enter here, an internal number assignment

is strictly necessary.

Requirement:

SAP Standard Settings are adopted.

Configuration:






4.3.1.L Maintenance Activity Type / Define Maintenance Activity Types

T.Code SPRO



Functions and Settings for Order Types Maintenance Activity

Type / Define Maintenance Activity Types


In this step, we determine the allowed maintenance activity types. A key for the type of

maintenance activity provided. Activities are divided into repairs, shutdowns, regularactivities, inspections and so on.

In cost evaluations, for example, total costs or number of orders for each technical

object, you can classify data according to maintenance activity type. The maintenance

activity types should not be confused with activities in the CO system.

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.

Requirement:

As per AAPL, requirement some of the activities are customized.

Configuration:






4.3.1.L Maintenance Activity Type / Assign Valid Maintenance Activity

Types to Maintenance Order Types

T.Code OIO5

Menu Path IMG Plant Maintenance & Customer Service Maintenanceand Service Processing Maintenance and Service Orders

Functions and Settings for Order Types Maintenance Activity

Type / Assign Valid Maintenance Activity Types to Maintenance

Order Types







In this step, we can determine which maintenance activity types allowed with which

order types.

Allocate the corresponding maintenance activities to the PM and CS order types.Requirement:

As per AAPL, requirement maintenance activities are assigned to maintenance order

types.

Configuration:

4.3.1.L Maintenance Activity Type / Default Values for Maintenance Activity

Type for Each Order Type

T.Code OIO4



Functions and Settings for Order Types

Maintenance ActivityType / Default Values for Maintenance Activity Type for Each

Order Type


In this step, we can assign a maintenance activity to an order type. This activity is

proposed during order processing.






Requirement:


Configuration:

Costing Data for Maintenance and Service Orders

Assign Costing Parameters and Results Analysis Keys






4.3.1.M Define Change Docs, Collective Purc. Req. Indicator, Operation No.Interval

T.Code SPRO



Functions and Settings for Order Types Define Change Docs,

Collective Purc. Req. Indicator, Operation No. Interval


In this step, we can define:

Whether changes to the order header are recorded using documents and are

displayed in the form of an action log

The increment at which numbers for the individual operations should be

assigned

Whether just one purchase requisition (collective purchase requisition)

should be generated for external material and operations for each order

Whether reservations or purchase requisitions relevant to materials

planning should be generated when an order is created or only when the

order is released

Requirement:

As per AAPL, requirement some of the settings are customized in standard SAP.

Configuration:






Goods Movements for Order

Define Documentation for Goods Movements for the Order






4.3.1.N Availability Check for Material, PRTs, and Capacities / Define

Checking Rules

T.Code SPRO



Functions and Settings for Order Types Availability Check for

Material, PRTs, and Capacities / Define Checking Rules


In this step, we can define checking rules for the following applications:

Sales and distribution

MRP

Production order processing

Maintenance order processing

Service processing

Inventory management

Requirement:


Configuration:






4.3.1.O Availability Check for Material, PRTs, and Capacities / Define

Inspection Control

T.Code OIOI



Functions and Settings for Order Types Availability Check for

Material, PRTs, and Capacities / Define Inspection Control


In this activity, we define the check control. The checking rule together with the

checking group specify the scope of the check.

we can make the checking rule as well as the actual check itself dependent on the

following parameters:

plant

order type

operation

The operation can have the following characteristics:

order created

release(d) order






Control parameters for the operation 'create'

In addition to this, you can specify whether a planned order can be converted to

a production order or process order using collective conversion in the case of:

missing parts

missing PRTs or

insufficient capacity

'Release' control parameters for operation

In addition, you can control whether an order can be released in the case of

missing materials

missing PRTs

insufficient capacity

Requirement:


Configuration:






4.3.2.B Define Account Assignment Cat. and Document Type for Purchase

Requisitions

T.Code SPRO



General Data Define Account Assignment Cat. and Document

Type for Purchase Requisitions


In this Customizing activity we define the purchasing account assignment category and

purchasing document type for purchase requisitions for maintenance and service

orders. For the document type, we can choose whether we always want to generate

purchase requisitions for standard purchase orders, contracts or other document typesof the purchasing system.

Purchase requisitions for PM/SM orders must always be assigned to PM/SM orders.

This means that you must change the standard setting for the account assignment

category only if you defined a new account assignment category for order-account

assignment in Customizing for the purchasing system.

In the standard delivery, account assignment categories and a document type for the

purchase requisitions are provided.

Requirement:

As per AAPL, requirement account assignment and document types are assigned tomaintenance orders for generate the purchase requisition.

Configuration:






Define Priorities

Define Priority Type for Orders

4.3.2.C Create System Conditions or Operating Conditions

T.Code SPRO



General Data Create System Conditions or OperatingConditions


In this Customizing activity, we define the possible asset conditions. Effects on the

capacity load in production In the reference objects functional location and equipment,

we have the option of defining a production work center.

We can enter a system condition in the maintenance order for every operation. Using

this system condition, we can determine whether the operation must be carried out in

production or when the system is shut down, for example.

This asset status does not affect capacities in production.

Requirement:







Configuration:

4.3.2.D Activate Default Value for Current Date as Basic Date

T.Code SPRO



General Data Activate Default Value for Current Date as Basic

Date


In this step, we can define for which plants the current date should be proposed as abasic date for the order.

Requirement:


Configuration:






4.3.2.E Define Default Values for Units for Operation

T.Code OIO9Menu Path IMG Plant Maintenance & Customer Service Maintenance


General DataDefine Default Values for Units for Operation


In this step, you can specify the default values for units of the duration and the work

output of an operation.

Bear in mind that you can only use units of the dimension 'ZEIT' as units of

measurement for the default values.

The processing time of individual operations should be specified in hours, the total timeof the task should be specified in days.

To achieve this, specify 'STD' as a time unit for work; the time unit for the duration is

'TAG'.

Requirement:


Configuration:






4.3.3 Scheduling

4.3.3.A Maintain Scheduling Types

T.Code OIOT



SchedulingMaintain Scheduling Types


In this step, you can maintain the allowed scheduling types. An indicator that shows

how the maintenance due date was generated.

Scheduling types are:

New start

Scheduled

Manual call

Start within the current cycle

Before you delete existing scheduling types because they are not needed for maintenance or service

processing, you should check whether they are used by other user departments.

Requirement:


Configuration:






4.3.4 Object Information4.3.4.A Assign Object Information Keys to Order Types

T.Code OIOJ



Object Information Assign Object Information Keys to Order

Types


In this step you can assign an object information key to each order type.

Requirement:


Configuration:






4.4 Completion Confirmations

4.4.1 Define Control Parameters for Completion Confirmations

T.Code SPRO


and Service Processing Completion Confirmations Define

Control Parameters for Completion Confirmations


In this work step, you maintain the control parameters for completion confirmations for

maintenance- and service orders. You can set control parameters for each order type.

Define the parameter settings for the completion confirmations in your plant for the

possible order types.

Requirement:


Configuration:






4.4.2 Define Causes for Variances

T.Code SPRO

Menu Path IMG Plant Maintenance & Customer Service Maintenanceand Service Processing Completion Confirmations Define

Causes for Variances


In this work step you can define reasons or causes for deviations. The definition of

deviations can be plant-specific.

Example

You plan duration of 5 hours for a particular operation. Because the necessary material

was not available or a certain tool was defective, you could not complete the task within

the time originally planned.In this situation, you could define reasons for deviation such as:

'Insufficient material' or

'Defective tool'.

Requirement:

As per AAPL, requirement some causes of variances are customized.






Configuration:

Following of the customization settings are done in quality management module which

are relevant to Plant maintenance module.

Maintain Settings at Plant Level






Define Identifier for Inspection Points