P R
Amol is right. This field is a part of OIAO and not the part of OIAL.
So you can hide this field by Hide button. If you have influencing condition Notification type then there is no issue.
----------------------------------------------------------------------------------------------------------------------------------------
But if you have Condition on any field other than Notification type or multiple conditions then you may have to go for user-exit with basic code like below.
For example:
You need prevent usage of this field only when the Notification type is 'M2' and Planner group is 'ABC' then this can be possible through user-exit only. Sample code below for such case to be used in the include ZXQQMU20 of function EXIT_SAPMIWO0_020 (user-exit QQMA0014).
IF i_viqmel-bautl IS NOT INITIAL and i_viqmel-qmart = 'M2' and i_viqmel-ingrp = 'ABC' .
MESSAGE: 'Notification can not be created on ''Assembly field''' TYPE 'E'.
ENDIF.
After this, whenever user tries to Save a Notification under these conditions with the Assembly field filled, the Notification would Refuse to Save by throwing this error message in the Status bar.
When he vacates the Assembly field and then clicks on Notification save, then it will be Saved.
-----------------------------------------------------------------------------------------------------------------------------------------
Regards
KJogeswaraRao







