Hi Alecsandra,
That's an interesting idea. Please let me ask a follow up question. If the Planning level is Product/Location and there could be thousands of combination in the system needed this DOH calculation, if we use Local Member to do calculation and macro to write back to another editable KF, you can only do the calculation for the combinations that you bring out to the planning view limited by the MAX_RESULT_ROW_SIZE and visibility filter. Is there a way to overcome this issue?
Moreover, my understanding is calculated KF doesn't take up database storage space but a stored editable KF does which makes this solution a bit less optimal it seems.
Please comment, thank you.
Yee Ann