1. SAP Equipment Record functionality

The equipment record is unique information associated with a material number, and a corresponding serial number for the material in SAP.

This document basically can be categorized into two major segments

• The functionality & features available in equipment record in SAP.
• And focuses on the integration of equipment masters with other external applications with help of Idocs

Majorly in HI Tech industries the business tracks these equipments in several ways, it’s inventoried within the plant with equipment numbers, and stock transfers are done to Distribution centers with Serial numbers. And lot of customer / End consumer information is stored in the Equipment record for future support purposes

2. Business purposes of Equipment

• Equipment records are delivered to customer sites.
• Equipment numbers (serial numbers) consumed in a production order as components
• Shipped from stock, Shipped to certain partner locations from where it undergoes installation protocols
• Set of Equipment records are then batched for customer acceptance Via SAP CRM
• Data updates happen on the Equipment records at various stages of the business, Address details are updated in the equipments.
• Customer acceptance is done with equipment record numbers.
• Material returns are taken back at plants with serial numbers / Equipment record.

3. Highlevel Integration flow

4. Partner functions definition and assignment

The feature in equipment record, allows you to define & assign partner functions in them.

• Sold to Party
• Ship to party
• Installation partner
• Bill to Party

The Equipment used in a customer delivery can automatically copy the values from the Sales order / or a delivery and assign the partner functions value in the equipment.

The partner functions could be driven later on for Billing relevant reports, it gives information on which equipment is delivered / or categorized with that sold to or Bill to customer.

5. Class / characteristics in Equipment record

There is a provision where you could define class with characteristics which can be assigned to an equipment record

Class type 002 – Equipment class can be created and assigned to equipments

Mainly the Bundle information in equipment is stored in the picture above, but otherwise any parameter related to the equipment could be stored as details in the characteristics.

6. Custom status in Equipment record

The Standard SAP status in an equipment indicates the Delivered / in stock / Available statuses.

Based on customers requirement the User status profile can be configured, and assigned to the equipment category.

The custom statuses could be numbered, and based on sequences certain controls could be put in place so that the user is prompted to select these in a order defined in the back end configuration.

This is the Equipment view – where the user status profile is assigned, and it shows the different level of the statuses. These statuses can be manually changed with IE02 / or IQ02, but in the current integration the Inbound Idoc to ECC controls the status set.

6.1 Configuration menu for the User status.

6.2 Definition of the Status profile, with different statuses.

7.Additional data Tab in Equipment record

The other important feature which is implemented is the View profile change in the Equipment. This gives the flexibility for the users to add more details, basically the end customer relevant information like customer hierarchy, Location where the device is set, the I P address of the equipment, and much other consumer information can be stored

7.1 Defining the view profile

7.2 Assign the view profile to the equipment level, Equipment category

Part 2 of this document - about the Idoc ALE technical setups

8. Idoc Settings of the Equipment record

Tcode  WE81

We will need message type for Equipment integration through IDOC. For this we may use the existing message type available in the system or create a new message type using Tcode WE81. Here we use the existing message type in the system.

Tcode WE30 & WE31

  We have created custom IDOC to handle our requirement. This IDOC will contain the standard sturctures and structures to hold the address of the equipment and the custom fields. The address will be passed using the segment E1BPAD1VL which is copied from standrard ADRMAS01 IDOC and the custom fields are passed using custom segment

Tcode WE82

  We have assigned the existing equipment create message type to the IDOC which created in the previous step. This is required for both the inbound and outbound IDOC processing as we need message type for each IDOC

9. Inbound IDOC settings:

Tcode WE57

  Inbound IDOCs are processed by Function modules. We copied the standard function group ITOB_BAPI_EQ to a custom function group including the function modules to custom fuction modules to write additional logic to update address and the custom fields. Then we have to configure the custom function module copied from the standard function module IDOC_INPUT_EQUIPMENT_CREATE in the tcode we57. So when ever an equipment IDOC comes into SAP then this function module will be triggered first with passing the IDOC details

Tcode BD51

  In this setting we instruct SAP system to process the IDOC one by one instead of executing in bunch as the custom function module cannot process such.

10. Outbound IDOC settings:

Settings for change pointer:

Change pointers are created with respect to message types. For each message type if the setting is there it will create a change pointer.

In Tcode BD50, message type should be enabled for change pointer creation.

