Codeunit 6173 "E-Document PEPPOL Handler"
EDocument · Microsoft.eServices.EDocument.Format
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Format · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
ReadIntoDraft(EDocument: Record "E-Document"; TempBlob: Codeunit "Temp Blob"): Enum "E-Doc. Process Draft"View(EDocument: Record "E-Document"; TempBlob: Codeunit "Temp Blob")GetResponseMessageType(EDocument: Record "E-Document"): Enum "E-Document Message Type"
Plus 23 local procedures.
Recent changes
- 2026-10-05 #12055 [E-Documents Core] Show error for unmatched inbound Order Response (main, BC30, fix)
- 2026-09-09 #11168 Restore E-Document vendor invoice field compatibility (main, BC30, fix)
- 2026-08-03 #9872 Add missing telemetry event IDs to E-Document Session.LogMessage calls (main, BC30, fix)
- 2026-07-27 #8698 [E-Documents Core] [Peppol] - Enabling EDI capabilities with E-Documents. PEPPOL Order Response Message Handling (main, BC30, feature)
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "E-Document PEPPOL Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.