Table 924 "Vendor Purchase Buffer"
Base Application · Microsoft.Purchases.Vendor
Across versions
- BC23-26present
- BC272 fields changed
- BC284 fields changed
- BC29-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Purchases.Vendor · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| DataClassification | SystemMetadata |
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 |
|---|---|---|---|---|
| 5 | Period Type | Option | — | |
| 6 | Period Name Δ BC28 | Text[50] | Specifies the name of the period that you want to view. | |
| 7 | Period Start Δ BC28 | Date | Specifies purchase statistics for each vendor for a period of time, starting on the date that you specify. | |
| 8 | Period End | Date | — | |
| 10 | Balance Due (LCY) Δ BC27 Δ BC28 | Decimal | Specifies the balance due to the vendor, in local currency. via Page 352 “Vendor Purchase Lines” | |
| 11 | Purchases (LCY) Δ BC27 Δ BC28 | Decimal | Specifies the purchases, in local currency. via Page 352 “Vendor Purchase Lines” |
Keys
- Key1: Period Type, Period Start (clustered)
Pages and codeunits on this table
- Page 352 “Vendor Purchase Lines” (source table)
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: "table", object_name: "Vendor Purchase Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.