pageSales & Receivablesofficial - Microsoftderived - from the source, no model text

Page 9082 "Customer Statistics FactBox"

Base Application · Microsoft.Sales.Customer

Across versions

  1. BC23-30present

Neighbourhood 5 connected objects and pages

Table 18 "Customer" (relates to)CustomerPage extension 20617 "Customer Statistics FactBox BF" (extended by)Customer Statistics FactBox BFPage extension 6490 "Serv. Customer Stat. FactBox" (extended by)Serv. Customer Stat. FactBoxCodeunit 9082 "Calculate Customer Stats." (calls, 8 links)Calculate Customer Stats.Page 21 "Customer Card" (calls)Customer Card

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Sales.Customer · captioned “Customer Statistics” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Customer Statistics
SourceTable Customer
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 Customer No. No. Specifies the number of the customer. 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 amount the customer owes you, or you owe them, based on all sales and credits for the customer. A positive amount means they owe you, and a negative amount means you owe them. The amount isn’t necessarily due today though. The customer’s payment terms determine due dates. Select … from the table field
Balance (LCY) As Vendor BalanceAsVendor Specifies the amount that you owe to this company. This is relevant when your customer is also your vendor. Customer and vendor are linked together through their contact record. Using customer’s contact record you can create linked vendor or link contact with existing vendor to enable calculation of…
Sales Outstanding Orders (LCY) Outstanding Orders (LCY) Specifies your expected sales income from the customer in LCY based on ongoing sales orders. from the table field
Shipped Not Invoiced (LCY) Shipped Not Invoiced (LCY) Specifies your expected sales income from the customer in LCY based on ongoing sales orders where items have been shipped. from the table field
Outstanding Invoices (LCY) Outstanding Invoices (LCY) Specifies your expected sales income from the customer in LCY based on unpaid sales invoices. from the table field
Payments Payments (LCY) Payments (LCY) Specifies the sum of payments received from the customer. from the table field
Refunds (LCY) Refunds (LCY) Specifies the sum of refunds received from the customer. from the table field
Last Payment Receipt Date LastPaymentDate Specifies the posting date of the last payment received from the customer.
Content Total (LCY) TotalAmountLCY Specifies the payment amount that the customer owes for completed sales plus sales that are still ongoing.
Credit Limit (LCY) Credit Limit (LCY) Specifies the maximum amount of credit that you extend to the customer for their purchases before you issue warnings. The value 0 represents unlimited credit. from the table field
Balance Due (LCY) OverdueBalance —
Total Sales (LCY) SalesLCY Specifies your total sales turnover with the customer in the current fiscal year. It is calculated from amounts excluding VAT on all completed and open sales invoices and credit memos.
Invoiced Prepayment Amount (LCY) InvoicedPrepmtAmountLCY Specifies your sales income from the customer, based on invoiced prepayments.

Procedures

  • CalculateFieldValues(CustomerNo: Code[20]): Calculates the customer statistics using a background task.

Plus 4 local procedures.

Triggers

OnAfterGetCurrRecord, OnPageBackgroundTaskCompleted

Relations

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.

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: "Customer Statistics FactBox"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources