Skip to content
D365 Reference

VendGroup

group

Vendor group master — the posting, payment-term, and number-sequence defaults shared by every vendor in the group

Module: Procurement & SourcingCompany-partitioned (DataAreaId)
What the badges mean
main
Table group: how F&O categorizes the table's role — main entity, group/header, transaction, worksheet header, worksheet line, reference, parameter, or framework.
Shared across companies
The table carries no DataAreaId— rows aren’t partitioned per company, so a query never needs (and can’t use) a company filter here (see the quirks guide).
Date-effective
The table carries a ValidFrom/ValidTo effectivity window — a join without a date filter multiplies every key by its history (see the quirks guide).
In field listings, K marks a key field.

Fields

6 fields · 1 key

6 fields.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 6 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyVendGroupVendGroupIdThe vendor group code — the natural keystring10
NameGroup descriptionstring60
PaymTermIdDefault terms of payment for vendors in the groupstring10
ClearingPeriodDefault payment clearing period for the groupstring10
TaxGroupIdDefault sales tax group for the groupstring10
VendAccountNumSeqRecIdRecId of the number sequence new vendor accounts in the group are drawn fromint64

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading VendGroup on Databricks — enums are decoded, 1900-01-01 dates are wrapped to NULL, and the DataAreaId anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters

3 parameters not filled: <catalog>, <schema>, <company>

-- ============================================================
-- Table  : VendGroup Vendor group master — the posting, payment-term, and number-sequence defaults shared by every vendor in the group
-- Purpose: Column-selected read of VendGroup — auto-generated from field metadata
-- Grain  : One row per company (dataareaid) + VendGroup
-- Notes  : Auto-generated skeleton for Synapse Link / Fabric Link-landed F&O data (lowercase column names). Enums decoded inline where verified; datetimes stored in UTC; 1900-01-01 dates are sentinels mapped to NULL. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
  v.vendgroup AS "The vendor group code — the natural key",
  v.name AS "Group description",
  v.paymtermid AS "Default terms of payment for vendors in the group",
  v.clearingperiod AS "Default payment clearing period for the group",
  v.taxgroupid AS "Default sales tax group for the group",
  v.vendaccountnumseq AS "RecId of the number sequence new vendor accounts in the group are drawn from"
FROM <catalog>.<schema>.vendgroup v
WHERE
  v.dataareaid = '<company>'
ORDER BY v.vendgroup;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • VendTableVendGroupforeign key · N:1
    ON vendtable.vendgroup = vendgroup.vendgroup AND vendtable.dataareaid = vendgroup.dataareaid

Data Entities That Expose This Table

No data-entity mappings populated for this table yet.

Browse more procurement tables

More Procurement & Sourcing tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Microsoft. Microsoft, Dynamics 365, and Microsoft Fabric are trademarks of the Microsoft group of companies.