In this blog, I am going to tell about some Tips and best practices of SAP BW and ECC you can utilize in your work –
1. While transporting a Composite provider after adding one field from underlying ADSO getting the error every time that the added field (Key) is missing in the CP node where source is the ADSO from which field is produced.
In practical scenario , there is a SAP note-
https://me.sap.com/notes/0002387953 SAP note to fix the issue.
But tried to rebuild index of the Composite provider. using RSDDB_LOGINDEX_CREATE but not resolved.
Also transporting all the underlying ADSO not fixed the issue.
Finally, using RSDDB_LOGINDEX_CREATE we build the index in the target transport system for all the underlying ADSO then it fixed the issue.
2. Another issue is that due to a transport all the ADSO got deactivated in our quality system . So in this scenario we can not activate each and every ADSO manually.
Execute SE38 -> execute RSDG_ADSO_ACTIVATE and then provide the name list of the ADSO need to be activated.
3. Check Business user access to a report before providing for UAT or delivery :
It is a good practice to check BW authorization access to BW queries of the users before providing for UAT or delivery of a any report which is using the BW query.
Steps : Execute RSECADMIN -> Analysis Tab -> Execution As “User ID”
Then execute the RSRT and put the query name.
if the query executes then the user will able to open the report.
Okumaya devam et...
1. While transporting a Composite provider after adding one field from underlying ADSO getting the error every time that the added field (Key) is missing in the CP node where source is the ADSO from which field is produced.
In practical scenario , there is a SAP note-
https://me.sap.com/notes/0002387953 SAP note to fix the issue.
But tried to rebuild index of the Composite provider. using RSDDB_LOGINDEX_CREATE but not resolved.
Also transporting all the underlying ADSO not fixed the issue.
Finally, using RSDDB_LOGINDEX_CREATE we build the index in the target transport system for all the underlying ADSO then it fixed the issue.
2. Another issue is that due to a transport all the ADSO got deactivated in our quality system . So in this scenario we can not activate each and every ADSO manually.
Execute SE38 -> execute RSDG_ADSO_ACTIVATE and then provide the name list of the ADSO need to be activated.
3. Check Business user access to a report before providing for UAT or delivery :
It is a good practice to check BW authorization access to BW queries of the users before providing for UAT or delivery of a any report which is using the BW query.
Steps : Execute RSECADMIN -> Analysis Tab -> Execution As “User ID”
Then execute the RSRT and put the query name.
if the query executes then the user will able to open the report.
Okumaya devam et...