Skip to Content
0
Former Member
May 10, 2008 at 12:01 AM

Does the Data Slice ignores CR derivation for data lock verification?

47 Views

We have characteristic relationship derivation defined to derive Company Code from Cost Center.

Accordingly, planning level contains Cost Center but not Company Code.

We have defined data slice based on company code.

Surprisingly, planning application allows to save or change data for cost centers beloging to Compnay Code for which data slice is active. Also, verified new data records in the cube and company code field is populated with company code for which data slice is active!

I couldn't find any documentation to see the limitaion of data slice where it works and doesn't. Couldn't find any OSS notes either to fix this issue.

Is it possible that data slice doesn't verify the plan records if they violate data lock imposed on the plannng area after the characterstic relationship derivation but before saving data? Is this a data slice related bug? I was expecting system error message for this type of situation.

Has any one came across this issue?

Best regards,

Sanjeeb