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.
| | | ---------------Original Message---------------
From: Rajan Subbaraman
Sent: Wednesday, November 02, 2011 11:16 PM
Subject: Warning vs. Error Message in In-completion Procedure
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. |
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  Typewriter
SAP Logistics Sales and Distribution Helper
Posted helpful replies on 50 threads in a group to earn a Silver Achievement Popular White Papers
In the Spotlight SAP BusinessObjects: Dashboards and Analytics. Learn more about this Toobox.com Marketplace online course.   _.____.__ |
