FAQ: PM/CS Cost Reports

Below is a list of standard SAP reports commonly used in Plant Maintenance, these reports can be run as and when required provided the user has access to the transaction code/s.

Please let me know if you would like to contribute and have a list of other useful reports which should be appended to the above list. I am also thinking of adding some useful reports from FICO, MM, PS, etc. which can benefit a Plant Maintenance consultant / end user, so please feel free to share what you know / have.

Introduction:

This document is about the field marked below in the  IK01 transaction screen. I'm sure many of us have noticed this, but yet to explore .

Let's consider TWO Dumpers as Equipments and their Tyres as Sub-Equipments for our Demo:

Two Dumpers, with SAP Equipment Ids V-1000 and V-1001, each having 6 Tyres as shown above.

V-1000 with tyres say TYRE0001, TYRE0002, TYRE0003, TYRE0004, TYRE0005, TYRE0006

And

V-1001 with tyres say TYRE0007, TYRE0008, TYRE0009, TYRE0010, TYRE0011, TYRE0012

(External numbering is used for easy understanding)

Each Dumper above has a meter showing the number of hours it operated.

The Objective

When we record a reading from the above meter  in the SAP system (using IK11, on a Measuring point), the counters of the 6 Tyres installed in this vehicle at this time, shall be automatically updated.

This means when we create one measuring document on the vehicle, system should create a total of 7 (1 + 6) , measuring documents so that the usage hours flow from the Vehicle counter  to the Tyre counter.

And then, when a Tyre is dismantled from one vehicle and installed in the other, the Tyre counter should derive its own usage hours from the present vehicle counter readings.

Let’s see how this happens:

Part1:

Preparing the Masterdata:

First let’s  have a characteristic RUNNINGHOUR as shown below (Tcode CT04).

Using this characteristic RUNNINGHOUR, let us create the measuring points, on the Vehicles first.

V-1000

V-1001

Now we need to create measuring points on all the Tyres. A sample screen is …

Compare the measuring point screen of Vehicle and the Tyre. The difference is the Red Box.

Remember all these measuring points are based on characteristic RUNNINGHOUR.

So we create 12 measuring points in a similar way, one for each Tyre.

Below is the IK07 screen,  where you can see at a glance, the measuring points we have created.

Notice that Transfer support‘X’ mark is there for all the 12 Measuring points of Tyres.

Now install Tyres under the Dumpers  V-1000 and V-1001 (Superior Equipment), using Tcode IE02.

Example:

Tyre: TYRE0001.

When we try to define the Superord. Equipmentas V-1000 (in the Structure Tab of IE02 )  wel get this screen.

System is asking for your confirmation for Transfer of Readings from the Superord.Equipment (V-1000 in this case) to the Tyre (TYRE0001).

Click on Copy  and Save the Equipment master.

In a similar way install all the Tyres under the respective Dumpers.

As mentioned above, the initial set-up will have is:

Dumper V-1000 as SuperOrd. Equipment for Tyres TYRE0001 to TYRE0006 and

Dumper V-1001 as SuperOrd. Equipment for Tyres TYRE0007 to TYRE0012.

Everytime we need to confirm Copy during Equipment installing under the Superord. Equipment.

Now the following is the Equipment tree we have just made.

The Masterdata preparation is completed.

End of Part1 ------------------------------------------------------------------------------------------------------------------------------------------------

Part2a:

Create Documents and understand the working of Transfer Support.

It is time now to see what happens when we record Dumper Hour Meter readings through IK11.

Create a measuring document on measuring point 3113 (Equipment Tyre0001), with reading 1000.

Let’s assume that the Dumper V-1000 operated for 1000 hours and its meter is showing a value 1000 Hours. We now create a measuring document to record this value.

Note:

Remember that we get the Cumulative Operating Hours from the Dumper Meter. So, we need to put this reading in the Counter Reading field of the IK11 screen.

When we save this document, we  see this message on the task bar.

This is exactly what we expect from the system. As explained above 1 document is what we have created just now and the other 6  documents are automatically created for the Tyres. This means the Usage Hour counter for all the 6 Tyres started with their first reading as 1000 hours.

Likewise when we create a document with value 500 hours for Dumper V-1001 (Measuring point 3114). Measuring documents are automatically created for Tyres TYRE0007 to TYRE0012, with this reading of 500 hours.

End of Part2a ------------------------------------------------------------------------------------------------------------------------------------------------

Part2b:

Let’s now see what happens when Tyres are relocated from one vehicle to the other.

We will examine a case of TYRE0004 is dismantled from Dumper V-1000 and installed in V-1001.

And TYRE0009  is dismantled from Dumper V-1001 and installed in V-1000.

When we try to dismantle TYRE0004 from V-1000 through Tcode IE02, we get this warning message.

We can understand what the message says, It is stopping Reading transfer for this equipment (TYRE0004) from V-1000.

We continue and give value V-10001 in the Superord. Equipment field. Now we get this screen (already seen before once), asking for confirmation to establish transfer relation with the new Superord. Equipment.

We continue by clicking on Copy and Save the Equipment master.

Repeat the same for dismantling Equipment Tyre0009 from V-1001 and installing it in V-1000.

See the new structure, notice the change in the places of swapped tyres.

Now we create measuring documents on Vehicles.

I have created a document with reading 1450 hours on V-1000 (Measuring point 3113) and a document with reading 1850 hours on V-1001 Measuring point 3114).

Now see the IK17 screen below in the sequential order of Document creation.

The upper half (Green) is before the Tyre swaps, and the lower half is after.

Give special attention to Swapped Tyres (TYRE0004 and TYRE0009) to observe the system intelligence, in transfer of readings during Sub Equipment relocations.

For better understanding Equipment-wise sorted list of above is attached herewith.

End of Part2b ------------------------------------------------------------------------------------------------------------------------------------------------

Note1:

One more thing that happens in the system background during this process was not shown in pictures above.

That is when we click Copy during Equipment installation under a Superord. Equipment in IE02, some changes happen in Measuring Point data (obviously),

i.e. in IK03 screen, which is shown in the field marked below.

As soon as we install TYRE0001 under V-1000, the field marked above is filled with the measuring point of V-1000.

Similarly this field is updated whenever Equipments are relocated from one place to other.

Note2:

In this demo Equipment – Sub Equipment scenario has been dealt.

This document is valid for Functional Location –Equipment Scenario also.

Concluding Remarks

Here, a vehicle scenario has been taken for demonstration of this Measurement Reading Transfer Support functionality of SAP. It is believed that there will be several other applications requiring this feature.

Thank you

Jogeswara Rao K

Introduction:

Often there are requirements like having a common large tasklist for a category of equipments and choosing the operations selectively into the Maintenance Order depending upon the equipment specifications on which the order is being made.

Let me explain with an example:.

Suppose there are 100 motors falling into 6 categories as under:

Now the operations to carry-out the work on these machines vary with different ratings (specifications), often due to the variance in the amount of work involved.

We can have all operations of such 6 categories of 100 equipments in a single large tasklist, yet use in maintenance orders created on these equipments.

i.e., While creating the maintenance order, system would choose only those operations from the tasklist which are relevant to the equipment on which the order is being made .

Such tasklist  is called a ‘Configurable Tasklist’.

Let’s assume the common large tasklist (General Maintenance tasklist) we have for all these motors is  the one shown here, which is to be configured.

Now let us see how, the tasklist is configured.

1. Create the characteristics (CT04)

Create a capacity characteristic for ‘MOTOR_CAP’.

          Now, specify the values and save.

Similarly  create a Type characteristic for ‘MOTOR_MDL’.

Specify the values and save.

2. Create a class (CL02) ,

Say class  ‘MOTOR_TYPES’  (type '300'),

Assign characteristics created  above and save.

3. Object dependencies (CU01)

Create object dependencies as below:

Here dependency ‘SQI5.5’ illustrated.

Go to  ‘Dependency Editor’  and  specify the dependency  as shown here.

Come back to CU01 initial screen and set the Status to 'Released'

Similar dependencies to be made for all combinations of Capacity and Type, viz.,

SQI7.5,

SQI11.5,

SLR5,5,

SLR7.5   and

SLR11.5

Here another illustration is given for dependency ‘SQI7.5’.

Come back to CU01 initial screen and set the Status to 'Released'

4. Tasklist configuration profile (CU41)

Create a Configuration Profile selecting General Maintenance Tasklist.

Create as shown below.

When you click on Class assignment icon (2) above, you will be in the screen below.

