SQL Generation Solution in SAP Business Objects 4.0. Introduction: This article helps us How to resolve the SQL Generation Issue Business Objects 4.

Transcription

1 Author: Madhukar Nambeti (SAP Business Objects Consultant) Date: April 15 th, Phone: SQL Generation Solution in SAP Business Objects 4.0 Introduction: This article helps us How to resolve the SQL Generation Issue Business Objects 4.0 SQL Generation issue will be occurred when we transport the Business Objects documents from one environment to other environments. Reason Incompatibility with SAP Objects 1. Missing Free Characteristics or Navigational Attributes or Key Figures 2. Incompatibility with SAP Technical Names 3. OLE DB external access disable In this article we will generate the issue with creating a test report and also solve the issue TERMINOLOGY USED HEREIN: Limited access user Attributes Dimensions User that does not have the ALL enablers as listed above, or users that are assigned the Toller key role. Please see figure 1 below. In terms of this documentation, attributes are the underlying detail objects in the available objects pane. Please see figure 2 below. In terms of this documentation, dimensions are the main info object or characteristic. Page 1 of 5

2 Figure 1 Figure 2 About: SQL generation failed occurs prior to prompt screen populating in BOBJ reports. If the prompt screen appears prior to this error, please investigate further. SQL generation error occurs for one of the 2 following reasons; both are related to security enablers: 1. Key Figure related enablers: a. The report has cost related key figures. AND. The report was created by an individual that has the general key figure role assigned. b. The user trying to run this report has the Toller key figure role assigned. c. The user with the Toller key figure role will get SQL generation failed error upon execution of report. 2. Sales Org, Company Code, Plant, Profit Center, and Distribution Channel authorizations a. It is important to understand the difference of dimensions and attributes in accordance with how they are used in BOBJ. SQL generation error does not give errors on the dimension objects, only the attributes. e.x. The dimension Company Code does not give an error; however, Plant Company Code attribute does. b. The report has one or many of the below listed attributes in the Available Objects pane. AND. The report was created by an individual that has ALL security authorizations assigned. c. The user trying to run this report has restricted access to Plant, Sales Org, Company Code, and/or Profit Center. d. When the limited access user tries to run this report, they will get SQL generation failed error upon execution of report. Page 2 of 5

3 ISSUE RESOLUTION FOR KEY FIGURE ENABLERS: 1. The assumption can always be made that the report was developed with a developer ID that has general key figure role 2. Ensure none of the attributes listed in the attachment above are not present. Easiest way to do this is to search on the key terms Plant Company Code Sales Organization Distribution Channel Profit Center 3. If any of the above are found as ATTRIBUTES, then the report was not developed correctly and must be corrected in production. If none of the key terms are found, then proceed to step Navigate to Applications Web Intelligence Application 5. Once this application loads, navigate to Open 6. A new Open dialog box will appear. Open the problematic report. Page 3 of 5

4 7. Once report loads, navigate to design mode 8. Navigate to data access tab 9. Click Edit 10. This will open the edit query panel. Click run query and return data. Your selections do not matter, simply ensure data is retrieved. 11. Once report output is generated, click Purge 12. Save Page 4 of 5

5 13. Issue resolved. 14. Follow same process for any additional problematic reports Page 5 of 5