codeunitIntegration & APIsofficial - Microsoftderived - from the source, no model text

Codeunit 6407 "E-Doc. DataExch. Purch Handler"

EDocument · Microsoft.eServices.EDocument.Processing.Import

Across versions

  1. BC23-28not present
  2. BC29-30present

EDocument · Microsoft.eServices.EDocument.Processing.Import · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Events published

  • OnAfterBridgeToStagingTables(DataExchNo: Integer; var EDocumentPurchaseHeader: Record "E-Document Purchase Header") (integration)
  • OnAfterMapLineToStaging(DataExchNo: Integer; RecordNo: Integer; var EDocumentPurchaseLine: Record "E-Document Purchase Line") (integration)

Procedures

  • ReadIntoDraft(EDocument: Record "E-Document"; TempBlob: Codeunit "Temp Blob"): Enum "E-Doc. Process Draft"
  • View(EDocument: Record "E-Document"; TempBlob: Codeunit "Temp Blob")

Plus 14 local procedures.

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. DataExch. Purch Handler"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources