on 05-13-2009 12:20 PM
Hi
Our system has been set up so that PO's are sent out when Orders are saved. Which is fine for Orders that are initially created
The Client wants to supress any subsequent changes orders that are saved using the "Order"
but allow orders to be printed using the "Order and Output Immediately" button
Is there anyway you can do this?
From debugging the buttons have Sy-Ucomm values of 'SAVE' and 'SEND'
but they use the same code to save the po and send the output.
I've looked at the condition dependant document output trans BBP_PO_ACTION_CONF, but there doesn't appear to be a way of creating a schedule condition that can identify what button has been pressed
Any help would be welcome
Geoff
Hi
We tried changing BBPD_COMP_FIELDS with mixed results
It prevented a repeat print if a description field was cahned
but if a price or quantity field was changed then the PO form was printed out regardless of the settings in BBPD_COMP_FIELDS
To resolve this I eventually put in a simple flagging system to identify if it was a changed PO
Geoff
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Geoff,
Try the following solution.
Maintain the table BBPD_COMP_FIELDS for the fields you change with the field value for
COMPARE_KIND as 'E'.
For the PO the comparison method is 'POO'.
Maintain the structure and field name depending on the field values you change in PO.
For the field values you maintain here the PO will not be output on Change.
Best Regards,
Sapna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.