Table extension 6165 "E-Document Vendor"
EDocument
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
EDocument · BC29-30 · source at ea08af5e · facts from BC29
Extends Vendor.
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 6161 “E-Doc. Vendor Page” | enum Enum 6121 “E-Document Type”; DataClassification SystemMetadata |
| 6102 | Use Reg. No. in E-Document | Boolean | Specifies whether the vendor registration number is used to identify the vendor in electronic documents when the GLN and VAT registration number are blank. via Page extension 6161 “E-Doc. Vendor Page” | DataClassification CustomerContent |
Keys
- EDocRegistrationNumber: Registration Number
Relations
- extends Table 23 “Vendor”
Recent changes
- 2026-08-26 #10631 Integration/main to releases 29.x 31a860b5 (releases/29.x, BC29, feature)
- 2026-08-24 #10349 [DE] Support registration numbers in E-Documents (main, BC30, feature)
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"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.