Hi Gersh,
Thank you for your response.
For some models, like consolidation and data collection, we are using the xxxx_B cubes, but for the planning model we are using the BPC cube in the BW multicube, as we have some IP/BEX input forms and IP planning functions in place.
I know that the Auth.Rel. flag can’t just disappear, I'm trying to find an explanation for this, as we haven’t changed the model structures in BPC. The only changes we have done, are on the BPFs, some minor changes on Data Access profiles and work status, and I believe this should not have an effect on the auth definition in the IOs.
A few days before this happened, we had copied the environment, for testing purposes, and the copied environment still has the Auth.Rel. flag set to true. I have check the Admin activity report in BPC, since the date the environment was copied, and there is no other change done in the original environment (other than the ones mentioned above).
My real concern now is how to fix this. Not sure if I can change the flag directly in BW, or if there is a transaction code to do this, or if there is a way to fix this from BPC.
I have tried to replicate the problem in DEV, to then see how to fix it before doing it in PRD, but even changing a dimension to not secure in BPC, the corresponding IO in BW does not changed to not auth relevant.
I’ll appreciate any suggestion.
Regards,
David