1) Firstly check with fresh orders with rejected items.
If issue persists,
2) Determine the print program by going into T code v/30, select the relevant output type and click on the processing routines folder on the left hand side window. Note the program for medium 1 (print output). It will mostly be a custom program, a copy of the standard RVADOR01. I am guessing your custom print program is the culprit. So..
3) Sit with ABAPer to review the code by searching with the following keywords:
"Print rejected item?
or
"IF vbdpa-dragr EQ space."
Table of importance is TVAG (reasons for rejection- config data) and filed is DRAGR but the program uses VBDPA structure, I guess. I am not an ABAPer.
Hopefully your ABAPer should be able to help you from here on.
Hello and thanks for your reply. We are all so new to the smartforms and have little experience...so your advice is greatly appreciated.
I did create a new order and still prints...this does not print on any of the delivery documents (del note, packing list, picking list) so I went looking in those for the table and fields you mentioned. I can not seem to find those anywhere....
I went and looked at the print program....processing routine and it does not appear to be a copy...as it does not start with a Z...it does say this...
/SMB40/RVADOR01
Form routine is Entry
Smartform is ZSD_SO_CONFIRM
If I am looking at the smartforms...trying to view the outputs of the ones that does not print this...I do see where it is calling a function..could these table and the code be hiding in a function?
If it is standard program and config is done, it should work by itself. I am wondering why not. Fine, if it not working, why don't you put a requirement in the output Determination Procedure against the relevant output. You need to copy standard requirement 2 ( Program LV61B002) and insert logic to not print if ABGRU or DRAGR is populated? This will be a 2 minute code to write.
SPRO/IMG/Sales and Distribution/Basic Functions/Output Control/Output Determination/Output Determination Using the Condition Technique/Maintain Output Determination for Sales Documents/Maintain Output Determination Procedure
But why don't you leave struggling with reasons for rejection and work with Delivery blocks instead. I suggested this before to somebody else in the forum. I think Delivery blocks (DB) work equally well without the bad effect of reasons for rejection (RRJ). Its like this: In stead of deleting an item, use RRJ, In stead of RRJ, use DB. Having said that, I am skeptical that it may also (not) work similar to RRJ. Try it after the Requirement (above) option.
If you want to go that 'route' (Pun intended):
SPRO/Logistics Execution/Shipping/Deliveries/Define Reasons for Blocking in Shipping
Hi and thanks for responding. The program you suggested appears to be at the header level....my problem is at the item level...
Item is rejected and prints on the sales order confirmation...
Is there a program for the item level of a sales order for the output or do we only work with the one you suggested for both item and header? Also, How do you know how to find programs?
Please check with your ABAPer to do changes in Print program, you can ask him to put a check while printing if Reason for rejection filed is filled with any value then those line items should not print.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.