2020 May 28 4:40 PM
Hello,
I develop a z program that makes the call:
CALL TRANSACTION 'ES61' USING lt_bdcdata MODE 'N' UPDATE 'S' MESSAGES INTO lt_messtab.
But in cdhdr is saved the transaction es61. How can i save in cdhdr the transaction related to my program?
2020 May 28 4:46 PM
Hi,
Unfortunately this is not possible, since you're actually calling transaction ES61. (the transaction runs in its own context)
The only way to prevent this is to do the update in your program, by using e.g. a function module, class that updates the object you're updating with transaction ES61.
The documentation for CALL TRANSACTION clearly states that the program runs in its own internal session and has its own SAP LUW.
https://help.sap.com/doc/abapdocu_752_index_htm/7.52/en-US/abapcall_transaction.htm
Best regards,
Geert-Jan Klaps
Hello,
I develop a z program that makes the call:
CALL TRANSACTION 'ES61' USING lt_bdcdata MODE 'N' UPDATE 'S' MESSAGES INTO lt_messtab.
But in cdhdr is saved the transaction es61. How can i save in cdhdr the transaction related to my program?
2020 May 28 4:43 PM
Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers (if you haven't already), as it provides tips for preparing questions that draw responses from our members. For example, you can outline what steps you took to find answers (and why they weren't helpful). The more details you provide, the more likely it is that members will be able to assist you.
Should you wish, you can revise your question by selecting Actions, then Edit (although once someone answers your question, you'll lose the ability to edit the question -- but if that happens, you can leave more details in a comment).
Finally, if you're hoping to connect with readers, please consider adding a picture to your profile. Here's how you do it: https://www.youtube.com/watch?v=F5JdUbyjfMA&list=PLpQebylHrdh5s3gwy-h6RtymfDpoz3vDS. By personalizing your profile with a photo of you, you encourage readers to respond.
Kind regards,
--Jerry
2020 May 28 4:46 PM
Hi,
Unfortunately this is not possible, since you're actually calling transaction ES61. (the transaction runs in its own context)
The only way to prevent this is to do the update in your program, by using e.g. a function module, class that updates the object you're updating with transaction ES61.
The documentation for CALL TRANSACTION clearly states that the program runs in its own internal session and has its own SAP LUW.
https://help.sap.com/doc/abapdocu_752_index_htm/7.52/en-US/abapcall_transaction.htm
Best regards,
Geert-Jan Klaps
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |