Page extension 6108 "E-Document Vendor Templ. Card"
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. 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 |
|---|---|---|---|
| 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. |
Relations
- extends Page 1386 “Vendor Templ. Card”
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-Document Vendor Templ. Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.