Table extension 6169 "E-Doc. Purchase Header"
EDocument · Microsoft.Purchases.Document
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
EDocument · Microsoft.Purchases.Document · BC29-30 · source at ea08af5e · facts from BC29
Extends Purchase Header.
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 |
|---|---|---|---|---|
| 6100 | E-Document Link | Guid | — | not editable; DataClassification SystemMetadata |
| 6101 | Amount Incl. VAT To Inv. | Decimal | — | FlowField: sum(“Purchase Line”.“Amount Incl. VAT To Inv.” where(“Document Type” = field(“Document Type”), “Document No.” = field(“No.”))); not editable |
Keys
- EDocKey1: E-Document Link
Procedures
IsLinkedToEDoc(EDocumentToExclude: Record "E-Document"): Boolean(internal)
Triggers
OnDelete
Relations
- extends Table 38 “Purchase Header”
- Amount Incl. VAT To Inv.: CalcFormula Table 39 “Purchase Line”
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: "tableextension", object_name: "E-Doc. Purchase Header"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.