In Tcode BD52, the fields were mentioned for which the change pointer should be added. For our scenario, we need to send IDOC for any change in the equipment, we set the table key as the change pointer field and we override the change pointer creation using the BADI mentioned below.

In Tcode BD60, a function module should be assigned. This function module will take care of creating IDOCs from the change pointer. Our function module is a copy of the standard function module MASTERIDOC_CREATE_SMD_EQUI. To accommodate the custom details like user status and the customer field data, we have copied the standard function module and changed it.

In Tcode BD64, settings are done as given below. This settings will determine to which system the IDOC needs to be sent.  For partner profile settings to send and receive IDOC please refer the SAP help documents.

11 Integration:

Create change pointer:

  Whenever equipment is changed, we have to send the changes to other party via IDOC. Because of having large number of additional fields and the fields may be added more in the future, also user status is not in the EQUI table, we have written our own logic to create change pointers for the equipment and user status changes. This logic was written in the BADI EQUI_UPDATE on the method IN_UPDATE which will be called during the update task. The following is the sample code for writing the logic to create change pointers. Pass ‘I’ as a value to the ‘object_change_indicator’ field to make an entry in the change pointer table BDCP2

Thank You.

  Authors – Karthi Selvanayagam & John Rajadurai

• It identifies the products/services under warranty
• Validate the authenticity of warranty claims
• Validates whether the product/service issue highlighted by customer falls under warranty
• Define the effects of warranties on pricing & invoicing
• Monitor expenses incurred under due to warranty issues

1. Vehicle Consumer come into dealership
2. Dealer determines if product/service defect is under valid warranty
3. If yes, dealer files warranty claim
4. Warranty assessors may review claim for accuracy
5. Claim is either approved or rejected
6. If approved, claim is processed through to Finance and dealer is reimbursed

1. Define Warranty Claim Type
2. Assign Number Range for Claim Type
3. Define Decision Codes
4. Define Pricing for warranty claim
5. Maintain Pricing Condition Records
6. Define Action Matrix for Claim Processing
7. Define GL Account Determination Procedure for Claim Processing
8. Assign Pricing, action matrix and GL Account Determination Procedure to Claim Type
9. Implement Validation/Substitution for claims (Optional)
10. Define Output Determination for claim credit note 
11. Maintain Output Condition Records

    

Assign Claim Type to the Group:

Introduction:

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

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

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

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

And

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

(External numbering is used for easy understanding)

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

The Objective

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

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

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

Let’s see how this happens:

Part1:

Preparing the Masterdata:

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

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

V-1000

V-1001

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

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

Remember all these measuring points are based on characteristic RUNNINGHOUR.

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

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

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

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

Example:

Tyre: TYRE0001.

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

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

Click on Copy  and Save the Equipment master.

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

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

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

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

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

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

The Masterdata preparation is completed.

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

Part2a:

Create Documents and understand the working of Transfer Support.

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

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

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

Note:

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

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

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

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

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

Part2b:

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

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

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

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

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

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

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

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

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

Now we create measuring documents on Vehicles.

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

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

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

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

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

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

Note1:

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

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

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

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

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

Note2:

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

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

Concluding Remarks

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

Thank you

Jogeswara Rao K

Introduction

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 Notification? A documentation on this subject would be helpful to the forum for ready reference.

Objective

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

Let's see how it is done.

Part1

Create Custom fields in the Notification Table

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

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

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

Now let us create our Customer fields.

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

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

Part2

Enhancement and Screen-Exit

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

2. Assign Enhancement QQMA0001 to this project .

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

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

Now the screen is like this.

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

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

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

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

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

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

Activate the screen-painter.

Part3

Codes to be given in Function-Exits

Go to the following screen

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

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

TABLES: QMEL.

MOVE-CORRESPONDING I_VIQMEL TO QMEL.

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

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

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

MOVE-CORRESPONDING QMEL TO E_VIQMEL.

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

Part4

SPRO setting to be done

Navigate to the Overview of Notification Type in SPRO.

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

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

Almost Done

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

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

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

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

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

Part5

Let's have these Custom fields in the Notification list output namely the ALV of Tcode IW28/29

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

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

Part6

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

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

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

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

MODULE STATUS_0103 OUTPUT.

     IF SY-TCODE = 'IW23'.

          LOOP AT SCREEN.

               SCREEN-INPUT = '0'.

               MODIFY SCREEN.

          ENDLOOP.

     ENDIF.

ENDMODULE.

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

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

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

Note

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

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

Expecting this document too would be of use to many of the members,

