pageManufacturingofficial - Microsoftderived - from the source, no model text

Page 2901 "Demand Forecast Card"

Base Application · Microsoft.Manufacturing.Forecast

Across versions

  1. BC23-24present
  2. BC25declaration changed
  3. BC26-27unchanged
  4. BC281 events added
  5. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Table 99000851 "Production Forecast Name" (relates to)Production Forecast NameCodeunit 1530 "Request Page Parameters Helper" (calls, 3 links)Request Page Parameters HelperCodeunit 9200 "Matrix Management" (calls)Matrix Management

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.Manufacturing.Forecast · captioned “Demand Forecast Overview” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Demand Forecast Overview
SourceTable Production Forecast Name
PageType Card

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 Demand Forecast Name Name Specifies the name of the demand forecast. from the table field
Description Description Specifies the description of the demand forecast.
View by View By Specifies the period of time for which amounts are displayed. from the table field
View as Quantity Type Specifies how amounts are displayed. Net Change: The net change in the balance for the selected period. Balance at Date: The balance as of the last day in the selected period. from the table field
Forecast Type Forecast Type Specifies whether the demand forecast entry is for a sales item or a component item. If you choose Sales Item, only sales orders net the forecast. If you choose Component Item, demand from production order components net the forecast. from the table field
Item Filter ItemFilter Specifies a filter that will show specific items on the Demand Forecast Matrix FastTab. This reduces the number of entries on the FastTab.
Forecast by Locations Forecast By Locations Specifies whether to create a forecast entry that includes locations. from the table field
Location Filter LocationFilter Specifies a location code if you want to create a forecast entry for a specific location.
Forecast by Variants Forecast By Variants Use this if you want to create a forecast entry including the variants. from the table field
Variant Filter VariantFilter Specifies an item variant code if you want to create a forecast entry for a specific item variant.
Date Filter Date Filter Specifies the dates that will be used to filter the amounts in the window. from the table field
Content Matrix part Page 2900 “Demand Forecast Variant Matrix” —

Actions

Group Action ToolTip Runs
Functions Copy Demand Forecast Entries — Report 99003803 “Copy Production Forecast”
Processing Previous Set Go to the previous set of data.
Previous Column Go to the previous column.
Next Column Go to the next column.
Next Set Go to the next set of data.

Events published

  • OnBeforeSetMatrix(var ProductionForecastName: Record "Production Forecast Name"; MatrixColumnCaptions: array[32] of Text[1024]; var MatrixRecords: array[32] of Record Date; CurrentSetLength: Integer) + BC28 (integration)

Procedures

  • SetMatrixColumns(StepType: Enum "Matrix Page Step Type") (protected)
  • SetMatrix() (protected)

Plus 3 local procedures.

Triggers

OnOpenPage, OnAfterGetRecord, OnNextRecord

Relations

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: "Demand Forecast Card"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources