Skip to Content
author's profile photo Former Member
Former Member

Update on Output Routines

Hello guys,

Regarding output routines like the ones attached to outputs like BA00 on sales orders or RD00 on invoices (or any customized output type), do you know if it is safe to include in those routines codes that will trigger a DB update? For example

a) a BAPI call to change a sales order within the output routine or

b) any call transaction that will update data or

c) an IDoc creation by calling function IDOC_INBOUND_SINGLE or

d) direct update to a table customized or otherwise.

I'm pretty sure commit statement is not allowed on these output routines that is why I'm asking.



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Aug 26, 2009 at 08:18 PM

    I think you have the right answer! I saw that some output routines were called inside update task, so any COMMIT WORK (so, especially a CALL TRANSACTION) would dump. In your case, I don't know, but I learnt from SAP that we should really use exits as they suggest. Try to execute these special processings in "background task as separate unit" so that there is no conflict with sap programs, or use implicit enhancement options (from SAP 7.0)

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.