‎2010 Jan 25 3:31 PM
Hi Guys,
I have created a custom program that calls transaction 'MSC1N'. During execution of MSC1N, the program forces a COMMIT WORK AND WAIT and then "Should" continue processing. This is how it works when I run it in the foreground. However, when I run my custom program, the call terminates right after the commit work and wait and I am returned to my program. I get no messages after the call terminates.
Please adice on how to make the call transaction run same as in foreground.
Thanks!
Edited by: freishz on Jan 25, 2010 4:32 PM
‎2010 Jan 26 5:20 PM
‎2010 Jan 26 5:28 PM
MSC1N looks like an EnjoySAP transaction and therefore not suitable for batch input in the background.
Rob
‎2010 Jan 26 10:08 PM
Hi,
When you are doing the recording for the transaction, there is a checkbox for "CONT after COMMIT". Select this checkbox during the recording. This will not stop the processing after commit.
Regards,
San