---
id: object/page/6652
type: object
title: Page 6652 "Posted Return Shipments"
summary: Page 6652 "Posted Return Shipments" in Base Application (Microsoft.Purchases.History). 1 events. Present since at least BC23, still in BC30, changed in BC24.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: "24"
  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: a31dbcd84789d4e9bae4e3c9589e3d83c75b3bca74415d1b993a13c687abbc5d
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Purchases/History/PostedReturnShipments.Page.al
    title: src/Layers/W1/BaseApp/Purchases/History/PostedReturnShipments.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/across-edit-posted-document
    title: Edit posted sales and purchase documents
    date: null
    commit: null
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/purchasing-how-process-purchase-returns-cancellations
    title: Process returns or cancellations
    date: null
    commit: null
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/across-edit-posted-document
    - https://learn.microsoft.com/dynamics365/business-central/purchasing-how-process-purchase-returns-cancellations
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/general-business-functionality
    - topic/business-central/business-functionality/purchasing
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 6652
name: Posted Return Shipments
caption: Posted Purchase Return Shipments
namespace: Microsoft.Purchases.History
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "24"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids:
  - docs/learn-smb-docs/business-central/across-edit-posted-document.md
  - docs/learn-smb-docs/business-central/purchasing-how-process-purchase-returns-cancellations.md
counts:
  fields: 0
  procedures: 1
  events: 1
  subscribers: 0
  controls: 27
  actions: 8
relations:
  out: 2
  referenced_by: 0
  pages: 2
  extended_by: 0
  event_subscribers: 0
  calls: 0
  called_by: 0
  implements: 0
---

# Page 6652 "Posted Return Shipments"

> Page 6652 "Posted Return Shipments" in Base Application (Microsoft.Purchases.History). 1 events. Present since at least BC23, still in BC30, changed in BC24.

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

## Properties

| Property | Value |
|---|---|
| Caption | Posted Purchase Return Shipments |
| SourceTable | Return Shipment Header |
| PageType | List |
| UsageCategory | History |
| ApplicationArea | PurchReturnOrder |

## 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 | No. | [No.](../table/6650.md#fields) | Specifies the number of the involved entry or record, according to the specified number series. <small>from the table field</small> |
|  | Buy-from Vendor No. | [Buy-from Vendor No.](../table/6650.md#fields) | Specifies the name of the vendor who delivered the items. <small>from the table field</small> |
|  | Order Address Code | [Order Address Code](../table/6650.md#fields) | Specifies the order address of the related customer. <small>from the table field</small> |
|  | Buy-from Vendor Name | [Buy-from Vendor Name](../table/6650.md#fields) | Specifies the name of the vendor who delivered the items. <small>from the table field</small> |
|  | Currency Code | [Currency Code](../table/6650.md#fields) | Specifies the currency that is used on the entry. <small>from the table field</small> |
|  | Buy-from Post Code | [Buy-from Post Code](../table/6650.md#fields) | Specifies the post code of the vendor who delivered the items. <small>from the table field</small> |
|  | Buy-from Country/Region Code | [Buy-from Country/Region Code](../table/6650.md#fields) | Specifies the city of the vendor who delivered the items. <small>from the table field</small> |
|  | Buy-from Contact | [Buy-from Contact](../table/6650.md#fields) | Specifies the name of the contact person at the vendor who delivered the items. <small>from the table field</small> |
|  | Pay-to Vendor No. | [Pay-to Vendor No.](../table/6650.md#fields) | Specifies the number of the vendor that you received the invoice from. <small>from the table field</small> |
|  | Pay-to Name | [Pay-to Name](../table/6650.md#fields) | Specifies the name of the customer who you received the invoice from. <small>from the table field</small> |
|  | Pay-to Post Code | [Pay-to Post Code](../table/6650.md#fields) | Specifies the post code of the customer that you received the invoice from. <small>from the table field</small> |
|  | Pay-to Country/Region Code | [Pay-to Country/Region Code](../table/6650.md#fields) | Specifies the country/region code of the address. <small>from the table field</small> |
|  | Pay-to Contact | [Pay-to Contact](../table/6650.md#fields) | Specifies the name of the person to contact about an invoice from this customer. <small>from the table field</small> |
|  | Ship-to Code | [Ship-to Code](../table/6650.md#fields) | Specifies a code for an alternate shipment address if you want to ship to another address than the one that has been entered automatically. This field is also used in case of drop shipment. <small>from the table field</small> |
|  | Ship-to Name | [Ship-to Name](../table/6650.md#fields) | Specifies the name of the customer at the address that the items are shipped to. <small>from the table field</small> |
|  | Name 2 | [Ship-to Name 2](../table/6650.md#fields) | Specifies an additional part of the name of the company at the address to which the items in the purchase return order were shipped. |
|  | Ship-to Post Code | [Ship-to Post Code](../table/6650.md#fields) | Specifies the postal code of the address that the items are shipped to. <small>from the table field</small> |
|  | Ship-to Country/Region Code | [Ship-to Country/Region Code](../table/6650.md#fields) | Specifies the country/region code of the address that the items are shipped to. |
|  | Ship-to Contact | [Ship-to Contact](../table/6650.md#fields) | Specifies the name of the contact person at the address that the items are shipped to. <small>from the table field</small> |
|  | Posting Date | [Posting Date](../table/6650.md#fields) | Specifies the entry's posting date. <small>from the table field</small> |
|  | Purchaser Code | [Purchaser Code](../table/6650.md#fields) | Specifies which purchaser is assigned to the vendor. <small>from the table field</small> |
|  | Shortcut Dimension 1 Code | [Shortcut Dimension 1 Code](../table/6650.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/6650.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/6650.md#fields) | Specifies the location from where inventory items to the customer on the sales document are to be shipped by default. <small>from the table field</small> |
|  | No. Printed | [No. Printed](../table/6650.md#fields) | Specifies how many times the document has been printed. <small>from the table field</small> |
|  | Document Date | [Document Date](../table/6650.md#fields) | Specifies the date when the related document was created. <small>from the table field</small> |
|  | Applies-to Doc. Type | [Applies-to Doc. Type](../table/6650.md#fields) | Specifies the type of the posted document that this document or journal line will be applied to when you post, for example to register payment. <small>from the table field</small> |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Return Shpt. | Statistics | View statistical information, such as the value of posted entries, for the record. | [Page 6655 "Return Shipment Statistics"](../page/6655.md) |
|  | Comments | View or add comments for the record. | [Page 66 "Purch. Comment Sheet"](../page/66.md) |
|  | 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. |  |
|  | Certificate of Supply Details | View the certificate of supply that you must send to your customer for signature as confirmation of receipt. You must print a certificate of supply if the shipment uses a combination of VAT business posting group and VAT product posting group that have been marked to require a certificate of supply ... | [Page 780 "Certificates of Supply"](../page/780.md) |
|  | Print Certificate of Supply | Print the certificate of supply that you must send to your customer for signature as confirmation of receipt. |  |
| Processing | Print | Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out. |  |
|  | Find entries... | Find entries and documents that exist for the document number and posting date on the selected document. (Formerly this action was named Navigate.) |  |
|  | Update Document | Add new information that is relevant to the document, such as the country or region. You can only edit a few fields because the document has already been posted. |  |

## Events published

- `OnBeforePrintRecords(ReturnShipmentHeaderRec: Record "Return Shipment Header"; var ReturnShipmentHeaderToPrint: Record "Return Shipment Header")` (integration)

## Triggers

OnOpenPage

## Relations

- card page [Page 6650 "Posted Return Shipment"](../page/6650.md)
- source table [Table 6650 "Return Shipment Header"](../table/6650.md)

## Pages and codeunits on this table

- [Table 6650 "Return Shipment Header"](../table/6650.md) (drill-down page)
- [Table 6650 "Return Shipment Header"](../table/6650.md) (lookup page)

## Across versions

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

## Documented on Microsoft Learn

- [Edit posted sales and purchase documents](https://learn.microsoft.com/dynamics365/business-central/across-edit-posted-document)
- [Process returns or cancellations](https://learn.microsoft.com/dynamics365/business-central/purchasing-how-process-purchase-returns-cancellations)

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