Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page Tree
rootBased on SAP Catalog Codes

Prerequisites

Object SRERRCODEACC should not exist in transaction /PACG/ECM_NOAS -No Object Assignment when this feedback approach is used.

...

Learn more about Activity Feedback Codes 

Technician can capture Feedback Codes to characterize defect, cause, activity, etc. This can be done on the mobile app, on activity level.

...


First a code group set for a specific level is selected, then one of this code group’s codes. After going through all the possible levels, a combined Activity Feedback Code is generated. It consists of all selected groups and codes. 

...

 

Saving this feedback triggers generation of an inbound /PACG/ECM_ITYPE_ACTFEED_IN idoc.

...

 

Depending on inbound configuration (transaction /PACG/ECM_SERFP - Level Nr Properties), a service notification will be updated with relevant items, causes, activities, etc. (using the code group and code data).

...

 

To create activity feedback codes, relevant code groups and codes should be transferred to SAP FSM beforehand. This should be maintained in transaction /PACG/ECM_SERCD - Code Groups.

...

 

For each company and level (1-5), one or more code groups can be defined. If two code groups are defined on level 1, a technician will be able to choose from one of these two code groups. If he chooses code group ZKAMTSK1, he will be then be able to choose from this code group’s codes. Then the code groups from level 2 will be displayed – the technician chooses one of the code groups and then one of the chosen code group’s codes. (And so on.)

...

 

If Level Nr configured varies from 1 to 5, then actually 10 levels of the tree in FSM mobile application will be used. Out of the below presented Configuration the user will choose in the FSM mobile application the following:

  1. Code Group from the groups ZKAMTSK* (KAM Task *)

  2. The codes belonging to the chosen group ZKAMTSK*

  3. Code Group from the given group ZKAMACT*

  4. The codes belonging to the chosen group ZKAMACT* (KAM Activity *)

  5. Code Group from the given group ZKAMIOP*

  6. The codes belonging to the chosen group ZKAMIOP* (KAM Item Object Parts *)

  7. Code Group from the given group ZKAMIDM*

  8. The codes belonging to the chosen group ZKAMIDM* (KAM Item Damage *)

  9. Code Group from the given group ZKAMCAU*

  10. The codes belonging to the chosen group ZKAMCAU* (KAM Cause *)

 

The code/code group solution is SAP standard. Codes of code groups are maintained in transaction QS41.  

...

 

These codes are retrieved during activity code transfer – based on catalog number and code group ID. Activity codes can be transferred to SAP FSM with transaction /PACG/ECM_TRIG_SERCD - Activity Codes from SAP Inspection Catalog Codes.

...

Feedback codes are transferred in idocs of type /PACG/ECM_ITYPE_SRERRCOD. Code groups’ IDs start with prefix ‘G’, followed by the catalog number and name of the code group.

...

Codes’ IDs start with prefix ‘C’, followed by the catalog number, code group name and finally code name. Codes are connected to code groups by the PARENT field.

...

In Query API code groups and codes can be found by selecting ActivityCode objects. 

...