Codeunit 6117 "E-Doc. Create Purchase Invoice"
EDocument · Microsoft.eServices.EDocument.Processing.Import
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
ApplyDraftToBC(EDocument: Record "E-Document"; EDocImportParameters: Record "E-Doc. Import Parameters"): RecordIdRevertDraftActions(EDocument: Record "E-Document")CreatePurchaseInvoice(EDocument: Record "E-Document"): Record "Purchase Header"
Recent changes
- 2026-09-01 #10700 29.x: PO matching API, E-Documents integration and receipt-on-invoice line tracking (releases/29.x, BC29, feature)
- 2026-08-28 #10526 Use BaseApp’s new PO Matching module in E-Documents (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. Create Purchase Invoice"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.