Thank you

Jogeswara Rao Kavala

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

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 IE03 also. Then repeat the same steps above to have IE03 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 Display Equipment. You are taken to the corresponding screen as per your choice.

Note:

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.

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:

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

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

Customizing new PM Notification type and other related components

1. Defining new notification
   type (I.E  B1) :

• Go to SPRO IMG - > Plant
  Maintenance and Customer Service - > Maintenance and Service Processing
  -> Maintenance and Service Notifications ->Notification Creation - > Notification
  Types - > Define Notification Types

• Press on "New Entries"
  button

• Fill the data fields like
  in the screen beneath (As to Catalog profile: I will explain in details what Catalog
  profile is and how to use it in different technical document). Press save when
  you finish filling up the details.

1. Assigning number range to
   the new notification type you have created:

• Go to SPRO IMG - > Plant
  Maintenance and Customer Service - > Maintenance and Service Processing
  -> Maintenance and Service Notifications -> Notification Creation - >
  Notification Types - > Define Number Ranges

• Now there are two options :
  • Create new Group with new
    number range
  • Assign notification type
    you've created to existing group with existing number range.

Creating new group with new number range

• Press on
• In next screen press on
  Group menu in upper part of the screen and then press Insert (Or press F6)

• In next screen type the
  name of the new group and submit the lower and upper limit of group's number
  range. You can also check the check box "Ext" - then the number range
  is external number range, meaning the user will have to type notification's
  code by himself instead of notification's code will be determined by the system
  if you uncheck this field (number range will be internal ' code will be
  determined by the system).

Tip: Choose External number range only if
there is any logic to notification's code numbering (i.e xxx/yyy/zzz).

• After you've created the
  new group there is one thing left : assigning notification type you've created
  to this group:
  1. Find your notification type in "Not assigned" - lower
     part of screen

1. Click on it
2. Check the group you wish to assign the notification type to

1. Press save , and save it to relevant CR code

• Here there are fewer steps
  to be done. Remember that existing groups already contain number ranges as a
  part of the group. As a matter of fact, only the last 4 steps mentioned in
  previous paragraph are necessary:
  1. Find your notification type in "Not assigned" - lower
     part of screen

1. Click on it
2. Check the group you wish to assign the notification type to

1. Press save , and save it to relevant CR code

1. Build screen structure for
   your notification type

• Go to SPRO IMG - > Plant
  Maintenance and Customer Service - > Maintenance and Service Processing
  -> Maintenance and Service Notifications -> Overview of Notification Type

• Here you should find the
  notification type you've created and mark that row

• Then, you should double
  click on the library icon named Screen Areas in Notification (first icon from up,
  in the left part menu - shown in print screen above)
  
  
  
  
• The screen which will open
  should be configured like this (screen type hdr = "H100" , ScrnType
  Object = "O100") :

• If this is the case ,
  double click on "Screen Structure for Extended View" library icon
  (second from up) this step is crucial for notification's type screens
  structure
• The following screen will
  appear
  
  
  
  
• The values in the left
  column determine notification's type main tabs. Here we can see that there will
  be 4 tabs for this notification's type "BA"
  
  
• Press on Tab's field search
  help button , and choose from that code bulk

• Every code has different
  tab's structure. Tip: You can change Tab's header to other tab's name for your convenience.  For example I changed 10\TAB19 tab name to
  "Attached Files".

• After you've finished
  choosing and submitting tab codes don't forget to save changes to relevant CR.
• Go back to this screen :

• Now you will built, in very
  similar manner , the inside screen parts of each tab you chose to configure
