Condition Based Maintenance


In the course of an inspection, a system is seen to be in a condition that will require repair in the foreseeable future,  then these findings can be entered as a maintenance notification and passed on to the planning group responsible.

In SAP Plant Maintenance, we can implement a condition-based process where a requester will create a notification in SAP and prints the notification for approval. The engineering manager will then approves the maintenance request made. The maintenance planner will encode the all approved request and prepare for maintenance work order creation. The maintenance planner will now plan,schedule,release(also print) the maintenance work order for corrective maintenance. The technician(s)(mechanic or groups of mechanics) will now execute the job indicated in the maintenance work order form and his findings if any.After all the work is being done, the requester will acknowledge the repairs/work done by the technician. Then, the maintenance planner will encode all findings in SAP and performs the technical completion of the maintenance order(TECO). Finance department will run a periodic settlement in which it will post the proper charges to the cost center. After all items are being settled, they fill perform the business completion of the maintenance work order(BUCO) to close the maintenance work order.


If this article is helpful, a small donation to my wallet address will be appreciated:





In a company’s Production Server, a Maintenance Planner wants to add a new Catalog in SAP Plant Maintenance using the Transaction Code QS41. But the Maintenance Planner was not successful because it is in Display Mode:

ImageAnd when you try to check your Authorization using the transaction code SU53, the Authority Check failed even if the Authorization team already set it up in your SAP ID Profile.

ImageThe reason it failed because the Maintenance of selected sets specially in QS41 requires transport request. And in the Production System, All Configurations in SAP are CLOSED.

In order to solve this, we should apply the SAP Note 736920 to correct the problem.