My response was more generic in terms of the attempt to use incompletion
procedure to generate a hard error.
Yes, you are right, USEREXIT_FIELD_TO_VBAP is at line item level and it
will run for each line (while not optimal, vbak is still available for
validation here). For header, one could use USEREXIT_FIELD_TO_VBAK.
USEREXIT_FIELD_MODIFICATION can be used to validate the screen field
content and raise an error if needed. The exit is called for all the
fields in the screen and the value of the desired screen field value can be
trapped. It will execute at the time of processing the screen and prevents
moving from the screen till the error is fixed. The reason I mentioned 'or
even' is because this is more complex to implement.
| | | ---------------Original Message---------------
From: Typewriter
Sent: Sunday, November 13, 2011 6:57 AM
Subject: Warning vs. Error Message in In-completion Procedure
Hi Rajan,
You have suggested two userexits, in your above post.
Could you please explain why one would use USEREXIT_FIELD_TO_VBAP? In other words, field Order reason is at header level; why would you want to take that to item table? And by doing this, how would the requirement be fulfilled?
USEREXIT_FIELD_MODIFICATION could you please describe how using this userexit the business requirement would be fulfilled?
I am trying to improving my knowledge on how to go-about customer requirements & fulfilling them by using programs and userexits. So if you have more explanations, please do not hesitate to give them too. |
| __.____._ 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 SAP BusinessObjects: Dashboards and Analytics. Learn more about this Toobox.com Marketplace online course.   _.____.__ |
