Overview

With mobility seeping every spectrum of our life like never before, it is little doubt that organizations are spending huge amount of dollars developing a variety of apps to make our lives easier and simpler. Be it accessing email on an Android or using an iPhone to facilitate a video conference from a remote location, everything has become a reality with a click of a button. If Forrester Research’s predictions are anything to be believed, around 60 million tablets and 175 million smartphones will be in use by global workforce by 2015. This is a clear indicator about how mobile has a major role to play in our professional work lives, considering that the major contributor to this new found interest would definitely be the industrial sector, particularly in asset intensive or manufacturing industries.

As already mentioned, mobility in the manufacturing environment has a key role to play with a plethora of activities including daily plant maintenance activities that work with enterprise asset management systems. This way organizations can save time and enhance efficiency by helping them to work anywhere, anytime without the need to constantly be attached to their desktops. This blog throws some light on the benefits of using mobile devices in routine plant maintenance activities.

How can mobile enhance plant maintenance?

Though many industries have recognized the importance of empowering their workforce with mobile devices, however, it is imperative that organizations clearly define the mobile strategy and identify why it can benefit their organization. This is particularly true in case of plant maintenance.

Can integrating mobile with day to plant maintenance activities really yield benefits? The answer is yes, and how is it possible? Take for an instance, a worker who has a tablet to help him gather field information instantaneously – not at the end of the day. This will enhance the pace at which the work orders are updated and completed.

So, what are the functional and commercial aspects that we need to look at when planning to purchase a solution for plant maintenance?

1. Access to real-time data

          Instantaneous access to information including real-time notifications and confirmations pertaining to various transactions such               as  breakdowns is one of the factors to consider while looking for a mobile solution for routine plant maintenance. By offering               real- time updates, technicians can save hours of work, while working on desktop, providing an accurate status of progress                   tracking of a work order.

2. Access to routes and inspections

     Maintenance supervisors and quality inspectors should be able to use the mobile           app on their tablets and smartphones to create, view and update maintenance      routes and measurements points in real-time. Apart from that, the solution      should help them respond and approve notifications on the fly, when they are out of        the plant floor. This way, they can enhance the wrench time and provide an      accurate picture of the completion status.

3. Simple and user-friendly interface

      This should be the primary goal of a good mobile application, considering that a            mobile screen is much smaller, compared to a  desktop screen. This means,           companies need to identify what key aspects of their daily maintenance process are to be displayed on the interface. It is always better to display lesser information with quicker access and updates, rather than having too many buttons or text, creating lot of clutter and confusion.

4. Ability to upload pictures

          Instead of typing endless text to provide the description of the equipment, a good mobile application for plant           maintenance   should have the ability to attach pictures associated with equipment breakdowns, thereby creating a better           visibility on  equipment reliability.

5. Barcode scanning

            This feature helps to identify the history of a piece of equipment under consideration as also helps to search for parts. One                     step ahead is the geo-tagging feature that lets you identify the exact location of the equipment, which is quite useful           during tracking and auditing of assets. A good mobile solution should be able to provide this barcode scanning feature with the           help of camera  available  on a smart phone or a tablet, saving lot of search time and avoiding information inaccuracies.

6. Search options

          A good mobile solution should provide a user-friendly search options for the availability and location of spare parts. This           way, it maximizes user’s efficiency, while improving the repair timelines.

7. Document viewing

            A right solution should provide access to key documents such as work order instructions, technical documents and safety                       instructions  in variety of formats including PDF. This way field technicians and plant personnel can make informed decisions                 about work orders and assignments, while considerably cutting down costs on printing.

8. Quick deployment

          A good mobile solution should be able to quickly adapt to an organization’s infrastructure, enabling quick deployment and                     minimizing implementation timelines.

9. Data Security

            Most of the organizations are concerned about the security of their data, particularly when they are dealing with costly           equipment  and assets. A right solution should be able to address these issues and provide an extra layer of data security,           without posing hindrances to the existing functionality, while executing day to day maintenance tasks.

10. Cost aspects

          Last, but not the least is the cost aspect that typically crops up in our mind – how much does a good mobile work order                     solution  cost  and will my organization be able to afford it? Hence, a good solution vendor cannot ignore this aspect,           irrespective of the  number of features that the solution can offer, as most of the companies are in the mid-level segment,           looking for a solution that  is affordable including costs related to installation, maintenance and future upgrades.

Innovapptive mobile order solution - mWorkOrder

Innovapptive Inc., a premier SAP certified partner had evaluated and understood the various pain points and challenges encountered by typical asset intensive industries and developed a cutting edge mobile work order management solution – mWorkOrder. mWorkOrder leverages the SAP’s Plant Maintenance module at the back-end to deliver a consistent, reliable and a productive asset maintenance experience across a wide range of industries.   It empowers maintenance technicians and quality inspectors to work safely and productively relating to installing new equipment or maintaining, inspecting and repairing existing assets. Apart from that, the mWorkOrder app also mitigates the risk of injury by helping workers complete safety checks and follow safe work practices.

Value Drivers

• Receive and update work orders.
• Get directions with GIS and GPS.
• View installed-base listings and access equipment, details, dependencies and maintenance history.
• View interactive part schematics (with the SAP Visual Enterprise Viewer).
• Follow guided workflows, steps and instructions.
• Install and geotag equipment.
• Perform maintenance, inspections and repairs.
• Track and automatically report status, progress and location.
• Capture readings, measurements and photos.
• Record problems, actions, time, parts and materials.
• Create work orders and notifications on the spot.

Business Benefits

• Extend and improve asset life and reliability.
• Improve plant, fleet and equipment performance.
• Improve workforce safety and productivity.
• Minimize accidents, failures and outages.
• Reduce unplanned downtime and maintenance backlog.
• Improve first-time resolution rates.
• Enhance the efficiency of warehouse, plant, field and accounts payable personnel.
• Ensure assets run at peak performance with shorter response times and timely maintenance.
• Complete safety checks and adhere to safe practices.

Abstract

In the past, assets were designed in large construction teams but companies in recent decades focus more and more on their core activities. The management of capital goods is being organized in the (supply) chain of owners, users, manufacturers, research institutes, IT, service providers and so on. The complexity of modern systems (e.g., mechatronics) and sustainability issues have placed more pressure on cooperation: openness, interaction and stability in the relationship foster joint innovation in product, process and technology. Focus on opportunities rather than risks makes this cooperation successful.

Please follow this link to download the whitepaper>>

Author:   Leo A.M. Van Dongen

NedTrain Fleet Services

University of Twente, Faculty of Engineering Technology

Hello friends,

Continuing the process of preserving the solutions to Frequently Asked Questions, today I chose this subject. Few might have understood the possible need behind this simple title. However, I will explain.

The Background:

There were threads asking for solution where they want Orders with some status to be prohibited from processing. The 'Do not Execute' function is the ready answer for the Orders which are in CRTD status. But generally the queries were for REL Orders? There are two situations of this requirement.

• In Case1, customer wants all the Orders of certain Order type and in REL status are to be prevented from changes, Only viewing should be possible through IW32.
• In Case2, specific Orders faultily created and released need to be prevented from processing.

Similarly there were queries where Authorization check at the initial screen of IW32 was sought. Obviously this as an alternative route to control through Roles.

• We take this as Case3 of this blog .

One way of doing addressing all these is definitely through user-exit IWO10009. But this method stops users at the time of Saving the Order. Means, user spends time and effort to make all changes in the Order and system refuses his changes when he tries to Save the Order. Also achieving a perfect solution for Cases1,2 through user-status (OIBS) transaction control is not possible.

So the requirement is to stop the user in the beginning itself of IW32. The ways to do it.

• Change the IW32 to display mode for all such Orders
• Stop user at the initial screen of IW32 itself by throwing a message such as 'This Order is prohibited from changes, use IW33 for viewing' OR 'You are not authorized for IW32' .

The Solutions:

The solutions discussed here are very effective using an Implicit Enhancement point in the include LCOIHF7R of Order program (SAPLCOIH). Here there is an enhancement point at line number 250 which is at the end of the form AUTHORITY_CHECK_AUART_SMOD .

The place to put our code:

Means, I have created an Enhancement named ZPM_STAT at the enhancement point provided by the system, where I got access to put my code. Now let's see the codes for various cases and situations.

First we look at the Case1, Situation1: For all Orders of certain Type and in REL status, Converting IW32 to Display mode

The code:

DATA: it_stat TYPE STANDARD TABLE OF jstat,       wa_stat TYPE jstat.
 IF caufvd-auart = 'ZM03' AND  sy-tcode = 'IW32'.   CALL FUNCTION 'STATUS_READ'     EXPORTING       objnr            = caufvd-objnr       only_active      = 'X'     TABLES       status           = it_stat     EXCEPTIONS       object_not_found = 1       OTHERS           = 2.   IF sy-subrc <> 0.   ENDIF.   LOOP AT it_stat INTO wa_stat.     IF wa_stat-stat = 'I0002'.       tc10-trtyp = 'A'.   "Replace 'V' by 'A'.       MESSAGE: 'Changing to Display' TYPE 'S'.     ENDIF.   ENDLOOP.
 ENDIF.

This code turns IW32 to Display mode for all released ZM03 Orders (you will change this Order type to yours)

Case1: Situation2: For all Orders of certain Type and in REL status, Stopping user to enter the Order through IW32.

The syntax to be used here has little changes. (Same code as above upto line no.18)

DATA: it_stat TYPE STANDARD TABLE OF jstat,       wa_stat TYPE jstat.
 IF caufvd-auart = 'ZM03' AND  sy-tcode = 'IW32'.   CALL FUNCTION 'STATUS_READ'     EXPORTING       objnr            = caufvd-objnr       only_active      = 'X'     TABLES       status           = it_stat     EXCEPTIONS       object_not_found = 1       OTHERS           = 2.   IF sy-subrc <> 0.   ENDIF.   LOOP AT it_stat INTO wa_stat.     IF wa_stat-stat = 'I0002'.     MESSAGE: 'This Order has been prohibited from changes. For viewing use tcode ''IW33''.'       TYPE 'E' DISPLAY LIKE 'I'.     ENDIF.   ENDLOOP.
 ENDIF.

This throws this error popup at the initial screen of IW32 for all ZM03 Released Orders.

.

NOTE:

In cases like this, the user can do TECO and CLSD through IW38.

Now let's look at Case2

Case2: Specific Orders to be barred from handling. Means users to be stopped at the initial screen of IW32.
Obviously, these Orders can be any type. Because this requirement as mentioned earlier is often for defective Creations which were already put into REL status.

Pre-requisite to handle this situation

Create a Ztable say ZPM_BLK_ORD having the Order(aufnr) field. (If you want more Order related fields you can have). Create this table with TMG (Table maintenance Generator) so that you will be able to update this table (Add/Delete) with Order numbers through tcode SM30 or through a Ztcode.

Now, the code in this case.

DATA: v_aufnr TYPE aufk-aufnr.
 CLEAR: v_aufnr.
 SELECT single aufnr FROM zpm_blk_ord  INTO v_aufnr WHERE aufnr = caufvd-aufnr.   IF v_aufnr IS NOT INITIAL.   MESSAGE: 'This Order has been prohibited from changes.' TYPE 'E' DISPLAY LIKE 'I'.   ENDIF.

This also throws similar error popup as shown earlier when user tries to use IW32 for all such Orders which are entered in the ztable ZPM_BLK_ORD.

Now let's see the Case3.

Case3: Specific Users to be restricted from handling IW32.

Pre-requisite to handle this situation

Create a Ztable say ZPM_BLK_USR having the UserId(uname) field. As above create this table with TMG .

Now the code in this case.

DATA: v_uname TYPE uname.
 CLEAR: v_uname.
 SELECT single uname FROM zpm_blk_usr  INTO v_unmae WHERE uname = sy-uname.   IF v_uname IS NOT INITIAL.   MESSAGE: 'You are not authorized for IW32.' TYPE 'E' DISPLAY LIKE 'I'.   ENDIF.

This also throws similar error popup as shown earlier when user tries to use IW32 , whoseuserId has been included in the ztable ZPM_BLK_USR..

Conclusion

We may have several similar situations. How this post helps is, it is giving the information about the enhancement point and giving sample codes which will be helpful in meeting similar requirements. All cases other than already illustrated can be very easily managed through simple changes in the codes given.

Hope members will find this post useful.

Thank you and Regards

KJogeswaraRao

this Blog is dedicated to the developers who focus on EAM.

Are you aware that the master data APIS have been enhanced to support more functionality like setting user status and is now support Custom fields? This has been an missing quite some time and is available Now.

This has been achieved by within the Customer Connect program which we have finalized quite some time ago.
The dedicated functionality which have been delivered in Customer Connect Cycle 3 you find in the Innovation Discovery
For Customers using SAP GUI Improvements in Asset Operations Maintenance

For Customers using the new Web User Interface  Improvements in Asset Operations Maintenance

The overall improvement Note  Note 2121573lists all the changes which have been made recently in the APi´s

• EQUIPMENT APIS:   Please review this Note 2215722
  • Setting user status is now supported by the new RFC enabled function module IBAPI_EQUI_USER_STATUS_CHANGE
  • Setting System Status Inactive is now supported by the  new RFC enabled function module IBAPI_EQUI_SET_INACTIVE
  • Resetting System Status Inactive to Active is now supported by the new rfc enabled function module IBAPI_EQUI_RESET_INACTIVE
  • Setting the system status Deletion Flag is now supported by the new rfc enabled function module IBAPI_EQUI_SET_DELETIONFLAG
  • Resetting the system Status Deletion Flag is now supported by the new rfc enabled function module IBAPI_EQUI_RESET_DELETIONFLAG
  • Custom fields which have been appended in the table EQUI. Please review  Note 2146575
    1. BAPI_EQUI_CREATE
    2. BAPI_EQUI_CHANGE
    3. BAPI_EQUI_GET_DETAIL
• Functional Location APIS: Please review this Note 2215722
  
  • Setting user status is now supported by the new RFC enabled function modul IBAPI_FUNCLOC_USER_STATUS_CHANG
  • Setting Systemn Status Inactive is now supported by the  new RFC enabled function module IBAPI_FUNCLOC_SET_INACTIVE
  • Resetting System Status Inactive to Active is now supported by the new rfc enabled function module IBAPI_FUNCLOC_RESET_INACTIVE
  • Setting the system Status Deletion Flag is now supported by the new rfc enabled function module IBAPI_FUNCLOC_SET_DELFLAG
  • Resetting the system Status Deletiin Flag is now supported by the new rfc enabled function module IBAPI_FUNCLOC_RESET_DELFLAG
  • Custom fields which have been appended in the table IFLOT. Please review  Note 2146575
    1. BAPI_FUNCLOC_CREATE
    2. BAPI_FUNCLOC_CHANGE
    3. BAPI_FUNCLOC_GET_DETAIL

Within another blog which will follow I will give you insights about the changes in the order and notification API´s

We hope that you enjoy and use this new functionality

thanks

Stephan Bantlin

Hello Friends,

One more useful tip in this blog. That's obviously about the subject line. Means what-if we want to hide application toolbar icons such as (Put in Process) and (Complete) in a Notification?

Some recent discussions and few in the past about this requirement show that in the very beginning members look towards OIAL (Field selection for Maintenance Notifications), where settings for flags and appear. But nothing happens when we set Hide radio-button here. This is because these icons here do not belong to Application toolbar of Notification Header, but these belong to Tasks Catalog tab. So what I want to say is Hiding these icons (Notification Put in Process / Complete) not possible through spro settings.

This blog is all about how we do it. SAP has given an exclusive user-exit for this purpose namely:

QQMA0024 - QM/PM/SM Deactivate function codes in CUA menu.

Let's see how we do it. Obviously we need to put some code in the Z-include provided in this exit namely ZXQQMU35. What is the code which makes an icon disappear. For this, first you need to know the Function code of an icon. How? Go to any IW21 or IW22 screen. Press the mouse key on the icon, hit F1 key and release mouse key.

When I did this for Put in Process flag I got this popup

And when I did this for Complete flag I got this:

Means the Function code for Put in Process icon is COWO and that of Complete icon is ARCH. These codes are required for us in coding in the above include.

Now the code to hide Put in Process icon.

APPEND 'COWO' TO t_ex_fcode.

This simple one line code in the include ZXQQMU35 hides the Green flag from all sorts of Notifications irrespective of any type etc. It is equal to OIAL setting without influencing criterion. Now let's see what if we want to give influencing effect. Suppose we want to hide this icon for M2 Notification,

then the code will be:

IF i_tq80-qmart = 'M2'.
   APPEND 'COWO' TO t_ex_fcode.
ENDIF.

Similarly, if we want to hide this icon in 'M2' Notifications only for few users, then we need to maintain their userIds in a Ztable (under field name say UNAME). In this case the sample code will be like:

IF i_tq80-qmart = 'M2'.
   DATA v_uname TYPE uname.
   CLEAR v_uname.
   SELECT SINGLE uname FROM ztable INTO v_uname WHERE uname = sy-uname.
   IF v_uname IS NOT INITIAL.
     APPEND 'COWO' TO t_ex_fcode.
   ENDIF.
ENDIF.

Similarly your ABAPer can extend this logic to very complex syntax using the Import structure I_VIQMEL given in the exit, making it possible for addressing all your conditions to hide an icon.

The Before and After pictures of the cases discussed above in Create Notification screen, are shown below

BEFORE the user-exit code.

AFTER the user-exit code.

Similarly when you use function code ARCH in place of COWO in the code the would disappear disabling the Notification Complete functionality. Though the title of this post mentions two widely used flags, other icons (like partner, Default values etc) also can be hidden in the same manner .

Though authorization objects are there to be used in Roles, there will be situations we will be needing this exit. For example, in my environment, we have 1000s of PM users where we maintained limited Roles and controlled many accesses through enhancements. There can be similar other situations too which demands this exit.

This post is equally applicable to PM/CS and QM notifications as given in the title. By now something might have stricken in your mind about the applicability of this function in your area. If so, show this to your ABAPer, it is a 2minute job for him/her.

Thank you and Regards

KJogeswaraRao

Hello Friends,

As the title tells, we are going to discuss here the two queries involved:

1. Whether we can default values in the Notification and Order header fields?
2. If we can, how to do it ?

First we see the case of Notifications:

The answer to the first question is 'YES'. SAP has provided exclusive user-exit for defaulting values while creating a Notification. The user-exit is QQMA0025. Every user-exit comes with a Z-include where we can write our code which the standard program i.e, Notification create program here, obeys.

Now the second question, How to do it?

It is very simple. For example: suppose you want to default planner-group value as 'XYZ' and Notification short text as 'HVAC Repairs' for Notification type 'HV' then the code you need to put here is:

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

   IF i_viqmel-qmart = 'HV'.
     e_viqmel-ingrp = 'XYZ'
     E_VIQMEL-QMTXT = 'HVAC Repairs'.
   ENDIF.

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

