/PACG/ECM_ACTGS - Act. Codes - General Settings
- proaxia
Learn more about Activity Feedback codes: Based on SAP Catalog Codes.
No group | Transfer only activity feedback codes (without the related code groups) to SAP FSM. This feature can be used to reduce the number of clicks needed to create Feedback - if code groups contain only 1 code or are in general not useful for technicians. |
|---|---|
New entry | Activity feedback will always create new entries in notification’s items instead of overwriting the existing ones.
Example 1 - disabled 
Service order’s notification before activity feedback posting:
Notice that there is one existing item with a cause and one existing task.
Service order’s notification after activity feedback posting:
Notice that the existing item and its cause is overwritten by the new one from Activity Feedback. The task is not overwritten.
Example 2 - enabled
Service order’s notification before activity feedback posting:
Notice that there is one existing item with a cause and one existing task.
Service order’s notification after activity feedback posting:
Notice that the existing item and its cause is not overwritten by the new one from Activity Feedback. There are two items, each with one cause, as well as two tasks. |
No group
When recording Activity Feedback codes, code groups are not displayed and the number of clicks made by technicians is reduced.
Make sure to check the ‘No group’ field for a relevant company in transaction /PACG/ECM_ACTGS - Act. Codes - General Settings.
Navigate to the sending transaction - /PACG/ECM_TRIG_SERCD - Activity Codes from SAP Inspection Catalog Codes. Enter the names of relevant code groups and execute.
Notice that only activity codes are sent (without corresponding code groups).
The outbound idocs of type /PACG/ECM_IS_ITYPE_SRERRCOD do not contain the ‘PARENT’ field.
Navigate to the SAP FSM mobile app and create Feedback for a relevant activity (the activity’s service call should be connected to a service notification).
Notice that codes are displayed right away and groups are not found.
The final feedback code also contains only codes.
Save the app and synchronize. Notice that the inbound /PACG/ECM_ITYPE_ACTFEED_IN idoc contains only code segments, without groups.
Navigate to the service order’s notification and observe that tasks and causes were added correctly, based on customizing in transaction /PACG/ECM_SERFP - Level Nr Properties.
Prerequisites
Make sure to customize code groups relevant for transfer to SAP FSM in transaction /PACG/ECM_SERCD - Code Groups.
For each feedback level specify which notification field should be created. This can be done in transaction /PACG/ECM_SERFP - Level Nr Properties.
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.