If you can register data in SE37, I don’t see a problem with the content.
SAP Application Scope and sessions are two different things.
SAP Application Scope is only supposed to be able to take over authentication information.
Therefore, the current specification, which makes the session separate for each activity, cannot be handled.
At this time, we know of no other way than to use InvokeCode to execute “BAPI_SALESORDER_CREATEFROMDAT2” and “BAPI_TRANSACTION_COMMIT” in the same session.
I can give you the InvokeCode sample code if you want it.