When I extract data from the timesheet area (the CATSDB table on ECC6 to be exact), I'm running into issues with the ENDUZ column when using RFC Streaming.
I keep getting errors saying that it encountered an illegal value - 240000, which seems logical as 24:00:00 is not a valid time format. It's either 23:59:59 or 00:00:00.
However, I am unable to resolve this problem - I have tried changing the data type in my Query Task to varchar(50) so I can at least capture the offending data. But it was still giving me errors. I then tried casting the ENDUZ column to varchar(50) but still errors. It was only after I either just mapped the output column to NULL or removed the column all together did I no longer receive any errors. But of course, I was also not getting the data I needed so that wasn't the solution.
So I then created an R/3 ABAP data flow against our open DEV client, uploaded the program and then ran it from our closed DEV client which was the source of my failed RFC Streaming data flow. (and thus using the same data.)
I had no problems getting the ENDUZ data from the CATSDB table this time around. However, I did notice that a few entries had NULL values, perhaps this was caused by the time issue?
However, there are 2 issues why I really want to use RFC Streaming rather than R/3 Data Flow:
1) when using RFC data flows, we do not have to transport ABAP programs across our landscape which saves us heaps of paperwork and hoopla.
2) the LTXA1 text column contains, by mistake, line feed characters which are wrecking havoc when the data flow is trying to consume the output data file created by the ABAP program.
As RFC Streaming flows from SAP straight into our database tables, it will allow us to capture this data - inclusive of special characters and all - and clean everything up ourselves.
However, the time conversion issue is really doing my head in and seems to prevent us from using RFC Streaming!
Any brilliant ideas anyone?
↧
SAP ECC RFC Streaming does not like the TIME data type?
↧