<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Avoid hard coding time periods in SAC Planning data actions in Data and Analytics Forum</title>
    <link>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13897690#M88</link>
    <description>&lt;P&gt;of course, you can make it as parameter as well if needed.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Oct 2024 07:25:44 GMT</pubDate>
    <dc:creator>William_Yu1</dc:creator>
    <dc:date>2024-10-14T07:25:44Z</dc:date>
    <item>
      <title>Avoid hard coding time periods in SAC Planning data actions</title>
      <link>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13896479#M85</link>
      <description>&lt;P&gt;We have the following data action to make a forecast for the next remaining months based on the index of the previous months. The index is calculated on past months. This index is used for the calculation of the future months. The below script will calculate the specific "PERIOD_FORECAST" (for example period 10 or 11 or 12) by multiplying the Budget for period 10 times the calculated index over the past 9 periods:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;// Context&lt;/DIV&gt;&lt;DIV&gt;MEMBERSET [d/Measures] = "AMOUNT"&lt;/DIV&gt;&lt;DIV&gt;MEMBERSET [d/BEDRIJFSNR] = %COMPANY_FILTER%&lt;/DIV&gt;&lt;DIV&gt;MEMBERSET [d/Date] = %PERIOD_FORECAST%&lt;/DIV&gt;&lt;DIV&gt;MEMBERSET [d/NIV4] = %RUBRIEK%&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;// Empty data&lt;/DIV&gt;&lt;DIV&gt;DATA([d/Date] = %PERIOD_FORECAST%) = 0&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;// Formules&lt;/DIV&gt;&lt;DIV&gt;DATA([d/Date] = %PERIOD_FORECAST%) =&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;((RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202301") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202302")&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202303") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202304")&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202305") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202306")&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202307") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202308")&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%, [d/Date] = "202309"))&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;/&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;(RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202301") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202302")&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202303") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202304")&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202305") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202306")&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202307") + RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202308")&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;+ RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = "202309")))&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;* RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%, [d/Date] = %PERIOD_FORECAST%)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;We would like to avoid the hard coded "2023xx" and replace it with a flexible solution&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2024 11:47:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13896479#M85</guid>
      <dc:creator>e_pos</dc:creator>
      <dc:date>2024-10-11T11:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: Avoid hard coding time periods in SAC Planning data actions</title>
      <link>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13897111#M86</link>
      <description>&lt;P&gt;Maybe you can try with something like this:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;MEMBERSET [d/Date] = PREVIOUS(9,"MONTH", %PERIOD_FORECAST%) TO %PERIOD_FORECAST%&lt;BR /&gt;MEMBERSET ...&lt;/P&gt;&lt;P&gt;VARIABLEMEMBER #PERIOD_VERSIE OF [d/Date]&lt;BR /&gt;VARIABLEMEMBER #PERIOD_VERSIE_VERGELIJK OF [d/Date]&lt;/P&gt;&lt;P&gt;DATA([d/Date] = #PERIOD_VERSIE) = RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE%)&lt;BR /&gt;DATA([d/Date] = #PERIOD_VERSIE_VERGELIJK) = RESULTLOOKUP([d/Version] = %BASELINE_INDEX_VERSIE_VERGELIJK%)&lt;/P&gt;&lt;P&gt;DATA( [d/Date] = %PERIOD_FORECAST%) = RESULTLOOKUP([d/Date] = #PERIOD_VERSIE)/RESULTLOOKUP([d/Date] = #PERIOD_VERSIE_VERGELIJK)&lt;/P&gt;</description>
      <pubDate>Sat, 12 Oct 2024 08:04:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13897111#M86</guid>
      <dc:creator>William_Yu1</dc:creator>
      <dc:date>2024-10-12T08:04:32Z</dc:date>
    </item>
    <item>
      <title>Re: Avoid hard coding time periods in SAC Planning data actions</title>
      <link>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13897660#M87</link>
      <description>&lt;P&gt;Thanks a lot for this very usefull information. Would it be possible to make the "9" in the code also as a parameter to make it flexible ? In the next month it should then be "10". Many Thanks !&lt;/P&gt;</description>
      <pubDate>Mon, 14 Oct 2024 06:55:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13897660#M87</guid>
      <dc:creator>e_pos</dc:creator>
      <dc:date>2024-10-14T06:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: Avoid hard coding time periods in SAC Planning data actions</title>
      <link>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13897690#M88</link>
      <description>&lt;P&gt;of course, you can make it as parameter as well if needed.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Oct 2024 07:25:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/data-and-analytics-forum/avoid-hard-coding-time-periods-in-sac-planning-data-actions/m-p/13897690#M88</guid>
      <dc:creator>William_Yu1</dc:creator>
      <dc:date>2024-10-14T07:25:44Z</dc:date>
    </item>
  </channel>
</rss>

