Skip to Content

Billing output processed at save with Dispatch time 3

Apr 18, 2017 at 09:12 PM


avatar image


We have a peculiar situation in billing outputs for ALE/ IDOC. This particular output is not defined as 'multiple issuing' and has default dispatch time set to 4 (send immediately). The condition record for output also has dispatch time as 4. For historic invoices, outputs are not needed and hence a billing output has been entered manually with dispatch time as 3 (send with application own transaction), so that for any updates in these invoices, system should not shoot an output as output determination will find an existing output in invoice and dispatch time 3 for manually entered output would prevent sending output on document save.
However, when such an invoice is cancelled, the output is processed automatically for original invoice. The output in original invoice should not have been processed as the dispatch time is set to 3. This is happening in one of the systems and is not other systems with same settings.

In summary, output determined during document save is overwriting dispatch time and sending the output. I can see that the output has been modified for its dispatch time as NAST entry still has original date and time when output was manually added to invoice.

Any help in why this could be happening?


10 |10000 characters needed characters left characters exceeded

Has anyone else encountered this issue?


Is the status of that output shows in Green or Yellow?


Hi Lakshmipathi

The status changes to green and the IDOC is sent to the interface application.

BR, William

* Please Login or Register to Answer, Follow or Comment.

1 Answer

Typewriter TW May 10, 2017 at 03:17 AM

If the company does not want to trigger the output for historical invoices, then why do you enter manually the output in these invoices with dispatch time 3?

Show 1 Share
10 |10000 characters needed characters left characters exceeded

At times, modifications are needed in these old invoices. Some directly to the document, some indirectly. An example of indirect change is 'Cancellation' of the invoice, which in turn saves the invoice along with cancellation invoice. And that causes an IDOC being triggered from old invoice.