This topic describes what is included in the Purchase spend analysis Microsoft Power BI content. It explains how to access the Power BI reports, and provides information about the data model and entities that are used to build the content.
The Purchase spend analysis Power BI content was designed to help purchasing managers and managers who are responsible for budgets keep an eye on purchase spending. Managers can analyze purchase spending in the following ways:
- Year-to-date purchase (by vendor group and individual vendors, procurement category and individual products, and vendor location)
- Year-over-year purchase change (by vendor group and procurement category)
The content uses purchase transactional data, and provides both an aggregate view of the company-wide purchase figures and a breakdown of purchase spending by vendor and product. Reports highlight changes in purchase spending over time. Therefore, the reports can be used to alert managers about positive and negative spending trends for individual vendors and products. Additionally, charts show purchase spending for different procurement categories and vendor groups. Therefore, category and regional managers can use the charts to help identify changes in spending behavior.
Accessing the Power BI content
If you're using Microsoft Dynamics 365 for Finance and Operations, Enterprise edition July 2017 update, the Purchase spend analysis Power BI content is shown on the Purchase and spend analysis page (Procurement and sourcing > Inquiries and reports > Purchase performance analysis > Purchase and spend analysis).
Metrics that are included in the Power BI content
The Purchase spend analysis Power BI content includes a report that consists of a set of metrics. These metrics are visualized as charts, tiles, and tables. The following table provides an overview of the visualizations.
|Purchase by vendor||
|Purchase by product||
|Purchase by period*||
|Purchase by vendor location||
|Purchase spend analysis by time||
|Purchase spend analysis by vendor||
* Purchase this year and last year, and growth by procurement category
Extending the Power BI content
By using the content packs that are available in Microsoft Dynamics Lifecycle Services (LCS), you can provide great analytics to people who don't sign in to Microsoft Dynamics 365. You can modify these content packs so that they include other reports or visuals, and then publish the content packs to your Power BI.com tenant for analysis.
You can find the Purchase spend analysis Power BI content in the Shared assets library in LCS. For more information about how to download the content and implement it in your organization, see Power BI content in LCS from Microsoft and your partners. To watch a demo that shows how to implement the Power BI content, see the Power BI content from Microsoft and your partners in Dynamics Lifecycle Services Office Mix.
Be sure to download the Purchase spend analysis content that applies to the version of Dynamics 365 that you're using.
If you're using Microsoft Dynamics 365 for Operations version 1611, KB 4011327 is a prerequisite for this Power BI content. After you sign in to LCS, you can access the KB at https://fix.lcs.dynamics.com/issue/results/?q=kb4011327.
Data model and entities
The following data is used to fill the report pages in the Purchase spend analysis Power BI content. This data is represented as aggregate measurements that are staged in the Entity store. The Entity store is a Microsoft SQL Server database that is optimized for analytics. For more information, see Overview of Power BI integration with Entity store.
The aggregate measurements in this content are the subset of aggregate measurements that were available in the Purchase Cube in Microsoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R3. To stage the cube’s aggregate measurements in the Entity store, you must make them deployable. For more information, see the procedure for staging aggregate measurements in the Entity store in Overview of Power BI integration with Entity store. The following key aggregate measurements are available directly from the Invoice lines entity and are used as the basis of the content.
|Entity||Key aggregate measurements||Data source||Field||Description|
|Invoice lines||Purchase||VendInvoiceTrans||SUM(LineAmountMST)||The amount in the accounting currency.|
The following table shows the key measurements in the content that are calculated from the Invoice lines entity.
|Purchase current year||Purchase current year = SUM('Invoice lines'[Purchase])|
|Purchase last year||Purchase last year = CALCULATE(SUM('Invoice lines'[Purchase]), SAMEPERIODLASTYEAR(Dates[Date]))|
|YOY purchase growth||YOY purchase growth = [Purchase current year] – [Purchase last year]|
The following key dimensions in the content are used as filters to slice the aggregate measurements, so that you can achieve more granularity and gain deeper analytical insights.
|Entity||Examples of attributes|
|Vendors||Vendor groups, Vendor country or regions, Vendor name|
|Products||Product number, Product name, Item groups name|
|Procurement categories||Procurement category, Procurement category names|
|Legal entities||Legal entity name|
|Dates||Dates, Year offset|
By default, the content shows data for the current calendar year. However, you can change the date filter in the report filters section. You can also change the company filter.