Here I would like to share some error examples and the approach to them.
- Wrong Data in the Output
In order to debug cases with wrong output data, it is helpful to check transaction NACE.
There we go to the output type V2 (Shipping) and navigate to our output type.
We can check the processing routines:
By placing a break-point in the Form Routine, we can easily debug the data retrieval.
- Critical errors
In this case the partner agreements are not maintained correctly. A customizing activuty needs to be done in transaction WE20. Then we can reexecute the output.
For example, in deliveries (transaction VL02N) ,after processing the output routines, the paper is printed correctly or the IDoc is sent but when you go to the log you find errors like missing translations or missing phrases / phrase sets.
Let's look at one example where we get the error message DG523:
The message is almost self-explanatory and it is clear there is master EH&S Data missing.
After maintaining the missing phrase set assignment, we reprocess and the log is green.
In case of missing master data, do not forget to maintain in the production system.
Some error messages in the output processing are nonthreatening but they appear and can be confusing for the end users.
- Minor errors
Let's look at one example where we get the error message DG523:
The message is almost self-explanatory and it is clear there is master EH&S Data missing.
After maintaining the missing phrase set assignment, we reprocess and the log is green.
In case of missing master data, do not forget to maintain in the production system.
No comments:
Post a Comment