Catalogs and Codes in SAP PM

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 1

Data on problems, malfunctions, damages, causes and problem solutions or malfunction corrections

is recorded in the system or reported to the planner responsible in the form of technical findings
after a visual check, after the object has been inspected or checked, or the problem has been
determined. This data forms part of the service or maintenance notification and is entered in the
maintenance history.
Catalog profile will group different characteristics of the notification which will cater the needs of
management to analyse the company assets & to ascertain the decisions accordingly. Catalog
profiles have sub class of code groups which will group the codes as per their feature.
All the codes (Damage, Cause, Task & Activities) illustrate why an asset failed during production,
what is the cause for that failure, tasks to be performed & activities done for that failure. The use of
codes in a SAP system ensures a consistent way of documenting the key aspects of the damage,
cause, etc., event according to pre-defined categories. Some examples include:

 Breakage
 Corrosion
 Imbalance
 Misalignment
 Overheating
 Vibration

Why are they used?


Catalog Profile are used in SAP which enables subsequent analysis possible, which leads to net
improved system availability. For example, the number of times an instance of a particular failure
code occurs, divided by the total operating age of the equipment, approximates the failure rate. For
maintenance organizations that don’t use failure codes, determining any sort of failure trend is a
labor-intensive process of searching through work orders and making several educated guesses.

Why should you use them?


Knowing the failure rate for a failure code

You might also like