---
id: object/table/99000800
type: object
title: Table 99000800 "Sales Planning Line"
summary: Table 99000800 "Sales Planning Line" in Base Application (Microsoft.Sales.Document). 13 fields. Present since at least BC23, still in BC30, changed in BC24, BC28.
tier: official
language: en
tags:
  - table
  - base application
versions:
  introduced: null
  last_changed: "28"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 57185eee5bf9a3446d19b575095b125a1f27441803a2afcaec6fbad15ebaf65d
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Sales/Document/SalesPlanningLine.Table.al
    title: src/Layers/W1/BaseApp/Sales/Document/SalesPlanningLine.Table.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/production-how-to-create-production-orders-from-sales-orders
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/planning
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: table
object_id: 99000800
name: Sales Planning Line
namespace: Microsoft.Sales.Document
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "24"
  - "28"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 13
  procedures: 0
  events: 0
  subscribers: 0
relations:
  out: 4
  referenced_by: 0
  pages: 1
  extended_by: 0
  event_subscribers: 0
  calls: 0
  called_by: 0
  implements: 0
---

# Table 99000800 "Sales Planning Line"

> Table 99000800 "Sales Planning Line" in Base Application (Microsoft.Sales.Document). 13 fields. Present since at least BC23, still in BC30, changed in BC24, BC28.

Base Application · Microsoft.Sales.Document · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Sales/Document/SalesPlanningLine.Table.al) · facts from BC29

Learn documents this table through its pages: [Page 99000883 "Sales Order Planning"](../page/99000883.md) (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"](../table/36.md) ("Sales Header"."No." where("Document Type" = const(Order))) |
| 2 | Sales Order Line No. | Integer | — | TableRelation [Table 37 "Sales Line"](../table/37.md) ("Sales Line"."Line No." where("Document Type" = const(Order), "Document No." = field("Sales Order No."))) |
| 3 | Item No. | Code[20] | Specifies the item number of the sales order line. | TableRelation [Table 27 "Item"](../table/27.md) |
| 4 | Description | Text[100] | Specifies the description of the item in the sales order line. |  |
| 5 | Shipment Date | 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 | Decimal | Specifies how many of the actual items are available. |  |
| 7 | Next Planning Date | Date | Specifies the next planning date. |  |
| 8 | Expected Delivery Date | Date | Specifies the expected delivery date. |  |
| 9 | Planning Status | 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 | Boolean | Specifies if it is necessary or not to reschedule this line. |  |
| 11 | Variant Code | Code[10] | Specifies the variant of the item on the line. | TableRelation [Table 5401 "Item Variant"](../table/5401.md) ("Item Variant".Code where("Item No." = field("Item No."), Code = field("Variant Code"))) |
| 12 | Planned Quantity | 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"](../table/27.md)
- Sales Order No.: TableRelation [Table 36 "Sales Header"](../table/36.md)
- Sales Order Line No.: TableRelation [Table 37 "Sales Line"](../table/37.md)
- Variant Code: TableRelation [Table 5401 "Item Variant"](../table/5401.md)

## Pages and codeunits on this table

- [Page 99000883 "Sales Order Planning"](../page/99000883.md) (source table)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC24, BC28

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