Table 99000800 "Sales Planning Line"

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

Learn documents this table through its pages: Page 99000883 “Sales Order Planning” (1 Learn page).

Properties

Property	Value
Caption	Sales Planning Line
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	Sales Order No.	Code[20]	—	TableRelation Table 36 “Sales Header” (“Sales Header”.“No.” where(“Document Type” = const(Order)))
2	Sales Order Line No.	Integer	—	TableRelation Table 37 “Sales Line” (“Sales Line”.“Line No.” where(“Document Type” = const(Order), “Document No.” = field(“Sales Order No.”)))
3	Item No. Δ BC28	Code[20]	Specifies the item number of the sales order line.	TableRelation Table 27 “Item”
4	Description Δ BC28	Text[100]	Specifies the description of the item in the sales order line.
5	Shipment Date Δ BC28	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.
6	Available Δ BC28	Decimal	Specifies how many of the actual items are available.
7	Next Planning Date Δ BC28	Date	Specifies the next planning date.
8	Expected Delivery Date Δ BC28	Date	Specifies the expected delivery date.
9	Planning Status Δ BC28	Option	Specifies the planning status of the production order, depending on the actual sales order.	OptionCaption: None,Simulated,Planned,Firm Planned,Released,Inventory
10	Needs Replanning Δ BC28	Boolean	Specifies if it is necessary or not to reschedule this line.
11	Variant Code Δ BC28	Code[10]	Specifies the variant of the item on the line.	TableRelation Table 5401 “Item Variant” (“Item Variant”.Code where(“Item No.” = field(“Item No.”), Code = field(“Variant Code”)))
12	Planned Quantity Δ BC28	Decimal	Specifies the quantity planned in this line.
15	Low-Level Code	Integer	—	not editable

Keys

Key1: Sales Order No., Sales Order Line No. (clustered)
Key2: Low-Level Code

Relations

Item No.: TableRelation Table 27 “Item”
Sales Order No.: TableRelation Table 36 “Sales Header”
Sales Order Line No.: TableRelation Table 37 “Sales Line”
Variant Code: TableRelation Table 5401 “Item Variant”

Pages and codeunits on this table

Page 99000883 “Sales Order Planning” (source table)

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