‎2009 Apr 16 4:00 PM
Hi all,
Currently, I have developed customized print program and SMARTFORMS for Goods Receipt via MIGO, with output type ZZGR.
Typically, this is a inter-plant transfer, where Plant A will issue a Delivery Order to Plant B, and Plant B will post goods receipt via MIGO (Movement Type 101), using Delivery Order number. As soon as the Material Document is posted, the SMARTFORMS shall be triggered by customized print program, in order to print out the goods receipt document upon material doc posted.
The config for output determination (via TCODE NACE) for goods receipt is configured. I have tested post a goods receipt using Delivery Order, and Material Document is posted successfully. However, I got a message from SAP Inbox (Businees Area), saying that my Material Document having an update error, and the root cause is specifically from calling Function Module to trigger Smartforms in the print program. From tcode ST22, I realized that the error is due to empty parameter being passed to the function module (where the parameter is required field for further processing in Smartform).
In order to rectify why empty parameter is bieng passed, I will have to debug the print program, after GR posted from MIGO. Therefore, can someone shed some lights on how to perform a debugging process, or any standard sap program involved, as I understand that the print program is triggered (in background) after GR posted?
Also, can I know why the Material Document will not be committed to MKPF table after GR posted, is it due to the update error from the above mentioned?
Many thanks.
Best regards,
Patrick
P/S: I'm using SAP ECC6.
‎2009 Apr 16 4:11 PM
About committing to DB/MKPF: yes, bcoz of issue with smartform, i guess, its not committing/DB is not updating. Once, I got the same issue, but, in my case, the issue with materail serial numbers, which r containing special cha´racters.
thanq
‎2009 Apr 16 4:12 PM
Hi,
Check the driver program in a table TNAPR
Give output type KSCHL = ZZGR
Regards
Krishna
‎2009 Apr 16 4:13 PM
Actually, this print program is being triggered in the update processing.
Put a breakpoint in your driver program.
In MIGO, before pressing the SAVE button start debugging.
Press the SAVE button.
Start the update debugging by Settings > Update Debugging.
As soon as you continue in debugging, it would open another debugging session for the Update debugging. You can press continue and it would stop at your breakpoint.
Regards,
Naimesh Patel
‎2009 Apr 17 11:05 AM