Document Formats & Delivery¶
Overview¶
An Electronic Document Format maps a document type and direction to the codeunit that builds or reads the file, and to the codeunit that delivers it. Dynapro Electronic Documents extends the standard format so each format can carry an import codeunit in addition to the standard export and delivery codeunits. Administrators manage formats and choose how documents reach the access point.
Electronic Document Formats¶
Open the standard Electronic Document Formats page. The app adds:
| Field | Description |
|---|---|
| Import Codeunit ID | The codeunit that manages receiving for this document type. |
| Import Codeunit Caption | The name of the import codeunit. |
The formats the app needs are created automatically when you enable it, or with Setup Electronic Document Formats on the setup page.
Format Usage¶
Each format is tied to a usage — the document type and direction. The app adds these usages to the standard list:
- Sales Order Confirmation
- Order (inbound)
- Order Change (inbound)
- Product Catalog
- Freight Invoice
- Despatch Advice
- Purchase Order
At runtime the app resolves the format from the customer's (or vendor's) Document Sending Profile, filtered by usage and by having a codeunit for the required direction. If it cannot find exactly one match, it reports an error.
How Formats Map to Codeunits¶
| Usage | Export | Import | Delivery |
|---|---|---|---|
| Sales Invoice | Export sales invoice | Forward to email (if forwarding is on) | File delivery |
| Sales Credit Memo | Export sales credit memo | Forward to email (if forwarding is on) | File delivery |
| Service Invoice / Credit Memo | Export service document | — | File delivery |
| Sales Order Confirmation | Export order confirmation | — | File delivery |
| Purchase Order (EHF) | Export EHF order | — | File delivery |
| Order (inbound) | — | Import sales order | — |
| Order Change (inbound) | — | Import order change | — |
Delivery¶
After an export codeunit builds the XML, the file delivery codeunit records a Transaction Entry, removes empty XML nodes, attaches the file, and sets the status to Ready for Upload. From there the file reaches the trading partner in one of these ways:
| Path | When used |
|---|---|
| Document exchange service (PEPPOL) | The customer's sending profile is PEPPOL. Documents go through the standard PEPPOL exchange. Validate Peppol Registration can check the recipient first. |
| Access point provider (Logiq) | A provider module handles transport. See Providers & Permissions. |
| Direct EDI | Selected documents go straight through file delivery, bypassing the exchange service. Enabled with Enable Direct EDI in setup. |
File names follow a prefix-DDMMYYYY-HHMMSS.xml pattern.