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

Codeunit 6120 "E-Doc. Purchase Hist. Mapping"

EDocument · Microsoft.eServices.EDocument.Processing.Import.Purchase

Across versions

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

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

Properties

Property Value
Access Internal

Event subscriptions

  • OnAfterPurchInvLineInsertUpdateTracking subscribes to Codeunit “Purch.-Post” OnAfterPurchInvLineInsert
  • OnAfterPostPurchaseDoc subscribes to Codeunit “Purch.-Post” OnAfterPostPurchaseDoc

Procedures

  • FindRelatedPurchaseHeaderInHistory(EDocument: Record "E-Document"; var EDocVendorAssignmentHistory: Record "E-Doc. Vendor Assign. History"): Boolean
  • UpdateMissingHeaderValuesFromHistory(EDocVendorAssignmentHistory: Record "E-Doc. Vendor Assign. History"; var EDocPurchaseHeader: Record "E-Document Purchase Header")
  • FindRelatedPurchaseLineInHistory(VendorNo: Code[20]; EDocumentPurchaseLine: Record "E-Document Purchase Line"; var EDocPurchaseLineHistory: Record "E-Doc. Purchase Line History"): Boolean
  • UpdateMissingLineValuesFromHistory(PurchInvLine: Record "Purch. Inv. Line"; var EDocumentPurchaseLine: Record "E-Document Purchase Line"; CustomExplanationTxt: Text[250]; MatchConfidence: Text): Takes a draft line EDocumentPurchaseLine and the corresponding historic record found for it PurchInvLine. If the values on the draft line have already been set by other mechanisms we don’t assign it to avoid overwriting it.
  • ApplyAdditionalFieldsFromHistoryToPurchaseLine(EDocumentPurchaseLine: Record "E-Document Purchase Line"; var PurchaseLine: Record "Purchase Line"): Applies the values configured as additional fields in the posted line, if the line had a historic match the values are retrieved from the Purchase Invoice Line.
  • OpenPageWithHistoricMatch(EDocumentPurchaseLine: Record "E-Document Purchase Line"): Boolean

Plus 3 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. Purchase Hist. Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources