Page extension 6161 "E-Doc. Vendor Page"
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 Card.
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(Registration Number) | Use Reg. No. in E-Document | Use Reg. No. in E-Document | Specifies whether the vendor registration number is used to identify the vendor in electronic documents when the GLN and VAT registration number are blank. |
| addlast(Receiving) | Receive E-Document To | Receive E-Document To | 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. |
| E-Document Service Participation | ParticipantIdCount |
Specifies the vendors participation for the E-Document services. |
Triggers
OnAfterGetCurrRecord
Relations
- extends Page 26 “Vendor Card”
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: "pageextension", object_name: "E-Doc. Vendor Page"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.