> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/entwicklerdokumentationen-business-central-dhl-connector/dhl-connector-entwicklerdokumentation/tabellenreferenz/72242953-soudhl-package-header.md).

# 72242953 SOUDHL Package Header

## Zweck

Zentraler Paketkopf für Quellbeleg, Box, Gewicht, Empfänger-Snapshot, Billing, Tracking, Label, Customs und Kartonbuchungsstatus. `DataClassification = CustomerContent`.

## Felder

### Identität, Paket und DHL-Ergebnis

* `1 ID: BigInteger` – AutoIncrement
* `2 Order No: Code[20]` – Auftrag oder Warehouse Shipment gemäß Document Type
* `3 Box Code: Code[20]` → `SOUDHL Box.Code`; OnValidate setzt Billing zurück, weist Default zu und kopiert Boxmaße
* Feld-ID 4 ist frei
* `5 Package Date: DateTime`
* `6 Weight UOM: Text[10]` – Default `g`
* `7 Weight: Integer` – Gesamtgewicht in Gramm
* `8 Uploaded: Boolean`
* `9 Upload Date: DateTime`
* `10 DHL Shipment No: Text[100]`
* `11 DHL Routing Code: Text[100]` – bei Express derzeit auch für Package Tracking verwendet
* `12 Label PDF: Blob`
* `13 Print Format: Text[100]`
* `14 Label Image: Media`
* `15 Document Type: Enum SOUDHL Document Type` – OnValidate leert den Empfänger-Snapshot
* `16 Posted Whse. Shipment No.: Code[20]` → Posted Whse. Shipment Header; nicht editierbar

### Empfänger-Snapshot

* `17 Recipient Name: Text[100]`
* `18 Recipient Address: Text[100]`
* `19 Recipient Address 2: Text[50]`
* `20 Recipient City: Text[30]`
* `21 Recipient Post Code: Code[20]`
* `22 Recipient Country/Region Code: Code[10]` → Country/Region
* `23 Recipient Contact: Text[100]`
* `24 Recipient Phone No.: Text[30]`
* `25 Recipient Email: Text[80]`

### Billing, Customs, Sales Shipment und Maße

* `26 Billing Number Code: Code[20]` → aktive SOUDHL Billing Number
* `27 Customs Doc PDF: Blob` – Parcel-DE-CN23
* `28 Posted Sales Shipment No.: Code[20]` → Sales Shipment Header; nicht editierbar
* `29 Custom Dimensions: Boolean` – false ruft `ApplyBoxDimensions` auf
* `30 Dimension Unit: Enum SOUDHL Dimension Unit` – Default cm
* `31 Length: Decimal` – 0:5, MinValue 0
* `32 Width: Decimal` – 0:5, MinValue 0
* `33 Height: Decimal` – 0:5, MinValue 0

### Kartonbestand

* `34 Inventory Posting Status: Enum SOUDHL Inventory Post Status` – nicht editierbar
* `35 Inventory Posting Error: Text[2048]` – nicht editierbar
* `36 Inventory Posted At: DateTime` – nicht editierbar
* `37 Item Ledger Entry No.: Integer` → Item Ledger Entry; nicht editierbar
* `38 Inventory Posting Started At: DateTime` – nicht editierbar

## Schlüssel

* Primary Key `(ID, Order No)` clustered
* `DocumentKey (Document Type, Order No)`
* `PostedWhseShptKey (Posted Whse. Shipment No.)`
* `PostedSalesShptKey (Posted Sales Shipment No.)`

## Trigger

`OnDelete` ruft `SOUDHL Customs Mgt.DeleteCustomsForPackage(ID, Order No)` auf. Package Lines werden nicht durch diesen Tabellen-Trigger gelöscht; Pages und Managementlogik müssen sie mitbereinigen.

## Öffentliche Table-Procedures

### `UpdateTotalWeight()`

Filtert Package Lines über Header ID und Order No., summiert `Quantity × Weight` in kg und schreibt gerundete Gramm sowie UOM `g`; anschließend `Modify()`.

### `AssignDefaultBillingNumber()`

Wenn leer, wird über `SOUDHL Billing Number.GetDefault` ein aktiver Default gesetzt. Kein eigener Modify.

### `ApplyBoxDimensions()`

Leert zunächst L/B/H, lädt die Box und kopiert deren Maße. `UOMOptions = mm` wird zu Dimension Unit mm, andernfalls cm. Kein eigener Modify.

## Lifecycle-Regeln

* `Get` immer mit ID und Order No.
* `Uploaded = true` ist historisch terminal; nicht automatisch löschen oder Empfänger neu synchronisieren.
* Label, Customs und Empfänger sind personenbezogene Versanddaten.
* Inventurfelder ausschließlich über Box Inventory Mgt ändern.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/entwicklerdokumentationen-business-central-dhl-connector/dhl-connector-entwicklerdokumentation/tabellenreferenz/72242953-soudhl-package-header.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.