Codeunit 6427 "E-Doc. Sales Doc. Helper"
EDocument · Microsoft.eServices.EDocument.Processing.Import.Sales
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Import.Sales · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Permissions | tabledata “Dimension Set Tree Node” = im, tabledata “Dimension Set Entry” = im |
Procedures
CreateSalesLineFromDraft(SalesHeader: Record "Sales Header"; EDocSalesLine: Record "E-Document Sales Line"; HasTotalDiscount: Boolean; LineNo: Integer): Creates a Sales Line from a staged E-Document Sales Line record.AllDraftLinesHaveTypeAndNumber(EDocSalesHeader: Record "E-Document Sales Header"): Boolean: Returns true if every staged sales line has a sales line type and item number set.FinalizeCreatedDocument(EDocument: Record "E-Document"; var SalesHeader: Record "Sales Header"): Sets the E-Document Link on the Sales Header and copies document attachments from the E-Document.RevertCreatedDocument(EDocument: Record "E-Document"): Copies document attachments back from the Sales Header to the E-Document and clears the E-Document Link.TryCheckSalesDocumentExists(SalesHeader: Record "Sales Header")GetLastSalesLineNo(DocumentType: Enum "Sales Document Type"; DocumentNo: Code[20]): Integer
Recent changes
- 2026-09-24 #11563 [E-Documents Core] [Peppol] - Add PEPPOL Requested Delivery Period support (header + line) (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-Doc. Sales Doc. Helper"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.