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 explains the Extraction and Selection Criteria for Long text of various SAP Master data objects.

Process for extracting the long texts data is – Go to SE38 and give the program as RSTXTC3, execute and enter the selection criteria as below for different objects. After entering the required selection criteria, select PROGRAM - EXECUTE and PRINT, save to local file.

Go to SE38

Selection Criteria:

1. Equipment Long Text

Object                  : EQUI

Text                     : 18 Digit Equipment Number (000000000010066375)

                                   [From and To values depend on Number Range]

Text ID                 : LTXT

Language           : EN

2.     Equipment Internal Note

Object                 : EQUI

Text                    : 18 Digit Equipment Number (000000000010066375)

                               [From and To values depend on Number Range]

Text ID               : INTV

Language             : EN

3. Equipment Task List Header Long text

Object                  : Routing

Text                      : CLIENT+”E”+8 DIGITGROUP NUMBER+* (ex. Task list 90 in client 230 – 230E000000090*)

                                   [From and To values depend on Number Range]

Text ID                  : PLKO

Language             : EN

4.   Equipment Task List Operation Long text

Object                  : Routing

Text                      : CLIENT+”E”+8 DIGITGROUP NUMBER+*(ex. Task list 90 in client 230 – 230E000000090*)

                                   [From and To values depend on Number Range]

Text ID                  : PLPO

Language             : EN

5.  Functional Location Task List Header Long text

Object                  : Routing

Text                     : CLIENT+”T”+8 DIGIT GROUP NUMBER+* (ex. Task list 9 in client 230 – 230T00000009*)

                                   [From and To values depend on Number Range]

Text ID                  : PLKO

Language             : EN

6. Functional Location Task List Operation Long text

Object                  : Routing

Text                     : CLIENT+”T”+8 DIGIT GROUP NUMBER+* (ex. Task list 9 in client 230 – 230T00000009*)

                                   [From and To values depend on Number Range]

Text ID                  : PLPO

Language             : EN

7.   General Task List Header Long text

Object                  : Routing

Text                     : CLIENT+”A”+8 DIGIT GROUP NUMBER+*(ex. Tasklist 7006 in client 230 – 230A00007006*)

                                   [From and To values depend on Number Range]

Text ID                  : PLKO

Language             : EN

8.  General Task List Operation Long text

Object                  : Routing

Text                      : CLIENT+”A”+8 DIGIT GROUP NUMBER+* (ex. Task list 7006 in client 230 – 230A00007006*)

                                   [From and To values depend on Number Range]

Text ID                  : PLPO

Language             : EN

9.   Maintenance Plan Long text

Object                  : MPLA

Text                     : 12 Digit Maintenance plan Number (000000023899)

[From and To values depend on Number Range]

Text ID                  : LTXT

Language             : EN

10.  Maintenance Item Long text

Object                  : MPOS

Text                      : 16 Digit Maintenance Item Number (0000000000000309)

                                     [From and To values depend on Number Range]

Text ID                  : LTXT

Language             : EN

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. 

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

Introduction

SAP offers the use of IBIP supported transactions from within the LSMW, But what if you cannot provide authorization to the PM users for LSMW with

recording capabilities in the production system or the LSMW is too complex in case of multi structures for the non technical user ?

Here is another alternative, Excel IBIP Tool  is an Excel  spreadsheet which enable plant maintenance data migration directly from the IBIP transaction .

This excel based  tool can generate flat files that matches SAP IBIP structures and hierarchy

Table of Contents

I. Requirement

II. Solution

III. How to do

1. 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- video exemple here

2. Upload Flat file to SAP

Upload Flat File from presentation server to IBIP transaction  

I. Requirement

• Microsoft excel 2007- 2013
• Macro enabled
• Download here the IBIP Tool

II. Solution.

• Step 1 : Create  IBIP Template Multi/single  level structures
• Step 2 : Fill the master data
• Step 3 : Generate Flat file from Excel
• Step 4 : Upload flat file with IBIP transaction
  
  

III. How to do

Exemple 1: Equipment creation with user status

Step 1 : Create template  

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

   1. Select Prepare to create new Tempate

   2. Select the Multi structures radio button

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

   4. Select the IBIPEQUI  structure  in the data structure listbox

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

Step 2-3  Fill template data  and press Execute

   6. Fill the template created from row4 in the data required for uploading to SAP

   7. Press on execute to generate the Flat file

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

Step 4 : Upload the Flat File to the IBIP transaction

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

            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"

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

2015/05/24:

• Updated Version 1.2 is available.
• FlatFile will be stored in the temp folder .
• Corrected screen shots.
• Added Tutorials  Video for General task list

Comments are welcome.

Cheers

Ziv

Background

In addition to the  IBIP tool for which was introduces    here

Here now an example how to upload BOM to SAP with multi structures like sub-items or/and long text using excel generating flat files , the following approach can be alternative to LSMW for this usage .

This solution provide excel spreadsheet generates flat files that can be uploaded to Standard Batch Input program for creating BOM with or without long texts ,This can save development of designated ABAP programs which writes data to a sequential file in the format required by the ABAP programs (RCSBI010 ,RCSBI040)

This spreadsheet support transactions :

• IB01 for equipment BOMs

• CS01 for material BOMs

• IB11 for functional location BOMs

• CS51 for standard BOMs

• CV11 for document structures

How to do it  (see exemple video for CS01 transaction)

step 1 : Download the BOM tool here

Step 2 : Enables Macros in the Excel menu

Step 3 : Create  template using structures (BGR00,BICSK,BICSP..)  - choose just the relevant fields .

Step 4 : Fill the BOM header and items data and press Execute in the Excel ribbon button

Step 6 : Upload the flat file generated at step 3 to the application server with transaction CG3Z
              the target file name is : BOM CREATE , the source file is the flat file that was genarated in step 4.

Step 7 : Run Transaction OS41 , Fill Logical File name : CS_BI_BOM_CRATE

Step 8 : See the program log and check SAP  in transaction CS02

    lets check in transaction CS02 that the BOM was created correctly

Examples( see attached )

Exemple 1 : program RCSBI010 -  (Create BOMs using Batch Input) Standard Batch Input program for creating BOM (Bill of material)

Exemple 2 : program RCSBI040 -  (Create BOMs using Batch Input) Standard Batch Input program for creating BOM (Bill of material) with long text

Comments are welcome

Best Regards

Ziv.

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

Default Notification Header Text

Introduction

Various posts over the years have expressed similar requirements: Loosely quoted they read:

"How can I default a (standard) text into the notification header text? I want my end users to be prompted to complete a set of questions"

The following document provides sufficient detail for this requirement to be achieved.

Realization Approach

Many posts have suggested the use of standard texts and the SAP supplied enhancement QQMA0025 - PM/SM Default values when adding a notification. The solution outlined in this document utilizes standard texts and the SAP supplied enhancement.

Standard Text

It is assumed that the text to be defaulted into the notification header text is defined as a standard text. Standard texts are maintained with the transaction SO10 in an SAP ECC system and can be read with the function READ_TEXT.

SAP Enhancement QQMA0025

The SAP enhancement is designed to allow the setting of default values in the notification, and dependent objects like activities, items and tasks. The interface provides the notification header, notification type configuration and the notification dependent objects.

Solution 1: Default Standard Text in the notification long text

Step 1: Read the standard text

the standard text can be read with the function module READ_TEXT; In this case reading a text with the name ZPMWOCMN_01.

CALL FUNCTION 'READ_TEXT'     EXPORTING       ID                      = 'ST'       LANGUAGE                = SY-LANGU       NAME                    = 'ZPMWOCMN_01'       OBJECT                  = 'TEXT'     TABLES       LINES                   = LT_LINES_STD     EXCEPTIONS       ID                                =  1     LANGUAGE                = 2       NAME                          = 3       NOT_FOUND              = 4       OBJECT                       = 5       REFERENCE_CHECK         = 6       WRONG_ACCESS_TO_ARCHIVE = 7       OTHERS                  = 8.

Step 2: Initiate the notification long text processing

CALL FUNCTION 'INIT_TEXT'     EXPORTING       ID       = 'LTXT'       LANGUAGE = I_VIQMEL-KZMLA       NAME     = wa_notification_text_name       OBJECT   = 'QMEL'     IMPORTING       HEADER   = WA_HEADER     TABLES       LINES    = LT_LINES_NOT     EXCEPTIONS       ID       = 1       LANGUAGE = 2       NAME     = 3       OBJECT   = 4
OTHERS   = 5

Step 3: Merge the standard text lines with the notification lines and save

APPEND LINES OF LT_LINES_STD TO LT_LINES_NOT.   CALL FUNCTION 'SAVE_TEXT'     EXPORTING       HEADER   = WA_HEADER     TABLES       LINES    = LT_LINES_NOT     EXCEPTIONS       ID       = 1       LANGUAGE = 2       NAME     = 3       OBJECT   = 4
OTHERS   = 5.

Step 4: Update indicator in header that long text exists

  E_VIQMEL-INDTX = 'X'.

Solution 2: Default Standard Text in the notification long text and branch to long text editor

similar to above, except after Step 1, the following steps:

Step 2: Merge standard text text and count lines

APPEND LINES OF LT_LINES_STD TO LT_LINES_NOT.
L_CNT_LINES = LINES( LT_LINES_NOT ).

Step 3: Call long text editor

CALL FUNCTION 'LANGTEXT_ONLY'     EXPORTING       OBJECT                = 'QMEL'       OBJECT_NR             = wa_notification_text_name       SPRAS                 = SY-LANGU       TXTID                 = 'TEXT'       X_XAKTYP              = 'H' "Creation mode        SAVE_MODE             = 'X'       TEXT_HISTORY          = I_TQ80-QMLTXT01       TEXT_PROPERTY         = I_TQ80-QMLTXT02       COUNT_INLINE          = L_CNT_LINES       IV_SUPPRESS_END_SPACE = SPACE                     TABLES       T_INLINES             = LT_LINES_NOT.

Hints and Tips

You can review the subroutine TEXT_ANLEGEN_F50 in the function group IQS0 or the function module IQS0_ADD_NOTIFICATION_LONGTEXT for more details of notification text processing. There you will see how to protect lines of text and to create history lines.

Limitations

The SAP enhancement isn't ideally suited to the generation of long text, because the interface does not allow the maintenance of the indicator (   WVIQMEL-INDTXTUPD) used in the function group IQS0 to indicate text processing changes. Without the user processing the long text, the defaulted long text will not be saved.

Other Frequently Asked Questions

Is there a possibility using configuration?

In short - no. There is no possibility using configuration.

Objective:

To develop an ALV report showing Equipment and the Class assigned to it.

Please see the screen capture of a report showing Equipment vs Class assigned.

Do we have such report in standard system? We didn't get when we needed this years ago. Ours is still ECC6.0 with no EHPs.

We expected such information from standard reports like IH08, but same unavailable.

Then I have developed a Quick-view fulfilling this need and assigned a Tcode to it.

Are you also one among those who need this report? If yes go through this document. It is a simple method of developing this report in PRD server itself through SQVI.

Step1

Run SQVI Tcode.

Create a QuickView eg., Equip_Class,'

Give a Title ýou like e.g., Equipment vs Classification

Choose 'Logical Database'  in the Data Source.

Type 'EQI' in the Logical Database field, and press Enter to continue.

(All this Means you are about to create a Quickview using Logical DatabaseEQI.)

Step2

If you are in 'Basis Mode' click on this button to switch to 'Layout Mode'.

Now you'll see the following.

You need not have to do anything on the left side 'Data Fields' area.

See in the Right side 'List fld. select.' tab.

Choose the fields you desire to have in the ALV output here. Select these from 'Available fields' (Right side list) and transfer to Left side.

In the above example, I have chosen 6 fieds as per my requirement.

Define your own Selection screen

Go to 'Selection fields' tab.

Here you'll see 4 fields have been already given by the system (with Lock icons), which you can not remove.

But you can add your own fields for selection criteria.

In the example below, I have added 5 such fields (5 to 9).

Step3

It is almost done now.

Save the work done so far by clicking on the Save button at the top of the QuickViewer screen..

Now click on Execute button to run this program.

The Selection-screen

The output

A report for Functional Location vs Class can also be made in exactly similar way by using Logical database TPI.

Step4

We have done all this work in PRD server and have seen the realtime data in the output by executing the QuickView.

Instead of going to SQVI and executing this quickview from there everytime, you can give a Tcode to this work.

Get the Report Name.

In the SQVI initial screen, select your Quickview, click on Quickview at top left corner --> Additional Functions --> Display Report Name.

You will be getting this pop-up displaying the Report name you've just made.

Now to create a Tcode there are two options.

1. Ask your technical person to create a Tcode you desire with the program name shown above.

OR

2. Do it yourself in ABAP client through SE93 Tcode and transport it to PRD.

This applies to the other Quickview also (FL vs Class)

Conclusion

Most of the steps described here apply while dealing with Infoset Queries also (SQ02, SQ01).

SAP has provided many Logical Databases in the system, which often come to our rescue while working with Queries and when we do not get proper tables to fulfill our requirements.

This document has been made with beginners in mind. For members with SQVI experience, it is a simple communication to use Logical database EQI or TPI to make Technical object vs Classification Report.

--------o--------

The purpose of this document is to provide an insight in to the SAP RDS Asset Analytics KPI’s. The document supplements a previous document on ‘Asset Analytics for Enterprise Asset Management’ posted by Peter Huyen which is available on SCN, a direct link to the document is provided below.

As a pre-requisite to understand the SAP Rapid Deployment Solutions Asset Analytics I recommend reading the following:

• Asset Analytics for Enterprise Asset Management by Peter Huyen
  • http://scn.sap.com/community/eam/blog/2012/03/31/asset-analytics-for-enterprise-asset-management
• Asset Analytics presentation by Hemant Rathod – SAP Labs LLC
  • http://events.asug.com/2012ac/2608_asset_analytics_.pdf
• Useful material on SAP RDS EAM at SAP Service Marketplace.
  • You will require a SAP Service Marketplace User ID to access below URL.
  • https://Service.sap.com/rds-EAM
• Asset Analytics KPI’s Detail Information can be accessed through below URL:
  • You will require a SAP Service Marketplace User ID to access below URL.
  • Note: Below URL and screenshot were provided to me by Peter Huyen - thanks Peter
  • https://websmp106.sap-ag.de/~sapidb/012002523100017033542013E/RDS_Cockpit/step-by-step-guide-iframe.html#RDS_EAM_ERP605V2_SERV

Note:

• Due to SAP Copyright Infringement I will not be attaching any documents. For those of you who have access to the SAP Service Marketplace you should be able to access the relevant documents through the URLs provided above.
• For the commonly used standard SAP Reports please check Standard SAP Plant Maintenance Reports

The SAP RDS Asset Analytics solution offers a range of predefined KPI's, these KPI’s have been categorised as:

• Maintainability
• Reliability
• Availability
• Supplies
• Sustainability

As part of the SAP RDS Asset Analytics solution there are 31 predefined KPIs, which are listed below.

The source for the above information is:

• Slide 30 and 31 of the Asset Analytics presentation by Hemant Rathod – SAP Labs LLC - URL provided in the pre-requisite reading section above.
• The Asset Analytics ‘KPI’s Detail Information’ document available on SAP Service Marketplace - URL provided in the pre-requisite reading section above.

Note: You will see a gap in the KPI numbering, this is due to RDS_EAM_028 missing from the list – I did not see RDS_EAM_028 in the ‘KPI’s Detail Information’ Excel document on SAP Service Marketplace.

The below section provides a high-level description of each of the KPI’s listed above. I hope the information provided in this document along with references to other sources will provide you with sufficient understanding of the SAP RDS Asset Analytics KPI’s.

Note: Please contact me if you have any feedback or can help 'fine tune' the KPI descriptions and / or provide formula / formulae for calculating the KPI's.

• RDS_EAM_001  - Total Person-Hour Capacity Available for Maintenance

• RDS_EAM_002  - Capacity for Preventive Maintenance

• RDS_EAM_003  - Capacity for Predictive Maintenance

• RDS_EAM_004  - Capacity for Breakdown Maintenance

• RDS_EAM_005  - Percentage of Work Orders for Preventive Maintenance

• RDS_EAM_006  - Percentage of Work Orders for Predictive Maintenance

• RDS_EAM_007  - Percentage of Work Orders for Breakdown Maintenance

• RDS_EAM_008  - Percentage of Work Orders for Emergency Requirements

• RDS_EAM_009  - Percentage of Work Orders for Critical Assets

• RDS_EAM_010  - Percentage of Capacity used for Performing Maintenance Tasks

• RDS_EAM_011  - Percentage of Work Orders Resulting from Condition Monitoring

• RDS_EAM_012  - Backlog of Activities

• RDS_EAM_013  - Completion Rate

• RDS_EAM_014  - Schedule Adherence

• RDS_EAM_015  - Notification Response Time

• RDS_EAM_016  - Maintenance Rework

• RDS_EAM_017  - Maintenance Cost as Percentage of Replacement Value

• RDS_EAM_018  - Budget Utilization

• RDS_EAM_019  - Number of Work Orders per Clock Hour

• RDS_EAM_020  - Number of Notifications per Clock Hour

• RDS_EAM_021 - Mean Time Between Failure (MTBF)

• RDS_EAM_022 - Mean Time To Repair (MTTR)

• RDS_EAM_023 - Mean Time Between Repair (MTBR)

• RDS_EAM_024  - Technical Availability of Assets

• RDS_EAM_025  - Operational Availability of Assets

• RDS_EAM_026  - Number of Stock Outages

• RDS_EAM_027  - Orders Delayed Due to Stock Outages

• RDS_EAM_029  - Subcontracted Work as a Percentage of Total Work

• RDS_EAM_030  - Maintenance Request to Correct Safety Incidents

• RDS_EAM_031  - Maintenance Request to Correct Incidents Due to Reported Injuries

• RDS_EAM_032  - Maintenance Request to Correct Incidents related to Environmental Compliance

I hope you find the document useful and that it can be used as a basis to understand the SAP RDS Asset Analysis KPI's. As mentioned above, if you have any feedback or can help update the document with additional detail on the KPI's including formula / formulae used to calculate the KPI' then please feel free to contact me.

A refurbishment order (IW81) differs from other order types in many ways:

1) The order is mostly created with respect to a material/spare (which may or may not be an equipment).

2) Split valuation is activated for the material.

3) Settlement is done to the material itself against which we are creating refurbishment order.

4) Provision of issuing as well as receiving the material wrt the order no. is there. Normal maintenance order only has provision for issuing the material wrt order no.

There is also a slight difference in how the actual cost is calculated in a refurbishment order. Below is the step by step procedure on how the cost is populated in a refubishment order.

a) Once you plan the order wrt material required and manhours required and release the order, you will get planned costs populated in the order.

b) After you issue the material to be refurbished and components required to refurbish the material along with confirming the operation, you will get actual costs populated in the system.

c) Now, when you receive the material against refurbishment order using IW8W, the actual cost again gets modifed. Below is the logic for this cost calcuation.

The current actual material cost is minus 436.01. The logic is that when we received the refurbished material using transaction IW8W, the cost in the material master for refurbished material (say valuation type C2) was 468.83.

The system calculates the actual material cost as 32.82 - 468.83 = -436.01

And the actual total cost of refurbishment is 100 - 436.01 = -336.01

It is this negative cost which would be settled to the material when we execute the settlement KO88.

It is a common understanding that Settlement of a Refurbishment Order happens on Material. This is true, but not always.

It depends upon whether the price control indicator for the Batch material in material master is Standard (S) or Moving average price (V).

Batch material refers to the material with Valuation types C1/C2/C3. So if the price control indicator of Batch material is:

1. V: Settlement happens on the Material Master.
2. S: Settlement doesn’t happen on Material Master, but on price difference account.

Scenario 1: Consider material 795, with Batch material’s price indicator = V

Have 1 unit each of batch C1, C2, C3. Therefore the material valuation = (200+80+10)/3 = 96.67

Created a Refurbishment Order for this material (for C3) using IW81. Done GI. Done GR using IW8W.

After GR, we have 1 unit of C1 and 2 of C2.

Therefore, Material valuation = (1*200 + 2*80)/3 = 360/3 = 120

Cost incurred in WO: 10 for GI of 1 unit of C3 and -80 for GR of 1 unit of C2.

So the balance amount on WO is -70.

Settlement: Since batch material price indicator is V, therefore settlement of balance amount happens on material.

So the settlement happens on GL Spare Parts, against material master.

Since the settlement happens on material, therefore material valuation also changes as:

1*200 + 2*80 = 360

360-70 (for settlement on material) = 290 /3 = 96.67

Scenario 2: Consider material 796, with Batch material’s price indicator = S

Have 1 unit each of batch C1, C2, C3. Therefore the material valuation = (200+80+10)/3 = 96.67

Followed same steps as above. Create Refurbishment Order, GI, GR. Skipped the screenshots.

Valuation of material after GR, but before settlement.

Therefore, Material valuation = (1*200 + 2*80)/3 = 360/3 = 120

Settlement: Since batch material price indicator is S, therefore settlement doesn’t happen on material, rather on Price diff account.

So the settlement happens on GL Price Diff account and not on material master.

Since the settlement doesn’t happen on material, therefore no change in material valuation:

1*200 + 2*80 = 360

360 - 0 (for settlement) = 360 /3 = 120

Infoset Query: User Defined Fields_______________________________________________________________________

Author: Jogeswara Rao Kavala

1.Introduction
We know that Infoset Query is a report development tool given to Functional people by SAP. Using this, a Functional person can be independent of ABAP to a large extent in the area of Report programs. Infoset query  is cross-functional application. Though this document demos in Plant Maintenance environment, it is believed to be useful for other Functional people also.

This document is based on the assumption that the readers have basic working knowledge in the area of Infoset Queries which involve Tcodes SQ03, SQ02 and SQ01.  Points discussed here, take an Infoset query closer to an ABAP report program.

2. Customer defined fields

Most of us, especially beginners, usually work on standard fields available in the tables we work on, in the Infoset (SQ02).  But, sooner almost everyone gets the desire to have his/her own defined fields in the report as a function of standard fields. Such fields are also referred to as Derived fields, Local fields or Additional fields.

About the task chosen to Demo this

A client has a requirement to compute the duration of fields Required Start Date & Time and Required End Date & Time in a Notification (VIQMEL table). The same is taken for demo here. Hereon we will be referring to this field as ' mnthr ' .

(The above is an example of how  requirements arise for derived fields. In IW28 standard report,  we have computed duration for Malfunction Dates, but not for the fields referred above.)

Two ways to do this:

1.To define and compute this 'mnthr' field in the Infoset (SQ02)

Define:

SQ02 --> Click on Extrasbutton

Click on Create icon in the Extras Tab.

In the pop-up, select Additional Field option and give the Additional field name as say MNTHR.

Continue and define the details and Continue .

After this step we see a node created for Additional fields in the left side.

Also in Extras tab on the right.

Now, place the cursor on the field name and click on ' CodingForAddition'  icon.

You are now taken to the Code tab.

Here, give the code to calculate the Duration (mnthr)

Note:

We have used a function module to easily calculate the duration between two Dates and Times.

This might  look complex initially for beginners, but if you try it is simple application to understand.

One data type ‘duration’ (type i) declared here for temporary use in this code, because we import the duration from FM in this form (seconds).

So, we got the value here for the additional field, we defined (in the form of seconds). To convert the same into Hrs the last line of coding used.

(In other situations, the additional-field value calculation might be much simpler like some arithmetic expression of few standard fields.  The coding will be done accordingly)

All done. Now, you can drag this mnthr intodesired Field Group on the right, to have this field in SQ01 for reports.

2.Now let’s see how we do this in Infoset Query way (SQ01)

Reach the following field selection screen in SQ01.

Then,

We see this (Short Name, Local field indicator columns appear)

Now go to the fields which are the components of the formula to calculate your duration (mnthr)

We know they are Required Start Date & Time and Required End Date & Time.

(I need not mention that these fields have come from the VIQMEL table fields selected in Infoset, SQ02)

And identify them with some Short names like shown below.

Now let us create our Local field (Additional field)  mnthr, as under.

Now define the parameters of the field as under.

Now we need to give our code in the Calculation formula seen at the bottom.

If our code is simple we can give it in this screen itself. If it contains more if s then we need to click on Complex Calculation button and to give the full code. (Our present case needs to go here)

So now, are giving the following code in the complex calculation screen.

(Note that what we mention against ‘Condition’ fields here, are nothing but ‘IF’ in ABAP coding.)

You may try to understand the logic (Condition vs Formula) given above, so that the formula giving would be easier for your other requirements.

Select this field by ticking the Check-box in the Field selection screen to have it in the Basic List Fields.

(Also we need to select this field in Basic List screen too as we always do.)

Now this field will appear in the Local Fields node of the Basic list screen of SQ01.

All done.

Notes:

• In an Infoset query, we can have user fields derived from both SQ02 and SQ01.
• A user field created in SQ02 would appear in ‘Additional Fields’ node and a user field created in SQ01 would appear in ‘Local Fields’ node in the Basic List screen (SQ01).
• The above narration mainly illustrates the procedure to have user defined fields. A little complex example has been demonstrated here, so that  simple requirements can be easily met.
• The author wishes to compile some more useful points in the area of Infoset queries, into another document.

Thank you

KJogeswaraRao

PS: The link given here will be of use to Infoset Query lovers:Infoset Queries: Collection of important posts

Introduction:

After the exposure to many standard ALV reports for masterdata , it is seen that the clients or end-users expect similar reports for Catalog-Profiles, Code Groups and Codes, so that it will be easier to search for such available profiles which suit to their requirements and they can make use of the same, saving lot of time, effort and data duplication.

For big organizations, comprising of several units where SAP-PM is adopted, this requirement is very common.

We do not have such ready report/s provided by SAP.  At the same time, SAP has given good tools for Functional persons to generate reports on their own.

These are Quick viewer, and Infoset Queries.Present article is based on Infoset Query.

Let's see what we are going to achieve in this article:

A report with selection screen like this

will generate a report like this: (list of all profiles related to 'Motors')

DO you find it is relevant and useful to you? Then here is how to make it !

Step 1. Create an Infoset as follows

- Create an infoset (Say 'CATCODES') using 'SQ02' Tcode. opting for Table-Join in the initial screen.

- In the Join  page Insert these tables as shown ( select left-outer-join for QPGR and QPCD tables join)

- Click Back,

- Select the required fields from tables (left) to the Field Groups in the right. (Drag & Drop) as shown here.

In order to arrange the Calatogs in the sort order of B, C, 5, 2, A  in the ALV screen, a user defined field 'SORT' is being created in the following section.

For this click on the  'Extras' tab on the application toolbar to have Extras window on the right.

Click on the 'New' icon and create 'Additional Field' named 'SORT'

The specification of field 'SORT' while creating

Now, keep cursor on the 'SORT' field (Red Boxed area) and click on the 'CODE' icon (Green box), and write the following code.

Save the code,

Making of 'Selection screen' of the report

Go to  'Selections' tab (next to 'Extras' tab) and create the select-option.

Here we are creating the 2 selection fields shown in the 1st image of this document. i.e., Catalog Profile' and 'Created By'.

For this click on 'New' icon in this tab and create two selection fields 'CATPROF' and 'CRTDBY' one after one as shown here.

Now the 'Selections' tab will look like this.

Save and Generate the Infoset.

This completes the job in Infoset creation (SQ02).

Come to initial screen of SQ02 and assign this infoset to your usergroup. (User group is created through SQ03)

Step 2. Create Infoset-Query through SQ01 as follows.

Create a Query (say 'CATCODES') using the infoset made above 'CATCODES'.

Click 'Next' arrow

Select all the 3 tables appearing here used in Infoset and click next.

Select the fields required for display in ALV.

Click on Basic List button and arrive at the following screen.

(If this screen does not appear go to 'Settings' menu, check the 'Graphical Menu Painter' option in the 'Settings' option)

The red box list shows the Field selections you need to appear in the output.

For column coloring you have to drag & Drop colors from tool box to the corresponding field as shown by the Red arrow on the right.

That's all. Now You save the query and return to the initial screen. Execute and test.

To have a Tcode for the program you've just generated

In the SQ01 screen

to get this result.

Copy this string (Report name), Run SE93 in Development Client and create a Z-Tcode with desired name using the above program name.

Transport the request to Production.

Now the report you've made is operated using the Tcode you've created.

To my end-users, this report was very much sought and proved very useful by them. They can now easily search the profiles available in the system (made by users in other shops)   for their similar equipments. This report has got many such uses.

The making of this report here has been demonstrated using 'Standard Client 'option in the SQ02 (Environment --> Query Areas), so that no transport needs to be done during creation or modifications. However as explained, the Z-Tcode has to be created in Workbench Dev Client, once.

Also, it is aimed through this document, the beginners in the Infoset query area to be benefited without referring to other detailed documents on SQ03, SQ02, SQ01.

Hoping it is useful to many.

-Jogeswara Rao K

Hello to everybody,

These are the basic steps for monitoring of consumption in the fleet management using PM (Plant Maintenance) module.

It is not very common to use these functionality, so I think that this guide will be useful.

You can follow these points:

1- Units of measurement - CUNI transaction

A) Choose dimensions

SURFACE: Consumption / Activity : i.e. : Liters / 100 km

SURINV: Activity / Consumption: i.e. : Km / liter

VOLFLO: Volumetric caudal : i.e. Liters / Hour

B) Once you have chosen your dimension, let's créate the unit:

Inside convesion area, conversión is done between entry unit and exit unit, in terms of:

• Simple formula: (if numerator and denominator is enough):

        N * Unit in T006 table = Z * IS (International System of Units) unit

        i.e. : 100 *  centimeters = 1 * meter

                 1 * hour = 3600 * seconds (as the example above)

• Complete formula :

      valor in IS unit = (Z/N) * 10 **E (T006 valor unit) + K

      i.e.

      Kelvin              Fahrenheit

      273,15 = (5/9) *10 **0 * 32 + 255,3722

2- Fleet management customizing

These are the customizing points:

The interesting points are:

- Define Special Measurement Positions for Fleet Objects

We select the group units, depending on whether the unit belongs to SURFACE, SURINV or VOLFLO.

- Define Calculation Method for Fleet Consumption Values

We add the unit in the corresponding calculation method.

3- Fleet master data

A) The first point is to create characteristics in CT04 transaction for Distance, Fuel and Time

i.e. TIme:

B) The second one is to add the counters at the vehicle in IE02: Distance, Fuel and TIme

In vehicle master data (View. "Vehicle technology"), define the calculation method for the monitoring of consumption.

i.e. : 1 (Usage volumen / distance)

C) In IFCU transaction, we créate measurement documents for the previous vehicle

After various measurement documents created, we can see consumption information. The easiest way to reach this information is through vehicle master data in IE02:

Button "Measuring points / Counters"

Click with the mouse on the counter you want to see the infor related and click in button "MeasDocuments"

You will see these screen

Execute the report and will show all the measurements related to these vehicle:

Also you can see an evolution graph with the button "Measurement Document Graphic" (Ctrl+Shift + F9)

Moreover, you can see more info at the vehicle master data in IE02 at the calculator button:
:

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.

Introduction

Subject matter is one of the FAQs where there has been a frequent and clear replies from forum to use the Enhancement, i.e., user-exit IWO10020 - Maintenance order: Automatically include task list. I was one among the members who received this reply but could not utilize because there existed no further info on 'How?' . The 'How to use this user-exit' has remained a big ? for me since then (quite long period). I know it is still an unresolved issue to many. Whenever I remembered about this issue, I searched forum vigorously but no where concrete solutions found. Due to this  I always avoided to reply to other members, advising to use this exit for automatic including of tasklist, becuase I was unaware of complete solution. I always tried to give the code to be used in user-exits during replies in discussions. Also I documented these solutions for ready reference.

The time for documenting the solution for the subject matter has finally arrived, because I recently found the key to use user-exit IWO10020 which automatically transfers Tasklist while creating Order through IW31.

So to start with, first let's see, what we achieve at the end of this document.

1. I prepared an Equipment Tasklist (IA01) like below for Equipment 53330333.

2. I run IW31 entered Order type and Equipment number

3. Pressed keyboard Enter button

What I found here in Create Order screen is the entire Equipment tasklist has been automatically copied to the Operations tab. Isn't this of a great convenience?

Similarly I created a Functional location tasklist (IA11) for a Functional location AEP-CCWE  as under.

then I run IW31.

and I see all the operations of the F/L tasklist are copied to my Order.

Note:

In both cases you notice that the Tasklist Short text became the Order Short text.

I am sure members would agree that this feature has got a great significance in creating PM Orders due to the convenience of having automatic operations. I need not specially mention that the Components details of the tasklist will also be transferred to Order alongwith the operations.

So now let's see how to do it?

We already talked about the user-exit which is responsible for this. It is IWO10020.  But the thing is this has been an half information.  The other half of the info in this regard is we need to use another user-exit namely IWO20001 - User exit to pass routing to order alongwith the above to achieve this result.

Having revealed this, it is now simple task for me to tell the readers about further-how by simply giving the codes to be written in these user-exits.

Code to be put in the include ZXWO1U06 (user-exit IWO10020)

IF CAUFVD_IMP-AUART = 'ZM03'.   PERFORM FCODE_PLSU(SAPLCOIH).  "This form calls User Exit IWO20001
 ENDIF.

The 01. and 03. lines above restrict the use of this feature to Order type 'ZM03'. (Means Automatic tasklist feature  applicable to this Order type only)

Code to be put in the include ZXWOCU03 (user-exit IWO20001)

 TYPES: BEGIN OF TY_SELTAB,       LV_PLNTY TYPE EAPL-PLNTY,       LV_PLNNR TYPE EAPL-PLNNR,       LV_PLNAL TYPE EAPL-PLNAL,   END OF TY_SELTAB.
 DATA: IT_SELTAB TYPE TABLE OF TY_SELTAB,       WA_SELTAB LIKE LINE OF IT_SELTAB.
 IF CAUFVD_IMP-EQUNR IS NOT INITIAL.   SELECT PLNTY PLNNR PLNAL FROM EAPL INTO TABLE IT_SELTAB WHERE EQUNR = CAUFVD_IMP-EQUNR.
 ELSEIF CAUFVD_IMP-EQUNR IS INITIAL AND CAUFVD_IMP-TPLNR IS NOT INITIAL.   SELECT PLNTY PLNNR PLNAL FROM TAPL INTO TABLE IT_SELTAB WHERE TPLNR = CAUFVD_IMP-TPLNR.
 ELSE.
 ENDIF.  SEL_TAB[] = IT_SELTAB[].

The job is done.

And... that was about Automatic Tasklist while creating Order directly. Let's now look into another user-exit namely IWO10021 - Automatic task list transfer when creating order from notif. As the name indicates, this is the enhancement which is supposed to give us above convenience while creating Order from a Notification. Let's see what to do to have this.

Put this code in the include ZXWO1U07 (user-exit IWO10021)

IF CAUFVD_IMP-AUART = 'ZM03'.   TYPES: BEGIN OF TY_SELTAB,         LV_PLNTY TYPE EAPL-PLNTY,         LV_PLNNR TYPE EAPL-PLNNR,         LV_PLNAL TYPE EAPL-PLNAL,     END OF TY_SELTAB.   DATA: IT_SELTAB TYPE TABLE OF TY_SELTAB,         WA_SELTAB LIKE LINE OF IT_SELTAB.   IF CAUFVD_IMP-EQUNR IS NOT INITIAL.     SELECT PLNTY PLNNR PLNAL FROM EAPL INTO TABLE IT_SELTAB WHERE EQUNR = CAUFVD_IMP-EQUNR.   ELSEIF CAUFVD_IMP-EQUNR IS INITIAL AND CAUFVD_IMP-TPLNR IS NOT INITIAL.     SELECT PLNTY PLNNR PLNAL FROM TAPL INTO TABLE IT_SELTAB WHERE TPLNR = CAUFVD_IMP-TPLNR.   ELSE.   ENDIF.   SEL_TAB[] = IT_SELTAB[].  ENDIF.

After this, when you create an Order of type ZM03, from the Create Order icon of a Notification     the Equipment tasklist OR the Functional location tasklist will be copied to operations tab automatically.

To be Remembered.

1. Configuration settings

Path: Maintenance and Service Orders > Functions ans Settings for Order Types > Default values for Tasklist Data and Profile Assignments

The above setting suppresses the tasklist pop-ups and copies entrie tasklist to the Order. (Ideal for this application). Due to some reason if some wants the tasklist operation pop-up before copying, then Tick  the 1st checkbox i.e., OprSelection.

2. Order personal Default values  settings

Inside Order: Extras > Settings > Default values...

Here in Control tab have this setting

It is observed that Operation selection pop-up can be triggered from the above setting (by tick marking the Operation select.) without going for SPRO settings as explained earlier in Point1.

3. Use of General Maintenance Tasklists

You can use GM Taklists also in this process, but you need to develop logic to relate a tasklist to some field value of the Equipment or F/Locn master. This logic will be replacing the code I provided in the includes ZXWOCU03andZXWO1U07.

4. Enhancements to be listed in a Project

This is a reminder point for use of any user-exit, that it is a pre-condition that the above discussed user-exits are required to be assigned to a project created through CMOD.

That's all friends on this topic. Hope this information will be useful to many. I document knowledge mainly for one purpose. That is to prevent losing important knowledge pieces due to memory erosion.

Thank you

KJogeswaraRao

This document explains the Extraction and Selection Criteria for Long text of various SAP Master data objects.

Process for extracting the long texts data is – Go to SE38 and give the program as RSTXTC3, execute and enter the selection criteria as below for different objects. After entering the required selection criteria, select PROGRAM - EXECUTE and PRINT, save to local file.

Go to SE38

Selection Criteria:

1. Equipment Long Text

Object                  : EQUI

Text                     : 18 Digit Equipment Number (000000000010066375)

                                   [From and To values depend on Number Range]

Text ID                 : LTXT

Language           : EN

2.     Equipment Internal Note

Object                 : EQUI

Text                    : 18 Digit Equipment Number (000000000010066375)

                               [From and To values depend on Number Range]

Text ID               : INTV

Language             : EN

3. Equipment Task List Header Long text

Object                  : Routing

Text                      : CLIENT+”E”+8 DIGITGROUP NUMBER+* (ex. Task list 90 in client 230 – 230E000000090*)

                                   [From and To values depend on Number Range]

Text ID                  : PLKO

Language             : EN

4.   Equipment Task List Operation Long text

Object                  : Routing

Text                      : CLIENT+”E”+8 DIGITGROUP NUMBER+*(ex. Task list 90 in client 230 – 230E000000090*)

                                   [From and To values depend on Number Range]

Text ID                  : PLPO

Language             : EN

5.  Functional Location Task List Header Long text

Object                  : Routing

Text                     : CLIENT+”T”+8 DIGIT GROUP NUMBER+* (ex. Task list 9 in client 230 – 230T00000009*)

                                   [From and To values depend on Number Range]

Text ID                  : PLKO

Language             : EN

6. Functional Location Task List Operation Long text

Object                  : Routing

Text                     : CLIENT+”T”+8 DIGIT GROUP NUMBER+* (ex. Task list 9 in client 230 – 230T00000009*)

                                   [From and To values depend on Number Range]

Text ID                  : PLPO

Language             : EN

7.   General Task List Header Long text

Object                  : Routing

Text                     : CLIENT+”A”+8 DIGIT GROUP NUMBER+*(ex. Tasklist 7006 in client 230 – 230A00007006*)

                                   [From and To values depend on Number Range]

Text ID                  : PLKO

Language             : EN

8.  General Task List Operation Long text

Object                  : Routing

Text                      : CLIENT+”A”+8 DIGIT GROUP NUMBER+* (ex. Task list 7006 in client 230 – 230A00007006*)

                                   [From and To values depend on Number Range]

Text ID                  : PLPO

Language             : EN

9.   Maintenance Plan Long text

Object                  : MPLA

Text                     : 12 Digit Maintenance plan Number (000000023899)

[From and To values depend on Number Range]

Text ID                  : LTXT

Language             : EN

10.  Maintenance Item Long text

Object                  : MPOS

Text                      : 16 Digit Maintenance Item Number (0000000000000309)

                                     [From and To values depend on Number Range]

Text ID                  : LTXT

Language             : EN

In this document we will learn about two different methods to identify authorization issues.

1. SU53 or /nSU53
2. ST01

SU53 or /nSU53

     Using this transaction you can analyze an access denied error in your system that just occurred. It displays the last failed authorization check, the user’s authorization and the failed HR authorization check.

Scenario:

User gets an authorization error on releasing a notification from IW22 transaction

IW22:

On clicking the release icon, users gets below error message

Press Enter or Click the green tick

Type /nSU53 in transaction code area

Press Enter

Now we will be able to identify the missing authorization objects and values for the user

These values can be used in SUIM transaction to identify the roles which you can assign to user.

ST01

          ST01 is one of the primary tools in the SAP Security Module. ST01 gives us a peek inside running ABAP program or standard transaction to record the SAP Authorization checks in your own or external system. The trace records each authorization objects, along with the object’s fields and the values tested.

Scenario:

          User is having access to perform “Do not Execute” in the work order, need to restrict the user with the functionality.

This particular access cannot be captured via SU53

IW32:

When the Work order is in CRTD status, system will allow you to set “Do Not Execute” from the Path Order – Functions – Complete - Do not Execute

To identify the access provide to this user, you can identify via Trace

ST01

Make sure you check Authorization check and select All

Click General Filters

Enter the Trace for User Only "PM01" and click the green tick or press enter

PM01 is the user ID i have created for my testing

Click Settings to Save

Before starting the Trace, request the user to be in IW32 transaction with the order number entered, this will reduce the trace length

Now Click

Request the user to execute “Do not Execute” function for the work order. Once the action is performed, click

You have successfully taken the trace. Click

Enter the User Name, Client. Date From/To and Select Authorization Check and All

Click Execute

Do check the value RC = 4 (No Authorization) and Double click the line item

Here you will be able to get the Authorization Field and Values.

Restricting above authorization access, will give no access to "Do not Execute" business transaction.

These values can be used in SUIM transaction to identify the roles which is giving access to user.

Objective:

To develop an ALV report showing Equipment and the Class assigned to it.

Please see the screen capture of a report showing Equipment vs Class assigned.

Do we have such report in standard system? We didn't get when we needed this years ago. Ours is still ECC6.0 with no EHPs.

We expected such information from standard reports like IH08, but same unavailable.

Then I have developed a Quick-view fulfilling this need and assigned a Tcode to it.

Are you also one among those who need this report? If yes go through this document. It is a simple method of developing this report in PRD server itself through SQVI.

Step1

Run SQVI Tcode.

Create a QuickView eg., Equip_Class,'

Give a Title ýou like e.g., Equipment vs Classification

Choose 'Logical Database'  in the Data Source.

Type 'EQI' in the Logical Database field, and press Enter to continue.

(All this Means you are about to create a Quickview using Logical DatabaseEQI.)

Step2

If you are in 'Basis Mode' click on this button to switch to 'Layout Mode'.

Now you'll see the following.

You need not have to do anything on the left side 'Data Fields' area.

See in the Right side 'List fld. select.' tab.

Choose the fields you desire to have in the ALV output here. Select these from 'Available fields' (Right side list) and transfer to Left side.

In the above example, I have chosen 6 fieds as per my requirement.

Define your own Selection screen

Go to 'Selection fields' tab.

Here you'll see 4 fields have been already given by the system (with Lock icons), which you can not remove.

But you can add your own fields for selection criteria.

In the example below, I have added 5 such fields (5 to 9).

Step3

It is almost done now.

Save the work done so far by clicking on the Save button at the top of the QuickViewer screen..

Now click on Execute button to run this program.

The Selection-screen

The output

A report for Functional Location vs Class can also be made in exactly similar way by using Logical database TPI.

Step4

We have done all this work in PRD server and have seen the realtime data in the output by executing the QuickView.

Instead of going to SQVI and executing this quickview from there everytime, you can give a Tcode to this work.

Get the Report Name.

In the SQVI initial screen, select your Quickview, click on Quickview at top left corner --> Additional Functions --> Display Report Name.

You will be getting this pop-up displaying the Report name you've just made.

Now to create a Tcode there are two options.

1. Ask your technical person to create a Tcode you desire with the program name shown above.

OR

2. Do it yourself in ABAP client through SE93 Tcode and transport it to PRD.

This applies to the other Quickview also (FL vs Class)

Conclusion

Most of the steps described here apply while dealing with Infoset Queries also (SQ02, SQ01).

SAP has provided many Logical Databases in the system, which often come to our rescue while working with Queries and when we do not get proper tables to fulfill our requirements.

This document has been made with beginners in mind. For members with SQVI experience, it is a simple communication to use Logical database EQI or TPI to make Technical object vs Classification Report.

--------o--------