---
id: object/page/525
type: object
title: Page 525 "Posted Sales Shipment Lines"
summary: Page 525 "Posted Sales Shipment Lines" in Base Application (Microsoft.Sales.History). Present since at least BC23, still in BC30, changed in BC27.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: "27"
  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: 88c41717cad851160b30e3032b55f5d8f898c3cdf8c933b95484b1fbb2893787
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Sales/History/PostedSalesShipmentLines.Page.al
    title: src/Layers/W1/BaseApp/Sales/History/PostedSalesShipmentLines.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/finance-work-with-vat
    title: How to work with VAT on sales and purchases
    date: null
    commit: null
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/finance-work-with-vat
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/finance/working-with-value-added-tax-vat
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 525
name: Posted Sales Shipment Lines
namespace: Microsoft.Sales.History
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "27"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids:
  - docs/learn-smb-docs/business-central/finance-work-with-vat.md
counts:
  fields: 0
  procedures: 0
  events: 0
  subscribers: 0
  controls: 17
  actions: 3
relations:
  out: 1
  referenced_by: 0
  pages: 2
  extended_by: 1
  event_subscribers: 0
  calls: 0
  called_by: 1
  implements: 0
---

# Page 525 "Posted Sales Shipment Lines"

> Page 525 "Posted Sales Shipment Lines" in Base Application (Microsoft.Sales.History). Present since at least BC23, still in BC30, changed in BC27.

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

## Properties

| Property | Value |
|---|---|
| Caption | Posted Sales Shipment Lines |
| SourceTable | Sales Shipment Line |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | Basic, Suite |

## 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 |
|---|---|---|---|
| Control1 | Document No. | [Document No.](../table/111.md#fields) | Specifies the shipment number. <small>from the table field</small> |
|  | Sell-to Customer No. | [Sell-to Customer No.](../table/111.md#fields) | Specifies the number of the customer. <small>from the table field</small> |
|  | Type | [Type](../table/111.md#fields) | Specifies the line type. <small>from the table field</small> |
|  | No. | [No.](../table/111.md#fields) | Specifies the number of the involved entry or record, according to the specified number series. <small>from the table field</small> |
|  | Variant Code | [Variant Code](../table/111.md#fields) | Specifies the variant of the item on the line. <small>from the table field</small> |
|  | Description | [Description](../table/111.md#fields) | Specifies the name of the item or general ledger account, or some descriptive text. <small>from the table field</small> |
|  | Description 2 | [Description 2](../table/111.md#fields) | Specifies information in addition to the description. <small>from the table field</small> |
|  | Shortcut Dimension 1 Code | [Shortcut Dimension 1 Code](../table/111.md#fields) | Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. <small>from the table field</small> |
|  | Shortcut Dimension 2 Code | [Shortcut Dimension 2 Code](../table/111.md#fields) | Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. <small>from the table field</small> |
|  | Location Code | [Location Code](../table/111.md#fields) | Specifies the code for the location of the item on the shipment line which was posted. <small>from the table field</small> |
|  | Quantity | [Quantity](../table/111.md#fields) | Specifies the number of units of the item specified on the line. <small>from the table field</small> |
|  | Unit of Measure Code | [Unit of Measure Code](../table/111.md#fields) | 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. <small>from the table field</small> |
|  | Unit of Measure | [Unit of Measure](../table/111.md#fields) | Specifies the name of the item or resource's unit of measure, such as piece or hour. <small>from the table field</small> |
|  | Appl.-to Item Entry | [Appl.-to Item Entry](../table/111.md#fields) | Specifies the number of the item ledger entry that the document or journal line is applied to. <small>from the table field</small> |
|  | Job No. | [Job No.](../table/111.md#fields) | Specifies the number of the related project. <small>from the table field</small> |
|  | Shipment Date | [Shipment Date](../table/111.md#fields) | 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. <small>from the table field</small> |
|  | Quantity Invoiced | [Quantity Invoiced](../table/111.md#fields) | Specifies how many units of the item on the line have been posted as invoiced. <small>from the table field</small> |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Line | Show Document | Open the document that the selected line exists on. |  |
|  | Dimensions | View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history. |  |
|  | Item Tracking Lines | View or edit serial, lot and package numbers that are assigned to the item on the document or journal line. |  |

## Triggers

OnOpenPage

## Relations

- source table [Table 111 "Sales Shipment Line"](../table/111.md)

## Pages and codeunits on this table

- [Table 111 "Sales Shipment Line"](../table/111.md) (drill-down page)
- [Table 111 "Sales Shipment Line"](../table/111.md) (lookup page)

## Extended by

- [Page extension 30109 "Shpfy Post. Sales Shipm. Lines"](../pageextension/30109.md)

## Called by

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.

- [Table 37 "Sales Line"](../table/37.md) (1 call: `ShowBlanketOrderPostedShipmentLines → (object)`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC27

## Documented on Microsoft Learn

- [How to work with VAT on sales and purchases](https://learn.microsoft.com/dynamics365/business-central/finance-work-with-vat)

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). 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: "Posted Sales Shipment Lines")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.