Page 9094 "Vendor Statistics FactBox"
Base Application · Microsoft.Purchases.Vendor
Across versions
- BC23-30present
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Purchases.Vendor · captioned “Vendor Statistics” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Vendor Statistics |
| SourceTable | Vendor |
| PageType | CardPart |
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 |
|---|---|---|---|
| Content | Vendor No. | No. | Specifies the number of the vendor. The field is either filled automatically from a defined number series, or you enter the number manually because you have enabled manual number entry in the number-series setup. from the table field |
| Balance (LCY) | Balance (LCY) | Specifies the total value of your completed purchases from the vendor in the current fiscal year. It is calculated from amounts including VAT on all completed purchase invoices and credit memos. | |
| Balance (LCY) As Customer | BalanceAsCustomer |
Specifies the amount that this company owes you. This is relevant when your vendor is also your customer. Vendor and customer are linked together through their contact record. Using vendor’s contact record you can create linked customer or link contact with existing customer to enable calculation of… | |
| Outstanding Orders (LCY) | Outstanding Orders (LCY) | Specifies the sum of outstanding orders (in LCY) to this vendor. | |
| Amt. Rcd. Not Invd. (LCY) | Amt. Rcd. Not Invoiced (LCY) | Specifies the total invoice amount (in LCY) for the items you have received but not yet been invoiced for. | |
| Outstanding Invoices (LCY) | Outstanding Invoices (LCY) | Specifies the sum of the vendor’s outstanding purchase invoices in LCY. | |
| Total (LCY) | TotalAmountLCY |
Specifies the payment amount that you owe the vendor for completed purchases plus purchases that are still ongoing. | |
| Balance Due (LCY) | OverDueBalance |
— | |
| Invoiced Prepayment Amount (LCY) | InvoicedPrepmtAmountLCY |
Specifies your payments to the vendor, based on invoiced prepayments. | |
| Payments (LCY) | Payments (LCY) | Specifies the sum of payments paid to the vendor. | |
| Refunds (LCY) | Refunds (LCY) | Specifies the sum of refunds paid to the vendor. | |
| Last Payment Date | LastPaymentDate |
Specifies the posting date of the last payment paid to the vendor. |
Procedures
CalculateFieldValues(VendorNo: Code[20])
Plus 4 local procedures.
Triggers
OnOpenPage, OnAfterGetRecord, OnFindRecord, OnPageBackgroundTaskCompleted
Relations
- source table Table 23 “Vendor”
Extended by
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 9083 “Calculate Vendor Stats.” (6 calls:
CalculateFieldValues → GetVendorNoLabel,OnPageBackgroundTaskCompleted → GetBalanceAsCustomerLabel,OnPageBackgroundTaskCompleted → GetInvoicedPrepmtAmountLCYLabel, …) - Page 26 “Vendor Card” (1 call:
ShowDetails → (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: "Vendor Statistics FactBox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.