Skip to Content
Product Information
Author's profile photo Anika Roeder

End-of-Use Date for Equipments and Functional Locations

Within equipments and functional locations, you have the possibility to define a start-up date as the date on which the corresponding technical object came into operation. To make planning with technical objects easier, we have implemented a solution which allows you to also define an end-of-use date for equipments and functional locations as the planned date when the corresponding technical object will end its operation.

End-of-Use%20Date%20within%20Equipments

End-of-Use Date within Equipments

End-of-Use%20Date%20within%20Functional%20Locations

End-of-Use Date within Functional Locations

You will find this new field also in the corresponding list transactions such as IE05, IL05, IH06 and IH08 as selection parameters and in the output list as well as in the output lists of transactions IL07, IE07, IE36 and IE37.

If you use such an equipment or functional location within an order or notification, and the end-of-use date is before the start date of the object, you receive a message. The message type (e.g. warning, info, error) is customizable.

The new functionality is now available with SAP Note 3039736, or with the SAP enhancement package 8 for SAP ERP as well as for SAP S/4HANA 1909 and 2020. You can enable the new functionality by implementing either the SAP Note or the corresponding support packages and switching on the Enterprise Asset Management Part 16 and Simplified Management of EAM Functions 17 business functions for the classical user interface and for the SAP Web UI for Plant Maintenance respectively. To find out more, refer to the linked SAP Note.

We’d love to hear your thoughts on the new functionality, so please comment if you have any questions!

To receive updates about future improvements, follow this blog post.

Assigned tags

      10 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Nic Teunckens
      Nic Teunckens

      Hello Anika Roeder

      Thank you for the useful glimpse these BlogPosts offer with regards to new innovations in EAM.
      Sadly, I do not always see the SAP-Documentation (SAP-Help) moving along with the same speed.

      For instance, this functionality is not updated in the EhP8 or EAM-related pages on the SAP-Help website yet. This is a bit unfortunate, as I would be enthousiastic to get some more information on the "ins and outs" for a specific Functionality from the moment the Blog is released.

      Now I am left with questions that are left unanswered because the SAP-Notes do not offer much assistance on the functional scope ...

      A question I have for this function, is, whether the "Start-Up" and "End-of-Use" dates can repeatedly be modified (made longer or shorter). Such behaviour would fit with requirements such as offering a "window of availablity" of an Asset that can be altered in a Flexible way. Think of the following : Upon (Re-)Certification of the Asset, the "End-of-Use" Date could be modified repeatedly, I would assume?

      All this aside, it is great to see the continuous innovation in the EAM area. And to me, these Blogs are very useful, so keep'em coming!

      Kind regards

      Nic T.

      Author's profile photo Anika Roeder
      Anika Roeder
      Blog Post Author

      Hi Nic Teunckens ,

      thank you very much for your feedback. The documentation/sap help is in progress and will be shipped with the next SP. Within the notes it is not possible to change the documentation. Sorry for this inconvenience.

      Regarding your question. Yes, it is possible to change these dates several times. This is also one of the reasons why maintenance plans/scheduling of maintenance plans are not touched through this development. These dates are only checked while creating/changing maintenance orders or notifications and can be used in all list transactions for your overview.

      Hope this information helps you.

      Best regards,

      Anika

      Author's profile photo Nic Teunckens
      Nic Teunckens

      Thank you for the reply, Anika.

      And yes, your answer to my question is as I expected, yet I appreciate your clarification in the meantime. This can help us by determining whether it is useful to investigate this Function in the future.

      Kind regards

      Nic T.

      Author's profile photo Vignesh Veerasamy
      Vignesh Veerasamy

      Hi Anika Roeder

      Simple and clear document.

      One question.

      For an equipment you have valid from - valid to date ?

      When start up date vs end of use date is used ? how system shall equate this ? so I will not be able to use the Equipment if it is exceeding the valid to date?

      Vignesh V

      Author's profile photo Anika Roeder
      Anika Roeder
      Blog Post Author

      Hi Vignesh Veerasamy,

      the start-up date was available before this new development. With this development the end-of-use date was introduced for equipments and functional locations. If you use this field within the technical object and enter such a technical object in an order or notification the end-of-use date field is checked against the basic start date of the order or notification. If the end-of-use date is before the start date and so the technical object seems to be unvalid a message (IW448) could be raised. This message type is customizable and you can decide if it should be an error or warning or if you don´t want to have a message at all.

      Hope this information helps you.

      Best regards,

      Anika

      Author's profile photo Prasad Shanware
      Prasad Shanware

      Hello Anika,

      I have small query.

      Could you please help me on below :-

      When excatly we can use this End of use date?

      As Start up date will be involve in calculating the MTBR and MTBF.

      How can we define end of use date here

      Could you please explain more detail

      Author's profile photo Anika Roeder
      Anika Roeder
      Blog Post Author

      Hello Prasad Shanware

      thanks for your comment. The end-of-use date is just an informal date field within the technical objects (equipment and functional location). It is checked within the notification and order creation and if you wants to, a message is raised accordingly. This message type is customizable as described in the blog post. But thats it. Besides of that it has no effect on any other object or calculation.

      I regret not beeing able to give you another answer, but I hope I could clarify the situation.

      Thanks and regards,

      Anika

      Author's profile photo Pardhasaradhi Reddy Chelikam
      Pardhasaradhi Reddy Chelikam

      Dear Anika Roeder ,

      Thank you for sharing key insights...I think, this new field will really help maintenance planner/gate keeper to avoid unwanted transactions against certain technical objects...

      To the best of my knowledge, currently we do not have "Valid From Date" & "Valid To Date" for a functional location master  and by definition which is understood for not having it at FL...I was wondering, how does it make a difference for on going maintenance transactions against functional locations where we do not see valid from/to date?...

      In fact, currently, we have "valid from date and valid to date" to identify the service timeline/history against  each equipment under respective location/plant section and functional location as well, this can be achieved using standard report...also, I just wanted to understand that, was there any key consideration happened to have this field?...In fact, so as in general procedure, users usually assign the user status  as "Not In Operation" whenever equipment undergoes for a major overhaul/repair etc. so that the planner can skip them  based on assigned user status...

      I was wondering , whether SAP has any plans to provide MTTF statistics for each "Model" of technical object by considering this field data?...just in case, If I update this field value when the object loses its design life...

      My view: I am just thinking (Correct me If I am wrong...)

      If we had the provision to set the control to trigger error/warning message at respective master level during creation/update process, we could avoid the whole process to trigger error/warning message during notification/work order process, I guess...

      Also we have certain settings viz: OPU7 configuration, which enables creation of work order in back dates as part of regularization process when user do not get opportunity to update the transaction in SAP during emergencies, and by the time he gets back to SAP to regularize the transaction, the   "End-Of-Use Date" will definitely be  before the work order start date, it might occur sometimes for major breakdowns in remote locations...just thinking in that aspect...

      Also we have historical order process in place, will it impact the historical order function?...also I felt, there could be a slight impact on the Preventive Maintenance program too...

      For example,

      I have planed PM checks for a centrifugal pump and it`s End-Of-Use Date is mentioned as 31-12-2021, as I have upgraded the system now with new functionality and provided the dates...the pump maintenance plan has had 1M/3M/6M/1Y/2Y strategy with 80% call horizon and 365 Days as scheduling period and the 2Y frequency falls on March 16th 2022...so as per the functionality of End-Of-Use Date system should trigger an error/warning and should not let the order create as It start date falls after the End-Of-Use Date...so, In this scenario, shall we have to modify the End-Of-Use dates of technical objects or Maintenance plans?...even for the calibration the process Is same, instead the system is configured such a way that calibration work order is being created and released so as to generate Inspection lot...is there any kind of report that has come along with this function to know "Due Package dates" Vs "End-Of-Use Date" of the technical objects...so that planners can take necessary action...

      It would be a great help if you could throw some light on these key factors...once again thank you! and appreciate your time and support!

      --

      Regards,

      Pardha Reddy.C

      Author's profile photo Anika Roeder
      Anika Roeder
      Blog Post Author

      Dear Pardhasaradhi Reddy Chelikam,

      thanks for your comment. I´ll try to answer all your questions as detailed as possible. The end-of-use date is just an informal date field within the technical objects (equipment and functional location). It is checked within the notification and order creation and if you wants to, a message is raised accordingly. This message type is customizable as described in the blog post. But thats it. Besides of that it has no effect on any other object or calculation. So the maintenance planning as you described is not affected. Also in case the order is created from a maintenance plan. Same for historical orders.

      Also there are no further plans regarding these field. This field was developed to have the possibility to enter a "end date" to the technical object. For reporting reasons. Therefore these field can be used also in the list transactions for any reporting. All list transactions where adapted as well (see blog post for details). Besides of that we check this field while order or notification creation against start date of the object.

      In case of order creation is back dated then the technical object end of use date shouldn´t be before that. Otherwise you will receive the message (message type is customizable) as described.

      I regret not beeing able to give you another answer, but I hope I could clarify the situation.

      Thanks and regards,

      Anika

      Author's profile photo Pardhasaradhi Reddy Chelikam
      Pardhasaradhi Reddy Chelikam

      Dear Anika Roeder,

      Thank you for taking the time to explain my queries and I appreciate the briefing you provided...

       

      --

      Regards,

      Pardha Reddy.C