Here, do not give values in the Characteristic value fields and Do not forget to select the 'Std Class' check-box.

5. Assign the class to equipments (IE02).

Assign class ‘MOTOR_TYPES’ to the these 100 equipments, with respective characteristic values as shown below:

(Go to 'Class Overview' screen and assign)

6. Assign the dependencies to tasklist operations (IA06):

As shown here:

Assign dependencies to all the tasklist operations which are equipment specific, in a similar way.

Leave the common operations untouched.

Now, the configuration is complete.

Let’s see what effect this exrecise has while selecting tasklist in an order  (IW31/32).

Menu :  Extras --> Tasklist selection --> Direct Entry

In the popup,  give the Tasklist group and counter, as shown.

In the resulting screen,  give the characteristic values of the order equipment,

Click ‘Back’ and go to the operations tab.

Here is the result:

System has chosen the relevant dependency operation (0040) and two operations, where no dependencies were specified. (0070, 0080).

This work can be extended to a tasklist of 100's of operations covering 1000s of equipments.

In my experience, very common application has been in Repair shops where equipments like Motors are repaired. Here very few numbers of Configurable tasklists are maintained covering 1000s of motors.

_________________________________________________________________________________________________________________________________

Related content:

http://scn.sap.com/docs/DOC-44023

Introduction :

Preventative maintenance (PM) is the systematic servicing of equipment to reduce the possibility of failure. It is a generic term for inspections, Preventative maintenance work, and planned repairs. PM deals with the maintenance tasks, for which the time and scope of the work can be planned in advance.

It ensures maximum availability of equipment (objects) in the long term is an important part of Plant Maintenance. Preventative maintenance is used to improve the availability of the technical objects, without which breakdown of the machines will increase and repair costs will be higher. The scope of Preventative Maintenance covers all the Plant & Machinery.

One of the most significant advantages offered by the SAP Plant Maintenance application

component is the option of split-level maintenance. You can use maintenance planning to describe the dates and scope of Preventative maintenance and inspection activities of technical objects. You can plan for your technical objects to be maintained on time and thereby function optimally.

Why Preventive Maintenance is required?

• To carry out Preventative maintenance on the technical object on a fixed frequency.
• To plan procurement of components and provision of service for any technical object in a fixed interval.
• Budgeting of resources like men and material.
• To have standard check lists with operations to check the health of the machine periodically and optimize the maintenance schedules based on the results.
• To perform tasks in Preventative Maintenance to maintain the target condition and to determine the condition of a technical system.
• Mass planning of Preventative maintenance of all the equipment in a section / area.
• Any maintenance activity, which needs to be carried out at a fixed frequency, can be planned and scheduled using this functionality.

Master Data required for Preventive Maintenance :

• Functional Location
• Equipment
• Work Center
• Catalogs
• Maintenance Task list

------------------------------------------------------------------------------------------------------------------------------------------------------------

1) Maintenance Strategy :

• The cycle in which the individual work should be performed (for example, every two months, every 3,106.86 Kms, every 500 operating hours and both)
• Other data which affects scheduling

Benefits of having maintenance strategy :

• Reduce maintenance plan creation time

Introduction:

Requirement to have Additional User-Fields in various Tabs of Equipment, Functional Location or Fleet Masters is very common. Though there is a hassle-free way of having the Z-fields through Class and Characteristic way, it has got its own limitations like unable to become a part of Standard reports.

In this article, the User-Exit way of having these custom fields has been elaborated.  Enhancement ITOB0001 has been demonstrated here. The process will be same for ITOB0003 (Fleet Master).

While trying to achieve this by joining the information pieces available in the forum and outside, the author spent sufficient time to achieve all requirements related to this.

Objective:

At the end of this article we will be able to:

1. Create our own fields in the Equipment, Functional Location or Fleet Masters
2. Input values and save these values to the related Database Tables
3. Edit these values through Tcodes IE02, IL02.
4. Will have these fields in standard reports like IH08, IH06, IE37.

Here we go (ABAP Workbench)

Step 1 (Preparation of EQUI Table)

Let’s suppose we are intending to have 40char long  field, named PO Number into the Equipment Master.

1^st step is to create this Z-field into the include table of EQUI table.

For this run Tcode SE11, Give value CI_EQUI and Go to Change mode. Add a Z-field  in this table say ZZITO_PONO

with component type TXT40 (for 40char long field). Activate table.

Note:

Here I want to share a vital information with the readers. i.e., as long as I tried this task with field names like ZZPONO etc, it never worked. And there consumed lot of time.  Then at some place I read about the SAP note 594757, which states that without a prefix ZZITO_  to theCustom fields, this task would not be successful.

Next,  we need to add this field ZZITO_PONO, also to the include table CI_EQUI _U  with component type IIND (Char1). Do it in the same way as above (through SE11). Activate table.

With this we completed adding our Z-field to the database table EQUI  (through its include tables)

Step 2 (Enhancement – Create Sub-Screen)

Create a project ZPMEQUIPthrough Tcode CMOD and assign the Enhancement ITOB0001.

Now Run Tcode SMOD with value ITOB0001 and click on Test button.

See here, we have 2 Function-exits and 5 Screen exits. Let’s select the first Screen, namely 1000 .  Double click on this and Create a Sub-Screen through the steps there on.

Now Click on Layout Arrow above to go to Screen Painter and Create your Fields here. In our case we are creating One field.

As shown in the picture , drag the 'T' icon to the screen are to create a Text field and name tis field as 'PO Number'.

Similarly drag the icon below to create an Input/Output field and Give the Dictionary address to the Input field i.e., EQUI-ZZITO_PONO .

(I hope you recall that this is the field we have created in EQUI table in the step1)

Step3 ( Enhancement – Give Codes in Function Exits)

We  have 2 function Exits, namely

EXIT_SAPLITO0_001

EXIT_SAPLITO0_002

The first Exit imports the Z-field values from the EQUI table to the Equipment Master

The second one exports Z-field values from the Equipment Master to the EQUI table.

Now the codes to be written in the Exits. 

Write following code in the include (ZXTOBU01) of function-exit EXIT_SAPLITO0_001.

TABLES: EQUI.
E_SUBSCREEN_NUMBER = '1000'.
I_OBJECT_TYPE = '02' .
I_ACTIVITY_TYPE = '3' .
EQUI-ZZITO_PONO = I_DATA_EQUI-ZZITO_PONO.

Write following code in the include (ZXTOBU02) of function-exit EXIT_SAPLITO0_002

E_UPDATE_DATA_EQ-ZZITO_PONO = EQUI-ZZITO_PONO.
E_UPDATE_FLAGS_EQ-ZZITO_PONO = 'X'.

Step 4 (SPRO  Preparation)

• Navigate to this section of SPRO.

• Select Screen Group (Equipment) on the right (Profile Standard) and D’Click on the Activity and layout of views on the Right.

• Give value 150 in the line of desired Tab page of Equipment Master.

• Assign this profile (in this case Standard) to the intended Equipment Category, through this setting.

After this SPRO setting, you will be able to see your Z-Field at the bottom of the Organization Tab page  of that particular Equipment Category. Verify by running IE02 / IE03 transactions.

Try by inputting a value, Save and rerun IE02 and verify your value is stored or not.

In fact, the part of Step3 above ( coding in the Exits ) did not work as long as I did not come across the above referred SAP note. After using the prefix ZZITO_ to the Z-field these codes started working. values inserting.

Almost done

Now if you go to IE03, unlike all other greyed-out fields, your Z-field will be seen Editable. Though there is no provision to save the edits here, you’d definitely like to have this too in Greyed-out mode.

For this we need to write a small code in the PBO (Process Before Output) module of the screen 1000 we have created.

Double click on the Screen number 1000 of the enhancement, (you are in the Flow Logic Tab) ,

D’Click on the STATUS_1000 of the PBO module. and insert this code between the MODULE, END MODULE lines like this

MODULE STATUS_1000 OUTPUT.
IF SY-TCODE = 'IE03'.
LOOP AT SCREEN.
SCREEN-INPUT = '0'.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
ENDMODULE. 

Related discussion:

Configure field selection for equipment user-fields

Lastly Do not Forget to

Activate the Function Group  XTOB  from  Tcode SE80.  Right click on the Function Group and click on the Activate option

Now the Last Step.

Step 5 (Have this Z-field in the Standard Report , in this case IE05, IH08)

To have our Z-field in IH08 output, first we need to know the structure of this report output.

For this click on any cell in the ALV screen and press F1 key.

Here click on the Technical Information icon. The resulting pop-up will show you the Structure against field name Table. Here the Structure is RIHEQUI_LIST .

Now through SE11 go to the above Structure, Click on an Append Structure on the Application toolbar and Create an Append structure having this field. Activate table.

Now Run IH08 and see in the output list in the Column Set (thelist not displayed). You should find this field PO Number.

Often you do not find this. It is time to clear ALV buffer through program BALVBUFDEL.

For this run Tcode SE38 give the above program and hit Execute.

Now run IH08 again and verify, your field is there.

Note:

This work is with a larger objective in mind to avoid re-inventing the wheel after sometime and at the same time providing the Total Solution about this task at one place.  This work involves Appending structures and Activation of Tables, which should be done by experienced ABPAers only.

Also this work can be extended to Functional Location Masters with the same enhancement used above and to the Fleet Masters with enhancement ITOB0003.

..and I feel it is important to mention the version I experienced all these and documented, it is ECC6.0 no EHPs.

Hope members find this useful.

Thank you

Jogeswara Rao K

Material Availability Check in Maintenance Order

The purpose of this document is to provide detail information on setting up the material availability check in SAP Plant Maintenance for stock Materials.

Material Availability check in the maintenance order is one of the useful functionality provided by SAP. When we plan materials in the maintenance order, you can either check the availability before the order is released or the system can do it automatically when the order is released. Material Planning is one of the important KPI’s for planning team.

Pre-requisites

1. Plant Maintenance Configuration
2. Material Master data Maintenance

Plant Maintenance Configuration

1. Define Checking Rules

     Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Orders - Functions and Settings for Order Types - Availability Check for Material, PRTs, and Capacities - Define Checking Rules

2. Define Scope of Check

     Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Orders - Functions and Settings for Order Types - Availability Check for Material, PRTs, and Capacities - Define Scope of Check

For Individual Requirements

Separate requirements will be generated for each order.

This document will deal only with Availability Check 02 (Individual Requirement)

3. Define Inspection Control

     Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Orders - Functions and Settings for Order Types - Availability Check for Material, PRTs, and Capacities - Define Inspection Control

This configuration needs to be done with a combination of Plant / Order type / Availability Check

Check availability during order creation

* Check material availability when saving order

* Assign the Checking rule created in Step 2

* Collect. Conversion is used to determine the action you want to do in case of Material not available. This will not be relevant when then Order is in creation phase

Check availability during order release

If Status Check is used, an availability check does not have to run ever time an order is released. This reduces the system load. (SAP help)

4. Define Change Documents, Collective Purchase Requisition, MRP relevance

This configuration plays a vital role on checking the Material Availability in SAP PM.

You need to make sure Res / Pur Req is set Immediately, else during Work Order Creation, Material availability check will not work.

Material Master data Maintenance

Availability check needs to be maintain for the Material in MRP3 view.

Availability Check 02 is maintained for the Material.

Case 1 : Check availability during Order creation

Scenario 1: Before Saving the Work Order

A work order creation in progress, after entering the Material availability icon highlighted below will give the pop-up "Non-Availability of Material See log"

System Status MSPT - Material Shortage will be updated.

Click the Log icon to see the messages

Click the Display log in Total to view all messages

Please make a note, this will not stop you on saving the Work Order in CRTD status.

Scenario 2: After the Work Order is saved

Material Availability was not checked manually

During creation System Status is set as MANC (Material Availability not checked)

After saving the Work Order

System Status MSPT (Material Shortage) is set automatically on save.

Work Order can be reviewed using System Status itself

Case 2 : Check availability during Order release

Scenario 1: Define Inspection Control - User decides on release  if parts are missing

When the Order is created, material planning is done and saved. Upon clicking the release flag, system gives below message

Based on the configuration, user have authority to bypass and release the order.

Click on Missing Parts List icon

Scenario 2: Define Inspection Control - No release if parts is missing

When the release flag is clicked, system pop-up below error message

In this configuration setting, you cannot release the work order, to check the log click Go to - Logs - Release

Click on Display log icon in Total to view all messages

This document is prepared based on the default configuration, explore more on the config for different kinds of scenarios.

ABSTRACT

SAP offers the use of IBIP supported objects from within the LSMW to support data transfer.

This abstract explore the "old" option to run transaction IBIP directly with pre made flat files that matches to the IBIP structures and hierarchy ,the Excel IBIP tool can be usesd as an alternative to LSMW

The Tool includes Demo templates are available to Downloadhere

BENEFITS

Authorizations- if your requirement is provide simple excel based tool for the end user for master data management and LSMW authorization in the PRD system is not an option
 

Fast and Simple - Use 1 Excel source file also for multi structures ,in the IBIP Tool there is no need to link between the files using key relations between the structures ( Using IDENT1 , IDENT2  etc..) as required by LSMW approach , The Flat file records are written to the flat file based on the location sequence of the structure in the Excel template.

Scheduleruns at night Jobs - by splitting the flat file to several flat files we can use the IBIP program to upload the data in a schedule job which includes also the option to define in advance on which servers the scheduled jobs will be executed for load balancing purpose and also achieve "parallel processing" functionality which speed up data upload  , This approach is very helpful when dealing with mass master data  update , For exemple if several millions of records can be completed over night (depends on the number of servers in the PRD system ) using this approach  .

Exemples for such changes for Functional locations or equipments :

- Mass update class and characteristic

- Mass update of system profile

- Mass update of the Address data  ( using structure IBIPBDCD)

Templates examples

Exemple 1 :Create Equipment with user status

Exemple 2 :Create Equipment with class and characteristics

Exemple 3 :General Task list with  operation and assignment to maintenance packages

Pre requirement

• Microsoft excel 2007- 2013
• Macro enabled

STEP A - Prepare template - Select the required  structuresand required fields

• Selected multi radio button
• Select structure IBIPEQUI
• Select the required fields from the IBIPEQUI  structure
• Select structure IBIPSTAT
• Select all the fields from this structure IBIPSTAT

   1. Open the add in file

   2 .Select IE01– Create equipment in the transaction combo box

   3. Select the IBIPEQUI  structure  in the data structure listbox

     5. Double click the IBIPSTAT  structure which holds the user status data

STEP B - Fill Excel source / template worksheet

  STEP C - Generate The Flat File for IBIP Transaction

   The flat file will Automatically created ( stored in the temp folder )

Step D -  Upload the Flat File to the IBIP transaction

    . Select  the created file from the flat file selected folder and press   in the IBIP transaction

Step E ( Optional ) store the files in the Application server

            Another alternative is to store the flat files at the application server which is mostly required  when the data migration duration takes       
            more then  several  hours and it is required to schedule the run at night (when system load is low) , in this case :

            Goto sm51 select the required server

Goto to transaction CG3Z and upload the flat file to the current application server

            3.Select the application server which the file was uploaded into  and select the Phys. file  and press on "Execute"

   Step F : Check the Log

      Lets Check and confirm that the equipment 10006947 created is created with the "0005" status which as displayed in the excel row 4         

     We can see the result : the equipment 10006947 was created with user status "0005"

Exemple 2: Equipment creation with class and characteristics

1 Goto transaction IBIP – press the information icon to see Structure hierarchy , So you can know which structures are required to your business scenario
                                                             

        3. Now –with the IBIP Tool Create  template using structures IBIPEQUI , IBIPCLAS  ,  IBIPFEAT

     (Unhide row 1-2 to view selected structures and fields technical names)

              4.Upload the Flat File to the IBIP transaction

               5. Let’s Check and see that the equipment created 200860 was created with the required class and characteristics  per the data  in
                   the excel rows 4 -6     

Exemple 3: Functional Location assign class and update characteristics values

Introduction

The way several features including coding in Extras of Infoset takes the work closer to an ABAP development, another function Alias in the Table-join screen also increases the versatility of an Infoset (SQ02) or a  Quick View (SQVI)

Objective:

To understand the concept of Alias Tables in Infosets and Quick Views, through a Demo application.

Demo Situation:

We have a task of developing, a report through Infoset or a Quick View, to display Notification details and corresponding Object part and Damage Codes details.

So the ALV we need will have these columns:

Let’s see how we do it.

Obviously the two tables we need are:

1. VIQMEL  - For Notification Details
2. VIQMFE - For Object Part, Damage Details.

But

In VIQMFE table, we do not have the Code texts (field name kurztext). These fields are shown in Red in the 1^st picture.  QPCT is the table we need to join to get this field value. Let’s take this into our join.

Then, What’s the problem ?

As per the join shown above we are getting kurztext (Damage Code Text) for Damage Code (FECOD) only.

What about the kurztext for Object Part Code(oteil).

To get this too, we need to have one more QPCT table into the join. But system does not allow this.

So what do we do?

Here comes  the use of the Alias Table.

We now need to create an alias table identical to QPCT (say QPCT1)

Follow the steps shown in the picture.

Now you have the desired table for you. Take this table too into the join.

Remember, system can not propose the right links for the join. You need to know this and Join Manually.

All done regarding the Alias Table.

Now you have your Selection-screen and List fields in QuickView (in case of Infoset make the Query through SQ01).

The Result is:

We find here the desired output with Code Texts also filled.

NOTE:

This is a simple case to demo the Alias tables. This feature has a big advantage during complex works of Infoset / Quick View.

The absence of Extras  facility in SQVI, makes this Alias feature more relevant to a Quick View work.

In infoset, this Alias feature can be substituted by Extras Add Table, Add field and Code functionalities.

Hope Infoset / Quick Viewer users find this useful.

The environment of this document is ECC6.0 no EHPs.

Readers might be interested in these posts also:

10 Useful Tips on Infoset Queries

Infoset Queries: Collection of important posts

Thank you

Jogeswara Rao K

In this document we will be going through various steps involved to develop Multiple counter plan.

A multiple counter plan is used in counter based maintenance. This type of maintenance planning is not based on a maintenance strategy. This means that you can create a multiple counter plan without maintenance strategy.

Master data requirement

     Below are the list of basic Master data required to process Multiple Counter Plan.

• Equipment
• Characteristics for measuring point / counter

• Measuring Point/Counter assigned to Equipment
• Cycle sets as per requirement

Equipment - IE01 / IE02

     I have created PUMP as Equipment for explaining this scenario.

Measuring Point / Counter - IK01

     We are going to record the running hours of the Pump. To record the running hours we need to create measuring point / counter.

     Create the Measuring point for Equipment, enter the object type IEQ

     To make the measurement point as a Counter, you need to check "MeasPoint is counter"

     Ensure characteristics you want to assign to measuring point / counter were created

In the measuring counter, you need to maintain below fields                                                       

MeasPosition                     - This describes the position of the measuring point / counter with respect to the Technical Object.

Counter Overflow reading - The first counter reading that the counter cannot display. Enter a logical value for the first counter reading.

Annual Estimate                - Estimated hours the equipment can run in a year. This needs to be filled, maintenance intervals are calculated based on this data.

On save, measuring point / counter is created.

Record the current running hours reading of the Pump using measuring documents (IK11), this is required to schedule the plan.

On save, first measurement document created for measuring point / counter. Two documents are posted for this measuring point / counter.

Cycle Sets - IP11Z

     Cycle sets are used as a copy model for the creation of multiple counter plan. It defines the period of time between two maintenance tasks. Also cycle sets can be complied directly in multiple counter plan itself.

     Cycle sets needs to be created based on business requirement.

Maintenance plan - IP01 / IP43

     Select the Maintenance plan category and Cycle set (Cycle set not mandatory)

     Press Enter

     Cycle sets will be copied to the maintenance plan

     Cycle set sequence needs to be filled and same has to be linked to maintenance item. Here the scenario has only one cycle set sequence.

     Cycle set sequence, Scheduling period, Start date will be populated in the multiple counter maintenance plan (IP43) after activating the "Configure Special Functions for Maintenance Planning" in SPRO.

     Kindly update the maintenance plan with relevant details like Maintenance Plan Description, Maintenance Item Description, Order Type, Planner Group, Work Center, Task list and Priority.

   Select the Maintenance plan scheduling parameters tab.

Kindly maintain the Sched Period and Start Date.

The important factor of Multiple Counter Plan is the Operation Type.

Kindly refer the scheduling column for the Operation type and difference on scheduling the maintenance plan.

On Save Maintenance Plan will be saved.

Scheduling - IP10 / IP30

On scheduling the plan, we need to consider the Operation Type and the behavior of scheduling will be different based on the type.

OR Operation Type:

For an OR Operation, a maintenance order is generated for the earliest possible planned date.

In our case, if the maintenance is due every 250 hrs or 3 months, the decisive factor is which occurs first.

On scheduling the Maintenance plan

Since the measuring counter reading is already reached 250, a maintenance is already due, on save, work order will be generated.

AND Operation type:

For an AND Operation, a maintenance order is generated for the last planned date.

In our case, if the maintenance is due every 250 hrs or 3 months, the decisive factor is which occurs last.

On scheduling the maintenance plan

Measuring counter is reached, but the 3 months is not reached so the maintenance is planned for the future date based on the start date.

Here I have covered the basic scenario of Multiple Counter Plan, there are lot of options available to explore in this area.

In this document we will discuss what is the Permit and what are the types of it (Technical Permit)

Note:The below steps are applied on SAP ECC6.0  EHP6.0

Table OF Contents:

1- Introduction

2- Technical Permit

2.1 Create theTechnical Permit

2.2 Assign The Technical Permit To The Technical Object

2.3 Technical Permits Influences The order

1- Introduction

Permits are created for the Maintenance Order to:

1. Adhere to health and safety regulations
2. Control order processing (Release - Completion<TECO>)

There are two types of permits:

1. Technical Permits (assigned manually to the technical objects (Equipment - Functional Location)

• If an order is created for the technical object, the permits are copied to the order and can influence the order release Or completion<TECO> (Depends On Your settings)

   2. Process-Oriented Permits (automatic assignment to the order)

• e.g. -> when creating a maintenance order with an order type and an activity type , the permits are copied to the order and can influence the order release Or completion<TECO> (Depends On Your settings)

2- Technical Permit

Steps:

1. Create The Technical Permit
2. Assign the Technical Permit To The Technical Object
3. Technical Permit Influences The Order

2.1 Create The Technical Permit

SAP ECC Menu: Logistics -> Plant Maintenance -> Management of Technical Objects -> Environment -> Permits

T Code: IPMD

Click On (Create/Change) Button To Enter The Change Mode

Then

• Permit (Code): Char(10)
• Permit Text : Char(30)
• Permit Category : Used for grouping the Permits -> Defined In Configuration
• Order Release : Used when you want to Control order processing (Release)
• Order Completion (TECO):  Used when you want to Control order  Completion
• The Possible Options in The Order  Release or Completion Fields:

• The 1st Option -> when you release the order, a warning message appears but if you pressed Enter, you can continue processing the order
• The 2nd option -> The order can not be released until the authorized user issue (Approve) the permit
• The 3rd Option -> No Warring Message,  just check the permits

• Not Modifiable Field: Used when you select the 2nd option as the user can not flag (Dimmed) the button not relevant (Ignore The Permit) when the permit influence the order  as The Permit must be issued by the authorized user

Note: We Will Work On Order release

2.2 Assign The Technical Permit To The Technical Object

Note: We Will Assign The Permit To An Equipment -> T Code: IE02

• Choose Your Permit that is created from the above Step

You can assign more than one technical permit to the equipment

2.3 Technical Permits Influences The order

When Creating a maintenance order for the equipment which the permit has been assigned to it:

1- If you used the 1st option in the permit (Permit to be issued after warning)

when you release the order, a warning message appears but if you pressed Enter, you can continue processing the order

2- If you used the 2nd option in the permit (Permit Must be issued else Error Message)

The order can not be released until the authorized user issue the permit

• You Can Issue the permit from the order(IW32) or From T Code IPM2 -> we will issue from the order

• Select the permit Then The Issue Button
• NR (Not Relevant is Dimmed) -> as I set the flag of Not Modifiable in the permit as any one can not ignore the permit

• The Permit is issued (You Can now Release The Maintenance Order)

3- If you used the 3rd option in the permit (Permit Must not be issued )

No Warring Message,  just check the permits  From The permit Button

Note:(I_Sogen) is the authorization object related to the permit (The User that will issue the permit)

• The Authorization Object Fields:
  • Permit Key (Permit)
  • Maintenance Plant

Note: The authorized user can reverse the Permit (Cancel the issue) only before the order being Released or TECO (Depend on your settings)

In this document we will discuss the Process Oriented Permit 

Note:The below steps are applied on SAP ECC6.0  EHP6.0

1- Introduction

Process-Oriented Permit is assigned automatically to the Maintenance Order

e.g: when creating a maintenance order using an order type with an activity type , the permits are copied to the order and can influence the order release or completion (TECO) ->  (Depends On Your settings)

In our example we will create a permit that control the order release when creating an order with:

• Order type: PMM1 and Activity Type: A02 0r A03

2- Steps :

2.1- Create two characteristics that represent (Order Type - Activity Type)

2.2- Assign the two characteristics to the permit class (PM_Permit)

2.3- Create the permit

2.1- Create Characteristics (T Code CT04)

• Enter the Name of The Characteristics Then create button

• Go To Addnl Data TAB & Enter The Table Name that contains the field (activity type) & The Field Name (Activity Type)

• An information message appear

• The Format of the field which is taken fro ABAP

• Then Choose the Value Assignment

• Single Value: only one value (For The Field) can be assigned to this characteristic.
• Multiple Value: more than one value (For The Field) can be assigned to this characteristic.

• Then Enter The Values Of the Activity Type

Then Repeat The previous Steps To create characteristic for the order type

-----------------------------------------------------------------------------------------------------------------------------------------------

2.2- Assign the two characteristics to the permit class (PM_Permit)

• T Code : CL02

• Put The Name of The Permit Class (PM_PERMIT) Then Change button

• Go To The Char TAB to assign the two characteristics which are created above

------------------------------------------------------------------------------------------------------------------

2.3- Create the permit -> T Code: IPMD

• After filling the below fields press the button classification to assign the Value of the characteristic (Fields ) To the Permit

Note :The Relation Between The two characteristics is AND

Means when the values A02,or A03 (Multiple Assignment ) & PMM1 are entered in the order will prevent the order from release

Note: Below are the table and the fields related to the permit when creating characteristic(s)

• The Table Name: CSEVPERMIT

Note: Intervals in the characteristic values are written in the following format

How maintenance is planned within your company?  De-Centralized, Centralized or Partial Centralized?

How is capacity planning performed in your maintenance plants?

Are certain types of maintenance work planned or executed with consideration to the plant sections?

Do you subdivide your maintenance plant in locations to facilitate the maintenance job or for purpose of reporting?

How is maintenance work organized?

How are the maintenance teams / labor resources organized?

How are your technical systems structured?

What types of technical objects do you handle (Types of Equipment and functional location)?

Is the hierarchy for functional locations structured according to spatial, functional or technical viewpoints? Is Real Estate objects are integrated?

How detailed should the functional location hierarchy be (for example, number of levels, installation and dismantling of equipment)?

Do you link documents to functional locations/Equipment?

Do you need to record the performance of functional locations using measuring points and counters?

Do you track warranties/Guaranties?

Are your technical objects classified (Class/Chars) used in you company?

List and describe the different categories of equipment/Functional Location that you maintain.

How many equipment and functional location you manage in your system?

Do you use Object part, Damage, Cause and Activity analysis?

Do you use Fleet Maintenance process?

Do you use Equipment BoMs? Whats the volume of data?

What types of Task List do you use? Whats the volume of data?

Do you use Maintenance Plans (for example Time based or Performance based or both)?

What maintenance type do you do (for example Breakdown, Corrective, Calibration, Refurbishment, Preventive etc.)?

Do you have any third party system integrated with SAP PM?

How do you settle the cost and how you see the cost reports on Equipment and Functional location?

Which reports do you use in SAP PM?

Service order has many date fields which capture the timing of planning and execution. More often than not the name of field does not convey the actual meaning. Via this document I    have tried   to build a quick reference of Service Order date fields.

Actual Start date:  It is the start date of first operation in Order.It does not get filled till we do the first confirmation on the Order. I would like to clarify that the First Operation does not mean the first operation in numerical sequence but the first operation which gets confirmed. The first Actual start date of an Operation flows is also the Actual Start date of the Order. In short this field captured the real start of work (Actualignores scheduling and goes with confirmation off course  that is why it is an Actual).

Actual Order Finish date:Similar to Actual start date the Operation finish date is populated as soon as the Operation is confirmed, only difference is in case of Order it is associated with the confirmation of the last operation. .For some reason if we choose not to record the confirmation for the Operation which has confirmation required in configuration and do the TECO, we miss the Actual Order Finish date, because Actual Order Finish date is very closely linked to confirmation of the last operation in time sequence.

Actual Release date:This is the Release date of an Order meaning when the system status of the Order has changed from Created to Release. If the order does not get released due to some issue (attains Release rejected RELR) then the value is not stored.

Available from date/Available to date: I am unable to determine the business logic behind these two fields. While trying to find its usage, I see them used in just one class "CL_EX_ES_MUL_LIST_TZ_CORE_IMPL" which appears to be more of a technical class (handling session programming) instead of having any business logic. I would like peers to comment on these two fields.

Basic Start/Finish Date:These are the most important date field on the Service order, as it contains the input required to initiate the scheduling. These dates are closely linked to Scheduling Type and used in scheduling to determine the start and end of Operations. So the key purpose of these fields to arrive at the schedule for each operation. Operation not having any duration are ignored are ignored in calculation.

Change date:This field stores an Order change date. The description of the field states “Change date for Order Master”. Order Master is AUFK and the field is updated regardless of changes done at AUFK or AFPO, RESB etc. (I have tried these three basic tables). There could be exceptions where this field is not updated despite changes done in IW32 but not to my knowledge.

Note: The label “Change data for Order Master” does not seem the best possible description of the field.

Created on:It is the date on which Order is created.

History from: It is stored on Maintenance Orders which are archived through Order archiving process. It contains the date on which the archiving was executed. This field will get the value after archiving so we can see it populated only on historical orders.

Period (Service Order Selection screen):If we take literal meaning of this field we understand it is a range. This mapping of period to a field in order Header is unclear from field label. This field acts as selection range for all the Orders which has reference date falling in the period specified. It refers to reference date on the Order.I have explained the significance of Reference date later in this document.

[I am sure we could have done better with the naming of this field as “Period” does not signify the business meaning]

Purchase Order Date:This field can contain the PO related date. At times we get the date on which Customer created and sent a PO for repair. This is one of the freely available fields which can be used to store the date if we want to store the information related to PO.As It is not linked to Purchase Order Technically and can store a value independent of Purchase order.

Reference Date:It contains two dates over the life cycle of the Order. If the Order is not completed it contains Order start date but once the Order is complete it store the technical completion date. It is also the date which gets referred in Period field on Order selection screen (T code IW73).

Scheduled Start/Finish date: It is the planned start date of first operation and the value is derived as soon as scheduling is executed. The calculation is primarily dependent on Basic dates, scheduling type and duration.

Note:Whenever an operation is dropped and scheduling is re executed the scheduled date changes. 

Though I have not seen the practical usage of each field above, this is my high level understanding of date fields  based on experience and search. If you have reached till this line then feel free to provide your feedback on document, I will be more than happy to incorporate any contextual missing information.

Anjan

Equipment Task list Display Report by using SQVI

Hi All,

This is my First Document in the Forum and hope this will be helpful for all.

Purpose:

IA10 and IA17 standard reports are available to display equipment task list, unfortunately this only brings across the information as it would be printed so there is a lot of work to be done in the spreadsheet to get what you want to see. But maybe not impossible! Hope this report will helps Plant Maintenance users to view the maintenance task list details of multiple equipment’s and save  into spreadsheet.

The report will be created by using T code SQVI

Used SAP Tables:

1. 1.      EQUZ
2. 2.      ILOA
3. 3.      EQKT
4. 4.      IFLOTX
5. 5.      EAPL
6. 6.      PLKO
7. 7.      PLPO
8. 8.      PLWP
9. 9.      T351X

Step 1:

Enter T Code SQVI

Enter Name of the program for the report in the quick view field and press create button

Now enter the Title for the report and select data source as table join.

Select basis mode and press enter

Step 2:

Press   to enter the table name

Step 3:

Again click on table and enter table which should be link to previous table. Example in EQUZ   Equipment number it is linked to EQKT equipent number.

We can take n number of tables which should linked to previous entered table.

Enter tables EQKT, EAPL, PLKO, PLPO, PLWP and T351X by following the previous step.

Step 4:

You can delete / edit table connections by selecting the black line and clicking with the right-mouse button.

Select the unwanted connections and delete by clicking the right –mouse button.

Step 5:

Enter 2 more tables ILOA and IFLOTX

Bring ILOA and IFLOTX tables to the starting screen to connect EQUZ table.

Step 6:

Click join condition button  on the top of the screen

Now give EQUZ and ILOA table and press enter

The logic:

1. 1. Select EQUNR field from EQUZ table and pass this into EQKT table to get equipment number and description
2. 2. Take EQUNR field from EQKT table and pass this into EAPL table to get the task list details.
3. 3. Take PLNNR field from EAPL table and pass this into PLKO table to get the planner group.
4. 4. Take PLNNR field  from PLKO table and pass this into PLPO table  to get operation details
5. 5. Take PLNNR & PLNKN fields from PLPO table and pass this into PLWP table to get the required maintenance strategy of task list.
6. 6. Take PAKET & STRAT fields from PLWP table and pass this into T351X table to get the maintenance schedule of operation.
7. 7. Select EQUNR field from EQUZ table and pass this into ILOA table to get functional location. description
8. 8. Select TPLNR field from ILOA table and pass this into IFLOTX table to get functional location description.

After removing the unnecessary links between tables the final links as given below

Table links:

EQUZ-EQUNR-EQKT

EQKT-EQUNR-EAPL

EAPL-PLNNR-PLKO

PLKO-PLNNR-PLPO

PLPO-PLNNR-PLNKN-PLWP

PLWP-PAKET-STRAT-T351X

EQUZ-ILOAN-ILOA

ILOA-TPLNR-IFLOTX

Step 7:

Press back button after connecting the table links

Press  to switch between filed names and technical names

Step 8:

Selection fields is for input screen of the report

List fields is for output of the report

Input Fields:

                       EQUZ-EQUNR (Equipment Number)

                       PLKO-VAGRP (Planner Group)

                       PLPO-WERKS (Plant)

Output Fields:

                      PLPO-WERKS (Plant)

                      ILOA-TPLNR (Functional Location)

                      IFLOTX-PLTXT (Functional location Description)

                      EQKT-EQUNR (Equipment Number)

                      EQKT-EQKTX (Equipment Description)

                      PLKO-VAGRP (Planner Group)

                      PLPO-LTXA1 (Task list Operation Text)

                      T351X-STRAT (Strategy)

                      T351X-KTEX1 (Maintenance Package Text)

Select the above input and output fields in the quick viewer screen                   

Press  to switch between filed names and technical names

Select the output fields for the report

Step 9:

Now go to sort fields tab to enter field names to sort

Select  to find required field

Click after entering the table and field name

Click   to enter sort fields into quick viewer

Sort Fields:

ILOA-TPLNR

EQKT-EQUNR

EQKT-EQKTX

PLPO-WERKS

IFLOTX-PLTXT

Select  at the top left side of the screen

Select output headings of the report to change if required, we can change and modify the output length as required

Press Back Button on the screen to save the SQVI report

The SQVI report has been saved, select the line item and press execute to run the report

Input Screen:

Output Screen:

Procedure to create tcode:

Go to system –status on the input screen

Copy the programme name and give it to the ABAPER to create TCODE for the report.

Hope you all will find the Document Helpful.

Thanks & Regards,

Sunil Boya

1.0 Why do we need effective Spare parts planning?

It is a challenge for asset intensive industries to maintain optimum level of spare parts in the inventory. Keeping lower levels of parts than required could mean non availability of parts in time to carry out planned and unplanned maintenance, thereby increasing equipment down time. Reduced availability of equipment can lead to lower production and impacts meeting customer delivery schedules. On the other hand, keeping higher inventory of spare parts means higher inventory carrying cost which will increase overall production cost. Also, industry often experiences the risk of excessive stock of parts in the inventory becoming obsolete over a period of time due to technology and engineering advancements. Either way, it is a challenge for maintenance planners and the MRO stock planners to keep the optimum level of stock on continuous basis.

2.0 Business criticality

Most manufacturing plants and maintenance departments face the challenge of lowering operating cost and improving service levels. Manufacturing systems have become more sophisticated due to demand for agility and flexibility over involving greater capital investments. This has added complexity in maintaining machinery in running condition with minimal impact to production and minimal impact to customer delivery schedules.

Demand unpredictability, part alternatives, high service levels, accurate forecast of part requirement also add to the complexity to the planning for spare parts.

3.0 Key business process requirements

Here are a number of business process requirements that drive spare parts planning:

• Ability to plan for parts based on a variety of factors such as criticality, cost, consumption, combination of these factors
• Integration of production and operation planning to optimize equipment availability
• Optimize spare parts storage with respect to usable life as well as storage space constraints
• Ability to dynamically update part availability due to material transfers
• Handle shelf life expiry and maximize usable life
• Ability to track service levels and parts consumption and to update planning dynamically
• Ability to carry out cycle counting based on criticality, parts consumption, parts value, etc.
• Use of performance metrics such as overall equipment efficiency (OEE), MTTR, MTTF, unplanned downtime, repair cost, etc.

4.0 SAP ERP functionality to support Spare parts management

SAP ERP supports these key requirements through Plant Maintenance module and integrated functions including inventory, warehouse, procurement, finance and costing. In addition, maintenance scheduling can impact production scheduling. Some of the key functions of SAP that support spare parts planning are described below:
.

4.1 Material Master Setup

Spare parts can be broadly classified as:

• Stock Items: Materials for which stock is usually maintained in the store room.
• Non-Stock Items: Materials that are usually one time purchases and not maintained as stock in store room.

Requirement for maintenance spare parts are usually generated in the following ways:

• Re-Order planning: Store room personnel maintains the minimum and maximum stock levels for most of the MRO items. Procurement process is triggered based on the Re-order level. System creates dependent requirements for all the parts that are subject to requirements planning.
• Manual purchase requirements: Purchase requirements are manually created by users as and when the parts are required (during emergency breakdown for example).
• Automatic purchase requisitions: System can automatically generate purchase requisitions for non-stock items, if they are used in the work orders.

The table below lists the combination of common MRP parameters used for re-order planning of MRO spares. The combination of MRP type and Lot size keys in conjunction with reorder point, fixed lot, max stock addresses most of the common planning needs for maintenance spare parts.

4.2 Integration of PM with Procurement processes

• Determination of requirements: Requirements are determined based on MRP planning or manual purchase requirements
• Approval process: Once purchase requisitions are approved by authorized personnel, they are converted to purchase orders to carry out the procurement process
• Source determination: Potential sources of supply based on past orders and existing long-term purchase agreements. This speeds up the process of creating the requests for quotation (RFQs)
• Quotations: Functionality to compare a number of quotations, different pricing and terms, etc.
• Purchase order processing: Information from requisition to quotation can be included in a purchase order. Different types of POs include scheduling agreements, contracts etc.
• Goods receipt and inventory management: Goods receiving personnel can confirm the receipt of goods simply by entering the PO number. By specifying permissible tolerances, 'over' and 'under', deliveries of ordered goods can be limited.
• Invoice verification: Invoices can be verified and accounts payable clerk is notified of quantity and price variances for clearing and payment.

4.3 Integration of PM with Warehouse processes

• Managing stock: Stock for materials is updated real-time when goods movement transactions are carried out. Stock overview of the current stock situation of any given material can be obtained. For example, stocks that -
  • are located in the warehouse
  • have already been ordered, but have not yet been received
  • are located in the warehouse, but have already been reserved
  • have other statuses like quality inspection
• Types of Physical Inventory
  • Periodic inventory
  • Continuous inventory
  • Cycle counting
  • Inventory sampling
• Cycle counting process
  • Cycle counting is a method of physical inventory where inventory is counted at regular intervals within a fiscal year. Cycle counting allows you to count fast moving items more frequently than slow moving items.
  • Materials can be grouped together into various cycle counting categories (such as A,B,C,D).

4.4 Core Plant Maintenance processes

Order Management: Work orders in SAP support component planning. Stock items as well as non-stock items can be planned on work orders. Stock items create reservations instantly on saving work orders. Materials are issued to work orders from stock. if parts are not available in stock, system creates purchase requisitions. Purchase requisitions are created immediately on saving work orders for non-stock items. System offers functionality to create planned, unplanned and emergency work orders.

Refurbishment process: Refurbishment Order is a special type of work order that allows repairing of damaged parts in-house or through external vendors. Damaged part is refurbished and then put back in stock for consumption. This process is fully integrated into inventory, costing and MRP functions of SAP.

Serial number management: Spare parts can be tracked individually through serial number management functionality in SAP. Parts can be serialized at the time of material receipts, issue or during stock transfers. Serialization also helps in tracking warranty on parts. vendors can be made accountable for parts that fail prematurely through this functionality.

5.0 Key Metrics

Here are a few key performance indicators that provide analysis on effectiveness of spare parts management:

Equipment efficiency: Percentage of the number of maintenance labor hours spent on an equipment vs equipment operating time.

Maintenance effectiveness: Operating time / (operating time + downtime for maintenance ) as a percentage. Represents equipment availability from maintenance perspective.

Unplanned downtime %: Percentage of time equipment/facilities are not available for production due to maintenance requirements.

Maintenance cost %: Equipment/facility maintenance cost as a percentage of manufacturing controllable costs.

MTTR: Mean time to repair equipment and facilities for a defined unit of measure such as operating hours, number of batch runs, etc.

MTTF: Average interval of time between failures of equipment and facilities for a defined unit of measure such as operating hours, number of batch runs etc.

Dear All,

Every Organization has their own implementation questionnaire defined for all SAP modules. Following is the list of sample questions. These question provide a platform for us to get into details during requirement gathering phase.

FAQ: PM/CS Cost Reports

Below is a list of standard SAP reports commonly used in Plant Maintenance, these reports can be run as and when required provided the user has access to the transaction code/s.

Please let me know if you would like to contribute and have a list of other useful reports which should be appended to the above list. I am also thinking of adding some useful reports from FICO, MM, PS, etc. which can benefit a Plant Maintenance consultant / end user, so please feel free to share what you know / have.

Introduction:

This document is about the field marked below in the  IK01 transaction screen. I'm sure many of us have noticed this, but yet to explore .

Let's consider TWO Dumpers as Equipments and their Tyres as Sub-Equipments for our Demo:

Two Dumpers, with SAP Equipment Ids V-1000 and V-1001, each having 6 Tyres as shown above.

V-1000 with tyres say TYRE0001, TYRE0002, TYRE0003, TYRE0004, TYRE0005, TYRE0006

And

V-1001 with tyres say TYRE0007, TYRE0008, TYRE0009, TYRE0010, TYRE0011, TYRE0012

(External numbering is used for easy understanding)

Each Dumper above has a meter showing the number of hours it operated.

The Objective

When we record a reading from the above meter  in the SAP system (using IK11, on a Measuring point), the counters of the 6 Tyres installed in this vehicle at this time, shall be automatically updated.

This means when we create one measuring document on the vehicle, system should create a total of 7 (1 + 6) , measuring documents so that the usage hours flow from the Vehicle counter  to the Tyre counter.

And then, when a Tyre is dismantled from one vehicle and installed in the other, the Tyre counter should derive its own usage hours from the present vehicle counter readings.

Let’s see how this happens:

Part1:

Preparing the Masterdata:

First let’s  have a characteristic RUNNINGHOUR as shown below (Tcode CT04).

Using this characteristic RUNNINGHOUR, let us create the measuring points, on the Vehicles first.

V-1000

V-1001

Now we need to create measuring points on all the Tyres. A sample screen is …

Compare the measuring point screen of Vehicle and the Tyre. The difference is the Red Box.

Remember all these measuring points are based on characteristic RUNNINGHOUR.

So we create 12 measuring points in a similar way, one for each Tyre.

Below is the IK07 screen,  where you can see at a glance, the measuring points we have created.

Notice that Transfer support‘X’ mark is there for all the 12 Measuring points of Tyres.

Now install Tyres under the Dumpers  V-1000 and V-1001 (Superior Equipment), using Tcode IE02.

Example:

Tyre: TYRE0001.

When we try to define the Superord. Equipmentas V-1000 (in the Structure Tab of IE02 )  wel get this screen.

System is asking for your confirmation for Transfer of Readings from the Superord.Equipment (V-1000 in this case) to the Tyre (TYRE0001).

Click on Copy  and Save the Equipment master.

In a similar way install all the Tyres under the respective Dumpers.

As mentioned above, the initial set-up will have is:

Dumper V-1000 as SuperOrd. Equipment for Tyres TYRE0001 to TYRE0006 and

Dumper V-1001 as SuperOrd. Equipment for Tyres TYRE0007 to TYRE0012.

Everytime we need to confirm Copy during Equipment installing under the Superord. Equipment.

Now the following is the Equipment tree we have just made.

The Masterdata preparation is completed.

End of Part1 ------------------------------------------------------------------------------------------------------------------------------------------------

Part2a:

Create Documents and understand the working of Transfer Support.

It is time now to see what happens when we record Dumper Hour Meter readings through IK11.

Create a measuring document on measuring point 3113 (Equipment Tyre0001), with reading 1000.

Let’s assume that the Dumper V-1000 operated for 1000 hours and its meter is showing a value 1000 Hours. We now create a measuring document to record this value.

Note:

Remember that we get the Cumulative Operating Hours from the Dumper Meter. So, we need to put this reading in the Counter Reading field of the IK11 screen.

When we save this document, we  see this message on the task bar.

This is exactly what we expect from the system. As explained above 1 document is what we have created just now and the other 6  documents are automatically created for the Tyres. This means the Usage Hour counter for all the 6 Tyres started with their first reading as 1000 hours.

Likewise when we create a document with value 500 hours for Dumper V-1001 (Measuring point 3114). Measuring documents are automatically created for Tyres TYRE0007 to TYRE0012, with this reading of 500 hours.

End of Part2a ------------------------------------------------------------------------------------------------------------------------------------------------

Part2b:

Let’s now see what happens when Tyres are relocated from one vehicle to the other.

We will examine a case of TYRE0004 is dismantled from Dumper V-1000 and installed in V-1001.

And TYRE0009  is dismantled from Dumper V-1001 and installed in V-1000.

When we try to dismantle TYRE0004 from V-1000 through Tcode IE02, we get this warning message.

We can understand what the message says, It is stopping Reading transfer for this equipment (TYRE0004) from V-1000.

We continue and give value V-10001 in the Superord. Equipment field. Now we get this screen (already seen before once), asking for confirmation to establish transfer relation with the new Superord. Equipment.

We continue by clicking on Copy and Save the Equipment master.

Repeat the same for dismantling Equipment Tyre0009 from V-1001 and installing it in V-1000.

See the new structure, notice the change in the places of swapped tyres.

Now we create measuring documents on Vehicles.

I have created a document with reading 1450 hours on V-1000 (Measuring point 3113) and a document with reading 1850 hours on V-1001 Measuring point 3114).

Now see the IK17 screen below in the sequential order of Document creation.

The upper half (Green) is before the Tyre swaps, and the lower half is after.

Give special attention to Swapped Tyres (TYRE0004 and TYRE0009) to observe the system intelligence, in transfer of readings during Sub Equipment relocations.

For better understanding Equipment-wise sorted list of above is attached herewith.

End of Part2b ------------------------------------------------------------------------------------------------------------------------------------------------

Note1:

One more thing that happens in the system background during this process was not shown in pictures above.

That is when we click Copy during Equipment installation under a Superord. Equipment in IE02, some changes happen in Measuring Point data (obviously),

i.e. in IK03 screen, which is shown in the field marked below.

As soon as we install TYRE0001 under V-1000, the field marked above is filled with the measuring point of V-1000.

Similarly this field is updated whenever Equipments are relocated from one place to other.

Note2:

In this demo Equipment – Sub Equipment scenario has been dealt.

This document is valid for Functional Location –Equipment Scenario also.

Concluding Remarks

Here, a vehicle scenario has been taken for demonstration of this Measurement Reading Transfer Support functionality of SAP. It is believed that there will be several other applications requiring this feature.

Thank you

Jogeswara Rao K

Introduction:

Often there are requirements like having a common large tasklist for a category of equipments and choosing the operations selectively into the Maintenance Order depending upon the equipment specifications on which the order is being made.

