on 11-13-2009 10:06 AM
Hi All,
Has SAP come up with permanent fix for this MD04 problem?
Please let me know. I would really appricite any response on this. We are getting this issue quite frequently. We need to run this report quite frequently. We want permanent fix.
Thanks,
Sanjeev
Hi,
I don't think so.
Check below SAP Notes.
sapnote_0000025444
sapnote_0000547277
In sapnote_0000025444, it says this note is release independent.
Best regards,
Anupa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
today, I accidentally came across this interesting OSS note
[Note 1093377 - Trap code: Help for single requirements errors analysis|https://service.sap.com/sap/support/notes/1093377]
which helps to determining which SD transactions generated the requirements errors.
If you have not solved your problem, this note could help you.
Regards,
Andrea
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
the requirements errors often occurs when, sales order and/or delivery processing user-exit , are implemented incorrectly.
The following OSS note
[Note 415716 - User exits in delivery processing|https://service.sap.com/sap/support/notes/415716]
contains the guidelines for the proper implementation of the exit routines in delivery processing.
The same rules, with the exception of some methods and table names, are also applicable in the sales order processing.
Andrea
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.