Table 1951 "LP ML Input Data"
LatePaymentPredictor · Microsoft.Finance.Latepayment
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 2 connected objects and pages
LatePaymentPredictor · Microsoft.Finance.Latepayment · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| DataClassification | CustomerContent |
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 |
|---|---|---|---|---|
| 1 | Number | Code[20] | — | |
| 2 | Payment Terms Days | Integer | — | |
| 3 | Corrected | Boolean | — | |
| 4 | No. Paid Invoices | Integer | — | |
| 5 | No. Paid Late Invoices | Integer | — | |
| 6 | Ratio Paid Late/Paid Invoices | Decimal | — | |
| 7 | Total Paid Invoices Amount | Decimal | — | |
| 8 | Total Paid Late Inv. Amount | Decimal | — | |
| 9 | Ratio PaidLateAmnt/PaidAmnt | Decimal | — | |
| 10 | Average Days Late | Decimal | — | |
| 11 | No. Outstanding Inv. | Integer | — | |
| 12 | No. Outstanding Late Inv. | Integer | — | |
| 13 | Ratio NoOutstngLate/NoOutstng | Decimal | — | |
| 14 | Total Outstng Invoices Amt. | Decimal | — | |
| 15 | Total Outstng Late Inv. Amt. | Decimal | — | |
| 16 | Ratio AmtLate/Amt Outstng Inv | Decimal | — | |
| 17 | Average Outstanding Days Late | Decimal | — | |
| 18 | Bill-to Customer No. | Code[20] | — | |
| 19 | Base Amount | Decimal | — | |
| 20 | Posting Date | Date | — | |
| 21 | Due Date | Date | — | |
| 22 | Closed Date | Date | — | |
| 23 | Closed | Boolean | — | |
| 24 | Paid Late Days | Integer | — | |
| 25 | UsedForPredict And ToBeDeleted | Boolean | — | |
| 100 | Is Late | Boolean | — | |
| 101 | Confidence | Decimal | — |
Keys
- PK: Number (clustered)
- CalculateKey: Bill-to Customer No., Closed, Closed Date, Due Date, Posting Date, Is Late, Base Amount, Paid Late Days
- PostingDateKey: Posting Date
- UsedAndToBeDeletedKey: UsedForPredict And ToBeDeleted
Procedures
InsertFromSalesHeader(SalesHeader: Record "Sales Header")InsertFromSalesInvoice(LppSalesInvoiceHeaderInput: Query "LPP Sales Invoice Header Input")AddParametersToMgt(var MLPredictionManagement: Codeunit "ML Prediction Management")
Plus 1 local procedures.
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 1954 “LP Feature Table Helper” (11 calls:
CalculateFeatures → CalculateAverageOutstandingDaysLate,CalculateFeatures → CalculateAveragePaidLateInvoicesDays,CalculateFeatures → CalculateNumberOutstandingInvoices, …) - Codeunit 2003 “ML Prediction Management” (4 calls:
AddParametersToMgt → AddFeature,AddParametersToMgt → SetConfidence,AddParametersToMgt → SetLabel, …)
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: "table", object_name: "LP ML Input Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.