Table 5440 "Supply What-If Scenario"
Base Application · Microsoft.Inventory.Planning
Across versions
- BC23-29not present
- BC30added
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Inventory.Planning · BC30 · source at f18567dc · facts from BC30
Properties
| Property | Value |
|---|---|
| Caption | Supply What-If Scenario |
| TableType | Temporary |
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 | Entry No. | Integer | — | |
| 2 | Scenario Name | Text[250] | — | |
| 3 | Document Type | Integer | — | |
| 4 | Document No. | Code[20] | — | |
| 5 | Item No. | Code[20] | Specifies the item number for the what-if analysis. via Page 5440 “Supply What-If Scenarios” | TableRelation Table 27 “Item” |
| 6 | Location Code | Code[10] | Specifies the location code for the what-if analysis. via Page 5440 “Supply What-If Scenarios” | TableRelation Table 14 “Location” |
| 7 | Original Quantity | Decimal | Specifies the original quantity on the purchase line. via Page 5440 “Supply What-If Scenarios” | |
| 8 | What-If Quantity | Decimal | Specifies the what-if quantity. Change this to see planning impact. via Page 5440 “Supply What-If Scenarios” | |
| 9 | Original Date | Date | Specifies the original expected receipt date. via Page 5440 “Supply What-If Scenarios” | |
| 10 | What-If Date | Date | Specifies the what-if expected receipt date. Change this to see timing impact. via Page 5440 “Supply What-If Scenarios” | |
| 13 | Document Table No. | Integer | — | |
| 14 | Document Line No. | Integer | — |
Keys
- PK: Entry No. (clustered)
- Document: Document Type, Document No., Item No.
Events published
OnUpdateBySourceRecordOnElseCase(Record: Variant; RecRef: RecordRef; var WhatIfScenario: Record "Supply What-If Scenario"; var IsHandled: Boolean)(integration)- subscribers: Codeunit 99000848 “Mfg. Supply What-If Plan. Eng.” OnUpdateBySourceRecordOnElseCase
Procedures
CreateScenario(Record: Variant)
Plus 3 local procedures.
Relations
- Location Code: TableRelation Table 14 “Location”
- Item No.: TableRelation Table 27 “Item”
Pages and codeunits on this table
- Page 5440 “Supply What-If Scenarios” (source table)
Calls
From the extracted call graph of BC30 (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 701 “Data Type Management” (1 call:
UpdateBySourceRecord → GetRecordRef)
Recent changes
- 2026-08-27 #9196 [Master] - What If Impact on Planning and Supply (main, BC30, feature, added)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC30 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: "Supply What-If Scenario"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.