Hello everyone,
I have a scenario within a planning application where I would like to allow the user to flip on and off an indicator to update either a master data attribute or a DSO characteristic which would then be the target characteristic in a characteristic relationship derivation to update this value in the real-time cube. For example, if the user chooses to turn on the indicator, the characteristic value is changed from # to 'X' in the attribute or DSO. After a change to this indicator is made, I can then execute a Repost (Characteristic Relationship) planning function to repost this value in the real-time cube.
My initial thought was to use a direct update DSO as the source for the characteristic relationship but direct update DSOs can't be used for this. I've also looked at the How-to document for creating master data in IP but not sure if that's the way to go since I'm not looking to create master data. I'm just wanting to change an attribute value. I suppose I could use a Repost planning function on an aggregation level that contains only the characteristic and the attribute but I would like to maintain these settings in a characteristic attribute or DSO instead of directly in the transaction data.
Any ideas on a possible design solution would much appreciated.
Regards,
John