2006 Sep 05 7:56 PM
Hi
I need to generate an XML file when PGI is done for a delivery. I need to create this file when 'Total good movement start' is changed to C ( completed).
please let me know if you have any idea about user exit or a badi at this point.
I tried LE_SHP_GOODSMOVEMENT' but its not helpful.
Thanks
2006 Sep 05 8:30 PM
Expanding a little on Naresh's 2nd suggestion: You could also create a new output type (see trans NACE) with an associated requirement (see trans VOFM again) which will prevent the message from being sent if PGI is not complete.
If using VOFM, go to Requirements->Output control. The requirements under "Requirements->Subsequent functions->Goods issue" control when a GI is allowed, not what you can do after a GI has been posted.
2006 Sep 05 8:24 PM
MV50AFZ1
FORM USEREXIT_SAVE_DOCUMENT should be triggered for PGI scenario as well.
Also try transaction code VOFM
Menu
Requirements->Subsequent Functions->Goods Issue routine.
2006 Sep 05 8:30 PM
Expanding a little on Naresh's 2nd suggestion: You could also create a new output type (see trans NACE) with an associated requirement (see trans VOFM again) which will prevent the message from being sent if PGI is not complete.
2006 Sep 05 9:26 PM
If using VOFM, go to Requirements->Output control. The requirements under "Requirements->Subsequent functions->Goods issue" control when a GI is allowed, not what you can do after a GI has been posted.
2006 Sep 06 12:55 AM
All i need to do is generate an XML once and only once when the PGI is done that is updated in database ( completed status).
I am trying my best to find a user exit or badi. but so far all of them are before database update.
please let me know any info on this
Thanks
2006 Sep 06 2:36 PM
You can do something like this within
FORM USEREXIT_SAVE_DOCUMENT.
IF not xlikp-wadat_ist is initial
AND ylikp-wadat_ist IS INITIAL.
*- Also check for Total Good Movement start is changed to 'C'
*-insert your logic
endif.
2006 Sep 06 2:56 PM
The solution provided by Naresh is fine as long as there isn't a problem processing the save. If something were to happen with the processing after this user-exit, the transaction would roll back and you would have generated the XML output.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |