Hi,
For those who landed here while searching on temporary table topic: this limitation of local temporary tables has been fixed in current version of Hana, so that local temp tables can be created within the stored procedure. They should be dropped upon session completing automatically, but It would not hurt to drop them at the end of procedure. Also, make sure to use right type of temp tables - row or column based. This will matter if you use such temp table in join with different type of persisted table. Because of different engines being used for different stores, the data transfer between engines will affect the performance on a bigger amounts of data
Steve, transaction scope depends how you execute command. You can initiate transaction from your application. Then you define the scope of transaction by starting it and either committing or rolling back.
Also, every hana stored procedure has its own transaction scope when triggered w/o externally initiated transaction. And stored procedure at the top of the calling stack defines its scope then. All nested SP calls will be bound to that transaction. I think SQL Server works precisely the same way
Artem