tableIntegration & APIsofficial - Microsoftderived - from the source, no model textobsolete - pending

Table 6163 "E-Doc. PO Match Prop. Buffer"

EDocument · Microsoft.EServices.EDocument.OrderMatch.Copilot

Across versionsobsolete pending since 29.0

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

Neighbourhood 5 connected objects and pages

Table 38 "Purchase Header" (relates to)Purchase HeaderTable 39 "Purchase Line" (relates to)Purchase LineTable 6121 "E-Document" (relates to)E-DocumentTable 6165 "E-Doc. Imported Line" (relates to)E-Doc. Imported LinePage 6163 "E-Doc. PO Match Prop. Sub" (pages and codeunits on it)E-Doc. PO Match Prop. Sub

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
Access Internal
Extensible false
TableType Temporary
DataClassification CustomerContent
ObsoleteState Pending
ObsoleteTag 29.0
ObsoleteReason The E-Document Purchase Order Matching Copilot has been deprecated. AI-assisted line matching is now handled at import time in the E-Document Purchase Draft experience by codeunit “E-Doc. AI Tool Processor”.

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 — 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 the E-Document line number. via Page 6163 “E-Doc. PO Match Prop. Sub” TableRelation Table 6165 “E-Doc. Imported Line” (“E-Doc. Imported Line”.“Line No.” where(“E-Document Entry No.” = field(“E-Document Entry No.”)))
5 E-Document Description Text[100] Specifies the E-Document line description. via Page 6163 “E-Doc. PO Match Prop. Sub”
6 PO Description Text[100] Purchase Order Line Description caption
7 E-Document Direct Unit Cost Decimal —
8 PO Direct Unit Cost Decimal Purchase Order Direct Unit Cost caption
9 E-Document Line Discount Decimal —
10 PO Line Discount Decimal Purchase Order Line Discount caption
11 Matched Quantity Integer Specifies the quantity that will be applied to purchase order line. via Page 6163 “E-Doc. PO Match Prop. Sub”
12 AI Proposal Text[2048] Specifies the action proposed by the AI. via Page 6163 “E-Doc. PO Match Prop. Sub”
14 Learn Matching Rule Boolean Specifies whether a matching rule should be created for this proposal. Item references are created for Items and Text To Account Mappings are created for G/L Accounts. via Page 6163 “E-Doc. PO Match Prop. Sub”

Keys

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

Procedures

  • GetStyle(): Text

Relations

Pages and codeunits on this table

Recent changes

Deprecations

  • object: Pending 29.0 (#if not CLEAN29), “The E-Document Purchase Order Matching Copilot has been deprecated. AI-assisted line matching is now handled at import time in the E-Document Purchase Draft experience by codeunit “E-Doc. AI Tool Processor”.”

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. PO Match Prop. Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources