Page 1159 "Purchase Documents"
Base Application · Microsoft.Purchases.Document
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Purchases.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Purchase Documents |
| SourceTable | Vendor Ledger Entry |
| PageType | ListPart |
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 |
|---|---|---|---|
| Group | Due Date | Due Date | Specifies when the purchase document is due. |
| Document Type | Document Type | Specifies the type of document. | |
| Document No. | Document No. | Specifies the purchase document number. | |
| Vendor Name | VendorName |
Specifies name of the Vendor. | |
| Remaining Amount. (LCY) | Remaining Amt. (LCY) | Specifies the net amount of in the local currency. The amount is calculated using the Remaining Quantity, Line Discount %, and Unit Price (LCY) fields. |
Procedures
SetFilterForOverduePurInvoiceAmount()SetFilterForPurchDocsDueToday()SetFilterForPurchInvoicesDueNextWeek()
Triggers
OnAfterGetRecord, OnModifyRecord, OnOpenPage
Relations
- source table Table 25 “Vendor Ledger Entry”
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 113 “Vend. Entry-Edit” (1 call:
OnModifyRecord → (object))
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "page", object_name: "Purchase Documents"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.