I have created some simple bespoke RF programs that are working fine.
However I am having problems with some more complicated programs that work in the normal environment but are struggling in RF. The programs require the use of 'commit work and wait' and it appears that its doesnt 'wait' as required. Is there a definite problem here ? Does all the work have to be in one LUW ?
By RF programs, do you ABAP programs running through SAPConsole?
If so, I have many of these applications and they all have <i>commit work and wait</i> in them. I have never had any problem with the <i>and wait</i> addition.
Yes they are ABAP programs running thru SAPConsole. Now I know it should work I will investigate further and ask you more questions later if you dont mind !?
The problems occur after calling Function 'HU_POST' and a 'commit' ( without a wait ) was being triggered. If I prevent that 'commit' and make my own explicit 'commit and wait' after the function I have a feeling it may be OK.
Perhaps there is some <i>on commit</i> form or asynchronous output being executed by this function. You never know what an unreleased SAP function module might be doing.
That is why I tend to stick to calling BAPIs in RF transactions. I know they should be safe because they are designed to be called by external systems. That way you don't get any suprises that SAPConsole can't handle.
As of 46C there a lot of really good BAPIs for Handling Units. You might check the BAPI Explorer. From the Alphabetical list they are all under <i>HandlingUnit</i>. I have used them before in RF transactions, so I know they are safe.
Thanks. The problem is now fixed by preventing a 'commit' within 'HU_POST' and then doing an explicit 'commit and wait' in my own code later. I inherited the non BAPI solution code on the project I am working on and it appeared OK at first glance. I tried to get the BAPI_HU_? functions working but had problems with the Unpack one I think. Maybe I will try again, I have been replacing BDCs and Functions with BAPIs were possible but they arent always the most user friendly to get working without lots of test data.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.