Skip to Content

If you are encountering repeated rollup failures. There are several steps you can do to research this.

If the rollup is failing on a “master data not yet indexed” error, then

  1. 1) Check for any failed attribute change runs.  If there are any, these need to be corrected first.
  2. 2) Check  the application log for the master data daemon indexing job.
    1. Run T-code SLG1 with:
  • Object:  RSDDTREX
  • Subobject:  TAGGRFILL
  • Ext. Identifier: *NEWMD_INDEX*

          b.  This will display all logs for the day, scroll down to the bottom for the most recent.

          c.  If you are seeing a lot of red statuses in the last 10-20 logs, then check the errors within them

      1. If the error is a lock on an info object. This means that most likely a load is currently running into this object. The lock should clear itself within 30 minutes as the load completes.  If it does not clear, it is most likely due to attribute change or load that has failed and is not completed successfully.


          ii. If the error is a BWA bad return code, then you have some indexing issue and if this error repeats across more than 10 of the most recent logs, then                you must drop the indexes on the cube, and then recreate them.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    Hi  Sheen.

    addition info to this blog:

    If the particular master data is present in the table RSDDTREXNEWSID then the rollup failes with the message as Master Data not yet indexed.

    So check the Info Cubes relavent master data is present in this table if present then the wait for some time till the job BI_BIA_NEWMD_INDEX completes ( This job will add the new master data entries in the BIA server ). Once this job is done then again  check the relavent master data entries in the table if the entries are not found. Then you are good to repeat the failed rollup step.


    Bhaskar V


Leave a Reply