Introduction

Recently I went through a Query, where the subject information was sought. i.e., How to have additional fields for Tasks ?. In fact SAP has provided the facility to have additional fields for line items of all Catalog tabs, namely Item, Cause, Task and Activity. The concerned enhancements are as under.

.The SPRO setting to have these Subscreen fields is very simple as shown below.

Objective

This documentation is intended to enable the readers to create the Custom fields for the line items of different Catalog Tabs of Maintenance Notification.

For Demo we are taking  the Tasks Catalog.

Part1

Create Custom fields in the Notification Table

The tables we need to append with our Z fields are as under:

For Item Catalog -- Table QMFE

For Cause Catalog -- Table QMUR

For Tasks Catalog -- Table QMSM

For Activities Catalog -- Table QMMA

The process of creating any custom field starts with creating a Data Element with desired Type and Length or with a Domain name and with the Field Labels we want to have for the Customer fields. For our Demo, we have created 2 Data Elements, namely :

1. Z_DELAY  - Type DEC Len 3 Dec 1  and Field Label ‘Delay(H)’
2. Z_REASON - Domain TXT40 and Field Label ‘Reason for Delay’)

Because we are understanding this implementation through Tasks Catalog, the table of our context is QMSM. We need to append our Z-fields to this through the Append structure in this Table. So I created an append Structure ZQMSM and assigned my Z fields as under..

As seen in the picture, we have created Two Customer-Fields namely ZZDELAY and ZZREASON. It is essential for all Customer fields used in Enhancement purposes to be prefixed with ZZ.

Part2

Enhancement and Screen-Exit

Run Tcode SMOD., Give value QQMA0011 and click on Test.  Here you will see number of screen-exits as under, provided for this purpose. Let's create the screen-0410 shown below. Also 2 Function Exits are provided for the purpose of Data Export to Table and Import to Notification. (Activate the Exit if found in Deactivated condition)

Refer to document User-Fields in QM and PM/CS Notifications : Screen-Exit QQMA0001 Part2 step4 onwardsfor details of creating a sub-screen. Remember that  your present table QMSM in place of the QMEL table of that document.

So we have created a sub-screen (screen no.410) with like this.

The input fields should be referred to the Dictionary fields we have just created. (QMSM-ZZDELAY and QMSM-ZZREASON) as shown above.

Activate the screen-painter.

Part3

Codes to be given in Function-Exits

Go to the following screen through SMOD.

Double click on the Function-Exit  EXIT_SAPMIWO0_015  and put the following code in the include   ZXQQMU14 .

*---------------------------------------------------------------------------------------------

TABLES: QMSM.

MOVE-CORRESPONDING I_VIQMSM TO QMSM.

*---------------------------------------------------------------------------------------------

Similarly put the following code in the include  ZXQQMU14   of the Function-Exit  EXIT_SAPMIWO0_016.

*---------------------------------------------------------------------------------------------

MOVE-CORRESPONDING QMSM TO E_VIQMSM.

*---------------------------------------------------------------------------------------------

Part4

SPRO setting to be done

Navigate to the Overview of Notification Type in SPRO.

Select your Notification Type (Here we are doing it in M2) and Enter the Screen Structure for Extended view

Give the screen number we have created (0410) in the Tasks Screen Area as shown below.

All Done

Let’s see the effect of work done so far.

