Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member4998
Active Contributor
8,721

Hi All,


I am explaining about safety belt and it's importance.

Safety belt is used to restrict and protects against large result-set of data retrieval from SAP BW as data source, which may be requested by the customer by entering slip-up prompts values while running the report. Retrieval of larger result-set of data could cause high memory consumption and decrease the system performance.

To avoid these issues, safety belt can be activated and need to be correctly set according to the system sizing, and no mass data requests should be processed that could exceed the safety belt limit.

To avoid the below error messages while running the reports, should not increase the safety belt value.

    • BW System QBW: Result too large,
    • Failed to execute query: ‘java.lang.NumberFormatException: For input string
    • Large reports not displaying rows but data exists
    • MDDataSetBW.GetCellData  in webI reports

Safety belt value Increasing might have negative impact on the system performance and, if too high, cause out-of-memory dumps.  Instead of increasing safety belt values suggest end users webI is an ad-hoc interactive analysis tool not a data dump tool and if end-user need to explore with more than 1 or 2 million records we should suggest to use SAP Business Objects Explorer.

Please find the below document for “selecting the Right SAP Business Objects BI Client Product based on your business requirements for SAP BW Customers”

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2046e5d7-2894-2e10-c6a0-ca59dbd72...


So safety belt needs to be used cautiously and in sync with available system resources. If using BW Java with the same ABAP back-end, this parameter will also impact front-end.


To activate and reconfigure safety belt login to BW system, Run the T.code SE38 --> enter the program SAP_RSADMIN_MAINTAIN then execute.

Enter the Object: BICS_DA_RESULT_SET_LIMIT_MAX and value as 100000 then execute.

If the object (BICS_DA_RESULT_SET_LIMIT_MAX) is already maintained in the Table (RSADMIN) and try to insert another value for same object then will get the below failed message.


so it means Table(RSADMIN) have some value and if you want to update with new values you need to select radio button update and then execute.

Then will able to see the new settings values.

To cross check the object values maintained correctly or not

Go to T.code:SE16 -> RSADMIN -> enter the objects BICS_DA_RESULT_SET_LIMIT_DEF and BICS_DA_RESULT_SET_LIMIT_MAX

Now the safety belt is activated and set BICS_DA_RESULT_SET_LIMIT_DEF and BICS_DA_RESULT_SET_LIMIT_MAX as value 1000000 and protects against large results-set data that may be requested by the customer by entering miscellaneous prompts value while running the report.

Hope this will be helpful.

Thanks,

Sreeni



8 Comments
Labels in this area