Versions Compared

Key

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

The Transactions described in the chapter before can be used to control the process of handling of Activity Feedback using E4C Tables. In that case the tree of codes which is presented in the FSM mobile application is built based on the content of E4C configuration tables. When the Activity Feedback is sent back to SAP, the new Notification is created.
Alternatively Alternatively, the tree used by the Activity Feedback can be built based on the SAP Catalog Codes. Use the transaction QS43 (SAP Menu -> Logistics -> Customer Service -> Service Processing -> Environment -> Catalog -> Code Groups -> QS43 - Individual Maintenance) to maintain the Code Groups and the Codes belonging to these Code Groups:



Once the Codes are maintained using SAP Standard Configuration, they can be referenced by E4C configuration and eventually sent to the Cloud as a value set building the Activity Feedback tree.

/PACG/ECM_ACTLE - Activity Codes Level

The level of each Activity Code used.
Image Removed
Definition of which codes exist on which level.

/PACG/ECM_ACTCD - Activity Codes

...

/PACG/ECM_ACTCO - Activity Composed Code

Image Removed
Image Removed
You have to define the allowed combinations. You have to define a proper text which will be shown in the cloud.
Internal means: Will not be printed on Customer documents like Service report

/PACG/ECM_ACTF - Activity Code Feedback

Image Removed
Per Activity Feedback, one Notification will be created. This Notification is linked to the Equipment and shows the Feedback Code of the Activity Feedback. You have to define the Text type per Notification type. The Service number history shows all notifications… Using this table enables defining if the GPS coordinates will be saved or not.
Anchor_Toc430630387_Toc430630387 Anchor_Toc430630392_Toc430630392