Table 99000852 "Production Forecast Entry"

Base Application · Microsoft.Manufacturing.Forecast · captioned “Demand Forecast Entry” · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 99000922 “Demand Forecast Entries” (1 Learn page).

Properties

Property	Value
Caption	Demand Forecast Entry
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	Production Forecast Name Δ BC28	Code[10]	Specifies the name of the demand forecast to which the entry belongs.	TableRelation Table 99000851 “Production Forecast Name” (Production Forecast Name); NotBlank
2	Entry No. Δ BC28	Integer	Specifies the number of the entry, as assigned from the specified number series when the entry was created.
3	Item No. Δ BC28	Code[20]	Specifies the item identification number of the entry.	TableRelation Table 27 “Item”
4	Forecast Date Δ BC28	Date	Specifies the date of the demand forecast to which the entry belongs.
5	Forecast Quantity Δ BC28	Decimal	Specifies the quantities you have entered in the demand forecast within the selected time interval.
6	Unit of Measure Code Δ BC28	Code[10]	Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted.	TableRelation Table 5404 “Item Unit of Measure” (“Item Unit of Measure”.Code where(“Item No.” = field(“Item No.”)))
7	Qty. per Unit of Measure Δ BC28	Decimal	Specifies the valid number of units that the unit of measure code represents for the demand forecast entry.	not editable
8	Forecast Quantity (Base) Δ BC28	Decimal	Specifies the quantity of the entry stated, in base units of measure. via Page 99000922 “Demand Forecast Entries”
10	Location Code Δ BC28	Code[10]	Specifies the location that is linked to the entry.	TableRelation Table 14 “Location”
11	Variant Code Δ BC28	Code[10]	Specifies the variant that is linked to the entry.	TableRelation Table 5401 “Item Variant” (“Item Variant”.Code where(“Item No.” = field(“Item No.”)))
12	Component Forecast Δ BC28	Boolean	Specifies that the forecast entry is for a component item.
13	Description Δ BC28	Text[100]	Specifies a brief description of your forecast.

Keys

Key1: Entry No. (clustered)
Key2: Production Forecast Name, Item No., Location Code, Forecast Date, Component Forecast, Variant Code
Key3: Production Forecast Name, Item No., Component Forecast, Forecast Date, Location Code, Variant Code

Events published

OnBeforeCallPlanningAssignmentAssignOne(var ProductionForecastEntry: Record "Production Forecast Entry"; var PlanningAssignment: Record "Planning Assignment"; var IsHandled: Boolean) (integration)

Procedures

GetLastEntryNo(): Integer

Plus 1 local procedures.

Triggers

OnInsert, OnModify

Relations

drill-down page Page 99000922 “Demand Forecast Entries”
lookup page Page 99000922 “Demand Forecast Entries”
Location Code: TableRelation Table 14 “Location”
Item No.: TableRelation Table 27 “Item”
Variant Code: TableRelation Table 5401 “Item Variant”
Unit of Measure Code: TableRelation Table 5404 “Item Unit of Measure”
Production Forecast Name: TableRelation Table 99000851 “Production Forecast Name”

Referenced by

2 fields in 2 objects relate to this table (TableRelation or CalcFormula).

Table 27 “Item”: Prod. Forecast Quantity (Base)
Table 2900 “Forecast Item Variant Loc”: Prod. Forecast Quantity (Base)

Pages and codeunits on this table

Page 99000922 “Demand Forecast Entries” (source table)

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 703 “Find Record Management” (1 call: GetLastEntryNo → GetLastEntryIntFieldValue)

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