> 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/72242951-soudhl-configuration.md).

# 72242951 SOUDHL Configuration

## Zweck

Mandantenweites Setup für Serviceauswahl, Parcel/Express, Absender, Packing, Labels, Benachrichtigung, Billing und optionalen Kartonverbrauch. Die Laufzeit verwendet `FindFirst()`; fachlich ist genau ein Datensatz je Company vorgesehen.

`DataClassification = CustomerContent`.

## Felder

### Identität und Parcel

* `1 ID` – Integer, AutoIncrement, Primärschlüssel
* `2 Name` – Text\[100]
* `3 API URL` – Text\[2048]; OnValidate ergänzt abschließenden Slash
* `4 Client ID` – Text\[250]
* `5 Client Secret` – Text\[250]
* `6 API User Name` – Text\[100]
* `7 API Password` – Text\[200]
* `8 Billing Number` – Text\[100], Legacy/Pending; Validation auf zehn Zeichen
* `9 Profile Name` – Text\[100], Installation setzt das Standardgruppenprofil

### Absender und Konvertierung

* `10 Shipper Name` – Text\[200]
* `11 Shipper Address Street` – Text\[300]
* `12 Shipper Add. Address Info` – Text\[300]
* `13 Shipper Postal Code` – Text\[50]
* `14 Shipper City` – Text\[100]
* `15 Shipper Country` – Text\[100]
* `16 Shipper Email` – Text\[250]
* `17 Shipper Phone` – Text\[50]
* `18 AzureWebServiceURL` – Text\[250], optionaler PDF-zu-JPG-Override
* `19 AzureAPIKey` – Text\[300], Legacy-Override; Secret Storage bevorzugen
* `20 Billing Number Short` – Text\[10], aktuelle EKP
* `21 Mode` – Option `Live,Sandbox`
* `22 ShipperReference` – Text\[100]

### Express

* `30 Label Format` – Option `PDF,ZPL,LP2,EPL2`, Default PDF
* `31 Label Template Name` – Text\[50], Default `ECOM26_84_001`
* `32 Send Notification` – Boolean, Default true
* `33 Notification Language Code` – Code\[3], Default `eng`
* `34 Notification Country Code` – Code\[2], Default `DE`
* `35 Default Incoterm` – Code\[3], Default `DAP`
* `36 Default Express Product` – Enum `SOUDHL Express Product`
* `37 Unit Of Measurement` – Option `metric,imperial`, Default metric
* `38 Account Set` – Boolean, SystemMetadata, nicht editierbarer Statusindikator
* `39 Credentials Set` – Boolean, SystemMetadata, nicht editierbarer Statusindikator
* `40 API Service` – Option `Parcel DE,Express`, Default Parcel DE

### Packing und Buchung

* `41 Packing Mode` – Enum `SOUDHL Packing Mode`, Default Bin Packing
* `42 Package Weight Source` – Enum `SOUDHL Package Weight Source`, Default Net Weight
* `43 Default Max Package Weight (kg)` – Decimal, Default 31,5
* `44 Reduce Box Inventory` – Boolean
* `45 Box Item Journal Template` – Code\[10] → Item Journal Template
* `46 Box Item Journal Batch` – Code\[10] → Batch des Templates
* `47 Box Inventory Location Code` – Code\[10] → Location
* `48 Dimension Unit` – Enum `SOUDHL Dimension Unit`, Default cm
* `49 Weight Unit` – Enum `SOUDHL Weight Unit`, Default kg
* `50 Assign Packages on Sales Post` – Boolean

## Schlüssel und Trigger

Clustered Primary Key `(ID)`. Keine Table-Trigger und keine Table-Procedures. Feldtrigger existieren für API URL und das Legacy-Billing-Feld.

## Schreibregeln

* `FindFirst()` verwenden, keine feste ID annehmen.
* EKP in Feld 20 oder `SOUDHL Billing Number` pflegen; Feld 8 nicht neu verwenden.
* Credentials bevorzugt über `SOUDHL Secret Mgt` und den Assistenten setzen.
* Flags `Account Set` und `Credentials Set` nicht als Credentialquelle behandeln.
* Packing-Einheiten zentral mit einer möglichen Host-Shipping-Konfiguration abstimmen.

## Berechtigungen

Volle RIMD-Rechte besitzt der Super User. User/Base erhalten Configuration über ein nicht assignbares Indirect-Permissionset.


---

# 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/72242951-soudhl-configuration.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.