Skip to content
D365 Reference

CustPackingSlipJour

transaction

Posted packing-slip header — one row per shipment document posted against a sales order, with delivery date, ship-to address reference, and carrier details

Module: Sales & MarketingCompany-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

17 fields · 3 key

17 fields.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 17 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyPackingSlipIdPackingSlipIdThe packing-slip number; unique together with SalesId and DeliveryDatestring20
KeySalesIdSalesIdSales order the shipment was posted against; part of the composite keystring20
KeyDeliveryDateDate the shipment was posted — the primary analysis date for outbound-shipment reporting; part of the composite keydate
OrderAccountCustAccountCustomer account that placed the shipped orderstring20
InvoiceAccountCustAccountCustomer account the shipment will be invoiced tostring20
DeliveryPostalAddressRecIdRecId of the ship-to address in LogisticsPostalAddressint64
DlvModeMode of delivery for the shipmentstring10
DlvTermTerms of delivery for the shipmentstring10
QtyTotal quantity shipped across the packing-slip linesreal
VolumeTotal volume of the shipmentreal
WeightTotal weight of the shipmentreal
inventLocationIdInventLocationIdWarehouse the shipment left from (note the CDM lowercase-i casing)string10
CustomerRefThe customer's own reference for the orderstring
PurchaseOrderThe customer's purchase order number for the shipped orderstring
DocumentDateDocument date printed on the packing slip, when it differs from the posting date; unset rows carry the 1900-01-01 sentineldate
LedgerVoucherLedger voucher for the shipment posting, when packing slips post to the ledgerstring20
PrintedWhether the packing-slip document has been printedenum

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading CustPackingSlipJour 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>, <SalesId>, <DATE_FROM>, <DATE_TO>

-- ============================================================
-- Table  : CustPackingSlipJour Posted packing-slip header — one row per shipment document posted against a sales order, with delivery date, ship-to address reference, and carrier details
-- Purpose: Column-selected read of CustPackingSlipJour — auto-generated from field metadata
-- Grain  : One row per company (dataareaid) + PackingSlipId + SalesId + DeliveryDate
-- 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
  c.packingslipid AS "The packing-slip number; unique together with SalesId and DeliveryDate",
  c.salesid AS "Sales order the shipment was posted against; part of the composite key",
  c.deliverydate AS "Date the shipment was posted — the primary analysis date for outbound-shipment reporting; part of the composite key",
  c.orderaccount AS "Customer account that placed the shipped order",
  c.invoiceaccount AS "Customer account the shipment will be invoiced to",
  c.deliverypostaladdress AS "RecId of the ship-to address in LogisticsPostalAddress",
  c.dlvmode AS "Mode of delivery for the shipment",
  c.dlvterm AS "Terms of delivery for the shipment",
  c.qty AS "Total quantity shipped across the packing-slip lines",
  c.volume AS "Total volume of the shipment",
  c.weight AS "Total weight of the shipment",
  c.inventlocationid AS "Warehouse the shipment left from (note the CDM lowercase-i casing)",
  c.customerref AS "The customer's own reference for the order",
  c.purchaseorder AS "The customer's purchase order number for the shipped order",
  CASE WHEN CAST(c.documentdate AS DATE) = DATE '1900-01-01' THEN NULL ELSE CAST(c.documentdate AS DATE) END AS "Document date printed on the packing slip, when it differs from the posting date; unset rows carry the 1900-01-01 sentinel",  -- 1900-01-01 sentinel → NULL
  c.ledgervoucher AS "Ledger voucher for the shipment posting, when packing slips post to the ledger",
  c.printed AS "Whether the packing-slip document has been printed"  -- enum: decode c.printed via GlobalOptionsetMetadata join — see quirks guide #enums
FROM <catalog>.<schema>.custpackingslipjour c
-- Resolve LogisticsPostalAddress (via DeliveryPostalAddress): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.logisticspostaladdress log ON log.recid = c.deliverypostaladdress
WHERE
  c.dataareaid = '<company>'
  -- AND c.salesid = '<SalesId>'
  -- AND c.deliverydate >= '<DATE_FROM>'  -- yyyy-MM-dd (UTC)
  -- AND c.deliverydate <= '<DATE_TO>'  -- yyyy-MM-dd (UTC)
ORDER BY c.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

  • CustPackingSlipJourCustTableforeign key · N:1
    ON custpackingslipjour.orderaccount = custtable.accountnum AND custpackingslipjour.dataareaid = custtable.dataareaid
  • CustPackingSlipJourLogisticsPostalAddressRecId ref · N:1
    ON custpackingslipjour.deliverypostaladdress = logisticspostaladdress.recid

Data Entities That Expose This Table

No research-verified standard export entity for posted packing-slip headers — land the raw table.

Browse more sales tables

More Sales & Marketing 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.