Does the external program run in the same SAP LUW as the caller, or in a separate one?
– Transactions run with a separate SAP LUW – Reports run with a separate SAP LUW – Dialog modules run in the same SAP LUW as the caller – Function modules run in the same SAP LUW as the caller The only exceptions to the above rules are function modules called with IN UPDATE TASK (V2 function only) or IN BACKGROUND TASK (ALE applications). These always run in their own (separate) update transactions.
– Transactions run with a separate SAP LUW – Reports run with a separate SAP LUW. – Dialog modules run in the same SAP LUW as the caller – Function modules run in the same SAP LUW as the caller. The only exceptions to the above rules are function modules called with IN UPDATE TASK (V2 function only) or IN BACKGROUND TASK (ALE applications). These always run in their own (separate) update transactions.
– Transactions run with a separate SAP LUW – Reports run with a separate SAP LUW – Dialog modules run in the same SAP LUW as the caller • Function modules run in the same SAP LUW as the caller The only exceptions to the above rules are function modules called with IN UPDATE TASK (V2 function only) or IN BACKGROUND TASK (ALE applications). These always run in their own (separate) update transactions.