After this whenever you create 'HV' Notification, you will find these two values are defaulted. You might wonder what is the need of defaulting the Notification short text? Though that was an example, there can be a case of Prefixing a certain string to the Notification Short text for a particular Notification type. Here the value we defaulted is the fixed part of the short text. User will add the variable part. Thus we are saving the punching effort to the end user. Similar are several other useful applications.

Please note that this is applicable to Create Notification only.

Note:

Things discussed above are relevant for QM Notifications also, but the exit is different. It is QQMA0007. The include here is ZXQQMU01. Codes are identical.

Let's see another way of doing it:

Suppose there is no need of editing a defaulted field value and our default value requirement is very clear, then we can use another user exit namely QQMA0014. The include here is ZXQQMU20. (It is the same for QM also).  We'll try to understand through the same code discussed above. This code in this exit AT THE TIME OF SAVING THE NOTIFICATION erases whatever present in the these fields (Planner Group and Short text) and Creates the Notification with these specified values. You can think of such applications for you.

The difference between these two exits is that the first one (QQMA0025) works only at Create (IW21) event, whereas this exit (QQMA0014) works at Create(IW21) and Change(IW22) both. Means whenever the Notification is subjected to SAVE. So if you want to confine the code to a particular tcode say IW21, then the above code changes like this.

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

IF sy-tcode =  'IW21'.
   IF i_viqmel-qmart = 'HV'.
     e_viqmel-ingrp = 'XYZ'
     E_VIQMEL-QMTXT = 'HVAC Repairs'.
   ENDIF.
ENDIF.

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

An example for this case is: I have one custom Notification type which is used as a Repair request to a central repair facility. What happens here is the Planner group, Work Center values are defaulted from the Reference Object Equipment on which the Notification is being created. Customer is supposed to change these values to specific values related to the Central Repair facility to which this notification is directed. They often forget doing so. So I used this exit, for replacing the correct values automatically when the Notification is saved.

Thus we have areached to the end of the Notification segment of this blog.

Now let's see the case of Order:

The answer to the first question here (Whether we can default Order header values?) is 'No'. SAP has not provided any user-exit like QQMA0025 discussed above in Order area. Even I do not know any such other enhancements are available. But....Updating Order header fields while at the Save event of Order is possible like that happens in the case of QQMA0014 discussed above.

So how can we do this:

Our objective here is to update few Order field values while Save event. The user-exit that makes this possible is IWO10009.  Here the Z-include where we put  our code is ZXWOCU07. Now what is the code.....

Let's consider an example of our requirement, where we need the Planner group, Work center and the Maintenance Planning Plant for an Order type are to be updated with specific values while Saving.

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

IF caufvd_imp-auart = 'PM08'.
   caufvd_imp-ingpr = 'HV1'.
   caufvd_imp-vaplz = 'MOTREP'.
   caufvd_imp-iwerk = '1000'.

   CALL FUNCTION 'CO_IH_SET_HEADER'
     EXPORTING
       caufvd_imp = caufvd_imp.

   PERFORM header_update(saplcoih).

ENDIF.

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

If we want to confine the code to IW31 only, then it can be done in a similar way as explained previously for IW21.

For quite sometime I felt the deficiency of not having the value defaulting user-exit for the maintenance order. But after I found this method using fm 'co_ih_set_header' , things became simpler for me for addressing special checks.

I want to give another example for this updating requirement. We wanted to update the Order short text field with a formatted Work Order number like DeptName/NNNN/YYYY while saving. The code here first determines the values of DeptName from the Planner Group, Running serial number NNNN on the basis of the serial number for the previously Order and the YYYY is the current year. Code then combines (concatenate) these three values all these values into a variable say v_text with / in between.

Then we use same code as above to update Order short text:

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

IF caufvd_imp-auart = 'PM07'.
   caufvd_imp-ktext = v_ktext.

   CALL FUNCTION 'CO_IH_SET_HEADER'
     EXPORTING
       caufvd_imp = caufvd_imp.

   PERFORM header_update(saplcoih).

ENDIF.

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

I feel we have adequately discussed on the titled subject.

Now, let me remind some general points on using user-exit.

• Use of user-exits is very simple. (tcode SMOD).
• If you sit with an ABAPer, you'd learn it within few minutes
• User-exit functions only if it is assigned to a project created through tcode CMOD.
• I feel every functional man should have the knowledge of enhancements especially user-exits.

Thank you & Regards

KJogeswaraRao

If you'd like to know how the creation or changes of master data such as technical assets or equipment can be governed with SAP Master Data Governance, you may check the SAP MDG enterprise asset management extension by Utopia. A nice video outlines how it provides maintenance pros and other asset management stakeholders with the relevant information, tools, and process control. Just click the graphic to watch it.

Best,

Markus

Hello friends,

Few years ago I had posted a query in scn on the subject matter, which had to be closed without solution. Same query was posted recently by one of the members, reminding me that old post of mine. Situation changed in these years. Now I am able to try and find out solutions technically wherever feasible, if they aren't possible functionally.  Present blog is about that worked-out solution for the above mentioned query and the subject line of the blog.

The Requirement

While creating Measuring Points (IK01) customer wants to have uniqueness of the field 'MeasPosition' (field name PSORT, also known as Sort field).

The Issue

The spro settings in the path: Plant Maintenance and Customer Service > Master Data in Plant Maintenance and Customer Service > Basic Settings > Measuring Points, Counters and Measurement Documents > Define Measuring Point Categories > ,

look like achieving this requirement, but it does not. In-spite of this setting we get warning message only(shown below), when the uniqueness of this field values is violated :

and as a result, the creation of Measuring point is not prevented.

The Solution:

First I tried the answer to this issue using the user-exit IMRC0001. This worked good, but has an issue, because this exit triggers After Commit work. The error message we arrange in the exit code (when the uniqueness of the MeasPosition value is violated) , interrupts the Commit work of the exit, leading to a short dump under some conditions.

The effort continued for a better solution and arrived at a right implicit enhancement pointin the MPt create program (IK01) namely SAPLIMR0in the includeLIMR0F1H at the beginning of the form PSORT_UNIQUE at Line 3.  The tested solution codes are given below for different situations.

Case1

If you want the standard Warning message we are getting to be converted to Error message without changing the message text, then the code:

The error message we get in the status bar in this case is:

Case2

If you want a Custom Error message text, then the code is as under:

The error message we get in the status bar in this case is:

Case3

Another case, where you want to have Uniqueness check within the Measuring Point Category, say 'M' . (Error message same as Case2).

Now for the convenience of copying, above three codes are given below:

Case1

DATA v_psort TYPE char20.     CLEAR v_psort.     SELECT SINGLE psort FROM imptt INTO v_psort WHERE psort = impt-psort .     IF v_psort IS NOT INITIAL.       MESSAGE E140.     ENDIF.

Case2

DATA v_psort TYPE char20.     CLEAR v_psort.     SELECT SINGLE psort FROM imptt INTO v_psort WHERE psort = impt-psort.     IF v_psort IS NOT INITIAL.       MESSAGE 'MeasPosition is not unique. This MeasPosition already exists.' type 'E'.     ENDIF.

Case3

DATA v_psort TYPE char20.     CLEAR v_psort.     SELECT SINGLE psort FROM imptt INTO v_psort WHERE psort = impt-psort and mptyp = impt-mptyp.     IF v_psort IS NOT INITIAL.       MESSAGE 'MeasPosition is not unique. This MeasPosition already exists.' type 'E'.     ENDIF.

Conclusion

As members are aware, the author believes in documenting all useful solutions worked out during replying to members queries, which builds a knowledge repository at the same time helps for quick reference in case of need. Also this way the solutions are not lost/misplaced.

Author's other posts

Thank you !

Regards

KJogeswaraRao

this Blog is dedicated to the developers who focus on EAM.

Are you aware that the order/ notification APIS have been enhanced to support more functionality like setting user status and is now support Custom fields? This has been an missing quite some time and is available Now.

This has been achieved by within the Customer Connect program which we have finalized quite some time ago.
The dedicated functionality which have been delivered in Customer Connect Cycle 3 you find in the Innovation Discovery
for Customers using SAP GUI Improvements in Asset Operations Maintenance

For Customers using the new Web User Interface  Improvements in Asset Operations Maintenance

The overall improvement Note  Note 2121573lists all the changes which have been made recently in the APi´s

• Notification APIS: Note 2215722
  • Setting user status on task level is now supported by the new RFC enabled function module IBAPI_ALM_NOTIF_TASK_CHANGE_US
  • Setting the system status Deletion Flag is now supported by the new rfc enabled function module IBAPI_ALM_NOTIF_SETDELFLAG
  • Resetting the system Status Deletion Flag is now supported by the new rfc enabled function module IBAPI_ALM_NOTIF_RESETDELFLAG
  • Custom fields which have been appended in the table QMEL and QFME can now be maintained and read . Please review  Note 2146575
    1. BAPI_ALM_NOTIF_CREATE
    2. BAPI_ALM_NOTIF_DATA_ADD
    3. BAPI_ALM_NOTIF_DATA_MODIFY
    4. BAPI_ALM_NOTIF_GET_DETAIL
• Order APIS: Note 2215722
  • Setting the user status on order operation is now supported via function module BAPI_ALM_ORDER_MAINTAIN
  • Setting the system status "Locked" is now supported via function module BAPI_ALM_ORDER_MAINTAIN method LOCK
  • Resetting the system status "Locked" is now supported via function module BAPI_ALM_ORDER_MAINTAIN method UNLOCK
  • Setting the system status "Technically completed"  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method TECHNICALCOMPLETE
  • Setting the system status "Technically completed" as well as setting the system status of the assigned notifications to "Notification completed" is now supported via function module BAPI_ALM_ORDER_MAINTAIN method TECO_WITH_NOTIF
  • Resetting the system status "Technically completed"  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method CANCEL_TECHNICAL_COMPLETION 
  • Resetting the system status "Technically completed" as well as set  the system status of the assigned notification to "Notification in process" is now supported via function module BAPI_ALM_ORDER_MAINTAIN method CANCEL_TECO_WITH_NOTIF
  • Setting the system status "Closed " which also is named as "Complete (Business)" is now supported via function module BAPI_ALM_ORDER_MAINTAIN method COMPLETE_BUSINESS
  • Setting the system status "Closed " which also is named as "Complete (Business)" as well as set the status of all the assigned notification to "Notification completed"  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method BUS_COMPL_WITH_NOTIF  
  • Reset the system status "Closed " which also is named as "Complete (Business)" is now supported via function module BAPI_ALM_ORDER_MAINTAIN method CANCEL_BUSINESS_COMPLETION
  • Setting system status "Deletion Flag"  for the order is now supported via function module BAPI_ALM_ORDER_MAINTAIN method SET_DEL_FLAG
  • Setting system status "Deletion Flag"   for the order and as well as for the assigned notifications is now supported via function module BAPI_ALM_ORDER_MAINTAIN method SET_DLFL_WITH_NOTIF
  • Reset the  system status "Deletion Flag" for the order is now supported via function module BAPI_ALM_ORDER_MAINTAIN method RESET_DEL_FLAG                                                                                             
  • Reset the  system status "Deletion Flag" for the order as well as for the assigned notifications  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method RESET_DLFL_WITH_NOTIF                                                                                   
  • For orders which are in status "Created" it is possible to execute the Do not Execute functionality via function module BAPI_ALM_ORDER_MAINTAIN method DO_NOT_EXECUTE
  • For orders which are in status "Created" it is possible to execute the Do not Execute functionality and also set for all the assigned notifications  the system status "Notification Completed" via function module BAPI_ALM_ORDER_MAINTAIN method DO_NOT_EXEC_NOTIF_CLOSE                                                                                                 
  • For orders which are in status Open it is possible to execute the Do not Execute functionality and also deallocate the assigned notifications from the order via function module BAPI_ALM_ORDER_MAINTAIN method DO_NOT_EXEC_NOTIF_DEALLOC 
  • Set the requirement date for an component in an BOM is supported via function module BAPI_ALM_ORDER_MAINTAIN
    

Within another blog which will follow I will give you insights about the changes in the order and notification API´s

We hope that you enjoy and use this new functionality

thanks

Stephan Bantlin

Identifying the true cost of owning an asset and maintaining it throughout its entire life cycle is one of the most important aspects that organizations struggle with!

This is why we identified this as one topic for our Customer Influence Program. SAP's Influencing Programs Customer Influence gives you the opportunity of interacting directly with SAP development teams. As a part of this SAP´s Influencing program the Customer Engagement Initiative (CEI) is a structured approach for close end-to-end collaboration between customers and SAP teams during the full development cycle for planned products and solutions and new releases or enhancement packages.

CEI offers an opportunity for customers to influence SAP development in collaboration with their peers. This helps SAP create products and solutions that meet our customers' needs, reflect best business practices and realize process and technology innovations. We are searching for customers supporting the project "Risk-Based Asset Life Cycle Costing".

The goal of this project is to document the requirements of maintenance planners, maintenance managers, financial controllers, and purchasers who help optimize life cycle costs and provide visibility into the inherent risks and reliability. This project will also focus on preparing a process map and respective use cases for a risk-based asset life cycle costing solution.

The Role of the customers in this project:

Since life cycle planning is a very critical process, it requires expert maintenance planners whose tasks include forecasting maintenance budgets, planning shutdowns or turn around operations, and preparing proposals to replace or upgrade assets (CAPEX/OPEX decisions). During the discussions it is also expected that a person with a good understanding of the IT system landscape is available for discussing the possibilities and helping design a reliable solution.

You will have the possibility to influence the solution and it´s capability by collaborating in an early stage of development.

Use the following link to read more about the project and to register for the CEI initiative:

https://influence.sap.com/51785822

To be part of this CEI initiative please directly connect with Rathod Hemant:  hemant.rathod@sap.com

Automatic Defect Notification create for Test Equipment with catalog codes during Inspection LOT RR 

Objective: - Whenever we are doing the result recording in Inspection Lot for Test equipment through calibration process and getting the negative result, whether it could be qualitative or qualitative result in the system will automatically open the defect notification screen with concern catalog codes.

And we can select the proper cause and defect during the Rejection of Result.

Following configuration and Transaction steps is given below.

Step 1 - Define catalog Profile for Test Equipment

Step2- Maintain Catalog code group with cause, damage, Activities & etc.

Step. - 3 Define Defect Recording for Notification

Assign Report type to the Work Center for Plant wise

As above configuration setting,after this one complete all master data 

• Equipment master
• MIC
• Selected set
• UD code
• Task List
• Maintenance Plan & etc.

Step 4. - Create Calibration Order

Create calibration order and assign the Task List

Step 5. – Check Inspection Lot and DO the Result Recording

Step 6. – Check Defect Notification

After receiving the defect Notification, Quality people will perform the calibration maintenance of Test Equipment and again will do the RR for the same.

And During the Usage decision he will decide whether it could be further used or Reject.

As above process, its complete calibration process for defect notification that captured during Inspection Lot RR.

Hope that this document would be helpful for your better run the calibration process.

Thanking You,

Akhilesh Singh

While the topic of predictive maintenance (PdM) has received heightened recognition because of new IIoT-enabled machine intelligence, it can be easy to get trapped in the belief that PdM and Asset Performance Management (APM) are the same.

It is understandable because definitions around APM can be vastly different depending upon who is supplying the definition. However, by most accounts, PdM focuses on the predictability of potential asset failure and equipment reliability, where APM looks at risk factors and performance interdependencies beyond the machines themselves.

According to ARC's definition for APM, "Asset performance has many dimensions including financial, health & safety, environmental, and sustainability.  Achieving these goals requires a collaborative effort by all groups involved in the use and care of the facility to manage the interdependencies that constrain performance.  To do this, they need an asset information management system that can deliver complete, accurate, timely information to APM workflows and enable seamless sharing of information across all APM stakeholders, internal or external to the organization."

Consistent with ARC's approach for APM, Asset-intensive industries like Oil and Gas, have always focused on the much bigger operating picture by incorporating People, Process, and Assets into a well-defined, highly efficient and proactive holistic management approach referred to as Operational Integrity.

While it would be silly not to recognize that improved machine intelligence and connectivity does positively impact PdM operations, it would be equally foolish to presume that improved machine intelligence by itself, provides the greatest business value for Asset Performance Management overall.

Looking closer at ARC's definition of Asset Performance Management,  let's focus on three of the areas they consider as critical success factors:

1) " manage the interdependencies that constrain performance."

2) " deliver complete, accurate, timely information to APM workflows."

3) "seamless sharing of information across all APM stakeholders, internal or external to the organization."

Manage Interdependencies that Constrain Performance

Until the day arrives, when machines operate other machines without people, Companies must manage the risk and performance dependencies, between how their people, processes, and equipment work together. While machine automation is eliminating many jobs, many of these machines still involve workers tied into other processes and performance dependencies beyond the machines themselves. Whether a machine stops as a result of a mechanical failure or, due to a related employee or environmental safety incident, the result is the same for a company- lost productivity and added cost. The same applies when that same equipment is subject to local operating permits for reporting air emissions or Wastewater. Failure to comply with operating permits could result in a company losing its license to operate, and if not managed efficiently, the permits process can be quite costly to administer for these businesses.  Not fully capturing, analyzing and managing risk and performance dependencies between machines, people, and processes, place a company's operations at risk and increases operating costs. When most catastrophic failures occur, it is when multiple and seemingly unrelated factors and processes fail together.

Moreover, as we move forward, a large part of a company's future asset performance management strategy must be tied to the recruitment, training and retention of its workforce. Manufacturers face two significant challenges impacting its future operations- a knowledgeable workforce leaving the market and the need for a new generation of workers and skills sets required to run the digitize manufacturing operations of the future. How well a company can balance these two shifting market dynamics will ultimately impact the success of its future operations.

Deliver complete, accurate, timely information to APM workflows

While the term Integration often is overused, what separates genuinely integrated solutions from other non-integrated reporting based solutions, is the ability to trigger a meaningful workflow.

In the prior example, let' suppose that an accident had occurred, which resulted in damage to the equipment and an employee injury.

From a required workflow perspective, new actions need to occur to document and correct that occurrence.

• The incident and factors leading up to that incident need capturing.
• All the associated financial costs involving the people and impacted equipment need to be documented and updated.
• Dependent on the severity of the incident, OSHA incident reports would need to be created and filed.
• An equipment lock tag is required, and new maintenance requests need to execute for repairing the equipment.
• The maintenance work needs to be scheduled, and the maintenance repair and safety instruction provided for fixing that piece of equipment.
• Spare parts may be required, and inventory needs checking and potentially updated.
• Companies might not have the right technician skills in-house to repair the equipment so they may have to look outside the company for contract labor.

        Etc., etc.

