Hello Rahul,
In the past this problem has happened because the corrections from the notes 1041000 and 1081423 were missing from the BI
system. If the notes are applicable to your release level please apply them and then try the loading and the activation of the
request again. If the problem still exists you can use the note 1052335 to trouble shoot the loading and activation of the
data in your system. A good tip is to switch of the automatic activation of the data or remove the DSO from the process
chain if its a process type in the chain that triggers the activation. Then you can check in the activation queue/new data table
of the DSO to see if the data is correct at this point. If yes then we know at least that the issue happens on activation of
the data.
Best regards,
Des.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.