Create a Maintenance Notification (IW21). Go to Catalogs & Codes  tab --> Give some item details in the Object Part & Damage  tab --> Go to Tasks tab fill a line item --> Select this line --> Click on the Lens icon in the left bottom (shown in the picture.

We see this in the pop-up

Success, Our user fields are appearing and ready for inputs. We get these user fields for all line items we have in this tab (Taks). Procedure is same for other Catalogs. Only Tables and Exits change as detailed in the beginning.

Test it

Create an M2 Notification, Give values to these User fields and Save. Now run IW22  go to the the User-fields pop-up and verify. The values you've put while creating the Notification will be seen there. Means the values are now a part of the QMSM table database.

These Screen-Exit documents are relevant to Quality Notification also.

Note

1. As this is largely a Technical job, it is recommended to be developed through an experienced ABAPer,

2. The Environment of Author is ECC 6.0 with no EHPs, hence the document applicability.

Hope this document too is helpful to many of our members.

Related posts by the author:

IWO10018: User Fields in Maintenance Order

ITOB0001, ITOB0003 : User-Fields in Equipment, Functional Location, Fleet Masters

User-Fields in QM and PM/CS Notifications : Screen-Exit QQMA0001

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

Author's other posts

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

Thank you

KJogeswaraRao

Introduction:

Graphs play a very vital role and have got great impact on business decisions. Senior Management, Clients, Customers all such stake-holders want to see information through Graphs to understand things easily. In SAP we have easy tool facility in ALV screens,  but ...... It has been observed that threads related to ALV Graphs are rarely seen here.

Objective:

At the end of this document, members will be familiar with the basics about the ALV Graphs, as well as about various features available. I am sure certain cross-section of members will be benefited by this post through which they will be learning how to interpret the ALV data into various types of Graphs.

Note:

The features discussed in this document are largely applicable to ALVs of custom programs developed through SAP Queries or ABAP codes using fm 'REUSE_ALV_GRID_DISPLAY'.  Things mentioned in this document are not applicable to ALV Graphs through Standard programs.

Here we start.....

How we get a Graph in ALV?

We know that Graphs need numeric fields for Y-Axis. So the ALVs  not containing a single numeric field are not Graph-relevant. Also the field for which you want to plot a Graph, looks like a Numeric, but if its data type is Character, then too it is not possible to plot a Graph for this field. In other-words we can say that, the ALV Layout where there is no icon in the Application Toolbar, we will not be able to draw Graphs.

Ok...Let’s come back to the Graph possibilities. We are in the following ALV screen. Here these are 2 fields for X-Axis namely FinYr and Equipment Description. We have 4 numeric fields for Y-Axis i.e., MTBR, MTTR, TotBDns and Avlb%.

Now select the first 2 columns (for X-Axis) and 3^rd column for Y axis (Means we are drawing graph for MTBR values) as shown in the picture below....

....and click on the Graph icon to get this graph window.

What we see in this picture is, system default scale presents only 5 bars in X-axis, for the rest we need to use horizontal Scroll (seen in the picture).

  Here we start our exploration of ALV Graphs  

1.To have all the Graph bars in one view (in other-words to remove horizontal scroll)

Place the Mouse pointer anywhere on the X-axis line and Right click, to get this menu.

Click on Format Axis... to get a pop-up screen. Go to the tab Scale.

Change the value shown above to as many as you want. In our case the bars are 8. So we change this value to 8. Now the graph has got rid of horizontal scroll showing a;; the Graph bars, like this.

2. The Y-Axis

We see the bar with maximum value is touching the top of the Graph area, by default setting, where we want create some room above this. This is nothing but we need to set the Y-Axis value. Our present maximum value of Y-Axis is 2400. We want to change this to say 3000.

In a similar way we did for X-axis, keep the mouse pointer anywhere on the Y-Axis line, and right click. Go to Scale tab. and .......

change the Maximum value to 3000. See the graph now.

3. Display values on the Bars:

Right click anywhere in the Plot Area to get this menu.

4. Change the Type of Graph (Say to a PIE chart)

Refer to menu picture in Point3 above. Click on chart Type and in the pop-up Select Pies.

Select the pie pattern you like, We here selected the 1^st one. Now see how our Graph looks like.

We got the Pies chart but the values disappeared. Follow the procedure explained in point3 to have Values of the Pies.

A number of Chart Type are available in this section of the Menu.

5. Titles to the Graph

Now Let’s Give a Title to our Graph and Configure it. Go to the Title tab of the menu in Point3, Give the Title you want. Say ‘MTBR Values FinYr-wise in Hrs’..

You can Drag & Drop this title to anywhere in the Chart Area. Also you can configure the Font, Font Size, Color etc by Right clicking on the edges of this Title box and choosing Format Chart Title.

In a similar way you can have Titles for yourAxes from the same tab (Title tab).

6. Similar Graphs can be drawn for the rest of the value fields viz., MTTR, TotBDn and Avlb% by selecting these fields as the 3^rd field for Graph (First two fields being FinYr and Equipment Description for X-Axis)..

7. Multiple Value Graphs:

Many times we have a requirement for multiple parameters for Y-Axis. This suits when we have an ALV report something like:

MTBR (Hrs) Financial Year wise:

In this case: The X-Axis will have FinYr, like the present case. The Y-Axis can have all the Equipment fields. In this case there will be 3 bars with different colors above each FinYr on X-Axis. This is a very suitable case for Multi-bar Graph because of the uniformity in UOMs for all 3 bars i.e., Hrs.

No two ALV fields in our current ALV are having same UOMs for demonstrating this case, we choose two fields  MTBR and Avlb%. for this demo.  I've selected first two columns(FinYr and Equipment Description), and MTBRand Avlb% (total 4 columns) . Now upon Clicking on the Graph icon, system presented the following Graph...

After Configuration

Now let’s discuss about the UOM (Unit Of Measure) on the Y-Axis. When this was a graph for MTBR alone the Y-Axis unit of Hrs is OK. But when we have plotted the Avlb% also, the Maximum value of which is 100, all these bars fell within the first grid line, which is 500 high.

8. Secondary Axis:

The above is the right situation to discuss about the Secondary Axis. i.e., we will have the vertical line on the right side converted as  Axis for the 2^nd bar (Avlb%). For this Right click on Plot Area ....

Select Secondary Axis.

Now your Graph looks better like this. (The Secondary Axis selected automatically has 0 - 100 Range)

To have values on the Secondary Axis, select as under in the Axes tab of Chart Options.

9. Changing the Colors of Bars, Pies etc.

For this Choose this option:

10. There are other features in the Plot Area / Chart Options Menu as shown below.

Some useful features are

- In the Grid-lines Tab youcan remove or set Grid lines  for both Axes.

- In the Legend tab you can have the Color Legend Settings.

You may explore what is there in other 2 tabs Data Table and Options. With this we have explored almost everything in ALV Graphs.

11. Now How to Save Graphs which we configured with so much effort.:

Simple,

Without closing the Graph-window in the ALV layout, click on the Save Layout button on the Application toolbar

and Save the Layout. Now your graph is saved. Any time you select this layout, the graph will be appearing, Similarly, when you save any Selection screen variant with this Layout, upon Executing the report you will be directly presented the Graph. Please read ALV Graphs : An Accidental Discovery for details.

Addition no.1

Graphs on Sub-Totals

While replying to a member's query, I'd recalled another feature that should be added to this document., i.e., Graphs on sub totals

Example

Suppose I try to draw a graph between Equipment and Breakdown duration for  IW28ALV by giving list of Equipments and range of Malfunction Start Date. In this case the output is likely to have several line items for a single equipment. The Graph (X-Axis) will be crowded with of Equipments repeating themselves several times. From such graph we would not get any information for analysis. Here comes the Sub-Total Graphs. For follow these steps. (Have Equipment and Breakdown Duration fields as 1st 2 columns for simplicity)

1. Sort the ALV by Equipment field

2. Select the Breakdown column and click on icon to display the totals.

(Notice that as immediately after this step a sub-total icon would be added to the toolbar next to icon.)

3. Now Select the Equipment column and click on this Sub-total icon. A report like this would appear.

This is giving Equipment wise Total Breakdown duration. Now let's draw graph for Equipment-wise Breakdown duration. For this, click on the icon at Red-Arrow shown in above picture. This collapses the details and only Sub-total are visible now. as under.

Now select the Equipment Column and click on the Graph icon to get the desired Graph. I have taken IW28 case for ease of demonstration of this section (Sub-total graphs).  As I said in the beginning, Graphs through standard reports are not that explorable as discussed in this document. For this very reason, I developed ZIW28 through Infoset query, where all these graph features are available.

Hope this document too helps members across the spaces in SCN.

Thank you.

Jogeswara Rao K

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

This document gives detailed list of all tables which are used in SAP PM/EAM. During archiving run, data must be deleted from each of the following tables.

1) Equipment

