Skip to Content

COPY operator vs DISAGG operator for Scenarios.

Hello,

With COPY operator we have ability to run only for a particular scenario:

However, the DISAGG operator cannot be run for a specific scenario and only gives the ability to choose a version:

Why is this? Is there a way to enable Scenarios for DISAGG operator? If not, is there an alternative way (ADVSIM?) to accomplish this?

Regards,

Shivaditya Singh

capture.jpg (44.4 kB)
capture.jpg (51.3 kB)
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

5 Answers

  • Best Answer
    Oct 25, 2018 at 10:43 AM

    I understand the problem...

    Easiest would be to have an additional calculation for CONSENSUSDEMANDQTY :

    @WKPRODCUST = SUM("CONSENSUSDEMANDQTY@WKPRODLOCCUST")

    And than use the COPY operator to copy that to CONSENSUSDEMAND@WKPRODCUST

    Pretty easy :-)

    You just need to make sure that your level WKPRODCUST has the same attributes than WKPRODLOCCUST except the location-specific ones

    Add comment
    10|10000 characters needed characters exceeded

    • Thanks Irmi- I guess it was as simple as that! Though I did have to add an intermediate key figure without UOM Conversion, because CONSENSUSDEMANDQTY had UoM conversion and was causing inflated values.

      Regards,

      Shivaditya

  • Oct 25, 2018 at 10:23 AM

    Hi Shivaditya

    it would be helpful if you had sketched out what YOU want to accomplish processwise...

    COPY and DISAGG originally had different target functionality, even though they have quite a big overlap, and both are intended for batch use only and not interactively.

    ADVSIM should ONLY be used in exceptional cases, as it does have a big impact on performance as it is running on the fly for whatever you have loaded interactively.

    In regards to versions or scenario, neither of the three is intended to copy between different scenarios / versions, but only within a specific scenario / version (except DISAGG when copying cross planning areas). To copy between different versions, you use the version management. To copy between different scenarios, you use the scenario management.

    As of today, DISAGG can not be used for scenarios and I am not sure if that technically would work.

    NOTE: The following is only speculation!!!:

    • As far as I know, scenarios don't store the whole data set which would duplicate the data as for versions, but only the delta if you have created a new scenario and CHANGE a value (but I am not 100% certain about this). That would be more difficult for DISAGG compared to COPY as it can copy on aggregated level and disaggregate according to the KF settings as you only have the delta

    So maybe you explain, what you want to achieve and why you think ADVSIM could be an alternative?

    Yours, Irmi

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Irmi,

      Thanks for your detailed inputs- appreciate as always!

      What our requirement is:

      Scenarios are for What-If analysis: for example, whats the impact on my supply plan when say moving production around. That is why SOP Operators can be run within a scenario to take modified inputs into account.

      Now we want to achieve this: we want to start on the Consensus Demand Plan Qty step: create a scenario for changes to Consensus Demand Plan Qty (kf CONSENSUSDEMANDQTY@WKPRODLOCCUST level) which is copied over using the DISAGG to CONSENSUSDEMAND (@WKPRODCUST level) as an input to heuristics. {standard Best Practices content in SAPIBP1}.

      However, since DISAGG cannot be run within the Scenario, this cannot be achieved. What are your thoughts on this?

      Regards,

      Shivaditya Singh

  • Oct 26, 2018 at 08:13 AM

    you do know that there is a new parameter in COPY that deals with the UoM conversion, so you DO NOT need another KF???

    Check the model config guide under COPY operator... Same for DISAGG

    Irmi

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 26, 2018 at 08:52 AM

    Hi Irmi, Hi Shivaditya,

    based on requests from several customers (e.g. improvement request 536) the DISAGG operator is enhanced in IBP 1902 to support scenarios. In general scenarios store only changes (Delta) as compared to the underlying planning version. When key figure values are copied in a user defined scenario with the COPY or DISAGG operator the values are stored in the scenario, even if they do not differ from the value of the underlying version.

    Kind Regards,
    Thomas

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 26, 2018 at 08:54 AM

    Sounds good! Thanks a lot Irmi and Thomas!

    Add comment
    10|10000 characters needed characters exceeded