Page 99000883 "Sales Order Planning"

Base Application · Microsoft.Sales.Document · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Sales Order Planning
SourceTable	Sales Planning Line
PageType	List

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
Control2	Item No.	Item No.	Specifies the item number of the sales order line. from the table field
	Variant Code	Variant Code	Specifies the variant of the item on the line. from the table field
	Planning Status	Planning Status	Specifies the planning status of the production order, depending on the actual sales order. from the table field
	Description	Description	Specifies the description of the item in the sales order line. from the table field
	Shipment Date	Shipment Date	Specifies when items on the document are shipped or were shipped. A shipment date is usually calculated from a requested delivery date plus lead time. from the table field
	Planned Quantity	Planned Quantity	Specifies the quantity planned in this line. from the table field
	Available	Available	Specifies how many of the actual items are available. from the table field
	Next Planning Date	Next Planning Date	Specifies the next planning date. from the table field
	Expected Delivery Date	Expected Delivery Date	Specifies the expected delivery date. from the table field
	Needs Replanning	Needs Replanning	Specifies if it is necessary or not to reschedule this line. from the table field

Actions

Group	Action	ToolTip	Runs
Item	Card	View or change detailed information about the record on the document or journal line.	Page 30 “Item Card”
	Ledger Entries	View the history of transactions that have been posted for the selected record.	Page 38 “Item Ledger Entries”
Item Availability by	Event	View how the actual and the projected available balance of an item will develop over time according to supply and demand events.
	Period	View the projected quantity of the item over time according to time periods, such as day, week, or month.	Page 157 “Item Availability by Periods”
	BOM Level	View availability figures for items on bills of materials that show how many units of a parent item you can make based on the availability of child items.
Item	Statistics	View statistical information, such as the value of posted entries, for the record.
Functions	Update Shipment Dates	Update the Shipment Date field on lines with any changes that were made since you opened the Sales Order Planning window.
	Order Tracking	Tracks the connection of a supply to its corresponding demand. This can help you find the original demand that created a specific production order or purchase order.

Events published

OnBeforeCalculatePlanAndDelivDates(var Item: Record Item) (integration)
OnMakeLinesOnBeforeInsertSalesOrderPlanningLine(var SalesPlanningLine: Record "Sales Planning Line"; var SalesLine: Record "Sales Line") (integration)
OnMakeLinesSetOnAfterSetFilters(var SalesLine: Record "Sales Line") (integration)
OnMakeLinesOnSetFromSourceLine(var SalesPlanningLine: Record "Sales Planning Line"; ReservEntry: Record "Reservation Entry") + BC26 (integration)
- subscribers: Codeunit 99000883 “Mfg. Sales Order Planning” OnMakeLinesOnSetFromSourceLine

Procedures

SetSalesOrder(SalesOrderNo: Code[20]): Sets the sales order to display planning information for.
BuildForm(): Builds the planning form by creating lines for all items in the sales order.
Caption(): Text: Returns the caption text for the page showing the sales order number and customer name.

Plus 3 local procedures.

Triggers

OnOpenPage

Relations

source table Table 99000800 “Sales Planning Line”

Extended by

Page extension 99000883 “Mfg. Sales Order Planning”

Documented on Microsoft Learn

Create Production Orders from Sales Orders

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). 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: "Sales Order Planning"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.