Skip to Content
avatar image
Former Member

Trigger Planning Sequence After Save

We want to execute a planning sequence immediately after the users save the data in analysis office query. The save is done by standard save button in AO ribbon.

Currently we are able to achieve the same by specifying the planning sequence in RSPLAN ->>> Planning Sequence when saving data. This works as expected. But this will be very computationally expensive and will lead to slow performance.

So when we check the option : Only read changed data. The system is not performing the sequence as expected.

Please guide if any additional checks/tasks we need to perform ?

Also help us with what aggregation level need to be specified in subsequent option of reading changed data ?

RSPLAN.jpg (81.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Feb 26, 2016 at 05:20 PM

    Hi Anurag,

    the flag 'Only Read Changed Data' does not mean that the system reads only the changed data records to be processed in the planning functions/sequence 'before save ⚠️. Observe that this does not make sense in the general case since the semantics of a planning function also depends on the characteristics to be changed, the selection (filter) and the reference data selection. Just to take the changed records in general leads to nonsense, take the disaggregation function as an example: the stuff to be disaggregated depends on the blocks (defined by the characteristics not to be changed), e.g. if you disaggregate values from Product Group '#' to some 'Products' (characteristics to be changed) per Period (block characteristic). Just to take a record with a Product (because of a change) does not make sense since the 'sender' Product Group '#' would not be read.

    So the system does the following:

    - as always, the system uses a 'run time' filter to define the data region in change mode that might be changed by the planning function

    - in delta mode the 'run time' filter will be 'derived' from the filter specified in the sequence and by the changed delta records, but only for block characteristics not used in reference data selection: for these characteristics the projection of the characteristics in the changed records will be used as 'in-list' restrictions in the 'run time' filter; the optional 'Aggregation Level for Reading Changed Data' can be used to specify not the aggregation level used in the planning function but another one. Using this can have an effect on the projection of the changed records to build the 'in-list' for the 'run time' filter.

    Based on this explanation you should be able to design the function 'before save' in such a way that the 'delta flag' has really an effect on the processed data (i.e. the 'run time' filter used).

    Regards,

    Gregor

    Add comment
    10|10000 characters needed characters exceeded