{"title":"Power BI Purchases app semantic model","url":"https://jonas-paprotka.de/docs/purchases-powerbi-app-semantic-model/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/purchases-powerbi-app-semantic-model, MicrosoftDocs/dynamics365smb-docs at 46907ac (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/purchases-powerbi-app-semantic-model","source":{"name":"Business Central application docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-docs","commit":"46907ace177f8d31deba47a2fdb57c3336e66252","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn about the fact and dimension tables and visible fields in the Power BI Purchases app semantic model for Business Central reports.","date":"2026-11-16","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Power BI Purchases app semantic model","slug":"power-bi-purchases-app-semantic-model","at":0,"chars":11087},{"level":2,"title":"Fact tables","slug":"fact-tables","at":555,"chars":10244},{"level":3,"title":"Purchase Budget","slug":"purchase-budget","at":835,"chars":242},{"level":4,"title":"Table definition","slug":"table-definition","at":918,"chars":159},{"level":3,"title":"Purchase Credit Lines","slug":"purchase-credit-lines","at":1077,"chars":509},{"level":4,"title":"Table definition","slug":"table-definition-1","at":1192,"chars":394},{"level":3,"title":"Purchase Invoice Lines","slug":"purchase-invoice-lines","at":1586,"chars":492},{"level":4,"title":"Table definition","slug":"table-definition-2","at":1696,"chars":382},{"level":3,"title":"Purchase Lines","slug":"purchase-lines","at":2078,"chars":1000},{"level":4,"title":"Table definition","slug":"table-definition-3","at":2174,"chars":904},{"level":3,"title":"Purchase value entries","slug":"purchase-value-entries","at":3078,"chars":851},{"level":4,"title":"Table definition","slug":"table-definition-4","at":3182,"chars":747},{"level":3,"title":"Dimension tables","slug":"dimension-tables","at":3929,"chars":262},{"level":3,"title":"Documents","slug":"documents","at":4191,"chars":515},{"level":4,"title":"Table definition","slug":"table-definition-5","at":4367,"chars":339},{"level":3,"title":"G/L Accounts","slug":"gl-accounts","at":4706,"chars":669},{"level":4,"title":"Table definition","slug":"table-definition-6","at":4780,"chars":595},{"level":3,"title":"Item","slug":"item","at":5375,"chars":541},{"level":4,"title":"Table definition","slug":"table-definition-7","at":5450,"chars":466},{"level":3,"title":"Item Category","slug":"item-category","at":5916,"chars":311},{"level":4,"title":"Table definition","slug":"table-definition-8","at":5993,"chars":234},{"level":3,"title":"Location","slug":"location","at":6227,"chars":354},{"level":4,"title":"Table definition","slug":"table-definition-9","at":6294,"chars":287},{"level":3,"title":"Project","slug":"project","at":6581,"chars":1205},{"level":4,"title":"Table definition","slug":"table-definition-10","at":6646,"chars":1140},{"level":3,"title":"Purchase Budget Name","slug":"purchase-budget-name","at":7786,"chars":328},{"level":4,"title":"Table definition","slug":"table-definition-11","at":7873,"chars":241},{"level":3,"title":"Purchaser","slug":"purchaser","at":8114,"chars":278},{"level":4,"title":"Table definition","slug":"table-definition-12","at":8195,"chars":197},{"level":3,"title":"Reason codes","slug":"reason-codes","at":8392,"chars":302},{"level":4,"title":"Table definition","slug":"table-definition-13","at":8468,"chars":226},{"level":3,"title":"Resources","slug":"resources","at":8694,"chars":611},{"level":4,"title":"Table definition","slug":"table-definition-14","at":8762,"chars":543},{"level":3,"title":"Type","slug":"type","at":9305,"chars":469},{"level":4,"title":"Table definition","slug":"table-definition-15","at":9418,"chars":356},{"level":3,"title":"Vendor","slug":"vendor","at":9774,"chars":1025},{"level":4,"title":"Table definition","slug":"table-definition-16","at":9837,"chars":962},{"level":2,"title":"Related information","slug":"related-information","at":10799,"chars":288}],"text":"# Power BI Purchases app semantic model\n> APPLIES TO: Generally available in Business Central 2024 release wave 2.\nThe semantic model in the Power BI Purchases app uses a Star Schema Model<https://learn.microsoft.com/power-bi/guidance/star-schema#star-schema-overview>.\nThe fact tables hold details about individual transactions, like purchase budgets, purchase lines, and posted purchase entries from Business Central.\nThe dimension tables add context and attributes to the transactional data, including vendor, item, project, and purchaser information.\n## Fact tables\nFact tables store transactional data and support summarizations such as SUM, AVG, COUNT, and more. The Power BI Purchases app includes several fact tables:\n #purchase-budget\n #purchase-credit-lines\n #purchase-invoice-lines\n #purchase-lines\n #purchase-value-entries\n### Purchase Budget\nThe app uses data from the following table:\n Item Budget Entry\n#### Table definition\nPower BI field name|Business Central field name|Description\nEntry No.|Entry No.|Specifies the entry number of the purchase budget entry.\n### Purchase Credit Lines\nThe app uses data from the following tables:\n Purch. Cr. Memo Line\n Purch. Cr. Memo Hdr.\n#### Table definition\nPower BI field name|Business Central field name|Description\nDescription|Description|Specifies a description of the posted purchase credit memo line.\nPurchase Credit Line No.|Line No.|Specifies the line number of the posted purchase credit memo line.\nExprected Receipt Date|Expected Receipt Date|Specifies the expected receipt date on the posted purchase credit memo line.\n### Purchase Invoice Lines\nThe app uses data from the following tables:\n Purch. Inv. Line\n Purch. Inv. Header\n#### Table definition\nPower BI field name|Business Central field name|Description\nDescription|Description|Specifies a description of the posted purchase invoice line.\nPurchase Invoice Line No.|Line No.|Specifies the line number of the posted purchase invoice line.\nExpected Receipt Date|Expected Receipt Date|Specifies the expected receipt date on the posted purchase invoice line.\n### Purchase Lines\nThe app uses data from the following tables:\n Purchase Header\n Purchase Line\n#### Table definition\nPower BI field name|Business Central field name|Description\nOrder Date|Order Date|Specifies the date when the purchase order was created.\nDocument Date|Document Date|Specifies the date when the purchase document was created.\nDue Date|Due Date|Specifies when the purchase invoice is due for payment.\nDescription|Description|Specifies a description of the purchase line.\nPurchase Line No.|Line No.|Specifies the line number of the purchase line.\nPlanned Receipt Date|Planned Receipt Date|Specifies the date when the item is planned to arrive in inventory.\nExpected Receipt Date|Expected Receipt Date|Specifies the date when you expect to receive the items.\nPromised Receipt Date|Promised Receipt Date|Specifies the date that the vendor promised to deliver the order.\nRequested Receipt Date|Requested Receipt Date|Specifies the date that you requested the vendor to deliver the order.\n### Purchase value entries\nThe app uses data from the following tables:\n Value Entry\n Item Ledger Entry\n#### Table definition\nPower BI field name|Business Central field name|Description\nItem Ledger Entry No.|Entry No.|Specifies the entry number of the related item ledger entry.\nValue Entry No.|Entry No.|Specifies the entry number of the value entry.\nValue Entry Type|Entry Type|Specifies the type of value entry.\nDocument No.|Document No.|Specifies the document number of the value entry.\nDocument Type|Document Type|Specifies the type of document that created the value entry.\nItem Ledger Entry Type|Entry Type|Specifies the entry type of the related item ledger entry.\nAdjustment|Adjustment|Specifies whether the value entry is an adjustment.\nCapacity Ledger Entry No.|Capacity Ledger Entry No.|Specifies the related capacity ledger entry number.\n### Dimension tables\nThe star schema model uses dimension tables and you can filter and group data.\n #documents\n G/L Accounts<#gl-accounts>\n #item\n #item-category\n #location\n #project\n #purchase-budget-name\n #purchaser\n #reason-codes\n #resources\n #type\n #vendor\n### Documents\nThe app builds this table in the semantic model from the following tables:\n Purchase Credit Lines\n Purchase Invoice Lines\n Purchase Lines\n Purchase Value Entries\n#### Table definition\nPower BI field name|Business Central field name|Description\nDocument No.|Document No.|Specifies the document number from the source purchase table.\nDocument Type|Document Type|Specifies the document type from the source purchase table.\nSource Table|-|Specifies the semantic model table that contributed the document.\n### G/L Accounts\nThe app uses data from the following table:\n G/L Account\n#### Table definition\nPower BI field name|Business Central field name|Description\nG/L Account No.|No.|Specifies the number of the general ledger account.\nG/L Account Name|Name|Specifies the name of the general ledger account.\nG/L Account Type|Account Type|Specifies the purpose of the account, such as Posting, Heading, Total, Begin-Total, or End-Total.\nG/L Account Income/Balance|Income/Balance|Specifies whether the account is an income statement account or a balance sheet account.\nG/L Account No. and Name|-|Specifies a combination of the general ledger account number and name in Power BI.\n### Item\nThe app uses data from the following tables:\n Item\n Item Category\n#### Table definition\nPower BI field name|Business Central field name|Description\nItem No. & Description|-|Specifies a combination of item number and description in Power BI.\nItem No.|No.|Specifies the number of the item.\nItem Description|Description|Specifies the description of the item.\nItem Unit Cost (LCY)|Unit Cost|Specifies the unit cost of the item in the local currency.\nItem Category Description|Description|Specifies the description of the item category.\n### Item Category\nThe app uses data from the following table:\n Item Category\n#### Table definition\nPower BI field name|Business Central field name|Description\nItem Category Code|Code|Specifies the code for the item category.\nItem Category Description|Description|Specifies the description of the item category.\n### Location\nThe app uses data from the following table:\n Location\n#### Table definition\nPower BI field name|Business Central field name|Description\nLocation Code|Code|Specifies the code for the location.\nLocation Name|Name|Specifies the name of the location.\nLocation Adjustment Bin Code|-|Specifies a location-specific adjustment bin code in Power BI.\n### Project\nThe app uses data from the following table:\n Project\n#### Table definition\nPower BI field name|Business Central field name|Description\nProject No.|No.|Specifies the number of the project.\nProject Description|Description|Specifies a short description of the project.\nProject Bill to Customer No.|Bill-to Customer No.|Specifies the customer that the project is billed to.\nProject Creation Date|Creation Date|Specifies the date when the project was created.\nProject Starting Date|Starting Date|Specifies the date when the project starts.\nProject Ending Date|Ending Date|Specifies the date when the project is expected to be completed.\nProject Status|Status|Specifies the current status of the project.\nProject Posting Group|Project Posting Group|Specifies the posting group that links project transactions to the appropriate general ledger accounts.\nProject Blocked|Blocked|Specifies whether the project is blocked from posting.\nProject Project Manager|Project Manager|Specifies the person who's assigned to manage the project.\nProject Complete|Complete|Specifies whether the project is complete.\nProject No. & Description|-|Specifies a combination of project number and description in Power BI.\n### Purchase Budget Name\nThe app uses data from the following table:\n Item Budget Name\n#### Table definition\nPower BI field name|Business Central field name|Description\nPurchase Budget Name|Name|Specifies the name of the purchase budget.\nPurchase Budget Description|Description|Specifies the description of the purchase budget.\n### Purchaser\nThe app uses data from the following table:\n Salesperson/Purchaser\n#### Table definition\nPower BI field name|Business Central field name|Description\nPurchaser Code|Code|Specifies the code for the purchaser.\nPurchaser Name|Name|Specifies the name of the purchaser.\n### Reason codes\nThe app uses data from the following table:\n Return Reason\n#### Table definition\nPower BI field name|Business Central field name|Description\nReturn Reason Code|Code|Specifies the return reason code.\nReturn Reason Description|Description|Specifies the description of the return reason.\n### Resources\nThe app uses data from the following table:\n Resource\n#### Table definition\nPower BI field name|Business Central field name|Description\nResource No.|No.|Specifies the number of the resource.\nResource Name|Name|Specifies the name of the resource.\nResource Base Unit of Measure|Base Unit of Measure|Specifies the base unit used to measure the resource.\nResource Unit Cost|Unit Cost|Specifies the cost of one unit of the resource.\nResource Unit Price|Unit Price|Specifies the price of one unit of the resource.\nResource No. and Name|-|Specifies a combination of resource number and name in Power BI.\n### Type\nThe app builds this table in the semantic model from the following tables:\n Item\n Resource\n G/L Account\n#### Table definition\nPower BI field name|Business Central field name|Description\nType|-|Specifies the type of the object, either item, resource, or general ledger account.\nType Key|-|Specifies a concatenated value generated by combining the No. and Type columns.\nNo.|No. or Account No.|Specifies the code of the item, resource, or general ledger account.\n### Vendor\nThe app uses data from the following table:\n Vendor\n#### Table definition\nPower BI field name|Business Central field name|Description\nVendor No. & Name|-|Specifies a combination of vendor number and vendor name in Power BI.\nVendor No.|No.|Specifies the number of the vendor.\nVendor Name|Name|Specifies the name of the vendor.\nVendor Address|Address|Specifies the street address of the vendor.\nVendor Address 2|Address 2|Specifies additional address information.\nVendor City|City|Specifies the city of the vendor.\nVendor Post Code|Post Code|Specifies the postal code.\nVendor State|County|Specifies the state, province, or county as part of the address.\nVendor Country/Region Code|Country/Region Code|Specifies the country/region of the address.\nVendor Posting Group|Vendor Posting Group|Specifies the vendor posting group.\n> TIP\n> You can easily track the KPIs that the Power BI reports display against your business objectives. See Track your business KPIs with Power BI metrics<track-kpis-with-power-bi-metrics>.\n## Related information\nPurchases KPI overview<purchases-powerbi-kpis>\nPower BI purchasing app<purchases-powerbi-app>\nUse Power BI with Business Central<admin-powerbi>\nFind free e-learning modules for Business Central here<https://learn.microsoft.com/training/dynamics365/business-central>"}