• Mark relevant tab row , and
  press in upper screen menu on Magnifying Glass button ("details" button
  
  
  
• The following screen will
  appear :

• You can name the Tab header
  here (tab header was mentioned in previous sections)
• The lower screen part is
  crucial for each tab inside structure (inside screen parts)
• Choose in the following fields:
  Screen area 1, Screen area 2, Screen area 3, Screen area 4, and Screen area 5
  the proper built in SAP codes. The order of inside screen parts is determined
  like this: first screen part will be the one that its code was submitted to
  Screen area 1, second one that its code was submitted to Screen area 2 and so
  on…
  
  
  
• For example my 10\TAB01 tab
  is configured like that :

• Don't forget to save every
  change to relevant CR.

1. These three major steps are
   main configuration step for creating new notification type. Your notification
   will work, just run it in IW21 tcode.
2. There are many additional
   configuration options for notification type like using catalog profiles, partner
   determination procedures and priority profiles (PM notification is a very
   powerful tool (!)). I will explain in detail those options in the following
   technical document.

1. SAP Equipment Record functionality

The equipment record is unique information associated with a material number, and a corresponding serial number for the material in SAP.

This document basically can be categorized into two major segments

• The functionality & features available in equipment record in SAP.
• And focuses on the integration of equipment masters with other external applications with help of Idocs

Majorly in HI Tech industries the business tracks these equipments in several ways, it’s inventoried within the plant with equipment numbers, and stock transfers are done to Distribution centers with Serial numbers. And lot of customer / End consumer information is stored in the Equipment record for future support purposes

2. Business purposes of Equipment

• Equipment records are delivered to customer sites.
• Equipment numbers (serial numbers) consumed in a production order as components
• Shipped from stock, Shipped to certain partner locations from where it undergoes installation protocols
• Set of Equipment records are then batched for customer acceptance Via SAP CRM
• Data updates happen on the Equipment records at various stages of the business, Address details are updated in the equipments.
• Customer acceptance is done with equipment record numbers.
• Material returns are taken back at plants with serial numbers / Equipment record.

3. Highlevel Integration flow

4. Partner functions definition and assignment

The feature in equipment record, allows you to define & assign partner functions in them.

• Sold to Party
• Ship to party
• Installation partner
• Bill to Party

The Equipment used in a customer delivery can automatically copy the values from the Sales order / or a delivery and assign the partner functions value in the equipment.

The partner functions could be driven later on for Billing relevant reports, it gives information on which equipment is delivered / or categorized with that sold to or Bill to customer.

5. Class / characteristics in Equipment record

There is a provision where you could define class with characteristics which can be assigned to an equipment record

Class type 002 – Equipment class can be created and assigned to equipments

Mainly the Bundle information in equipment is stored in the picture above, but otherwise any parameter related to the equipment could be stored as details in the characteristics.

6. Custom status in Equipment record

The Standard SAP status in an equipment indicates the Delivered / in stock / Available statuses.

Based on customers requirement the User status profile can be configured, and assigned to the equipment category.

The custom statuses could be numbered, and based on sequences certain controls could be put in place so that the user is prompted to select these in a order defined in the back end configuration.

This is the Equipment view – where the user status profile is assigned, and it shows the different level of the statuses. These statuses can be manually changed with IE02 / or IQ02, but in the current integration the Inbound Idoc to ECC controls the status set.

6.1 Configuration menu for the User status.

6.2 Definition of the Status profile, with different statuses.

7.Additional data Tab in Equipment record

The other important feature which is implemented is the View profile change in the Equipment. This gives the flexibility for the users to add more details, basically the end customer relevant information like customer hierarchy, Location where the device is set, the I P address of the equipment, and much other consumer information can be stored

7.1 Defining the view profile

7.2 Assign the view profile to the equipment level, Equipment category

Part 2 of this document - about the Idoc ALE technical setups

8. Idoc Settings of the Equipment record

Tcode  WE81

We will need message type for Equipment integration through IDOC. For this we may use the existing message type available in the system or create a new message type using Tcode WE81. Here we use the existing message type in the system.

Tcode WE30 & WE31

  We have created custom IDOC to handle our requirement. This IDOC will contain the standard sturctures and structures to hold the address of the equipment and the custom fields. The address will be passed using the segment E1BPAD1VL which is copied from standrard ADRMAS01 IDOC and the custom fields are passed using custom segment

Tcode WE82

  We have assigned the existing equipment create message type to the IDOC which created in the previous step. This is required for both the inbound and outbound IDOC processing as we need message type for each IDOC

9. Inbound IDOC settings:

Tcode WE57

  Inbound IDOCs are processed by Function modules. We copied the standard function group ITOB_BAPI_EQ to a custom function group including the function modules to custom fuction modules to write additional logic to update address and the custom fields. Then we have to configure the custom function module copied from the standard function module IDOC_INPUT_EQUIPMENT_CREATE in the tcode we57. So when ever an equipment IDOC comes into SAP then this function module will be triggered first with passing the IDOC details

Tcode BD51

  In this setting we instruct SAP system to process the IDOC one by one instead of executing in bunch as the custom function module cannot process such.

10. Outbound IDOC settings:

Settings for change pointer:

Change pointers are created with respect to message types. For each message type if the setting is there it will create a change pointer.

In Tcode BD50, message type should be enabled for change pointer creation.

In Tcode BD52, the fields were mentioned for which the change pointer should be added. For our scenario, we need to send IDOC for any change in the equipment, we set the table key as the change pointer field and we override the change pointer creation using the BADI mentioned below.

In Tcode BD60, a function module should be assigned. This function module will take care of creating IDOCs from the change pointer. Our function module is a copy of the standard function module MASTERIDOC_CREATE_SMD_EQUI. To accommodate the custom details like user status and the customer field data, we have copied the standard function module and changed it.

In Tcode BD64, settings are done as given below. This settings will determine to which system the IDOC needs to be sent.  For partner profile settings to send and receive IDOC please refer the SAP help documents.

11 Integration:

Create change pointer:

  Whenever equipment is changed, we have to send the changes to other party via IDOC. Because of having large number of additional fields and the fields may be added more in the future, also user status is not in the EQUI table, we have written our own logic to create change pointers for the equipment and user status changes. This logic was written in the BADI EQUI_UPDATE on the method IN_UPDATE which will be called during the update task. The following is the sample code for writing the logic to create change pointers. Pass ‘I’ as a value to the ‘object_change_indicator’ field to make an entry in the change pointer table BDCP2

Thank You.

  Authors – Karthi Selvanayagam & John Rajadurai

• It identifies the products/services under warranty
• Validate the authenticity of warranty claims
• Validates whether the product/service issue highlighted by customer falls under warranty
• Define the effects of warranties on pricing & invoicing
• Monitor expenses incurred under due to warranty issues

1. Vehicle Consumer come into dealership
2. Dealer determines if product/service defect is under valid warranty
3. If yes, dealer files warranty claim
4. Warranty assessors may review claim for accuracy
5. Claim is either approved or rejected
6. If approved, claim is processed through to Finance and dealer is reimbursed

1. Define Warranty Claim Type
2. Assign Number Range for Claim Type
3. Define Decision Codes
4. Define Pricing for warranty claim
5. Maintain Pricing Condition Records
6. Define Action Matrix for Claim Processing
7. Define GL Account Determination Procedure for Claim Processing
8. Assign Pricing, action matrix and GL Account Determination Procedure to Claim Type
9. Implement Validation/Substitution for claims (Optional)
10. Define Output Determination for claim credit note 
11. Maintain Output Condition Records

    

Assign Claim Type to the Group:

Transaction Variant

Prepared By: Eslam Hosny

In This Document we will learn the concept & how to create Transaction and Screen Variants to change screen layouts.

And how to assign those transactions and screens variants to:

• A Standard Transaction
• A group of users
• A new transaction

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

Transaction Variants can simplify transaction runs as they allow you to:

• Pre assign values to fields
• Hide and change the 'ready for input' status of fields
• Hide menu functions
• Hide entire screens

A Transaction Variant is made up of a series of screen variants.

Screen variant contains field values and attributes for exactly one screen.

Transaction Code -> SHD0

The above Three Tabs in the T Code SHD0:

• Transaction Variants – > Create Transaction Variants and assign Screen Variants
• Screen Variants – > Create Screen Variants.
• Standard Variants -> Used to assign Transaction Variants to standard transaction

                                               Create and assign Variant Groups to specifics users

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

Creating Transaction Variant from a Transaction (Transaction Variant TAB)

• You can create the Screen Variant first  (Screen Variant TAB)and then create Transaction Variant (Transaction Variant TAB)
• Or create both at the same time (Transaction Variant TAB) -> Preferred

Our Below Example will be on T Code IW31 (Create Maintenance Order)

• Once You Pressed Create, The System Will Call The T Code IW31
• Fill all the required fields  & Any Field you Want Then Press Enter

Once You Pressed Enter, The System Will Call A Configuration Screen That Represents The T Code IW31 In Forms Of Screens with its own Fields

• W.Content: set the value you entered as default
• Output Only: Dimmed
• Invisible
• Required: Mandatory

In Our Example

Then

• Press Enter If you want to change the another available screen In The T Code IW31
• Press Exit & Save If You Finished

Result -> Transaction Variant Created With Its Screen Variants

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

Then You Can Test Your Transaction Variant

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

Using the Transaction Variant You Have Created

• Assign it to The Standard Transaction
• Assign it to a group of users
• Assign it to a new transaction (Variant Transaction)

1- Assign The Transaction Variant To The Standard Transaction (Standard Variants TAB)

If you assign the Transaction Variant to transaction IW31 the changes will affect all the users that use the transaction.

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

2- Assign The Transaction Variant To A Group Of Users (Standard Variants TAB)

Here We Create a Group (Variant Group)

• A Transaction Variant Generated Automatic Once You Create The Variant Group
• Then Assign Users To The Variant Group
• Set Proposal : To Active The Variant To The user

Then Go To Transaction Variants TAB & Put The Transaction Variant Generated in the previous step With The group & Create it as normal transaction variant or Assign the Screen Variants to it

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

3- Assign The Variant To A New Transaction (Variant Transaction)

You Have Two Options:

A- In T Code SHD0,  Then From Go To Menu -> Create Variant Transaction

B- From T Code SE93

We Will Work From T Code SE93

Then Save

You Can Now Use Your T Code

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

Note:

• You cannot activate more than one transaction variant to a standard transaction, only one

For example:

If you created two transaction variant from T Code MM01, and you need to assign the two variant to the standard T Code (MM01) -> You cannot, only one can be assigned

• If you created two transaction variants for example from T code MM01, and you assigned one to the T Code MM01 & the other to a user(s)

So all the users will work with first (assigned to the T Code MM01) & The User(s) will work with the variant that is assigned to

• You can assign to a group (User(s)) more than one variant -> but the these variants must be from different T Codes

Dear EAM community,

a new additional documentation for Configuration Control is available under SAP note ‘2106827 - Getting started with
Configuration Control’.

The document has the title 'Getting Started With Configuration Control'

Motivation of the document:

• This document is made to arouse the understanding how Configuration Control is
  working.
• Basic modeling skills of the data used for Configuration Control should be provided.
• If available, technical chapters should provide an insight into the coding of the
  application to enable users to adjust the application to their needs.
• Specific chapters provide information on industry specific enhancements of Configuration
  Control e.g. Aerospace & Defense (IS-ADEC).
• This document is making use of the Configuration Control functionality since EhP4.
• This document does not explain the used transactions and the underlying applications
  like LO-VC and the customizing in detail. Explanations are given as far they
  are necessary to understand the basics of configuration control.
• This document does not make an experienced Configuration Control consultant obsolete
  when you want to introduce Configuration Control at your company!

Regards

Robert Hügel

Introduction

I would like to explain how to create new PM order Shop paper for your customers specific needs.

A shop paper is a type of printout of data stored in SAP system (I.E data in PM order). After your user has filled all data in PM order, he can print this data in any style - I.E: like he used to print in his previous data system. Usually shop papers from SAP are converted customised to become PDF file for print preview / for print.

1. First step : Customise new PM order Shop paper

Go to : SPRO -> Plant maintenance and customer Service -> Maintenance and Service Processing -> Maintenance and Service Orders -> Print Control -
> Define Shop Papers, Forms and Output Programs.

Choose "Define Shop Papers"

SAP already contains 8 Shop papers :Shop paper 2010 , Shop paper 2020 , .... , Shop 2072 . each Shop paper displays the printed data from Pm order little bit diffrently. I highly recommend to copy 2010 shop paper into new shop paper created. Give a name like Y___ to the new copied shop paper (I gave YBDL because Y represents new shop paper created by me and not by SAP developers , BDL represents the idea behind my shop paper : Delivery printout.

Below - Print screen that shows how to copy 2010 to new Shop paper - mark 2010 and press copy button in upper screen menu :

Then you will see the next screen :

Because I have seen a lot of opinions regarding the extraction of the long texts from Notifications and Work orders, I suggest a very easy way.

When a long text exist in one Notification, you go to the text editor, GoTo-HEADER, and read the info from there:

Then enter SE37, Function Module READ_TEXT, and execute with the data from the Notification

Click on the 2 entries and you'll get the Long text from the Notification.

For the Work Order the data that have to be provided in SE37 is:

You proceed the same way.

I hope this is useful.

Best regards,

Sorin

This document should be used as a reference to understand the SAP APO <> SAP PM Integration which will allow for the maintenance orders to be reflected on the APO Planning Board. The maintenance orders on the APO Planning Board are to request for capacity to be blocked on the production work center for maintenance as well as providing visibility to the maintenance schedule.

Requirement:  The Production Planners to have visibility of planned maintenance work against the production resource and the Maintenance Planners to have visibility to the APO planning board so they can schedule the maintenance work based on the availability of the production resource.

Below steps enable the setup required to fulfil the above requirement.

• Identify the maintenance order types which need to be sent to SAP APO.
• On the ERP side for SAP PM you need to maintain the Production (PP) Work Center on the Equipment master record (transaction code IE02).
  • The PP Work Center will go in the Work Center field on the Location tab.

• The PM Work Center is in the Main Work Center field on the Organisation tab.

• Configure and setup the CIF in SAP APO (CIF is the interface which enables data to be exchanged between SAP APO and SAP ERP system).
  • CIF needs to be setup with the Order Types which are identified to be reflected on the APO Planning Board as well as the System Condition field and any other relevant selection criteria.
  • Note: The way we had it setup was that if the System Condition field was set to '0' (not in operation) by the user then the maintenance order will be displayed on the APO Planning Board. For us setting the system condition field was a manual job.
    You do not want to flood the APO planning board with all maintenance orders hence, the need to manage it through the System Condition field manually and only reflecting those maintenance orders where there is a need for the production equipment to be stopped for maintenance.

• Below screenshots show how the APO Planning Board will look if the System Condition was set to ‘0’ on the maintenance order, then if it was set to ‘1’ and finally, if the system condition was just left blank on the maintenance order.

• After the setup is complete and the integration between SAP APO and SAP PM is working you need to look at granting display only access to PM planners to the APO planning board through the following two transaction codes:
  • /SAPAPO/RES01 - Resource-Production Resource Display
  • /SAPAPO/CDPS0 - Detailed Scheduling Planning Board

The above setup will allow the Production Planners to have visibility to the maintenance schedule as well as the Maintenance Planners to plan maintenance around the Production Planning Schedule.

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

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

This measure indicates the total internal as well as external capacity available to perform / execute maintenance tasks.

• RDS_EAM_002  - Capacity for Preventive Maintenance

The measure provides visibility to the capacity of maintenance work which is executed as preventive maintenance and indicates maturity of planning.

• RDS_EAM_003  - Capacity for Predictive Maintenance

The measure provides visibility to the capacity of maintenance work which is executed as predictive maintenance (Condition Based Maintenance). Typically, there could be multiple variants of it: based on planned man hours, available man hours, actual man hours.

• RDS_EAM_004  - Capacity for Breakdown Maintenance

The measure provides visibility to the capacity of maintenance work which is executed as breakdown maintenance. Typically, there could be multiple variants of it: based on planned man hours, available man hours, actual man hours

• RDS_EAM_005  - Percentage of Work Orders for Preventive Maintenance

This measure reflects the percentage of work orders created (completed) in the system as a result of preventive maintenance. The percentage of preventive maintenance orders created will exclude canceled orders as well as orders with the deletion flag. Preventive maintenance can typically be identified through the use of order type or maintenance activity type or planning indicators to understand preventive work from total work.

• RDS_EAM_006  - Percentage of Work Orders for Predictive Maintenance

This measure reflects the percentage of work orders created (completed) in the system as a result of predictive maintenance (Condition Based Maintenance). Predictive maintenance can typically be identified through the use of order type or maintenance activity type or planning indicators to understand predictive work from total work.

• RDS_EAM_007  - Percentage of Work Orders for Breakdown Maintenance

This measure reflects the percentage of work orders created (completed) in the system as a result of a breakdown. Breakdown maintenance can typically be identified through the use of order type or maintenance activity type or planning indicators to understand breakdown work from total work.

• RDS_EAM_008  - Percentage of Work Orders for Emergency Requirements

The measure provides visibility on the percentage of maintenance orders created as a result of an emergency work or after event recordings.

• RDS_EAM_009  - Percentage of Work Orders for Critical Assets

The KPI will indicate the percentage of orders raised against critical plant assets. The measure will be based on identifying orders based on equipment criticality assignment, the ABC indicator for technical objects on maintenance orders.

• RDS_EAM_010  - Percentage of Capacity used for Performing Maintenance Tasks

The measure will identify the percentage capacity being utilized to perform actual maintenance work from the total available maintenance capacity. This assumes all maintenance time including maintenance performed by external resources is confirmed in the system. If time for external resources is not confirmed then the KPI will not reflect a true picture of the capacity used for performing maintenance tasks.

• RDS_EAM_011  - Percentage of Work Orders Resulting from Condition Monitoring

The KPI will provide visibility in understanding the percentage of maintenance orders created as follow-up maintenance post the inspection task. This can be managed through a maintenance order with a specific notification type that can identify 'follow on of condition monitoring‘. This could be enhanced by using maintenance activity type, planning indicator, and order type.

• RDS_EAM_012  - Backlog of Activities

Backlog is the volume of work which remains outstanding for maintenance activities. The measure will reflect the number of orders in released status but not completed.  All maintenance orders which are not technically completed are part of the backlog.

• RDS_EAM_013  - Completion Rate

The measure reflects the percentage of maintenance orders completed by the latest allowed finish date out of the total number of maintenance orders created in the system. Maintenance compliance monitors whether the work is being completed on time (which is determined through consistent risk assessment).

• RDS_EAM_014  - Schedule Adherence

The measure shows the number of maintenance orders which were scheduled and have been confirmed to have started and finished (completed) within the scheduled period. The measure reflects the number of maintenance orders being completed on time within the planning bucket.

• RDS_EAM_015  - Notification Response Time

The measure provides visibility on the time it takes to respond to a notification created by the operations team.

• RDS_EAM_016  - Maintenance Rework

The measure helps identify the number of times an asset fails in the same mode in quick succession after maintenance was performed and completed. For example, the same damage code on the same technical object within 7 days is seen as maintenance rework.

• RDS_EAM_017  - Maintenance Cost as Percentage of Replacement Value

The measure provides visibility of the cost to maintain an asset. It helps determine how cost effective the asset is.

• RDS_EAM_018  - Budget Utilization

The measure shows the approved maintenance budget and how it is being utilized.

• RDS_EAM_019  - Number of Work Orders per Clock Hour

The measure provides visibility on the number of maintenance orders created per hour.

• RDS_EAM_020  - Number of Notifications per Clock Hour

The measure provides visibility on the number of maintenance notifications created per hour. Operators / users of assets regularly create notifications to report breakdown or malfunction. To ensure maintenance team can respond to such maintenance requests with little or no impact on production the KPI helps in identifying when the maintenance planner may be required most within a day.

• RDS_EAM_021 - Mean Time Between Failure (MTBF)

Mean Time Between Failure (MTBF) is a measure of equipment reliability. The MTBF of an equipment is calculated from the total equipment downtime in a specific period reviewed divided by the number of failures in that period. MTBF is an equipment specific measure which is used to identify opportunities to improve equipment reliability.

• RDS_EAM_022 - Mean Time To Repair (MTTR)

Mean Time To Repair (MTTR) is a measure of efficiency of the diagnostic, procurement, maintenance preparation, scheduling, repair and re-instatement process. The MTTR is calculated from the total equipment repair time in a specific period divided by the number of repairs in that period. MTTR is an equipment specific measure and is used to set continuous improvement targets.

• RDS_EAM_023 - Mean Time Between Repair (MTBR)

Mean Time Between Repair (MTBR) is a measure of the average time between repair for component, equipment or units. The calculation is based on total uptime between repair divided by the number of repairs over a period of time.

• RDS_EAM_024  - Technical Availability of Assets

The technical availability of an asset is a measure reflecting the number of hours an asset is available or how many hours this machine can be kept working in a period

• RDS_EAM_025  - Operational Availability of Assets

The operational availability of an asset is a measure which shows the number of hours the asset is operational. The operational availability is calculated by taking the maintenance activities and / or downtime of the asset from the total operational available capacity of the asset.

• RDS_EAM_026  - Number of Stock Outages

This measure will provide visibility on the number of orders for which there was a material shortage / material out of stock.

• RDS_EAM_027  - Orders Delayed Due to Stock Outages

The measure will provide an understanding on the number of maintenance orders which were delayed due to material stock shortage. The calculation is based on the basic finish date of the order which if not adhered to reflects a delay in maintenance. The measure will exclude and not evaluate the maintenance orders where the basic finish date is not maintained.

• RDS_EAM_029  - Subcontracted Work as a Percentage of Total Work

The measure provides visibility on the number of external resource man hours procured to perform maintenance tasks.

• RDS_EAM_030  - Maintenance Request to Correct Safety Incidents

The measure can help identify the number of times a safety incident was recorded and the action taken after the root cause analysis to perform maintenance to an asset to prevent a future incident.

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

The measure can help identify the number of times an injury was recorded which resulted in the root cause analysis and led to maintenance being performed on an asset to prevent future incidents.

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

The measure can help identify the number of times an environment related incident was recorded.

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.

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.