Table 6164 "E-Doc. Order Match"

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

Properties

Property	Value
Access	Internal
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Document Order No.	Code[20]	—	TableRelation Table 38 “Purchase Header” (“Purchase Header”.“No.” where(“Document Type” = const(Order)))
2	Document Line No.	Integer	Specifies Purchase Order Line No. via Page 6164 “E-Doc. Order Match”	TableRelation Table 39 “Purchase Line” (“Purchase Line”.“Line No.” where(“Document Type” = const(Order), “Document No.” = field(“Document Order No.”)))
3	E-Document Entry No.	Integer	—	TableRelation Table 6121 “E-Document” (E-Document)
4	E-Document Line No.	Integer	Specifies E-Document Imported Line No. via Page 6164 “E-Doc. Order Match”	TableRelation Table 6165 “E-Doc. Imported Line” (“E-Doc. Imported Line”.“Line No.” where(“E-Document Entry No.” = field(“E-Document Entry No.”)))
5	Quantity	Integer	—	obsolete Pending 26.0; #if not CLEANSCHEMA29
6	E-Document Direct Unit Cost	Decimal	Specifies the direct unit cost of the E-Document line. via Page 6164 “E-Doc. Order Match”
7	PO Direct Unit Cost	Decimal	Specifies the direct unit cost of the purchase order line. via Page 6164 “E-Doc. Order Match”
8	Line Discount %	Decimal	Discount % caption
9	Unit of Measure Code	Code[20]	Unit of Measure caption
10	E-Document Description	Text[100]	Specifies the description of matched E-Document line. via Page 6164 “E-Doc. Order Match”
11	PO Description	Text[100]	Specifies the description of matched Purchase Order Line. via Page 6164 “E-Doc. Order Match”
12	Fully Matched	Boolean	—
13	Precise Quantity	Decimal	Specifies the quantity that was matched for the imported line to the purchase order line. via Page 6164 “E-Doc. Order Match”
14	Learn Matching Rule	Boolean	—

Keys

Key1: Document Order No., Document Line No., E-Document Entry No., E-Document Line No. (clustered)
Key2: E-Document Entry No., E-Document Line No., Document Order No.

Procedures

GetPurchaseLine(): Record "Purchase Line"
GetImportedLine(): Record "E-Doc. Imported Line"
InsertMatch(var TempAIProposalBuffer: Record "E-Doc. PO Match Prop. Buffer" temporary; var TempEDocMatches: Record "E-Doc. Order Match" temporary)

Relations

Document Order No.: TableRelation Table 38 “Purchase Header”
Document Line No.: TableRelation Table 39 “Purchase Line”
E-Document Entry No.: TableRelation Table 6121 “E-Document”
E-Document Line No.: TableRelation Table 6165 “E-Doc. Imported Line”

Pages and codeunits on this table

Page 6164 “E-Doc. Order Match” (source table)

Recent changes

2026-08-27 #10675 Temporarily suppress AS0072 (ObsoleteTag 29.0) on 10 Base App elements for v30 prep (main, BC30, fix)
2026-07-22 #9572 Obsolete E-Document Purchase Order Matching Copilot (main, BC30, obsoletion)

Deprecations

procedure InsertMatch: guarded (#if not CLEAN29)
field Quantity: Pending 26.0 (#if not CLEANSCHEMA29), “This field has been replaced by the Precise Quantity field.”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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: "table", object_name: "E-Doc. Order Match"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.