pageextensionPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Page extension 6162 "E-Doc. Purch. Payables Setup"

EDocument · Microsoft.Purchases.Document

Across versions

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

Neighbourhood 1 connected objects and pages

Page 460 "Purchases & Payables Setup" (relates to)Purchases & Payables Setup

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.Purchases.Document · BC29-30 · source at ea08af5e · facts from BC29

Extends Purchases & Payables Setup.

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
addafter(Document Default Line Type) E-Document Matching Difference E-Document Matching Difference Specifies the maximum allowed percentage of cost difference when matching incoming E-Document line with Purchase Order line
E-Document Learn Copilot Matchings E-Document Learn Copilot Matchings Specifies whether Copilot E-Document line matchings are learned by default (Item References and Text To Account Mappings). This can be overwritten on the matching page.
E-Doc. Def. Posting Date E-Doc. Def. Posting Date Specifies how the posting date is set on purchase invoices created from e-documents. Work Date uses the current work date. Document Date uses the document date from the e-document.
Apply VAT Diff. For Purch EDoc Apply VAT Diff. For Purch EDoc Specifies whether VAT difference should be applied when matching incoming E-Document line with Purchase Order line
Resolve VAT Group Purch EDoc Resolve VAT Group Purch EDoc Specifies whether to resolve VAT Product Group for purchase lines created from e-documents based on the VAT rate and the vendor’s VAT posting setup. If disabled, the VAT Product Group will not be identified based on the purchase e-document.

Relations

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: "pageextension", object_name: "E-Doc. Purch. Payables Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources