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)

ABSTRACT

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

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

The Tool includes Demo templates are available to Downloadhere

BENEFITS

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

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

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

Exemples for such changes for Functional locations or equipments :

- Mass update class and characteristic

- Mass update of system profile

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

Templates examples

Exemple 1 :Create Equipment with user status

Exemple 2 :Create Equipment with class and characteristics

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

Pre requirement

• Microsoft excel 2007- 2013
• Macro enabled

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

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

   1. 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 B - Fill Excel source / template worksheet

  STEP C - Generate The Flat File for IBIP Transaction

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

Step D -  Upload the Flat File to the IBIP transaction

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

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

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

            Goto sm51 select the required server

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

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

   Step F : Check the Log

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

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

Exemple 2: Equipment creation with class and characteristics

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

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

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

              4.Upload the Flat File to the IBIP transaction

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

Exemple 3: Functional Location assign class and update characteristics values

Introduction:

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. (Do not give values in the 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.

The author is a maintenance manager with 30 years experience in a large manufacturing industry, associated with SAP-Plant maintenance since more than 6 years

_________________________________________________________________________________________________________________________________

Related content:

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

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

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 my Maintenance Order? In the recent months the author had replied 3 times to discussions related to this topic. It is thought that this topic if documented would be helping many.

Objective

This documentation is intended to enable the readers to create the Custom fields in the Maintenance Order, update the Order Master data Table and also display these fields in IW38 Order list output.

Let's Start

Part1

Create Custom fields in the Order Table

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

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. ZCUSTFLD1 (Domain CHAR12 and Field Label ‘Customer Field 1’)

2. ZCUSTFLD2 (Domain CHAR40 and Field Label ‘Customer Field 2’)

Now let us create our Customer fields Run Tcode SE11 --> give value AUFK in the Database Table field -->Click on Display. Scroll-down to find include table CI_AUFK. Double click on this, Go to Change mode and Add 2 new fields of our interest as shown in the picture and Activate.

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

Part2

Enhancement and Screen-Exit

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

2. Assign Enhancement IWO0018 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)

As we see here, there is One screen-exit (screen 0900) and Two Function-Exits namely EXIT_SAPLCOIH_018 and EXIT_SAPLCOIH_019 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 LayoutArrow 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. (AUFK-ZZCUSTFLD1 and AUFK-ZZCUSTFLD2)

See the picture.

Activate.

Part3

1. Declare table AUFK

Declare table AUFK in the top include LXWOCTOP of Function group XWOC by Clicking on and creating the include ZXWOCTOP .

2. Codes to be given in Function-Exits

Go to the following screen of the User-exit

Double click on the Function-Exit EXIT_SAPLCOIH_018 and put the following code in the include ZXWOCU15.

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

MOVE-CORRESPONDING COCI_AUFK_IMP TO AUFK.

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

Similarly put the following code in the include ZXWOCU16  of the Function-Exit EXIT_SAPLCOIH_019.

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

MOVE-CORRESPONDING AUFK TO COCI_AUFK_EXP.

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

Now let’s see the effect of work done so far.

Create a Maintenance Order (IW31). You will see an Additional Tab named 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 Order.

Run IW32, open the Order and verify whether the values are updated to table or not. If they are appearing in the Enhancement tab as you have entered and saved, this means the AUFK table has been updated with these values when Order was saved.

Part4

Let's have these Custom fields in the Order list output namely the ALV of Tcode IW38

So far we have succeeded in creating our Custom fields and updating the values to the Order Master data. Next natural requirement of a user would be to have these fields in IW38 ALV screen. For this purpose we, need to create an Append Structure in the Structure RIHAUFK_LIST, as shown in the picture below. The

Tcode is SE11 again for this task. Here we have created an Append Structure named ZCUSTFLD and in this structure we have added both the Custom fields.

Now let's create one more Order, fill the custom fields with some values and Save. The second order is to have ALV output in IW38. (Because single Order in the output takes to IW33 screen instead of ALV screen). Now run IW38 with selection parameters to display these 2 orders 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.

Almost Done

Now if you go to IW33, unlike all other greyed-out fields, the Custom fields in Enhancement Tab 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 0900 we have created.  Double click on the Screen number 0900 of the enhancement,

Now you are in the Flow Logic Tab ,

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

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

MODULE STATUS_0900 OUTPUT.

     IF SY-TCODE = 'IW33'.

          LOOP AT SCREEN.

               SCREEN-INPUT = '0'.

               MODIFY SCREEN.

          ENDLOOP.

     ENDIF.

ENDMODULE.

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

Lastly Do not Forget to
Activate the Function GroupXWOC 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 AUFK.

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 of the members,

Added on 08.10.2015

A post relevant and useful: How To add Custom Fields as Selection Inputs to IW38/39

Thank you

KJogeswaraRao

Introduction

Reports on Equipment BOMs, Functional Location BOMS or Material BOMs are not available in standard.  We can make these reports using respective tables through infoset queries. SAP provided a great facility in the form of Logical Databases in these areas using which, the report making becomes very easy. Using LDB eliminates the hassles of using independent tables and troubleshooting the joins. LDB has everything in-built for you.

Logical Databases

CTC      -       Functional Location BOM

CEC      -       Equipment BOM

CMC      -      Material BOM

Using LDBs we can design the output as Boxed Reports, i.e., One BOM for each box. See this

Like It? Let's see how we make it .

This post might not cover every detail at basic level as these aspects are discussed in detail at the post Infoset Queries: Collection of important posts

So here we see the vital aspects of how to make subject reports.

We are learning through the example of Equipment BOM

Infoset (SQ02)

The Infoset is created based on Logical Database CEC as shown below.

As mentioned already everything is already in-built in LDB. You need to just select the fields you want to take into Query. I have taken these.

Here I’ll share with you about the extra fields I’ve created for my report.

My report needs ABC Indicator and Planner Group (LDB does not have these fields). So I created these 2 fields as above and fetched the values as under.

Code for ABCKZ

Code for INGRP

All done here in SQ02. We will have Program (user) selection fields from SQ01 (Query). Let’s Before we swich to SQ01, generate the Infoset we created and assign to our Usergroup.

Infoset Query (SQ01)

Create an Infoset Query based on the Infoset we’ve just created. Take the fields you require into the output. I have taken these shown below.

Now Go to Settings in the Menu and click on Settings to get this pop-up.

Clear Graphical Query Painter checkbox if checked already. This allows us to  design each record in the output in separate boxes in ABAP List option.

Click on Basic list . Here you can define the line structure. Here instead of detailing I’m giving the screens of my work one after one.. (You can play with other options and study the behaviour).

The first screen of Line Structure (Line numbers, Field sequence, Sorts etc)

Next page of Line structure. (through Downward arrow)

Now Press F6 (or click on the icon below) to go to Next Screen The screens are given here one after another.

Next Screen1

Next Screen2

Next Screen3

Next Screen4

Here in this screen you can define the Feilds for colors in the Column Format  shown above. OR you can give colors to the fields by switching to Graphical Basic List Option and as explained in the document referred in the beginning.

Next Screen5

This completes the Box design.

Now let's save the Query and execute. See the Selection screen here.

Give your selection field values (in Planner Group etc), Select the ABAP List option and execute. See the output.

One Box for each Equipment BOM, where Equipment details are given in the first line and the component details in Green anf the count summery at the bottom. I like this boxed report.

Then, if someone wants to see this report in ALV only, then a mouse click on the icon in the Application toolbar converts this report into ALV. Click on Back  button to come back to Boxes format.

So that's everything about this. It is obvious that the respective reports on Functional Location BOMsand Material BOMs are made in a very similar manner using the respective Logical Databases.

Expecting that this document too would be of help to members.

Thank you

Jogeswara Rao K

Introduction

The first usual improvisation requirement in self-made Infoset Queries by beginners, is often the requirement of calling other reports from ALV output, just the same way we do in Standard reports.  In ABAP-coded Z Report Programs, there are several techniques of achieving this by syntax like Call Transaction,Submit etc.

The very objective of this documentation is to achieve the same. This topic was briefly discussed in the document 10 Useful Tips on Infoset Queries. But, when the author experienced few exceptions in the technique suggested there and found a solution subsequently, he got the idea of having an exclusive document on this topic.

This document has assumption that readers have working knowledge in developing Infoset Queries.

Here we Start

We have seen earlier, that for enabling Report Calling from the ALV output of an Infoset Query, we need to do these steps in SQ01.

Note: 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'

Click here on   then on then select  TR (Transaction Code) or RT (Report Program),

1. When we select TR we need to put only the Transition code.

Example:

IE03 if our ALV lines are having Equipment field and we want Equipment Master display upon clicking on the ALV row.

If we have a Maintenance Order Number in the ALV, and we want to have Display Order Screen upon clicking on this row, then we give the Tcode IW33 here.

     2.  In the other case, when we want to call List Reports like IW37 , then we need to select RT in the Report type, where we need to give the

          Program  name (in this case RIAFVC20) in the Report field  and the variant name.

So far, it looked very much OK, until I found recently that few field names like EQUNR, MATNR, DOKNR etc, do not exhibit the desired behaviour.

Few cases  where this call report was not working are discussed here.

In one of my Queries, I have Material number (MATNR) in the ALV output, for which I used Report Type TR with Tcode MM03, for the purpose of  Material Master Display. What happened here, was no Material number was passing to the MM03 initial screen, so the display interrupted, In another case, the first attempt display was coming, but the next attempt on different material line in the ALV, the material master display of the first attempt was repeating. Broadly there is a technical problem in passing the Material number.

Another such case was with the Tcode CV03N  (Display of DMS Document) , where the DOKNR, DOKAR field values were not passing to the CV03N initial screen.

Here is the solution I worked-out, using the QUReport Type of Report Assignment

We are taking the MM03 case

As mentioned above, the report Type QU (Query), in the Report Assignment came to rescue.

This option has 3 fields.

First field (User Group):  You know, your User Group.

Second field (Query): We need to develop a simple query for this field.

Third field (Variant): Optional.

So, what required was that a simple Infoset query using MARA table (Material Master) to be created.

And this Query name, was given in the field 2 above.

Let’s see the steps of creating the simple Query for Report Assignment purpose.

SQ02

We are Creating an Infoset (I named it MM03) with Direct read of table option.

This is because, we use only one table.

Select this default option, and Continue.

With this the Key field MATNR is added to the Field Group folder in the Infoset.

And in the Infoset Code Section, give the following code

  Generate Infoset and do not forget to assign it to your User Group.

SQ01

Create a Query (Say MM03) using the above Infoset.

Note:

This query name is going to be used in the Report Assignment.

Go to Basic list screen and Tick the MATNR field in the List fields column.

Save the Query.

Testing.

Here we are examining, the behaviour of 3 cases of Report Assignment)  in the ALV output of an Infoset Query.

We know that when multiple Call report assignments are there in the query, then the options appear as a menu as shown above, upon clicking on a row.

• Here the first option in the menu namely Display PM Order, is that where I used report type TR and given Tcode IW33,
• Second one, namely Report Assignment MM03 is through Report Type QU with Query field value MM03 (created as explained above)
• Third one was the option which was malfunctioning i.e., Report Type TR and Tcode MM03

Now when tested, the first option with TR report-typeworks satisfactorily, without any problem, passing the Order number (AUFNR) correctly everytime.

The third option, again with report type TR works erratically, unable to pass material number (MATNR) correctly.

The second option is our solution to the erratic behaviour of MM03 through TR report type. i.e., through QU report type. This works very correctly like the first case.

In the case of Display Equipment (IE03) , the above method would work, with the following code in SQ02.

PARAMETERS:

EQUNR LIKE EQUI-EQUNR.
SET PARAMETER ID 'EQN' FIELD EQUNR.
CALL TRANSACTION 'IE03' AND SKIP FIRST SCREEN.
EXIT.

So that is about the Problems and the Solutions

As referred in the beginning, another parameter which gave trouble in calling reports through report-type TR was, DOKNR (DMS document number).

I have solved this issue too in a similar manner.  The transaction called was CV03N. The code used in the Infoset is given below.

Note

See the Syntax used  PARAMETER ID  in the syntax used in both the cases above.

The Parameter Id used in MM03 case was, MAT,  and in the CV03N case was CV1  and CV2.

MAT is the Parameter Id for field MATNR, CV1 is for DOKNR and CV2 is for DOKAR.

This parameter-id is the key factor for any Call report to function properly.

Where do we get this?

For example for MATNR, place cursor in MATNR field of any screen, and press F1 on key-board. The pop-up has this value.

Similarly for any other field.

That’s everything I think, about this document.

The author hopes that this document also will be useful to the members, the way the  other documents by the author, in the series of Infoset-queries.

Thank you

Jogeswara Rao K

IH01 Structure Customizing beyond I_INGRP Authorization Object

_____________________________________________________________________________

Author: Jogeswara Rao K

Introduction

In an enterprise, the mapping /structuring  of assets (as Functional Locations & Equipments) is generally done as per the process flow.  The structure is nothing but the Asset tree, how the assets are installed in the shop-floor. We know this structure is seen through IH01, which we can say the gateway to SAP-Plant maintenance.

Agencies with different expertise are usually involved in the upkeep/maintenance of these assets such as

-Mechanical Maintenance

-Electrical Maintenance

-Instrumentation

-Air Conditioning

All these agencies record their jobs through Notifications and Maintenance Orders on their respective equipments

of this Equipment tree (Structure).

So far we are discussing about the Maintenance Agencies owned by the the Shop.

But there is a situation in Organizations where Centralized Maintenance Agencies exist and they are authorized to access some of these Assets and these Agencies are labelled with different Planner Groups.

The constraint to provide them the IH01 tree, displaying only their Equipments, is that all these equipments have planner groups filled with those of the agencies owned by Shop.

The present topic is about this situation.

Objective

Need to give a Customized IH01 Structure to these Central Service agencies, using a field  other than the Planner Group.

(Because the Planner Group field is already consumed by maintenance agencies owned by shop)

How?

Here Comes the idea of using the I_BEGRPAuthorization Object.

That is, uUsing the Authorization Group field in Equipment Master.

Let's see a sample structure shown below.

Now suppose the Equipment to Agency relation in each branch (Pusher) is as under:

As said before the objective is to restrict the display to their respective equipment.

Create Authorization Groups for these Central Agencies in SPRO

Now go to ‘Change Equipment Master’ (IE02) of each of these equipments, give the respective authorization group values and save, as shown below.

Then

Create 4 Roles (One each for these 4 agencies) through PFCG or modify existing Roles as under:

Shown below is the role for AGR1 Mechanical Maintenance Agency

Assign these Roles to the respective Users.

Now when the user1 (Centralised Mechanical services)  goes to the Structure (IH01) the following is the tree he will be seeing.

(Only those 2 of his jurisdiction)

Similarly, when the user2 (Centralised Electrical services)  goes to the Structure, he will be seeing…

….. So on for other users.

Now an exapmle of the real application of this feature

There is an Enterprise having about 60 shops (departments). The structure here has thousands of functional locations, lakhs of equipments and many hundred Planner groups.

Now there exist a central repair agency which attends major repairs on a certain category of equipments through-out the enterprise. The list of the equipments relevant to this agency, covers only those equipments of a particular planner group of shop, which satisfy certain conditions (e.g., Motors >50KW).

Here comes the use of controlling the structure display though an object other than a planner group.

So all such equipments have been assigned an Authorization Group and a display role was created on this object (I_BEGRP) and assigned to the users of this central agency, to display structure with equipments of their jurisdiction only.

Pictorial depiction of required equipments in the structure.

Important Note:

One Pre-requisite is that AuthorizGroup fields in 100% Equipments need to be in filled condition with some value. If it is not so, then the user will see the Equipments with blank AuthorizGroup field also alongwith Equipments with his own AuthorizGroup values.

Hope this knowledge piece is of relevance to some of the members.

Thank you

Jogeswara Rao K

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:

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

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

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.

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

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.

Purpose

This step demonstrates how completion confirmations for a production order can influence maintenance measures performed on production resources and tools. This example has been created for a bottling/canning plant. Here, tins are filled with paint. The bottling/canning plant contains a filter press which is recorded as PRT equipment in the task list for material Y-351.The maintenance plan for the PRT equipment contains three performance related maintenance cycles. This means that every time the PRT equipment above is used, different operations are used for the scheduled maintenance plan. In cases of high use this may lead to a change of filter

Data for This Example

Equipment –IE03

Note - (Prerequisits)

• Equipment should be a PRT
• Equipment used for Production should have PRT view enable
  • In PRT View
    • Usage Formula should assigned
    • Measuring Point & MP which are used for capturing Reading and scheduling are assigned in this Tab of equipment.

Maintenance Plan – IP03

Note - Before creating MP you should craete Performance Statergy with required Cycles in IP11.

Measuring Point –IK01/02/03

Characteristic used is based on production (Unit- Kg)

Creation a Production Order

Use

To create a completion confirmation containing a measurement document, create and confirm a production order.

Procedure

Production Order – CO03

Operation

Click "PRT" Button

Confirming the Production Order

Result

You have confirmed the order. A measuring point was defined as a production resource in the task list, enabling the SAP system to create a measurement document. This document creates a new call after the maintenance plan has been scheduled.

Displaying the Measurement Document

Use

The starting situation for scheduling of production resources and tools (PRT equipment) is displayed.

Procedure

• Measurement document

• .

You see a list of existing measurement documents.

• GotoMeasurement document.

This screen allows you to check the data in the completion confirmation for the order.

Ik13

F4

F8

++++++++++++++++++++The End++++++++++++++++++++

Overview:  Pool asset management (PAM) allows an organization to manage its pool assets using a graphical planning board. Examples of pool assets can be vehicles, beamers, laptop etc. In this document, I will take an example of pool asset as vehicle to go through the different steps. By using PAM, a planner can request, issue, return and then finally settle the service provided using the graphical planning board.

Steps involved in PAM:

The entire end-to-end scenario for PAM involves below steps:

1) Creation of demand

2) Demand Planning with Graphical Planning Board

3) Issue of pool asset

4) Return of pool asset

5) Settlement

Before I go into detailed steps, I would like to mention some pre-requisites that must be fulfilled before this scenario is run:

1) A functional location is created and all pooled equipment (vehicles) installed at functional location

2) A pool of vehicle is created using transaction code PAM01 and functional location assigned to this pool

3) Equipment created as pool asset must have a measuring point assigned for odometer reading and PAM category (PCM_KAT) assigned in equipment characteristics

4) All configuration related to PAM are done. Refer this link: Customizing - Pool Asset Management - SAP Library

Now, let's go through all the steps for pool asset management in detail:

1) Creation of demand:

Demand can either be created by a requester or a planner. Let's assume that the demand is created by a requester. This is done by using transaction IW21 for creating a notification with a standard notification type MF.

Requester enters user and requester information along with notification description exp. 'Request vehicle'.

Location is entered where the vehicle is required.

In 'Pool Asset' tab, start and end time for requested vehicle is entered along with the Pool Name by the requester.

In 'Settlement' tab, details of settlement object is entered.

Notification is released and saved

2) Demand Planning with Graphical Planning Board

Planner logs in the planning board using transaction PAM03 and views created notification in the bottom half section of the planning board.

Planner can drag the demand and move it to the upper portion of the planning board and can assign it to one of the available vehicle in the pool.

The planner can double click the demand and click on 'Reserve' button to reserve the demand of the vehicle on a particular time.

This changes the color of the demand to say red in the planning board.

3) Issue of pool asset

The planner will then issue the pool asset by double clicking on the request and entering odometer reading.

This changes the color of request to green meaning the vehicle is issued to the requester.

4) Return of pool asset

After the requester uses the vehicle and returns the vehicle back, planner will then enter the details in the system (such as new odometer reading) by double clicking on the green bar. This changes the green bar to a small line on the planning board.

5) Settlement

The planner then double click the small line and click on the 'Settle' button to capture the costs in a work order.

Planner assigns value against the value category from say actual vehicle usage time.

An order of type xxxx as defined in configuration is created automatically in the backend.

If you open the order, you will see the costs are reflected in the order in the 'Costs' tab.

This cost can then be settled to the final cost object by the finance team during their settlement run.

This completes the entire cycle for pool asset management.

Thanks,

Tajinder

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.