Introduction:
Catalog is the customizing master data from Qulity Management (QM) application & in this blog I shall explain how the same is used in SAP Enterprise Asset Management application (henceforth it will be called as EAM) to describe the equipment’s problems through „code“ format (key that uniquely identifies the qualitative contents of a problem) in the „notification“.
Catalogs are created in the golden/customizing client & copied to other clients. It is used in various business processes of EAM to capture information related to maintenance history in the form of codes. Each code is assigned to a code group in the catalog. You can assign codes to different code groups. Catalog code and descriptions can be stored in a catalog.
There are many catalog codes delivered by SAP & we use only the following 5 catalog codes in the EAM application:
|
Sr.No. |
Business Description |
Catalog Codes |
SAP Description |
|
1 |
Problems/Failures |
C |
Damage Overview |
|
2 |
Causes of Damage |
5 |
Causes |
|
3 |
Tasks to be done |
2 |
Tasks |
|
4 |
Activities Completed |
A |
Activities (PM) |
|
5 |
Sub – parts |
B |
Object Parts |
Apart from these standard code groups, users are free to create own code groups as per their requirements in customizing client.
All the codes illustrate why an asset failed during production, what is the cause for that failure, tasks to be performed & activities done to overcome that failure. The use of codes in a SAP system ensures a consistent way of documenting the key aspects of the damage, cause, events etc. according to pre-defined categories. Few examples of „codes“ for „cause“ code-group are:
- Breakage
- Corrosion
- Imbalance
- Misalignment
- Overheating
- Vibration
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 multiple codes groups which will group/merge multiple codes as per their features. This is used for the damage analysis.
Transactions:
QS41 & 43: Maintain Catalog. Create new code groups & codes.
QS42: Display Catalog.
Working example:
Catalog codes are maintained in customizing – SPRO:
TA: S_ALR_87001010_1: Create own catalog & maintain the same. Catalog names 0 to 9 & A to O are used/assigned by SAP. You are free use catalog types P to Z.
Next step is to create code groups & codes under the catalog in TA: QS41 & maintain them. Example shown here is for catalog type „object parts“ (B).
Status of the code group should be „released“ to use.
Now, maintain the codes for the created code-groups.
In this example, we created catalog codes, code groups & codes only for the „object parts“ code-group. Similarly, create codes for all the code-groups of all the catalog-codes.
Next step is to assign the created catalog to catalog profile & in-turn assign the catalog profile will be assigned to „notification“ type so that these codes will be displayed in the notification screen (TA: IW21) only of that notification type.
Maintaining catalog profile is done in SPRO:
User can use the TA: OQN6 for the same.
Assign the catalog & its code-group to catalog profile.
Note that you can assign any code groups (which is assigned to other catalog’s also) & a catlog profile can have multiple catalog codes.
Assign this catalog profile to notification type (M1) in the SPRO:
Notification type can have only one notification profile.
Let’s see how it works while creating the notification (type M1).
Use TA: IW21 to create a notification with type M1.
You can see the values of F4 help of Object Part (catalog code = B): the one which we created in earlier steps & assigned (PM1 missed out) to catalogs profile will be displayed. The additional sub-screen „item“ section in the notification home screen & also the new tabs: „item“, „task“ & „activities“ can be added as shown in below.
To accommodate these (screen) changes in the notification screen, you need to change or add the new section in the customizing of notification type:
For the tab01, add new „item“ section. Include other new tabs for items, task & activities.
Kindly note that these catalogs & code groups can be assigned only to „notification“ in plant maintenance.
Reports
Earlier LIS reports: MCI5 & MCI7 are used to analyse the data w.r.t code-groups & codes. In SAP S/4 HANA, SAP recommends to use the SAP Fiori app „Technical Object Damages“ for the same.
Migration:
These catalogs can be migrated (migration object: S4_QM_CATALOG_CODE) to SAP S/4 HANA system using the BAPI: BAPI_QPGR_SAVEREPLICA. Required authorization object is Q_CAT_GRP.
from New blog articles in SAP Community https://ift.tt/6U3OW18