Supported by predefined business rules and integrated digitized systems between maintenance, finance, HR, procurement and EH&S related processes, the required workflow can be triggered automatically. In the absence, of having this integration, these APM related procedures would need to be separately managed, which increases operating costs and risk of non-compliance with company operating policies and regulatory reporting requirements. Well-defined end to end processes supported by digitized, integrated systems, reduces operating costs and improves APM joint business collaboration within and outside the company.

Seamless sharing of information across all APM stakeholders, internal or external to the organization 

The part of the statement above, I will focus on, is related to sharing information "external to the organization."  In the digital economy, companies must think and operate more broadly. Business processes including APM, are increasingly becoming intertwined with an organization's Business Ecosystem. Companies must learn to manage their business as part of a larger network, and APM is no different.  Being able to operate successfully and leverage a company's entire Business Ecosystem is why having a digitized operating core is so critical. A digital operating system empowers companies to create the right kinds of connection points that seamlessly integrate internal and external stakeholders, supporting APM processes, across an enterprise's entire extended supply chain.

While improved machine intelligence, Big Data, and the IIoT are very positive developments for PdM operations, PdM by itself, can't sufficiently address other non-machine related risk and performance interdependencies, required for overall APM success.

I invite you to learn how SAP customers are better managing APM performance and EH&S risk more holistically and efficiently, during these upcoming conferences:

• SAP EAM-Centric
• TA Cook EHS Conference
• Chemical Best Practice Conference

We look forward to meeting with you and helping you on your digital journey.

Warmest regards,

Harry Blunt

Marketing Director, N.A. Extended Supply Chain Program Lead

Do you have ideas on how SAP can add improvements to Plant Maintenance transactions?

Login with your S-user account and make your request or vote on other peoples request.

https://influence.sap.com/EAMPMPRM

EAM solution helps organizations efficiently and sustainably manage the whole lifecycle of physical assets. Tools for managing production equipment, roads, machinery, vehicles, facilities, and power grids can help them reduce operating costs, minimize risk, and manage capital expenditures more effectively.

In  the area of Enterprise Asset Management SAP just recently kicked off a new customer connection cycle on February 2nd.

The project workspace is now active for collection of improvement requirements until April 16th, 2016

Find more information and additional links here:

https://influence.sap.com/ct/ct_a_view_blog.bix?c=BDCE9FC5-DCD4-45B7-939A-31DC30A49673&bID=916FFD27-3DA7-4D04-8CF3-4D9F13628A54

Dear Friends,

As the title indicates this is about Checks while creating Measuring Documents and hence about a user-exit namely the very useful IMRC0004 . I felt an immediate need to record and preserve the solutions for various types of checks discussed so far, because it has been realized today that 3 times in last half year, I started by suggesting solutions through user-exit IMRC0001 for these queries and corrected myself in the end by giving final solution through IMRC0004. Also, being such an useful exit, this IMRC0004 is very less talked about exit.

Now few lines about the difference in using the above referred two exits for these checks.

IMRC0001

I always remembered this exit as the one which triggers at the Saving of a MPt or MDoc as the description starts so. 'MeasPoint/MeasDoc: Exit before update (after COMMIT WORK)'. All such requirements about checks while creating Measuring documents, look work well with this exit but there is an issue caused by this part of the exit description i.e, 'after COMMIT WORK'. 

What happens is, our code successfully prevents the MDoc from getting saved if the conditions are not met, but it interrupts the COMMIT WORK. So after preventing the MDoc when the system takes us to IK11 initial screen, if we continue by hitting Enter or by clicking on Back key etc, it would result in a short dump, because the code interrupted the COMMIT WORK.  (We can avoid this short dump by coming out of the screen by using some tcode in the command bar).

So that is a clear limitation for using this exit for such purposes.

IMRC0004

The description here says: 'Measure.doc.:Exit according to stndrd checks for new mes.doc' . So far this description failed to trigger in my mind at right time in using for MDoc checks. But not here onwards because this event of blog creation will have its punch in the mind and would not let me forget again.

The basic difference in triggering of these exits is, the former triggers at the time of Saving the MDoc and the later namely our subject exit, triggers instantly at the time of entering values in the IK11 screen.

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

Now, I am listing below some typical requirements of Checks while creating MDocs and the Codes to be written in the include ZXMRCU04 of the exit IMRC0004 .

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

Case1

To prevent users from entering readings in the 'Counter reading' field of the Measuring document (of a counter obviously).

The code

As mentioned earlier all these codes being discussed are needed to be put in include ZXMRCU04.

IF sy-tcode = 'IK11' AND impt_data-indct = 'X' AND imrg_ins-idiff IS INITIAL.
   MESSAGE: 'Reading in ''Counter reading'' field is not allowed. Please enter your reading in the ''Difference'' field.' TYPE 'E'.
ENDIF.

This code first checks whether the tcode is IK11, then checks whether the Measuring document is for a Counter and then checks whether the field Counter reading entered as difference(IDIFF) is empty. If this field is empty, then it understands that the Reading is entered in the Counter reading field and throws the following error in the status bar of IK11 screen.

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

Case2

To prevent users from entering readings in the 'Difference' field of the Measuring document for 'M' category of the MPts.

The code

IF sy-tcode = 'IK11' AND impt_data-mptyp = 'M' AND impt_data-indct = 'X' AND imrg_ins-idiff IS NOTINITIAL.

    MESSAGE: 'Reading in ''Difference'' field is not allowed. Please enter your reading in the ''Counter reading'' field.' TYPE 'E'.

  ENDIF.

This throws an error in the status bar the moment someone enters a reading in the Difference field and hits Enter (for 'M' category of measuring points)

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

Case3

To prevent creating of a MDoc of a particular MPt, in case the difference between previous reading and current reading is more than a value say 20,000.

The code

DATA: l_readg TYPE imrg-readg,
           l_point TYPE imrg-point,
           l_prvrdg TYPE imrg-readg,
           l_diff TYPE imrg-readg.

     CLEAR: l_readg, l_point, l_prvrdg, l_diff."wains

     l_point = imrg_ins-point.
     l_readg = imrg_ins-readg * 1000.

     SELECT SINGLE readg FROM imrg INTO l_prvrdg WHERE point = imrg_ins-point.
     l_diff = l_readg - l_prvrdg.

     IF l_diff < 0.
       l_diff = - l_diff.
     ENDIF.

     IF l_point = '000000000500' AND l_diff > '20000'.
       MESSAGE: 'The difference between consecutive readings is more than ''20000''' TYPE 'E'DISPLAY LIKE 'I'.
     ENDIF.

This throws the following error popup

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

Case4

