Page 5830 "Demand Overview"
Base Application · Microsoft.Inventory.Availability
Across versions
- BC23-24present
- BC254 procedures added, 3 events added
- BC26-27unchanged
- BC283 procedures removed, 1 events removed
- BC29-30unchanged
Neighbourhood 10 connected objects and pages
Base Application · Microsoft.Inventory.Availability · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Demand Overview |
| SourceTable | Availability Calc. Overview |
| PageType | Worksheet |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | Planning |
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 |
|---|---|---|---|
| General | Start Date | StartDate |
Specifies the start date of the period for which you want to calculate demand. |
| End Date | EndDate |
Specifies the end date of the period for which you want to calculate demand. Enter a date that is later than the start date. | |
| Demand Type | DemandType |
Specifies a list of the types of orders for which you can calculate demand. Select one order type from the list: | |
| Demand No. | DemandNo |
Specifies the number of the item for which the demand calculation was initiated. | |
| Calculated | IsCalculated |
Specifies whether the demand overview has been calculated. The check box is selected after you choose the Calculate button. | |
| Control1 | Item No. | Item No. | Specifies the identifier number for the item. from the table field |
| Matches Criteria | Matches Criteria | Specifies whether the line in the Demand Overview window is related to the lines where the demand overview was calculated. from the table field | |
| Type | Type | Specifies the type of availability being calculated. from the table field | |
| Date | Date | Specifies the date of the availability calculation. from the table field | |
| SourceTypeText | SourceTypeText |
Specifies the source type of the availability calculation. | |
| Source Order Status | Source Order Status | Specifies the order status of the item for which availability is being calculated. from the table field | |
| Source ID | Source ID | Specifies the identifier code of the source. from the table field | |
| Description | Description | Specifies the description of the item for which availability is being calculated. from the table field | |
| Location Code | Location Code | Specifies the location code of the item for which availability is being calculated. from the table field | |
| Variant Code | Variant Code | Specifies the variant of the item on the line. from the table field | |
| Quantity | QuantityText |
Specifies how many units of the item are demanded. | |
| Reserved Quantity | ReservedQuantityText |
Specifies how many units of the demanded item are reserved. | |
| Running Total | Running Total | Specifies the total count of items from inventory, supply, and demand. from the table field | |
| Inventory Running Total | Inventory Running Total | Specifies the count of items in inventory. from the table field | |
| Supply Running Total | Supply Running Total | Specifies the count of items in supply. from the table field | |
| Demand Running Total | Demand Running Total | Specifies the count of items in demand. from the table field | |
| Filters | Item Filter | ItemFilter |
Specifies the item number or a filter on the item numbers that you want to trace. |
| Location Filter | LocationFilter |
Specifies the location you want to show item availability for. | |
| Variant Filter | VariantFilter |
Specifies the variant code or a filter on the variant code that you want to trace. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Calculate | Update the window with any demand. |
Events published
OnBeforeOnLookupDemandNo(var AvailabilityCalcOverview: Record "Availability Calc. Overview"; DemandType: Enum "Demand Order Source Type"; var Result: Boolean; var IsHandled: Boolean; var Text: Text)+ BC25 (integration)OnLookupDemandNo(var AvailabilityCalcOverview: Record "Availability Calc. Overview"; DemandType: Enum "Demand Order Source Type"; var Result: Boolean; var Text: Text)+ BC25 (integration)- subscribers: Codeunit 6452 “Serv. Availability Mgt.” OnLookupDemandNo, Codeunit 99000871 “Job Planning Availability Mgt.” OnLookupDemandNo, Codeunit 99000872 “Sales Availability Mgt.” OnLookupDemandNo, Codeunit 99000874 “Assembly Availability Mgt.” OnLookupDemandNo, Codeunit 99000875 “Prod. Order Availability Mgt.” OnLookupDemandNo
OnSourceTypeTextOnFormat(var AvailabilityCalcOverview: Record "Availability Calc. Overview"; var Text: Text)+ BC25 (integration)- subscribers: Codeunit 6452 “Serv. Availability Mgt.” OnSourceTypeTextOnFormat, Codeunit 99000871 “Job Planning Availability Mgt.” OnSourceTypeTextOnFormat, Codeunit 99000872 “Sales Availability Mgt.” OnSourceTypeTextOnFormat, Codeunit 99000874 “Assembly Availability Mgt.” OnSourceTypeTextOnFormat, Codeunit 99000875 “Prod. Order Availability Mgt.” OnSourceTypeTextOnFormat, Codeunit 99000876 “Transfer Availability Mgt.” OnSourceTypeTextOnFormat, Codeunit 99000973 “Purch. Availability Mgt.” OnSourceTypeTextOnFormat
Procedures
InitTempTable()SetRecFilters()SetParameters(NewStartDate: Date; NewDemandType: Enum "Demand Order Source Type"; NewDemandNo: Code[20]; NewItemNo: Code[20]; NewLocationFilter: Code[250])+ BC25SetCalculationParameter(CalculateDemandParam: Boolean)
Plus 3 local procedures.
Triggers
OnAfterGetRecord, OnInit, OnOpenPage
Relations
- source table Table 5830 “Availability Calc. Overview”
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 5830 “Calc. Availability Overview” (6 calls:
ExpandAll → CalculateDate,ExpandAll → CalculateItem,ExpandAll → EntriesExist, …)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "Demand Overview"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.