Hello All,
Could you please help me on this issue,
===Product===
BO XIR4.1 Sp03
WEBI Report is created on BEx query.
BEx query contains one hierarchy object.(eg.Zone;Div;District;territory). We have activated the hierarchy display in BEx and using
this object in webi report.
We have applied the security in BW such that corresponding data for the user logged in will be shown. (e.g. if Division manager logs in he will be able to see the data for his Div only.(District and territory under his DIV))
SSO is configured. Hence same security is reflected in BO.
===================== Problem Decription=========================
If we open the report in launch pad with lowest level user (territory manager), then the report goes in running mode.
Schedule of report(with lowest level user) is also not working. It goes in running mode forever.
If top level user (zone/div/district manager) logs in, the report works fine.
BEx is working fine in rsrt (for all level users).
========================Steps Tried So Far======================
1. Generated trace of APS and WEBI. Attached is the Zip file for the same
2. We checked the SM50 transaction while running the report, and observed that query is coming there for that user(non working i.e going in loop) and going away which is the symbol that query execution is completed.
3. We checked the ST05 transaction, enabled RFC and SQL traces.
After that started and executed the report from frontend, we were able
to see “BICS_PROV_GET_RESULT_SET “ . It means it is returning the data to DSL bridge
4. We have split the APS and added dedicated APS for DSL services.
5. Added -Dbicsbookmarkqv=true to APS which is having only DSL and associated services. We have captured the Bookmark ID generated in the trace and used this Bookmark ID in RSRT1 transaction. There we were able to see the results.
6. Schedule also sits in running forever
7. We have added sufficient RAM (i.e 8GB) for DSL bridge APS
8. We have exchanged the user levels.( i.e top level to lowest level and vice versa) to check if its user specific problem. But it is
not user specific. Because for lowest level user when assigned to top level, report works fine. And for top level user when assigned to
lowest level, report goes in running phase.
Thank You,
Amol