2) Functional Location

3) Notification

4) Work Order

5) Maintenance Plans

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

Dear All,

Every Organization has their own implementation questionnaire defined for all SAP modules. Following is the list of questions you can ask your client which will help you make your preliminary preparations as an input to your BBP discussions.

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.

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

Often it is seen that. Infoset-query users, stop exploring  at the 1st hurdle and switch to ABAP report programs, for requirements a little bit beyond simple ones. But, it is the author's experience, that we can use this tool (Infoset Query) given to Functional people by SAP,  to reach very close to the ABAP report programs, with features like those discussed in the other document and also some discussed here.

In this document the author tried to put together the pieces of his knowledge to present in the form of a document.

Tip1

To have a Tcode to your work in Infoset Query.

The following screen with report name appears..

Now you give this report name to your ABAPer and ask him to create a Tcode

OR

You do it yourself through SE93 Tcode, if you have access.

Steps for SE93

And Save. Thus your Infoset query will now be working with Tcode ZTCODE

(This applies also to Quick Viewer report SQVI)

Tip2

Calling Reports from Infoset Query reports.

The output of your query contains key fields like Notification no., Equipment No. etc.

It is natural that one wants to go to the Notification screen or the Equipment screen from the output.

Do this way.

In SQ01

We get this screen

Click here on  then on  then select

In the resulting pop-up, specify the Tcode you want to link with the Row in the SQ01 output.

Say IW23 and Save.

It is Done.

Now upon D'clicking anywhere on a particular line item in the query output, you are directed to IW23 screen of the notification of the line-item (row).

You can have many such report assignments.

Suppose you want to have IW22 also. Then repeat the same steps above to have IW22 Tcode.

Now when you D'click (anywhere) on one line-item (row) of the Query output, you will be presented a pop-up menu to select which one you want. i.e.,

Display Notification  or Change Notification. You are taken to the corresponding screen as per your choice.

Note:

1.If your Report Assignment option is found disabled, then the reason and setting to restore is here: How to make 'report assignment' available in 'SQ01'

2.We always need to remember that, after Tcode assigning, the modifications done in SQ02 or SQ01 would be in effect to the Tcode, only after executing SQ01 once.

3.More Details on this subject here: Calling Reports from an Infoset Query

Tip3

Make your report colorful with giving different colors in order to group columns

In SQ01 Basic ListScreen

Here just Drag & Drop the color from Right Tool-Box to the desired field in the Centre portion.

OR

Double click on a field in the Centre, to display field details and color options on the left. Now you select the color.

Example of such output.

Tip4

Always have Selection Fields from Infoset (SQ02).

What does this mean and Why?

This means

We have options for Selection Screen designing both in SQ02 and in SQ01.  It is advantageous if we declare selection options in Infoset (SQ02),

Here is how we do it. (In the Extras area), Go to Selections Tab, Click on Create icon, select Selection Criterion or Parameter like below.

And define the Selection field as under.

Observe here the strings written in Extras field.

OBLIGATORY makes this field in the selection screen mandatory.

NO INTERVALS removes the selection range (Removes the To field of the selection criterion)

NO-EXTENSION removes the multiple selection push button

DEFAULT 'M2' provides the M2 value as default in the field.

Like-wise you can design a selection screen as shown below by defining fields one after another.

Note that, we can declare only Standard Selection Fields here. Additional Fields are to be taken into Selection Screen only from SQ01.

The disadvantage in having these standard fields into selection screen from SQ01 is, the previously used values reappear as defaults for new running of the report. We need to erase and type our values. Also there is no provision for making a field mandatory.

Tip5

This is to develop queries in Standard Arearather than in Global Area.

What is this?

See the option below in SQ02 while creating an Infoset Query.

In the Query Areas above we have two options: Global Area, Standard Area.

When we are working in Development Server (client 200 or 210), we work in Global Area option, which generates a transport request, subsequently this will be transported to QAS and PRD at the end of work.

When we select Standard Area as the name indicates, it is client-specific. This means you can directly develop in PRD with this option. To have a Tcode for reports developed so, we need to use the same way explained earlier in this document. But  it is to be noted that, we get the report name from the PRD client where we developed the report, and create a Tcode in Development server (client 210 or 200) and same will be. transported to PRD.  (One time job)

The main advantage I always enjoyed here is, the moment some addition/deletion/modifications performed on this repor, it is instantly available in PRD.

(No hassles of transport requests). Only requirement is to run SQ01 once. The Tcode will be giving the changed report.

Also, the testing of the the report work is done in a perfect environment with real-time data.

(Working through the Global Area option in Development clients may be having its own advantages, like work back-up , but I never felt such necessity in my environment.If needed we can have a copy report in PRD itself)

Tip6

In case we do not want a certain category of records in the output, then go to SQ02 --> Extras--> Code tab --> Record Processing section, and

Give a code like the sample given below.

( check viqmel-abckz <> '' .)

What does this do?

With this code, the Infoset query does not bring any records where the ABC indicator field is blank.

Like-wise if you give a code like: check crhd-arbpl <> 'xyz123'.

the output will ignore the records with maint. work center value 'xyz123'.

(Note that these are permanent filters, For optional filters either the Selection Screen OR the Filter in the  ALV output display can be used.)

Tip7

F4 help related

F4 Help is not available in infoset query.

Tip8

How to create a radio button in SAP Query SQ01/SQ02.

Tip9

User defined fields

Tip10

We know that, the infoset reports work on Table joins in Infoset. In complex cases, where many tables are joined, the correctness of report depends upon the quality of joins we define. Though system suggests some joins, user can define more joins as per his table knowledge. This is what controls the multiplicity of identical rows appearing in the output sometimes.

It is seen that in situations where the user is unable to control the duplicate (or multiple) identical rows , the CHECK statement used in Tip6 works conditionally. In other cases this multiplicity becomes one of  the points where one is forced to go for an ABAP report.

The author has been working in this area since few years. This is an effort to share his knowledge about some very common requirements in this area with the forum. Hope member friends especially those who love Infoset queries, find this useful.

Thank you

KJogeswaraRao

PS: This post and all further posts in the area of Infosets have been compiled to this blogInfoset Queries: Collection of important posts

Introduction

One of the very frequently asked questions in this space, is about the subject matter, i.e., How can I add Custom fields to a Notification? A documentation on this subject would be helpful to the forum for ready reference.

Objective

This documentation is intended to enable the readers to create the Custom fields in different tabs of Maintenance Notification, update the Noyification Master data Table and also display these fields in IW28 / IW29 output.

Let's see how it is done.

Part1

Create Custom fields in the Notification Table

The table of our context is QMEL. We need to append our Z-fields to this through the include structure namely CI_QMEL.

The process of creating any custom field starts with creating a Data Element with desired Type and Length or with desired Domain name and with the Field Labels we want to have for the Customer fields. For our Demo, we have created Two Data Elements, namely :

1. Z_DELAY  - Type DEC Len 3 Dec 1  and Field Label ‘Delay(H)’
2. Z_REASON - Domain TXT40 and Field Label ‘Reason for Delay’)

Now let us create our Customer fields.

Run Tcode SE11 --> give value QMEL in the Database Table field --> Click on Display. Scroll-down to find include tableCI_QMEL. Double click on this,  Go to Change mode and Add Two new fields of our interest as shown in the picture and Activate.

As seen in the picture, we have created Two Customer-Fields namely ZZDELAY and ZZREASON. It is essential for all Customer fields used in Enhancement purposes to be prefixed with ZZ.

Part2

Enhancement and Screen-Exit

1, Create an Enhancement Project say ZPMNOT using Tcode CMOD.

2. Assign Enhancement QQMA0001 to this project .

3. Click on Components in the picture above to reach this screen.

4. Activate by clicking on the Activate Icon (shown in picture above)

Now the screen is like this.

As we see here, there are several screen-exits (27) and Two Function-Exits namely EXIT_SAPMIWO0_008 and EXIT_SAPMIWO0_009  in this enhancement.

Double Click on this screen number to create a Sub-Screen for holding our Custom Fields. You’ll get this pop-up.  Press Enter and Continue.

You’re in the screen below, where you’ll  give a Description,  Select the Subscreen Radio button,  Save and Activate.

Click on Layout Arrow in the Application Toolbar of (See the picture above) to reach the Screen-Painter pop-up window, where we will be creating :

1. A Box to hold our Z-fields
2. Text Fields to for Z-field  labels
3. Input Fields for Z-fields

The input fields should be referred to the Dictionary fields we have just created. (QMEL-ZZDELAY and QMEL-ZZREASON) as shown above.

Activate the screen-painter.

Part3

Codes to be given in Function-Exits

Go to the following screen

Double click on the Function-Exit EXIT_SAPMIWO0_008 and put the following code in the include  ZXQQMU07 .

*---------------------------------------------------------------------------------------------

TABLES: QMEL.

MOVE-CORRESPONDING I_VIQMEL TO QMEL.

*---------------------------------------------------------------------------------------------

Similarly put the following code in the include  ZXQQMU08   of the Function-Exit EXIT_SAPMIWO0_009.

*---------------------------------------------------------------------------------------------

MOVE-CORRESPONDING QMEL TO E_VIQMEL.

*---------------------------------------------------------------------------------------------

Part4

SPRO setting to be done

Navigate to the Overview of Notification Type in SPRO.

Select your Notification Type (Here we are doing it in M2) and Enter the Screen Structure for Extended view

Give the following settings in the Malfunction Tab (the tab where we want to have our custom fields)

Almost Done

Let’s see the effect of work done so far.

Create a Maintenance Notification (IW21). You will see the following addition of subscreen area in the Malfunction Start/End  Tab.

Enhancement has been added here by the system, in which our Custom fields appear with their labels and the input fields.

Now let’s add some values in these fields and Save the Notification.

Run IW22, open the Notification and verify whether the values are updated to table or not. If they are appearing  as you have entered and saved, this means the QMEL table has been updated with these values when Notification was saved.

Part5

Let's have these Custom fields in the Notification list reports namely the ALV of Tcode IW28/29 (QM10/QM11 in case of Quality Notifications)

So far we have succeeded in creating our Custom fields and updating the values to the Notification Master data. Next natural requirement of a user would be to have these fields in IW28/29 ALV screen. For this purpose we, need to create an Append Structure in the Structure RIHQMEL_LIST (RQMQMEL1 in case of QM10/QM11 reports), as shown in the picture below. The Tcode is SE11 again for this task. Here we have created an Append Structure named ZDLAY and in this structure we have added both the Custom fields.

Now let's create few more Notifications, with custom fields filled with some values. Now run IW28 with selection parameters to display these Notifications we created. Click on the icon shown , You'd find the Custom fields in the Column-set list, Bring them to Displayed list on the Right hand side.

Related SAP Note: 370191  (Image of the note is attached herewith for the benefit of the members who can not access OSS)

Part6

Now if you go to IW23 of any of these Notifications, unlike all other greyed-out fields, the Custom fields will be seen Editable. Though there is no provision to Save the edits here, you’d definitely like to have these fields too in Greyed-out mode.

For this we need to write a small code in the PBO (Process Before Output) module of the screen 0103 we have created.  Double click on the Screen number 0103 of the enhancement,

Un-comment line MODULE STATUS_103. and D’Click on the STATUS_0103 of the PBO module. Insert the following code between the MODULE, END MODULE lines like this.

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

MODULE STATUS_0103 OUTPUT.

     IF SY-TCODE = 'IW23'.

          LOOP AT SCREEN.

               SCREEN-INPUT = '0'.

               MODIFY SCREEN.

          ENDLOOP.

     ENDIF.

ENDMODULE.

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

Lastly Rememebr to
Activate the Function GroupXQQM from Tcode SE80. Right click on the Function Group and click on the Activate option

...... and thus we reach to the end of this knowledge sharing Documentation.

Note

1. As this is largely a Technical job, it is recommended to be developed through an experienced ABAPer, especially Part1 which involves Activating the Standard table QMEL.

2. The Environment of Author is ECC 6.0 with no EHPs, hence the document applicability.

Expecting this document too would be of use to many members from mainly from EAM and QM spaces.

Related content

User-fields in Catalog Tabs of Notifications

*Author's other Posts

Thank you

KJogeswaraRao

Foreword

The author believes that the tip given in this document  simplifies and drastically cuts down the amount of data upload to QS41 transaction, In fact this tip should be made use of invariably by every-one who designs the Catalogs & Codes to the Equipments. 

What is it?

An addition of character ‘&’ at the end of Code Group Description helps the Code-text (kurztext) to be very short, but while using the Code-texts  are prefixed by Code Group Texts giving full meaning.

This is being explained through Screen-captures in the following example .

QS41:

1.Object part Code Group ‘MOTOR’

  Description : ‘MOTOR &’

Codes

2a. Damage Code Group:  ‘SHFT’

Description :  ‘SHAFT&’

Codes

2b. Damage Code Group:  ‘FNDN’

Description :  ‘FOUNDATION &’

Codes

OQN6:

3. Catalog Profile

The result in IW21 / IW22

Note:

1. The above explanation is applicable for all Catalogs (B,C,2,5, A &  others).

2. Because this is a change in Description field, it is applicable to the Code Groups created and used earlier. Accordingly, the Code-Texts will  be modified in all History Notifications.

Hope members find this article useful.

Thank you

KJogeswaraRao

Introduction

Recently I went through a Query, where the subject information was sought. i.e., How to have additional fields for Tasks ?. In fact SAP has provided the facility to have additional fields for line items of all Catalog tabs, namely Item, Cause, Task and Activity. The concerned enhancements are as under.

