-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 1/11
Getting Started Newsletters Store
Products Services & Support About SCN Downloads
Industries Training & Education Partnership Developer
Center
Lines of Business University Alliances Events & Webinars
Innovation
Log On Join UsHi, Guest Search the Community
Activity Communications Actions
Browse
2 Tweet 1
created by Maheswaran KD . on Jul 1, 2012 3:34 PM, last modified
by Maheswaran KD . on Jul 1, 2012 5:45 PM
Introduction Data on problems, malfunctions, damages, causes and
problem solutions or malfunction corrections is recorded in
thesystem or reported to the planner responsible in the form of
technical findings after a visual check, after the object hasbeen
inspected or checked, or the problem has been determined. This data
forms part of the service or maintenancenotification and is entered
in the maintenance history. Catalog profile will group different
characteristics of the notification which will cater the needs of
management toanalyse the company assets & to ascertain the
decisions accordingly. Catalog profiles have sub class of code
groupswhich 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 forthat failure,
tasks to be performed & activities done for that failure. The
use of codes in a SAP system ensures aconsistent 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 systemavailability.
For example, the number of times an instance of a particular
failure code occurs, divided by the totaloperating age of the
equipment, approximates the failure rate. For maintenance
organizations that dont use failurecodes, determining any sort of
failure trend is a labor-intensive process of searching through
work orders and makingseveral educated guesses. Why should you use
them?
Catalog Profile
Share 7 5Like
Version 1
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 2/11
Knowing the failure rate for a failure code can help in doing
the following:
Optimize PM intervals
Improve failure response
Improve work practices
The consistent use of the failure codes / cause codes provides a
convenient method of getting statistics about equipmentfailures or
breakdowns. They aid your ability to effectively identify trends
and problems. Lets say that there are similarkinds of machines. A
report could be run for a period of time and, by selecting a
failure code / cause code / object partcode, determine how many
times the failure occurs / cause creates a damage / object part
where damage happens on anindividual system. You can then compare
this data across the entire fleet. If the failure rate / cause rate
is above average,it may be worthwhile proactively replacing parts
or shortening the PM interval. Who should input the codes?
Ideally, it is best to have the data entered correctly closer to
the event by those who investigated and corrected thefailure /
found the cause and / or object part. In most cases, this is the
technician that responds to the failure / rectifiesthe cause to
correct the failure. How many should you have?
These codes should provide an easy way to quickly analyze
equipment failures, problems, causes and faults. Withoutdoubt,
effective and accurate code lists are required for identifying
trends but deciding what selection choices to placeon such pick
lists is no trivial matter. Too few and they would not support the
level of data analysis desired or the datawill be meaningless.
Equally if there are too many options, technicians tend to suffer
from choice overload and thedefault will become either the
Miscellaneous or Other option, which will again render the data
meaningless. Ideally,you should aim for 20-30 codes under each
heading The Catalog will be consisting of different details like
damages, causes, tasks, object parts, activities, etc., Based on
theequipment type, catalogs will be created. According to the
equipment type, these damages, causes, object parts,
tasks,activities, etc., will be defined & assigned to catalog.
Subsequently, this catalog will be assigned to catalog profile, so
that different catalogs will be grouped & it can beassigned to
equipment. Definition of Code Groups & Codes Definition of code
groups & codes in SAP are very much important to build the
common ERP system among differentcategory of people, among
different skills ofpeople. In the general business practice,
different catalog types will be used on regular basis. Each company
will havetheir own standards to define the catalog types. Each
company will have their own standard in naming those catalogtypes.
As the names of these catalog types are different within company
across different locations, it will becomecumbersome process to
group the categories. To overcome that, many quality standards
institutions like ISO, CMMS, etc., have suggested the catalog types
for each &every equipment types. Code groups & codes should
be defined with global naming convention with some
standardtechnique so that it can be used by the company across
locations. CMMS hassuggested some naming convention standards for
coding the Failures, Damages, etc., Failure Codes as per CMMS
Standards:
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 3/11
Note: The complete list of Failure & other catalogs codes
are available in CMMS websites. By defining the Catalog codes as
per some standards, these codes can be used & can be recognised
by different categoryof people & different level of people.
This will make the common SAP system across the locations of the
company. Nowin ERP system, similar kind of catalogs can be grouped
easily for the management analysis purpose. Creation of Catalog
Profiles in SAP
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 4/11
Step 2: Define Catalog code groups & codes
Here against each catalog (Damage, Cause, etc.,), code groups
will be given to group those codes. This code groupnaming
convention will follow the naming convention of Equipment object
types. For example, for FIREEXTING FireExtinguishers, code group
can be defined as FIREEXTN.
The status of the code groups should be as Released if the same
can be used for assigning to catalog profile. If the codegroups are
yet to be approved, the status can be as Being created.
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 5/11
Likewise, for all the equipment types, all the catalog types
(Damage, Cause, Task, Object Part, Activities, etc.,) should
bedefined & against those catalog types, code groups &
codes should be created. Step 3: Creation of Catalog Profile: After
creating Catalog code groups & codes for those catalog groups,
catalog profile will be created according to objecttype of
equipment.
For catalog profile, the equipment object types naming
convention can be used as the naming convention.
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 6/11
As shown in above 2 figures, catalog profile will be created (as
shown in fig1) & different catalogs will be assigned (fig2). As
the catalog for damages & causes, other catalogs like tasks,
activities, object parts, etc., can be grouped under thecatalog
profile. Assignment of Catalog Profile All the created Catalog
Profiles will be assigned either to Notification types or in
Equipment Masters. Catalog Profile Assignment to Notification Type
All the catalogs will be assigned to notification type to identify
the exact catalog types against each heading likeProblems, Causes,
Tasks, Activities, Object Parts, etc.,
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 7/11
Generally catalog profile should not be assigned to notification
types. As notification is common across different typesof
equipments & common across the company, assigning catalog
profile to notification type will make the processcumbersome i.e.,
the list will be large to select from the long list. So catalog
profile assignment to equipment isrecommended here. All the
catalogs will be assigned against each heading to refer the
specific (if customized) catalog types which havedefined &
created in Catalog creation. Assignment of Catalog Profile to
Equipments: The Catalog Profiles can also be assigned to equipment
master. As per the Equipment Object Type, catalog profiles havebeen
created. In the equipment master,according to Object type of
equipment, catalog profile should be selected.
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 8/11
Application of Catalog Profile in Notifications Based on the
assignment of catalog profile either to notification type or
equipment, the catalogs & corresponding codescan be utilized in
the notification. These catalogs will be used in the management
analysis part.
Apart from mentioning the catalogs in Notification header, if
more than one object part or damage happened or morethan one cause
for the damage, based on notification screen view template,
multiple catalogs can be assigned innotification.
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 9/11
Average User Rating
(9 ratings)
2 Tweet 1
Who should develop them?
These codes should be easily available and understandable to the
people who request work, to themaintenance personnel that complete
the work and to the engineers who want to get the data they need
tounderstand what is occurring in the field. Fault coding
development really requires an integrated approachwith these 3
groups, especially if there is a desire to do some sort of wide
ranging analysis. Ultimately, thecodes have to allow the field
personnel a relatively painless way to provide the information that
theengineers need. Unless that occurs, the end product will not be
used.
Benefits of Catalog Profile General Usage:
1. Different management analysis report is available2. Object
part wise, Defect wise, Cause wise notifications can be listed.3.
By mentioning the catalogs in notification, maintenance department
person can understand the malfunction
quickly.
4. It will make the PM process more transparent.
Important Transactions for Analysis:
1. MCI5 Damage Analysis (Based on Damage, Cause & Activity,
analysis can be done by listing no. of notifications)2. IW69 List
of Items with Damages, Causes & other catalog details3. IW65
List of Activities with Damages, Causes & other catalog
details4. IW67 List of Tasks done for the Damages
Conclusion
In general, proper catalog profile with catalog codes for the
purpose of analysis. Analysis, in turn, providesknowledge of
equipment behavior patterns with respect to other external and
internal factors such asworking age, PM frequency, EHM parameters
and decision models etc. We can then use this knowledgeto improve
system availability and ultimately, the companys bottom line.
9781 Views Topics: enterprise_asset_management Tags: catalogs,
catalog_profile
Share 7 5Like
12 Comments
Like (1)
James Prabaharan Nov 22, 2012 10:09 AM
Dear Maheswaran,This is an excellent overview on
Catalog.Thanks,James Prabaharan
Like (0)
Dipak Joshi Nov 28, 2012 11:48 AM
Good One.. Rgds,
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 10/11
Like (0)
Ajaya Sahu Feb 6, 2013 6:47 AM
Dear Maheswaran, Very good document, great ! Thanks,Sahu
Like (0)
naga suribabu Feb 19, 2013 7:58 AM
Dear Maheswaran, Very good document, great ! Thanks, Suri
babu
Like (0)
Rahul Gujarathi May 31, 2013 2:52 PM
Very Helpful Document. Thank You.
Like (0)
Minhaj Ahmed Jul 16, 2013 11:19 AM
Very much helpful and plz keep posting these type of
documents
Like (0)
Lingaraj Pattajoshi Oct 22, 2013 9:25 AM
very good documentthank you...:)
Like (0)
Lori Abney Oct 29, 2013 5:11 PM
Can anyone explain the logic of how catalog object parts are
displayed in the notification if theEquipment Catalog profile does
not match the Object Parts? I am seeing some very strange
things.Thanks.
Like (0)
Maheswaran KD . Oct 29, 2013 5:17 PM (in response to Lori
Abney)
Check the following points.
Generally, equipment catalog profile will have preference than
the notification type catalogprofile. Sometimes, catalog profile
might be changed in notification.
1. In notification, Assigned technical object is having catalog
profile or not.2. If the notification equipment is having catalog
profile, check the object parts assigned
to that catalog profile3. Check the catalog profile assigned to
notification4. Check the catalog profile assigned to notification
type in configuration
Like (0)
Lori Abney Oct 29, 2013 5:22 PM (in response to Maheswaran KD
.)
Here is my exact scenarioFunctional Location has PM Catalog of
PMVEHICLE, there is not matching ObjectCode of PMVEHICLE. When I
create notification with the functional location, dropdown for
object parts gives me PMENGINE. Default for notificaiton type
isPMGENERAL
Maheswaran KD . Oct 29, 2013 5:27 PM (in response to Lori
Abney)
You attach following screen shots.
1. Notification reference object2. Notification Catalog profile
(you can get it from menu)3. Reference object(s) catalog profile
assignment in its master data
-
11/12/2014 Catalog Profile | SCN
http://scn.sap.com/docs/DOC-29637 11/11
Follow SCNSite Index Contact Us SAP Help PortalPrivacy Terms of
Use Legal Disclosure Copyright
Like (0)
Like (0)
saifudin hajar Oct 9, 2014 9:08 AM
very helpfulthank's gurus,,