User Exit ‘QQMA0014’, the applications
Author: Jogeswara Rao K
As the name of the user exit indicates, (Checks before saving a notification), this user exit when used, prevents user from saving a notification if the conditions specified in the code (written in include ZXQQMU20) are not satisfied.
Often users are forced to use this exit, due to a strange behaviour of Notification configuration.
That is: When configuring a notification type, the user marks few fields as ‘Required’ in the SPRO settings. While working on these notifications it is seen that such mandatory fields inside a tab other than ‘Header’ tab fail to force the user to fill them, if he does not enter the tab before saving.
Here this user exit comes to help:
An example code is given below to be written in the include (ZXQQMU20) of the exit.
This code prevents user from saving the notification of type ‘M4’ if he does not fill the ‘Cost Center’ field in the ‘Location’ tab.
Such many innovative uses can be derived out of this exit in this area.
This can be for intelligence in ‘Catalogs & Codes’ tab for relating values of one catalog to the other.
An example code is here:
When ‘Object part’ code is ‘PR’ in the catalog-codes tab, and ‘Damage’ code is not filled, then the notification does not save, wth the custom message (blacked-out).
Similarly, when ‘Object part’ code is other than ‘PR’ and the ‘Damage’ code is filled then also the notification saving is prevented.
This code is just to illustrate. Readers can apply in similar way to all their respective requirements.
-Jogeswara Rao K
PS: After going through many discussions on the subject topic, the idea of posting this to documents section came, where there is no document available on this topic.