SAP R/3 форум ABAP консультантов

[admin]

From SAP:
Regarding your answer in connection with the Z-program, I have sent you,please find following background information:
In earlier releases EDI_OUTPUT_NEW has been called in
MASTER_IDOC_DISTRIBUTE directly. This has lead under certain errors to
the problem, that the IDoc has been set to status 03, even if the
sending was not successful. These IDocґs could not be resent on a
"normal" way.
In later releases the sending process of EDI_OUTPUT_NEW is carried out
asynchron in a new session. This session requires unlocked IDocґs and
will be started by a "COMMIT WORK".
This causes also, that the status after MASTER_IDOC_DISTRIBUTE is set ina correct way to 30 and will only be changed to 03 through the sending
process (after the COMMIT WORK).
This way it can be ensured, that even in case of an abort of the sendingthe IDoc has the right status.
This new system behaviour must always be taken into account by the givenapplication.
Unfortunately, not every application takes this system behaviour in
account and in these cases the z-program, as described by me in my
previous answer, can help. It is not possible, to deliver a central
solution from basis side for this issue.
Could you please check, which message types are affected in your system?If we have the exact message types, we can check, if the given
application has an appropriate solution for your problem.
Please, send us as well a short description, how such IDocґs in status
30 can be created in your system!