Let me explain with an example:.

Suppose there are 100 motors falling into 6 categories as under:

Now the operations to carry-out the work on these machines vary with different ratings (specifications), often due to the variance in the amount of work involved.

We can have all operations of such 6 categories of 100 equipments in a single large tasklist, yet use in maintenance orders created on these equipments.

i.e., While creating the maintenance order, system would choose only those operations from the tasklist which are relevant to the equipment on which the order is being made .

Such tasklist  is called a ‘Configurable Tasklist’.

Let’s assume the common large tasklist (General Maintenance tasklist) we have for all these motors is  the one shown here, which is to be configured.

Now let us see how, the tasklist is configured.

1. Create the characteristics (CT04)

Create a capacity characteristic for ‘MOTOR_CAP’.

          Now, specify the values and save.

Similarly  create a Type characteristic for ‘MOTOR_MDL’.

Specify the values and save.

2. Create a class (CL02) ,

Say class  ‘MOTOR_TYPES’  (type '300'),

Assign characteristics created  above and save.

3. Object dependencies (CU01)

Create object dependencies as below:

Here dependency ‘SQI5.5’ illustrated.

Go to  ‘Dependency Editor’  and  specify the dependency  as shown here.

Come back to CU01 initial screen and set the Status to 'Released'

Similar dependencies to be made for all combinations of Capacity and Type, viz.,

SQI7.5,

SQI11.5,

SLR5,5,

SLR7.5   and

SLR11.5

Here another illustration is given for dependency ‘SQI7.5’.

Come back to CU01 initial screen and set the Status to 'Released'

4. Tasklist configuration profile (CU41)

Create a Configuration Profile selecting General Maintenance Tasklist.

Create as shown below.

When you click on Class assignment icon (2) above, you will be in the screen below.

Here, do not give values in the Characteristic value fields and Do not forget to select the 'Std Class' check-box.

5. Assign the class to equipments (IE02).

Assign class ‘MOTOR_TYPES’ to the these 100 equipments, with respective characteristic values as shown below:

(Go to 'Class Overview' screen and assign)

6. Assign the dependencies to tasklist operations (IA06):

As shown here:

Assign dependencies to all the tasklist operations which are equipment specific, in a similar way.

Leave the common operations untouched.

Now, the configuration is complete.

Let’s see what effect this exrecise has while selecting tasklist in an order  (IW31/32).

Menu :  Extras --> Tasklist selection --> Direct Entry

In the popup,  give the Tasklist group and counter, as shown.

In the resulting screen,  give the characteristic values of the order equipment,

Click ‘Back’ and go to the operations tab.

Here is the result:

System has chosen the relevant dependency operation (0040) and two operations, where no dependencies were specified. (0070, 0080).

This work can be extended to a tasklist of 100's of operations covering 1000s of equipments.

In my experience, very common application has been in Repair shops where equipments like Motors are repaired. Here very few numbers of Configurable tasklists are maintained covering 1000s of motors.

_________________________________________________________________________________________________________________________________

Related content:

http://scn.sap.com/docs/DOC-44023

Introduction:

Requirement to have Additional User-Fields in various Tabs of Equipment, Functional Location or Fleet Masters is very common. Though there is a hassle-free way of having the Z-fields through Class and Characteristic way, it has got its own limitations like unable to become a part of Standard reports.

In this article, the User-Exit way of having these custom fields has been elaborated.  Enhancement ITOB0001 has been demonstrated here. The process will be same for ITOB0003 (Fleet Master).

While trying to achieve this by joining the information pieces available in the forum and outside, the author spent sufficient time to achieve all requirements related to this.

Objective:

At the end of this article we will be able to:

1. Create our own fields in the Equipment, Functional Location or Fleet Masters
2. Input values and save these values to the related Database Tables
3. Edit these values through Tcodes IE02, IL02.
4. Will have these fields in standard reports like IH08, IH06, IE37.

Here we go (ABAP Workbench)

Step 1 (Preparation of EQUI Table)

Let’s suppose we are intending to have 40char long  field, named PO Number into the Equipment Master.

1^st step is to create this Z-field into the include table of EQUI table.

For this run Tcode SE11, Give value CI_EQUI and Go to Change mode. Add a Z-field  in this table say ZZITO_PONO

with component type TXT40 (for 40char long field). Activate table.

Note:

Here I want to share a vital information with the readers. i.e., as long as I tried this task with field names like ZZPONO etc, it never worked. And there consumed lot of time.  Then at some place I read about the SAP note 594757, which states that without a prefix ZZITO_  to theCustom fields, this task would not be successful.

Next,  we need to add this field ZZITO_PONO, also to the include table CI_EQUI _U  with component type IIND (Char1). Do it in the same way as above (through SE11). Activate table.

With this we completed adding our Z-field to the database table EQUI  (through its include tables)

Step 2 (Enhancement – Create Sub-Screen)

Create a project ZPMEQUIPthrough Tcode CMOD and assign the Enhancement ITOB0001.

Now Run Tcode SMOD with value ITOB0001 and click on Test button.

See here, we have 2 Function-exits and 5 Screen exits. Let’s select the first Screen, namely 1000 .  Double click on this and Create a Sub-Screen through the steps there on.

Now Click on Layout Arrow above to go to Screen Painter and Create your Fields here. In our case we are creating One field.

As shown in the picture , drag the 'T' icon to the screen are to create a Text field and name tis field as 'PO Number'.

Similarly drag the icon below to create an Input/Output field and Give the Dictionary address to the Input field i.e., EQUI-ZZITO_PONO .

(I hope you recall that this is the field we have created in EQUI table in the step1)

Step3 ( Enhancement – Give Codes in Function Exits)

We  have 2 function Exits, namely

EXIT_SAPLITO0_001

EXIT_SAPLITO0_002

The first Exit imports the Z-field values from the EQUI table to the Equipment Master

The second one exports Z-field values from the Equipment Master to the EQUI table.

Now the codes to be written in the Exits. 

Write following code in the include (ZXTOBU01) of function-exit EXIT_SAPLITO0_001.

TABLES: EQUI.
E_SUBSCREEN_NUMBER = '1000'.
I_OBJECT_TYPE = '02' .
I_ACTIVITY_TYPE = '3' .
EQUI-ZZITO_PONO = I_DATA_EQUI-ZZITO_PONO.

Write following code in the include (ZXTOBU02) of function-exit EXIT_SAPLITO0_002

E_UPDATE_DATA_EQ-ZZITO_PONO = EQUI-ZZITO_PONO.
E_UPDATE_FLAGS_EQ-ZZITO_PONO = 'X'.

Step 4 (SPRO  Preparation)

• Navigate to this section of SPRO.

• Select Screen Group (Equipment) on the right (Profile Standard) and D’Click on the Activity and layout of views on the Right.

• Give value 150 in the line of desired Tab page of Equipment Master.

• Assign this profile (in this case Standard) to the intended Equipment Category, through this setting.

After this SPRO setting, you will be able to see your Z-Field at the bottom of the Organization Tab page  of that particular Equipment Category. Verify by running IE02 / IE03 transactions.

Try by inputting a value, Save and rerun IE02 and verify your value is stored or not.

In fact, the part of Step3 above ( coding in the Exits ) did not work as long as I did not come across the above referred SAP note. After using the prefix ZZITO_ to the Z-field these codes started working. values inserting.

Almost done

Now if you go to IE03, unlike all other greyed-out fields, your Z-field will be seen Editable. Though there is no provision to save the edits here, you’d definitely like to have this too in Greyed-out mode.

For this we need to write a small code in the PBO (Process Before Output) module of the screen 1000 we have created.

Double click on the Screen number 1000 of the enhancement, (you are in the Flow Logic Tab) ,

D’Click on the STATUS_1000 of the PBO module. and insert this code between the MODULE, END MODULE lines like this

MODULE STATUS_1000 OUTPUT.
IF SY-TCODE = 'IE03'.
LOOP AT SCREEN.
SCREEN-INPUT = '0'.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
ENDMODULE. 

Related discussion:

Configure field selection for equipment user-fields

Lastly Do not Forget to

Activate the Function Group  XTOB  from  Tcode SE80.  Right click on the Function Group and click on the Activate option

Now the Last Step.

Step 5 (Have this Z-field in the Standard Report , in this case IE05, IH08)

To have our Z-field in IH08 output, first we need to know the structure of this report output.

For this click on any cell in the ALV screen and press F1 key.

Here click on the Technical Information icon. The resulting pop-up will show you the Structure against field name Table. Here the Structure is RIHEQUI_LIST .

Now through SE11 go to the above Structure, Click on an Append Structure on the Application toolbar and Create an Append structure having this field. Activate table.

Now Run IH08 and see in the output list in the Column Set (thelist not displayed). You should find this field PO Number.

Often you do not find this. It is time to clear ALV buffer through program BALVBUFDEL.

For this run Tcode SE38 give the above program and hit Execute.

Now run IH08 again and verify, your field is there.

Note:

This work is with a larger objective in mind to avoid re-inventing the wheel after sometime and at the same time providing the Total Solution about this task at one place.  This work involves Appending structures and Activation of Tables, which should be done by experienced ABPAers only.

Also this work can be extended to Functional Location Masters with the same enhancement used above and to the Fleet Masters with enhancement ITOB0003.

..and I feel it is important to mention the version I experienced all these and documented, it is ECC6.0 no EHPs.

Hope members find this useful.

Thank you

Jogeswara Rao K