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

CALL TRANSACTION UPDATE 'L' - SET UPDATE LOCAL TASK effects

Hi,

I'd like to know if the effect of having UPDATE 'L' on a CALL TRANSACTION is have that process go at the end of LUW aside from being on the same LUW of the calling program. Meaning it will finish executing the calling program then proceed with the CALL TRANSACTION.

The reason i'm asking this is because I have a requirement that I will use a user exit MB_DOCUMENT_UPDATE from BADI MB_DOCUMENT_BADI from MIGO that will call an custom program to generate a file. this interface should select on a table MKPF and MSEG, so it needs that the document number that is on the exit must already be on the table before executing the CALL TRANSACTION.

i plan to do this way so i only need to work on the custom program and don't need to update both the custom program and exit if there is need for future developments.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Dec 06, 2011 at 09:39 AM

    Create a RFC , wrap your code in it. Then in Method MB_DOCUMENT_BEFORE_UPDATE [call it in background task|http://help.sap.com/saphelp_nw04/helpdata/en/8f/53b67ad30be445b0ccc968d69bc6ff/content.htm].

    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.