Incompletion procedure just flags the document as incomplete and could
affect the subsequent document creation. It does not issue a hard error,
but only warnings - always. That is the purpose and design of incompletion
procedure. You cannot change the message from warning to error.
If a hard error is what you need, create a validation using one of the user
exits in MV45AFZZ - USEREXIT_MOVE_FIELD_TO_VBAP or even
USEREXIT_FIELD_MODIFICATION.
| | | ---------------Original Message---------------
From: Elizabeth Long
Sent: Wednesday, November 02, 2011 10:25 PM
Subject: Warning vs. Error Message in In-completion Procedure
Hi TW,
You have got my point right. In our system, it only prompt user the error message that the Order Reason field is a must to filled in but if the user ignore it, the system still allowed user to proceed and save the SO.
So what I meant to said was, as you have pointed out as follow:
'By some way (may be coding or noncoding) the system has to be setup in such a way that the user cannot leave the initial screen of the sales order, of a particular Sales document type (i.e. for process - goods free of charge), if the field Order Reason is not filled.'
Or maybe in this case, the system should be setup in a way if the Order Reason is not filled, user won't be able to proceed to the next field at all.
I think that is the best way to ensure the user do not miss out that field.
I've marked your post helpful. :)
Thanks,
Liz |
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  PSD Rajan
SAP Logistics Sales and Distribution Helper
Posted helpful replies on 5 threads in a group to earn a Bronze Achievement Popular White Papers
In the Spotlight   _.____.__ |