.The SPRO setting to have these Subscreen fields is very simple as shown below.

Objective

This documentation is intended to enable the readers to create the Custom fields for the line items of different Catalog Tabs of Maintenance Notification.

For Demo we are taking  the Tasks Catalog.

Part1

Create Custom fields in the Notification Table

The tables we need to append with our Z fields are as under:

For Item Catalog -- Table QMFE

For Cause Catalog -- Table QMUR

For Tasks Catalog -- Table QMSM

For Activities Catalog -- Table QMMA

The process of creating any custom field starts with creating a Data Element with desired Type and Length or with a Domain name and with the Field Labels we want to have for the Customer fields. For our Demo, we have created 2 Data Elements, namely :

1. Z_DELAY  - Type DEC Len 3 Dec 1  and Field Label ‘Delay(H)’
2. Z_REASON - Domain TXT40 and Field Label ‘Reason for Delay’)

Because we are understanding this implementation through Tasks Catalog, the table of our context is QMSM. We need to append our Z-fields to this through the Append structure in this Table. So I created an append Structure ZQMSM and assigned my Z fields as under..

As seen in the picture, we have created Two Customer-Fields namely ZZDELAY and ZZREASON. It is essential for all Customer fields used in Enhancement purposes to be prefixed with ZZ.

Part2

Enhancement and Screen-Exit

Run Tcode SMOD., Give value QQMA0011 and click on Test.  Here you will see number of screen-exits as under, provided for this purpose. Let's create the screen-0410 shown below. Also 2 Function Exits are provided for the purpose of Data Export to Table and Import to Notification. (Activate the Exit if found in Deactivated condition)

Refer to document User-Fields in QM and PM/CS Notifications : Screen-Exit QQMA0001 Part2 step4 onwardsfor details of creating a sub-screen. Remember that  your present table QMSM in place of the QMEL table of that document.

So we have created a sub-screen (screen no.410) with like this.

The input fields should be referred to the Dictionary fields we have just created. (QMSM-ZZDELAY and QMSM-ZZREASON) as shown above.

Activate the screen-painter.

Part3

Codes to be given in Function-Exits

Go to the following screen through SMOD.

Double click on the Function-Exit  EXIT_SAPMIWO0_015  and put the following code in the include   ZXQQMU14 .

*---------------------------------------------------------------------------------------------

TABLES: QMSM.

MOVE-CORRESPONDING I_VIQMSM TO QMSM.

*---------------------------------------------------------------------------------------------

Similarly put the following code in the include  ZXQQMU14   of the Function-Exit  EXIT_SAPMIWO0_016.

*---------------------------------------------------------------------------------------------

MOVE-CORRESPONDING QMSM TO E_VIQMSM.

*---------------------------------------------------------------------------------------------

Part4

SPRO setting to be done

Navigate to the Overview of Notification Type in SPRO.

Select your Notification Type (Here we are doing it in M2) and Enter the Screen Structure for Extended view

Give the screen number we have created (0410) in the Tasks Screen Area as shown below.

All Done

Let’s see the effect of work done so far.

Create a Maintenance Notification (IW21). Go to Catalogs & Codes  tab --> Give some item details in the Object Part & Damage  tab --> Go to Tasks tab fill a line item --> Select this line --> Click on the Lens icon in the left bottom (shown in the picture.

We see this in the pop-up

Success, Our user fields are appearing and ready for inputs. We get these user fields for all line items we have in this tab (Taks). Procedure is same for other Catalogs. Only Tables and Exits change as detailed in the beginning.

Test it

Create an M2 Notification, Give values to these User fields and Save. Now run IW22  go to the the User-fields pop-up and verify. The values you've put while creating the Notification will be seen there. Means the values are now a part of the QMSM table database.

These Screen-Exit documents are relevant to Quality Notification also.

Note

1. As this is largely a Technical job, it is recommended to be developed through an experienced ABAPer,

2. The Environment of Author is ECC 6.0 with no EHPs, hence the document applicability.

Hope this document too is helpful to many of our members.

Related posts by the author:

IWO10018: User Fields in Maintenance Order

ITOB0001, ITOB0003 : User-Fields in Equipment, Functional Location, Fleet Masters

User-Fields in QM and PM/CS Notifications : Screen-Exit QQMA0001

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

Author's other posts

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

Thank you

KJogeswaraRao