<?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: Price Variance Actuals vs Budget in separate tables (calculated at Product &amp;amp; Customer Level) in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Price-Variance-Actuals-vs-Budget-in-separate-tables-calculated/m-p/4748331#M181834</link>
    <description>&lt;P&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="1297250" data-lia-user-login="pmxgs" class="lia-mention lia-mention-user"&gt;pmxgs&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are, but I would&amp;nbsp;&lt;SPAN&gt;stick with the UNION approach since&amp;nbsp;&lt;SPAN&gt;you’re calculating at a higher level (e.g., product &amp;amp; customer) and already using prod-cust_key,&amp;nbsp;&lt;/SPAN&gt;unless you have a business constraint that prevents merging the tables...&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jun 2025 11:15:06 GMT</pubDate>
    <dc:creator>MasonMA</dc:creator>
    <dc:date>2025-06-30T11:15:06Z</dc:date>
    <item>
      <title>Price Variance Actuals vs Budget in separate tables (calculated at Product &amp; Customer Level)</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Price-Variance-Actuals-vs-Budget-in-separate-tables-calculated/m-p/4748303#M181829</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Presently, my data is in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;single table&lt;/STRONG&gt;, where I have the typical columns, like date, product, customer, sales, volume.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Scenario&lt;/TD&gt;&lt;TD&gt;Customer&lt;/TD&gt;&lt;TD&gt;Product&lt;/TD&gt;&lt;TD&gt;Volume&lt;/TD&gt;&lt;TD&gt;Sales&lt;/TD&gt;&lt;TD&gt;prod-cust_key&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Actual&lt;/TD&gt;&lt;TD&gt;A&lt;/TD&gt;&lt;TD&gt;p1&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;TD&gt;10&lt;/TD&gt;&lt;TD&gt;Ap1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Actual&lt;/TD&gt;&lt;TD&gt;A&lt;/TD&gt;&lt;TD&gt;p2&lt;/TD&gt;&lt;TD&gt;7&lt;/TD&gt;&lt;TD&gt;15&lt;/TD&gt;&lt;TD&gt;Ap2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Actual&lt;/TD&gt;&lt;TD&gt;B&lt;/TD&gt;&lt;TD&gt;p1&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;23&lt;/TD&gt;&lt;TD&gt;Bp1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Actual&lt;/TD&gt;&lt;TD&gt;B&lt;/TD&gt;&lt;TD&gt;p1&lt;/TD&gt;&lt;TD&gt;7&lt;/TD&gt;&lt;TD&gt;16&lt;/TD&gt;&lt;TD&gt;Bp1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Budget&lt;/TD&gt;&lt;TD&gt;A&lt;/TD&gt;&lt;TD&gt;p1&lt;/TD&gt;&lt;TD&gt;5&lt;/TD&gt;&lt;TD&gt;10&lt;/TD&gt;&lt;TD&gt;Ap1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Budget&lt;/TD&gt;&lt;TD&gt;A&lt;/TD&gt;&lt;TD&gt;p2&lt;/TD&gt;&lt;TD&gt;7&lt;/TD&gt;&lt;TD&gt;15&lt;/TD&gt;&lt;TD&gt;Ap2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Budget&lt;/TD&gt;&lt;TD&gt;B&lt;/TD&gt;&lt;TD&gt;p1&lt;/TD&gt;&lt;TD&gt;9&lt;/TD&gt;&lt;TD&gt;23&lt;/TD&gt;&lt;TD&gt;Bp1&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Budget&lt;/TD&gt;&lt;TD&gt;B&lt;/TD&gt;&lt;TD&gt;p1&lt;/TD&gt;&lt;TD&gt;7&lt;/TD&gt;&lt;TD&gt;16&lt;/TD&gt;&lt;TD&gt;Bp1&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With this data setup, so far I've used the following approach to calculate variances between actuals and budget (at customer &amp;amp; product level).&lt;/P&gt;&lt;P&gt;Volume Act=&amp;nbsp;calculate (volume,phase="Actuals ")&lt;/P&gt;&lt;P&gt;Volume Bud=&amp;nbsp;calculate (volume,phase="Bud ")&lt;/P&gt;&lt;P&gt;Avg Price Act = calculate (sales,phase="Actuals ")/Volume Act&lt;/P&gt;&lt;P&gt;Avg Price Bud = calculate (sales,phase="Budget ")/Volume Bud&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Price Variance=sumx(values(prod-cust_key),(Avg Price Act-Avg Price Bud)*Volume_Act)&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now I will &lt;STRONG&gt;have two separate tables&lt;/STRONG&gt;, one for actuals and another one for Budget (actuals has finer granularity for product codes, etc), but I want to keep calculating price variance at the same level (main product &amp;amp; customer level).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm thinking of creating a single table using UNION (adjusting the budget table to have the same structure as actuals), so that I keep calculating price variances the same way.&lt;BR /&gt;&lt;BR /&gt;I would like to know if there is an alternative way of reaching the same goal, without having to join both tables using UNION.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;pm&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 10:53:25 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Price-Variance-Actuals-vs-Budget-in-separate-tables-calculated/m-p/4748303#M181829</guid>
      <dc:creator>pmxgs</dc:creator>
      <dc:date>2025-06-30T10:53:25Z</dc:date>
    </item>
    <item>
      <title>Re: Price Variance Actuals vs Budget in separate tables (calculated at Product &amp; Customer Level)</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Price-Variance-Actuals-vs-Budget-in-separate-tables-calculated/m-p/4748310#M181831</link>
      <description>&lt;P&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="1297250" data-lia-user-login="pmxgs" class="lia-mention lia-mention-user"&gt;pmxgs&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Create relationships between Actuals and ProductCustomer, and Budget and ProductCustomer on Customer and Product.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Define measures to calculate the actual and budget volumes and sales.&lt;/P&gt;
