Hi to all,
just one question about bapi's and parallel processing.
I'm using BAPI_DOCUMENT_CHANGE and BAPI_DOCUMENT_CREATE2 bapi to modify material documents. With SM50, i see that the bapi, uses all free DIALOG work process of the application server.
Is that a parallel processing. Isn't it? All BAPI's works in that way??
Probably this could improve the performance, but i dont' care and i would like to avoid this way of work, and use ONLY ONE dialog work process (also if i run the program in batch).
Is there a method to use ONLY one DIALOG work process with these BAPIs??
Thx a lot
Andrea
Hi,
same for me: time is running out before travelling.
Background won't help in case of starting new task.
There is general system parameter, which can prohibte usage of last 1-2 dailog sessions (not much of a help, but system stays unblocked).
I bet for user-exits, not standard.
Sophisticated resource usage needs additional programming (examples can follow later, anyway calls have to be identified in beforehand).
Regards,
Christian
Hello Andrea,
I don't think what you see can be classified as <i>parallel processing.</i>
Only one work process will be utilized at any instant of time, unless you explicitly specify the options to make use of parallel processing (STARTING NEW TASK etc.,).
It may be possible (though I don't think it likely) that the two BAPIs use a different work process to execute. But the processing is actually still serial in nature.
Just observe one thing. Are the two BAPIs ( in one instance of your running program ) getting executed at the same instant with different work processes? Please confirm.
Also, this topic can be best understood if you supplement your observations with the online documentation.
Regards,
Anand Mandalika.
Hi Andrea,
to sum some facts: obviously you are not starting new sessions with '... new task', obviously your calling is total sequential.
And now a really blind guess: there are some minor extensions in user-exit(s), which are calling new tasks to make some necessary steps of a follow-on process...
BAPI's don't have a hidden life. Only update might be asynchronous - which you can avoid by calling bapi_transaction_commit with 'wait'.
Do you have a complete overview of customer programming in this part?
Regards,
Christian
Add a comment