Table extension 6108 "E-Document Vendor Template"
EDocument · Microsoft.eServices.EDocument.Extensions
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · Microsoft.eServices.EDocument.Extensions · BC29-30 · source at ea08af5e · facts from BC29
Extends Vendor Templ..
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 |
|---|---|---|---|---|
| 6101 | Receive E-Document To | Enum “E-Document Type” | Specifies the default purchase document to be generated from received E-document. Users can select either a Purchase Invoice or Purchase Order. This selection does not affect the creation of corrective documents; in both scenarios, the system will generate a Credit Memo. via Page extension 6108 “E-Document Vendor Templ. Card” | enum Enum 6121 “E-Document Type”; DataClassification CustomerContent |
Relations
- extends Table 1383 “Vendor Templ.”
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-Document Vendor Template"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.