We have a process chain in BW that is run monthly and has been in production for a number of years with no issues.
After applying patches to our ERP6 system and upgrading to EHP4 - the process chain failed on a number of objects because the date & time stamp was different to the backend system.
I replicated the individual objects and the process chain ran successfully and the cube was available for reporting.
The business were not able to run their BEX queries as they were getting an error RFC_ERROR_SYSTEM_FAILURE TABLE_NOT_EXISTS
In BW, I ran program u201CSAP_DROP_TMPTABLESu201D. I Ticked every thing to make sure that all types of temp tables and temp reports were deleted.
The business were then able to run thier BEX queries but they said that their queries were not picking up all expected data.
The queries reported on employees with FTE headcount > 0 and Salary > 0.
I viewed the contents of the cube and I can see the employees with their FTE and Salary figures.
I ran the program u201CSAP_DROP_TMPTABLESu201D again and this time when the busines ran their BEX query it picked up the employees FTE figures but the salary is still not showing.
I have proved that the data is there by viewing the contents so what is the BEX query looking at and how can I get it to pick up the salary figures?
Edited by: Beverley Draper on Dec 29, 2011 2:43 PM
I forgot to mention that the employees who are not being picked up correctly by the BEX query have all had cost centre changes during last month. I don't see how this should affect it but it is something that they all have in common.
I have not been able to replicate the issue in our test or QA environment.
I need to assure the business that it will work when it is run again at month end on Sunday 31st December 2011. (Each time it is run it drops the cube and rebuilds it to contain 2 years worth of data).
Does any one have any ideas how I can get the BEX query to pick up the data that I can see when I view the contents of the cube?