I am investigating the reason why a process in my DS job has stopped working.
We have been using this function call and I think it has been working up until this month. But it may have been longer.
The function call is setup properly(or so I think) but it is returning all NULL values.
If I run the function directly in SAP I get information returned so what am I missing? 
toscajo (BOB member since 2002-09-04)
MAybe an input value is wrong, e.g. you are passing a MATERIAL NUMBER field but its value is NULL or something less obvious.
The BAPI has some return fields like return message, AL_RFC_RETURNCODE and things like that. What is in those fields after calling the BAPI?
Werner Daehn 
(BOB member since 2004-12-17)
Thanks and just got a disturbing scene.
I recreated the jobflow EXACTLY as it was setup. I ran the job and it worked ?!
Wondering if BAPI is unstable within BO?
I will continue to run it to see if it breaks
toscajo (BOB member since 2002-09-04)
Please change your dataflow so that you can lookup the return messages later. With RFC/BAPI calls things are different, if that fails the dataflow is successful still but the reason of failure is returned by the function. It is just the way BAPIs work. They never throw an exception, the tell you verbally what was wrong.
Werner Daehn (BOB member since 2004-12-17)
The return message always said the RFC is okay.
This is a bug within Data Services and how it uses RFC into SAP.
The developer at SAPBO support said he never heard or saw this before but will check to see if there is a patch or fix available.
I will post the information once I hear back from him.
In the meantime, I have a workaround which is to redo the DF if or when I have any kind of update to make. A bit of a nuisance but at least I was able to get it working.
toscajo (BOB member since 2002-09-04)