erptips sap training manual sample chapter from plant maintenance

Plant Maintenance ECC 6.0 Rev. 10/24/09 1 SAPtips Sample Plant Maintenance Asset Data

This segment from our 357 page SAP Plant Maintenance manual is being made available as a sample of our training manuals. Please contact [email protected] if you have any SAP training needs, or visit www.ERPtips.com for more information.

Written by Warren Bell and Jocelyn Hayes

Published by Klee Associates, Inc.

Copyright Klee Associates, Inc., 2009

Unit 3: Plant Maintenance Asset Data

In this unit, we will cover the following topics:

Functional Locations

Basic Functional Location Configuration

Equipment

Basic Equipment Configurations

Additional Technical Objects

Sub-Equipment

Assemblies

Materials

Object Linking

Functional Locations

The primary building block of the asset hierarchy is the technical object known as a functional location. Most computer users are familiar with the way data files are structured into a hierarchy, and functional locations are arranged in a similar parent/child or superior/subordinate type of relationship. The classic example looks very much like a pyramid, with the uppermost level at the top, and the subordinate elements cascading down through the different levels until the bottom of the hierarchy is reached. This example is described as a “classic” example, because while there is almost no end to the possible combinations of structures that can be created using the many potential approaches when constructing an asset hierarchy, the “process” style is the most common. Other styles include physical location (spatial), and function, where areas of similar function are grouped together regardless of process relationship or physical location. We looked at an example of the classic structure in Unit 1 (Bob's Bagel Factory). “Out of the box” SAP allows creation of basic “no frills” functional locations with minimal configuration. Transaction IL01 Is used, and in this example we will walk through the “create” transaction. Keep in mind, we will not discuss every single aspect of USING the elements we will explore, but instead will include the configuration needed to facilitate their usage. To help understand how that configuration is relevant, we will first create several Functional Locations.

mailto:[email protected]

http://www.erptips.com/

Unit 3: Plant Maintenance Asset Data Klee Associates, Inc.

2 Rev. 10/24/09 Plant Maintenance ECC 6.0

Creation of Functional Locations

The menu path to reach IL01 is:

Logistics Plant Maintenance Management of Technical objects Functional Location Create

Above is a screen shot of the IL01 transaction we will use to create our level one functional location (here after called a “FLOC”....)

Take note of the first group of fields:

To Do This

Functional loc. BOBS

Edit mask XXXX-XXX-AA-NN

HierLevels 1 2 3 4

Labeling system A IDES AG

StrIndicator A Structure A

FunctLocCat M Technical system – standard

Description Bob's Bagel Factory

Klee Associates, Inc. Unit 3: Plant Maintenance Asset Data

Plant Maintenance ECC 6.0 Rev. 10/24/09 3

I have entered the value "BOBS" in the "Functional loc." field (representing the first four "X's" in the edit mask), but the system has pre-populated the rest. This is normally a "top" level object, because we are only using the first set of characters (XXXX = BOBS) Two of the other values that are already populated are attributes for which we will discuss configuration later:

StrIndicator (Structure Indicator), which defines the lay out of the functional location code

FunctLocCat. (Functional Location Category)

In the next screen shot, we see a description added to our first FLOC; also visible are some of the other fields available with this category (M) of FLOC.



In the next screenshot, the functional location is saved, which creates the uppermost level of our demo structure.

Now, the same transaction is used to create two subordinate FLOCs to represent the second level of our demo structure.



Below is a screen shot of the second FLOC, which shows that the system has automatically detected a “superior” functional location based on the code and edit mask we used.

…and finally, a third FLOC is created by repeating this step (not shown), representing another second level FLOC.

At this point, we will look at how we have progressed by executing transaction IH01 (display structure list); this view shows the default data hierarchy view, and the three FLOCs created so far. The top level is “BOBS”, with two subordinate FLOCs; note the two subordinate FLOCs are indented (BOBS-MBP and BOBS-S_R).



Demonstration and Exercise

Using the steps provided in the previous section, create your own Functional Location using the following data:

1. Create a new Structure Indicator based on the following:

Field Value

Functional Location BOBS-S_R-PL-0X (where X your student number)

StrIndicator A

Functional Location Category

M

Labeling System A

Copy Reference BOBS-S_R-PL-02

After creating the functional location, using transaction IH01, view the technical object hierarchy headed by the Functional Location “BOBS” to see where your new functional location has been located in the hierarchy.

Now that we have examined the basics of how FLOCs are created, let's examine some of the basic configuration settings for Functional Locations.



Basic Functional Location Configuration

Define Functional Location Categories Functional Location creation requires selection of a category for the object; there are numerous categories pre-defined, but custom categories are often created to meet business requirements. The IMG path to reach the node for accomplishing this configuration is shown in the next screen shot, and is reached by the path:

"SPRO" then click

Plant Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical Objects Functional Location Define Category of Functional location

The table view for creating a new category is shown in the next screen shot; note that there are a number of categories already configured.



To add a custom category, initiate the transaction by clicking the "New Entries" button, which opens the view shown below:

The view above shows a proposed category for Bagel related functional locations; note that a number of specific attributes may be controlled here; this is where, for instance, change documents are activated for this FLOC category.



Define Functional Location Structure Indicator

The structure indicator establishes how the various levels of a structure are related to each other, including the length, number, and method of separation for the character groups of the functional location code. The relationship is known as the edit mask. The screenshot below shows the IMG path to reach the node for accomplishing this configuration. The path in the IMG is as follows:

Plant Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical Objects Functional Location Create Structure Indicator for Reference Location/ Functional Locations

The transaction is as shown in the next screenshot:

As with categories, there are multiple indicators already in the system. A new indicator can be created by clicking the “New Entry” button, which will open the transaction shown below:



The above screen shot shows a new three group indicator being proposed, with two numeric groups of four and three characters, followed by a 20-character alpha-numeric group. The groups are separated by hyphens.

Define Field Selection for Functional Locations

SAP allows control over the number and behavior of the various fields in the functional location master record. The record can be simplified by hiding unused or unneeded fields. To effect these changes, the following IMG Menu path is used, and is shown below:

Plant Maintenance and Customer Service Master Data in Plant Maintenance and Customer Service Technical Objects Functional location Define Field Selection for Functional Location

Clicking on the transaction will open a node selection dialog box; click on the upper node Specific Fields for (Reference) Functional Location and then press Enter.



This will open the field control screen shown here:

By using the circular radio buttons, field behavior can be set to regular input, required, display only, or hidden. In addition, a field can be highlighted (with the tick box) to make it easier to locate (recommended for required fields).



Demonstration and Exercise

Using the steps provided in the previous section, create your own Structure Indicator as follows:

1. Create a new Structure Indicator based on the following:

Field Value

StrIndicator TRXXX (where XXX is your student number)

StructIndText Trainee XXX Structure Indicator

Edit Mask AAA-XXXXXXXX-AANNN-XXXXXX-XXXXXX

Heir Levels 1 2 3 4 5

Where the first level of the hierarchy is the training organization: TRN

The second level is your company name expressed within the 8-character space: XXXXXXXX

The third level is your trainee number expressed as TRXXX

The fourth and fifth levels are whatever you would like to make up to fit in the space available, which will serve your exercises in the rest of the course

2. Modify the following Functional Location fields as specified below:

Hide the fields:

o Business area

o Construction type

o Distribution channel

o Division

o Root cause

o Sales group

o Sales organization

Highlight the fields

o ABC Indicator

o Catalog profile

o Cost Center

o Main Work Center

o Planner Group

o Panning Plant



Make the highlighted fields above also Required fields.

3. Create functional locations via IL01, using the structure indicator you have created, at two or three levels to test the hierarchy described by the structure indicator.

4. Check the fields of the functional locations created to verify the fields modified by the class in the field selection tables.



Legal Speak:

Purchase of this book or acquisition at an ERPtips class, constitutes an implied agreement by the purchaser to a limited, license granted to the purchaser by Klee Associates, Inc., specifically for purposes limited to improving your personal knowledge of SAP software which does not in any way compete with Klee Associates.

This manual is protected by copyright law, and is sold or is part of an ERPtips class with the following conditions:

The manual will be used for your personal professional development.

The manual will not be physically copied for distribution to other individuals or converted to an electronic copy for distribution to other individuals, unless copyright permissions for copying have been acquired from Klee Associates, Inc.

The manual will not be used to conduct training classes by you or other individuals, without the written permission of Klee Associates, Inc.

Inclusion of the concepts in this book in any internal client training material is allowed if the source of the concepts is acknowledged as follows:

Copyright 2009

All rights reserved.

Used with permission.

Klee Associates, Inc.

NO WARRANTY: This documentation is delivered as is, and Klee Associates makes no warranty as to its accuracy or use. Any use of this documentation is at the risk of the user. Although we make every good faith effort to ensure accuracy, this document may include technical or other inaccuracies or typographical errors. Klee Associates reserves the right to make changes without prior notice.

ERPtips is a valued resource for thousands of clients and consultants worldwide. Visit our web site for more information about upcoming training, books, and newsletters.

www.ERPtips.com

ERPtips is a registered trademark of Klee Associates, Inc.

No Affiliation: Klee Associates, Inc. and this publication are not affiliated with or endorsed by SAP AG. SAP AG software referred to on this site is furnished under license agreements between SAP AG and its customers and can be used only within the terms of such agreements. SAP AG is a registered trademark of SAP AG. All other product names used herein are trademarks or registered trademarks of their respective owners.

http://www.erptips.com/

erptips sap training manual sample chapter from plant maintenance

Documents