User Exit - Call Stack - BAPI

Former Member — Tue, 18 May 2010 06:38:33 GMT

Dear Experts,

Greetings.

we are accessing data in an user exit via ABAP call stack & field symbols for our enhancement. It works fine when we access the transaction online. However when we use the standard BAPI available for achieving the same, the call stack is different and we are unable to get the required data. How to resolve this?

Another thing is, in our transaction there are three tabs and our enhancement has something to do with all the three tabs. So we are using an exit which is used for validation purpose (which has the data of all the three tabs as import parameters) and we are altering the values by accesing the call stack. Is it ok? or do we have a better approach.

Thanks and Regards

Sathya

Re: User Exit - Call Stack - BAPI

former_member186444 — Tue, 18 May 2010 06:59:27 GMT

Hi Sathya,

you can expect the call stack will be different as you are coming at the exit from a different route. By calling the bapi directly you are not processing all of the same code that the transaction processes, so the call stack is bound to be different. If you want to be sure where this has originated, why don't you put a wrapper function around the bapi and then call that instead. Then check your call stack to see if your wrapper function is in there.

Malcolm.

topic User Exit - Call Stack - BAPI in Application Development and Automation Discussions

User Exit - Call Stack - BAPI

Re: User Exit - Call Stack - BAPI