&lt;P&gt;Volume_Act = CALCULATE(SUM(Actuals[Volume]))&lt;BR /&gt;Sales_Act = CALCULATE(SUM(Actuals[Sales]))&lt;BR /&gt;Volume_Bud = CALCULATE(SUM(Budget[Volume]))&lt;BR /&gt;Sales_Bud = CALCULATE(SUM(Budget[Sales]))&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Define measures to calculate the average prices for actuals and budget.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Avg_Price_Act = DIVIDE([Sales_Act], [Volume_Act])&lt;BR /&gt;Avg_Price_Bud = DIVIDE([Sales_Bud], [Volume_Bud])&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Finally, define a measure to calculate the price variance.&lt;/P&gt;
&lt;P&gt;Price_Variance = SUMX(&lt;BR /&gt;VALUES(ProductCustomer[prod-cust_key]),&lt;BR /&gt;([Avg_Price_Act] - [Avg_Price_Bud]) * [Volume_Act]&lt;BR /&gt;)&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 10:59:24 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Price-Variance-Actuals-vs-Budget-in-separate-tables-calculated/m-p/4748310#M181831</guid>
      <dc:creator>bhanu_gautam</dc:creator>
      <dc:date>2025-06-30T10:59:24Z</dc:date>
    </item>
    <item>
      <title>Re: Price Variance Actuals vs Budget in separate tables (calculated at Product &amp; Customer Level)</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Price-Variance-Actuals-vs-Budget-in-separate-tables-calculated/m-p/4748331#M181834</link>
      <description>&lt;P&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="1297250" data-lia-user-login="pmxgs" class="lia-mention lia-mention-user"&gt;pmxgs&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are, but I would&amp;nbsp;&lt;SPAN&gt;stick with the UNION approach since&amp;nbsp;&lt;SPAN&gt;you’re calculating at a higher level (e.g., product &amp;amp; customer) and already using prod-cust_key,&amp;nbsp;&lt;/SPAN&gt;unless you have a business constraint that prevents merging the tables...&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 11:15:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/Price-Variance-Actuals-vs-Budget-in-separate-tables-calculated/m-p/4748331#M181834</guid>
      <dc:creator>MasonMA</dc:creator>
      <dc:date>2025-06-30T11:15:06Z</dc:date>
    </item>
  </channel>
</rss>

