---
id: object/page/131
type: object
title: Page 131 "Posted Sales Shpt. Subform"
summary: Page 131 "Posted Sales Shpt. Subform" in Base Application (Microsoft.Sales.History). 1 public procedures, 2 events. Present since at least BC23, still in BC30.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: null
  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: 67c6272188081ffe1c0dc854d4bf5de35a19d819de35115ad35291db4893683e
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Sales/History/PostedSalesShptSubform.Page.al
    title: src/Layers/W1/BaseApp/Sales/History/PostedSalesShptSubform.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations:
    - localization/ca
    - localization/ch
    - localization/fr
    - localization/mx
    - localization/us
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 131
name: Posted Sales Shpt. Subform
caption: 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: []
source_major: "29"
obsolete: null
countries:
  - ca
  - ch
  - fr
  - mx
  - us
ms_search_form_ids: []
counts:
  fields: 0
  procedures: 7
  events: 2
  subscribers: 0
  controls: 38
  actions: 8
relations:
  out: 1
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
  calls: 3
  called_by: 0
  implements: 0
---

# Page 131 "Posted Sales Shpt. Subform"

> Page 131 "Posted Sales Shpt. Subform" in Base Application (Microsoft.Sales.History). 1 public procedures, 2 events. Present since at least BC23, still in BC30.

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

## Properties

| Property | Value |
|---|---|
| Caption | Lines |
| SourceTable | Sales Shipment Line |
| PageType | ListPart |

## 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 | Type | [Type](../table/111.md#fields) | Specifies the line type. <small>from the table field</small> |
|  | Type | `Rec.FormatType()` | Specifies the type of transaction that was posted with the line. |
|  | 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> |
|  | Item Reference No. | [Item Reference No.](../table/111.md#fields) | Specifies the referenced item number. <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 a description of the record. |
|  | Description 2 | [Description 2](../table/111.md#fields) | Specifies information in addition to the description. <small>from the table field</small> |
|  | Return Reason Code | [Return Reason Code](../table/111.md#fields) | Specifies the code explaining why the item was returned. <small>from the table field</small> |
|  | Location Code | [Location Code](../table/111.md#fields) | Specifies the location from where inventory items to the customer on the sales document are to be shipped by default. |
|  | Bin Code | [Bin Code](../table/111.md#fields) | Specifies the bin where the items are picked or put away. <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> |
|  | 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> |
|  | Qty. Shipped Not Invoiced | [Qty. Shipped Not Invoiced](../table/111.md#fields) | Specifies the quantity of the shipped item that has been posted as shipped but that has not yet been posted as invoiced. <small>from the table field</small> |
|  | Requested Delivery Date | [Requested Delivery Date](../table/111.md#fields) | Specifies the date that the customer has asked for the order to be delivered. <small>from the table field</small> |
|  | Promised Delivery Date | [Promised Delivery Date](../table/111.md#fields) | Specifies the date that you have promised to deliver the order, as a result of the Order Promising function. <small>from the table field</small> |
|  | Planned Delivery Date | [Planned Delivery Date](../table/111.md#fields) | Specifies the planned date that the shipment will be delivered at the customer's address. If the customer requests a delivery date, the program calculates whether the items will be available for delivery on this date. If the items are available, the planned delivery date will be the same as the requ... <small>from the table field</small> |
|  | Planned Shipment Date | [Planned Shipment Date](../table/111.md#fields) | Specifies the date that the shipment should ship from the warehouse. If the customer requests a delivery date, the program calculates the planned shipment date by subtracting the shipping time from the requested delivery date. If the customer does not request a delivery date or the requested deliver... <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> |
|  | Shipping Time | [Shipping Time](../table/111.md#fields) | Specifies how long it takes from when the items are shipped from the warehouse to when they are delivered. <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> |
|  | Job Task No. | [Job Task No.](../table/111.md#fields) | Specifies the number of the related project task. <small>from the table field</small> |
|  | Outbound Whse. Handling Time | [Outbound Whse. Handling Time](../table/111.md#fields) | Specifies a date formula for the time it takes to get items ready to ship from this location. The time element is used in the calculation of the delivery date as follows: Shipment Date + Outbound Warehouse Handling Time = Planned Shipment Date + Shipping Time = Planned Delivery Date. <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> |
|  | Correction | [Correction](../table/111.md#fields) | Specifies that this sales shipment line has been posted as a corrective entry. <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> |
|  | ShortcutDimCode[3] | `ShortcutDimCode[3]` | — |
|  | ShortcutDimCode[4] | `ShortcutDimCode[4]` | — |
|  | ShortcutDimCode[5] | `ShortcutDimCode[5]` | — |
|  | ShortcutDimCode[6] | `ShortcutDimCode[6]` | — |
|  | ShortcutDimCode[7] | `ShortcutDimCode[7]` | — |
|  | ShortcutDimCode[8] | `ShortcutDimCode[8]` | — |
|  | Unit Gross Weight | [Gross Weight](../table/111.md#fields) | Specifies the gross weight of one unit of the item. In the sales statistics window, the gross weight on the line is included in the total gross weight of all the lines for the particular sales document. <small>from the table field</small> |
|  | Unit Net Weight | [Net Weight](../table/111.md#fields) | Specifies the net weight of one unit of the item. In the sales statistics window, the net weight on the line is included in the total net weight of all the lines for the particular sales document. <small>from the table field</small> |
|  | Unit Volume | [Unit Volume](../table/111.md#fields) | Specifies the volume of one unit of the item. In the sales statistics window, the volume of one unit of the item on the line is included in the total volume of all the lines for the particular sales document. <small>from the table field</small> |
|  | Units per Parcel | [Units per Parcel](../table/111.md#fields) | Specifies the number of units per parcel of the item. In the sales statistics window, the number of units per parcel on the line helps to determine the total number of units for all the lines for the particular sales document. <small>from the table field</small> |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Functions | 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. |  |
|  | Undo Shipment | Withdraw the line from the shipment. This is useful for making corrections, because the line is not deleted. You can make changes and post it again. |  |
| Line | 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. |  |
|  | Comments | View or add comments for the record. |  |
|  | Item Tracking Entries | View serial, lot or package numbers that are assigned to items. |  |
|  | Assemble-to-Order | View the linked assembly order if the shipment was for an assemble-to-order sale. |  |
|  | Item Invoice Lines | View posted sales invoice lines for the item. |  |
|  | Document Line Tracking | View related open, posted, or archived documents or document lines. |  |

## Events published

- `OnBeforeUndoShipmentPosting(SalesShipmentLine: Record "Sales Shipment Line"; var IsHandled: Boolean)` (integration)
- `OnAfterSetDimensionsVisibility()` (integration)

## Procedures

- `ShowDocumentLineTracking()`: Opens the document line tracking page for this shipment line.

Plus 4 local procedures.

## Triggers

OnAfterGetRecord, OnInit, OnOpenPage

## Relations

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

## 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 408 "DimensionManagement"](../codeunit/408.md) (1 call: `SetDimensionsVisibility → UseShortcutDims`)
- [Codeunit 5815 "Undo Sales Shipment Line"](../codeunit/5815.md) (1 call: `UndoShipmentPosting → (object)`)
- [Codeunit 9179 "Application Area Mgmt. Facade"](../codeunit/9179.md) (1 call: `OnInit → IsFoundationEnabled`)

## Across versions

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

## Countries that replace it

[CA](../../localizations/ca.md), [CH](../../localizations/ch.md), [FR](../../localizations/fr.md), [MX](../../localizations/mx.md), [US](../../localizations/us.md)

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 Shpt. Subform")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.