D365 Reference
VendPackingSlipJour
transactionPosted product receipt (packing slip) header — one row per receipt posted against a purchase order, the record of when goods physically arrived
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/ValidToeffectivity 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.
Used in the library
KPI definitions
Dashboard patterns
Fields
15 fields · 2 key
15 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | PackingSlipId | The vendor's packing slip / product receipt number | string | 20 | ||
| Key | PurchId | PurchId | Purchase order the receipt was posted against — the same slip number can recur across vendors, so the order is part of the key | string | 20 | |
| DeliveryDate | Date the goods were received; the primary analysis date | date | ||||
| OrderAccount | VendAccount | Vendor account the goods were ordered from | string | 20 | ||
| InvoiceAccount | VendAccount | Vendor account the eventual invoice settles against | string | 20 | ||
| DocumentDate | The vendor's document date; unset rows carry the 1900-01-01 sentinel | date | ||||
| DeliveryName | Name at the receiving address | string | 60 | |||
| DlvMode | Mode of delivery for the receipt | string | 10 | |||
| DlvTerm | Delivery terms for the receipt | string | 10 | |||
| PurchaseType | Kind of order the receipt belongs to | enum | ||||
| Requester | RecId | RecId of the worker who requested the goods | int64 | |||
| InterCompanySalesId | Intercompany sales order that shipped the goods, when sourced from a sister company | string | 20 | |||
| FreightSlipNum | Freight slip number from the carrier | string | 20 | |||
| NumberSequenceGroup | Number sequence group the receipt number was drawn from | string | 10 | |||
| DefaultDimension | RecId | RecId of the receipt's default financial-dimension value set in DimensionAttributeValueSet | int64 |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading VendPackingSlipJour 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
6 parameters not filled: <catalog>, <schema>, <company>, <PurchId>, <DATE_FROM>, <DATE_TO>
-- ============================================================
-- Table : VendPackingSlipJour Posted product receipt (packing slip) header — one row per receipt posted against a purchase order, the record of when goods physically arrived
-- Purpose: Column-selected read of VendPackingSlipJour — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + PackingSlipId + PurchId
-- 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.packingslipid AS "The vendor's packing slip / product receipt number",
v.purchid AS "Purchase order the receipt was posted against — the same slip number can recur across vendors, so the order is part of the key",
v.deliverydate AS "Date the goods were received; the primary analysis date",
v.orderaccount AS "Vendor account the goods were ordered from",
v.invoiceaccount AS "Vendor account the eventual invoice settles against",
CASE WHEN CAST(v.documentdate AS DATE) = DATE '1900-01-01' THEN NULL ELSE CAST(v.documentdate AS DATE) END AS "The vendor's document date; unset rows carry the 1900-01-01 sentinel", -- 1900-01-01 sentinel → NULL
v.deliveryname AS "Name at the receiving address",
v.dlvmode AS "Mode of delivery for the receipt",
v.dlvterm AS "Delivery terms for the receipt",
v.purchasetype AS "Kind of order the receipt belongs to", -- enum: decode v.purchasetype via GlobalOptionsetMetadata join — see quirks guide #enums
v.requester AS "RecId of the worker who requested the goods",
v.intercompanysalesid AS "Intercompany sales order that shipped the goods, when sourced from a sister company",
v.freightslipnum AS "Freight slip number from the carrier",
v.numbersequencegroup AS "Number sequence group the receipt number was drawn from",
v.defaultdimension AS "RecId of the receipt's default financial-dimension value set in DimensionAttributeValueSet"
FROM <catalog>.<schema>.vendpackingslipjour v
WHERE
v.dataareaid = '<company>'
-- AND v.purchid = '<PurchId>'
-- AND v.deliverydate >= '<DATE_FROM>' -- yyyy-MM-dd (UTC)
-- AND v.deliverydate <= '<DATE_TO>' -- yyyy-MM-dd (UTC)
ORDER BY v.packingslipid;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
ON vendpackingslipjour.purchid = purchtable.purchid AND vendpackingslipjour.dataareaid = purchtable.dataareaid
Data Entities That Expose This Table
No clean standard export entity for posted product receipts — land the raw table.
More Procurement & Sourcing tables
- VendTableVendor master — one row per vendor account, with the RecId link to its global-address-book party
- PurchLinePurchase order line — one row per order line; the core buy-side transaction, joined to its header by PurchId
- PurchTablePurchase order header — one row per order carrying vendor, status, and delivery date
- VendGroupVendor group master — the posting, payment-term, and number-sequence defaults shared by every vendor in the group
- VendInvoiceJourPosted vendor invoice header — one row per posted AP invoice, carrying totals, due date, cash-discount terms, and the ledger voucher
- VendInvoiceTransPosted vendor invoice line — one row per invoiced line with quantity, price, and the links back to its purchase order and inventory movements