To restrict users from entering values below or above certain limit if particular ValCode is chosen.

The code

IF imrg_ins-codgr = 'DEDR' AND imrg_ins-vlcod = '0010' AND imrg_ins-cancl <> 'X'.

   IF imrg_ins-readg < 3.

     MESSAGE: 'Incorrect Reading, For the selected ValCode reading can not be less than ''3''' TYPE 'E'.

   ENDIF.

ENDIF.

Here is the IK11 screen with the values and the error in the status bar.

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

Case5

To prevent users from entering same Counter reading as the last MDoc.

The code

IF impt_data-indct = 'X' AND imrg_ins-cancl <> 'X'.

   DATA: old_readg TYPE imrg-cntrr.

   SELECT SINGLE MAX( cntrr ) FROM imrg INTO old_readg WHERE point = impt_data-point.

   IF imrg_ins-cntrr = old_readg.

     MESSAGE: 'Counter reading equal to previous reading not accepted' TYPE 'E'.

   ENDIF.

ENDIF.

In this case system throws this Standard warning message first in the status bar:

Upon continuing by pressing Enter key, an error triggers in the status bar preventing MDoc creation, which is as a result of above code.

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

So, like these there can be many cases. But the different  code samples discussed here, have the potential to address all such requirements by suitably using.

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

Notes

• User-exits are very effective and convenient means of having checks, by having little knowledge about ABAP syntax.
  
• As the author always reminds, any user-exit functions only when it is assigned to a Project created through CMOD.
• If you are not a Technical person take help of an ABAPer and test well before transporting to target Client.

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

Hope the forum especially EAM space will be benefited through this knowledge sharing.

Author's other posts

Thank you.

KJogeswaraRao

User experience is one of the main challenge most companies face to improve adoption of SAP EAM by maintenance technicians. Award wining Fiori concepts could help in crossing this hurdles. (Refer this link to know more about Red Dot Design Award  http://news.sap.com/sap-fiori-2-0/)

SAP is now offering a training course to learn these concepts so that you can quickly implement these new concept in your organization. Above all it is free training and does not need any technical background. Most people who are participating in EAM SCN space are able to participate in this community based learning and stand a chance to win an iPAD. For more information please have look at link given below.

https://open.sap.com/courses/fiux2

Regards

Hemant

In a very short time we have received 150 improvement request for our customer connection project for SAP PM.

Details of some of these requests would be discussed by originator of the request during speaker’s corner sessions.

Register and join first speaker corner session to know more about the request so that you can subscribe for request that are relevant for you.

Link to register this event is given below..

https://influence.sap.com/ct/ct_a_view_blog.bix?c=BDCE9FC5-DCD4-45B7-939A-31DC30A49673&bID=A50992E3-6FC2-4E30-9649-73842A8F467B

Regards

Hemant

Reporting is one the important features in SAP. SAP has built lot of standard reports in order to solve the basic benefits of the customers to avoid custom developments.

In reality due to complex business processes we tend to build custom reports for customers but in case of any issues, we tend to compare the standard SAP report with custom build report, to confirm whether the values are populated correctly from the tables or there are any selection issues and list goes on.

In this blog, I would like to share a special transaction provided by SAP to identify the list of Standard Reports available for each module.

Are you aware SAP has provided a transaction SAP1? If no, then below is for your information.

Whenever we login into SAP, SAP Easy Access or User Menu will be displayed. To check the reports first we should know the transaction or navigate the structure in the respective module.

Now Go to Transaction SAP1 in transaction code area and Press Enter

It opens a screen SAP Easy Access – Report Selection

If we drill down Plant Maintenance – Management of Technical Objects

This will list out the transaction based on Technical Objects.

As an additional example, if we want to see PR / PO reports available in MM Structure.

Drilling down Materials Management – Purchasing – Purchase Requisition / Purchase Order

To return back to SAP Easy Access Menu, Click the highlighted below

Similarly, you will be able to get all reporting transactions in one place. This transaction will reduce the dependency towards other module consultant or raising SCN thread to identify reports.

More you explore,

More you learn &

More you will use SAP

The SAP-Centric EAM Conference is North America’s most comprehensive event designed specifically for the SAP enterprise asset management (EAM) community.

Join us in Denver on March 7–10 to learn how the SAP extended supply chain portfolio incorporating enabling technologies like the cloud, business networks, and the Internet of Things, are delivering unprecedented value for EAM professionals.

Don’t miss this unique opportunity to:

• Hear case studies from multiple SAP customers as they discuss how they leverage SAP software and the SAP ecosystem to improve EAM performance using predictive analytics, the SAP HANA platform, and IoT
• Gain insight on the SAP vision for IoT, predictive maintenance, and analytics
• Discover how the SAP Asset Intelligence Network will revolutionize asset management with global collaboration
• Find out how to make unplanned asset downtime a thing of the past with the SAP Predictive Maintenance and Service solution
• Discover how to enrich asset management business processes through SAP HANA and geospatial systems

Continue the conversation and meet with SAP experts at our demo kiosks and see how SAP solutions are improving EAM performance for:

• Multi-resource scheduling
• IoT and cloud predictive maintenance and services
• Operational integrity with integrated asset, process, and environmental health and safety risk protection

The complete agenda can be found here.

We are looking forward to seeing you there!

The SAP Asset Data Quality rapid-deployment solution has now been merged with theSAP Information Steward rapid-deployment solution V3.420 which apart from the EAM (SAP PM) master data objects, covers materials, supplier and customer master data.

The solution gives customers the ability to assess, validate and continuously monitor the quality of their asset master data, with information visualization and governance capability. With SAP's industry-leading data quality management tool Information Steward, and predefined content, this solution lays a solid foundation for a comprehensive Enterprise Asset Management (EAM) solution.

The scope of the solution includes processes for creating or changing business and validation rules, identifying corresponding data quality issues, and ongoing analysis of historical data with continuous insight for SAP ERP.

Key domains include:

• Functional location
• Equipment
• BOM
• Maintenance plan
• Task List
• Catalog Profile

Business Benefits

• Identify issues with data completeness, accuracy, integrity etc.
• Reduce data maintenance costs, ensure cross-system data consistency, accelerate the execution of business processes, and greatly improve decision-making
• Reduce safety and compliance incidents
• Improve efficiency in spare parts management
• Consolidate and harmonize master data within heterogeneous IT landscapes

Access the SAP Information Steward rapid-deployment solution from the SAP Service Marketplace.