Skip to Content
avatar image
Former Member

BW Navigational Attribute Issue

We had a process chain failure during the weekend where in the ACR for masterdata was running and in parallel the transaction data started loading as well. It shouldn't have happened but it was a result of a design flaw.

As a result of this, we are having issues with a masterdata object say for eg bh_batch.

We are no longer able to find data related to this master data in any of the bex reports. But this is applicable for certain batch numbers only. Whenever the naviagational attributes for this masterdata object is dragged to the rows, the execution of the report results in No applicable data found.

Once we remove the navigational attribute from the rows, the bex report starts displaying data again.

Please pour in suggestions to rectify the situation. Needless to say the business is impacted.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 11, 2017 at 01:11 PM

    Hi Chitra,

    This kind of behavior happens when the X table of the masterdata is not consistent with the P table.

    Execute a RSRV on the characteristic containing this navigational attribute:



    Add comment
    10|10000 characters needed characters exceeded