Page 9311 "Purchase Return Order List"
Base Application · Microsoft.Purchases.Document
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Purchases.Document · captioned “Purchase Return Orders” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Purchase Return Orders |
| SourceTable | Purchase Header |
| PageType | List |
| UsageCategory | Lists |
| 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. | Specifies the number of the involved entry or record, according to the specified number series. |
| Buy-from Vendor No. | Buy-from Vendor No. | Specifies the name of the vendor who delivered the items. | |
| Order Address Code | Order Address Code | Specifies the order address of the related vendor. from the table field | |
| Buy-from Vendor Name | Buy-from Vendor Name | Specifies the name of the vendor who delivered the items. | |
| Vendor Authorization No. | Vendor Authorization No. | Specifies the compensation agreement identification number, sometimes referred to as the RMA No. (Returns Materials Authorization). from the table field | |
| Buy-from Post Code | Buy-from Post Code | Specifies the post code of the vendor who delivered the items. from the table field | |
| Buy-from Country/Region Code | Buy-from Country/Region Code | Specifies the city of the vendor who delivered the items. from the table field | |
| Buy-from Contact | Buy-from Contact | Specifies the name of the contact person at the vendor who delivered the items. from the table field | |
| Pay-to Vendor No. | Pay-to Vendor No. | Specifies the number of the vendor that you received the invoice from. from the table field | |
| Pay-to Name | Pay-to Name | Specifies the name of the vendor who you received the invoice from. from the table field | |
| Pay-to Post Code | Pay-to Post Code | Specifies the post code of the vendor that you received the invoice from. from the table field | |
| Pay-to Country/Region Code | Pay-to Country/Region Code | Specifies the country/region code of the address. from the table field | |
| Pay-to Contact | Pay-to Contact | Specifies the name of the person to contact about an invoice from this vendor. from the table field | |
| Ship-to Code | Ship-to Code | 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. from the table field | |
| Ship-to Name | Ship-to Name | Specifies the name of the customer at the address that the items are shipped to. from the table field | |
| Ship-to Post Code | Ship-to Post Code | Specifies the postal code of the address that the items are shipped to. from the table field | |
| Ship-to Country/Region Code | Ship-to Country/Region Code | Specifies the country/region code of the address that the items are shipped to. from the table field | |
| Ship-to Contact | Ship-to Contact | Specifies the name of the contact person at the address that the items are shipped to. from the table field | |
| Posting Date | Posting Date | Specifies the entry’s posting date. | |
| Shortcut Dimension 1 Code | Shortcut Dimension 1 Code | 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. from the table field | |
| Shortcut Dimension 2 Code | Shortcut Dimension 2 Code | 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. from the table field | |
| Location Code | Location Code | Specifies the location where the items are to be shipped. This field acts as the default location for new lines. You can update the location code for individual lines as needed. | |
| Purchaser Code | Purchaser Code | Specifies which purchaser is assigned to the vendor. from the table field | |
| Assigned User ID | Assigned User ID | Specifies the ID of the user who is responsible for the document. from the table field | |
| Currency Code | Currency Code | Specifies the currency that is used on the entry. | |
| Document Date | Document Date | Specifies the date when the related document was created. from the table field | |
| Status | Status | Specifies if the record is open, waiting to be approved, invoiced for prepayment, or released to the next stage of processing. | |
| Payment Terms Code | Payment Terms Code | Specifies a formula that calculates the payment due date, payment discount date, and payment discount amount. from the table field | |
| Due Date | Due Date | Specifies when the purchase invoice is due for payment. from the table field | |
| Payment Discount % | Payment Discount % | Specifies the payment discount percent granted if payment is made on or before the date in the Pmt. Discount Date field. from the table field | |
| Shipment Method Code | Shipment Method Code | Specifies the delivery conditions of the related shipment, such as free on board (FOB). from the table field | |
| Completely Received | Completely Received | Specifies if all the items on the order have been shipped or, in the case of inbound items, completely received. from the table field | |
| Campaign No. | Campaign No. | Specifies the campaign number the document is linked to. from the table field | |
| Applies-to Doc. Type | Applies-to Doc. Type | 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. from the table field | |
| Expected Receipt Date | Expected Receipt Date | Specifies the date you expect the items to be available in your warehouse. If you leave the field blank, it will be calculated as follows: Planned Receipt Date + Safety Lead Time + Inbound Warehouse Handling Time = Expected Receipt Date. from the table field | |
| Job Queue Status | Job Queue Status | Specifies the status of a job queue entry that handles the posting of purchase return orders. | |
| Amount | Amount | Specifies the sum of amounts on all the lines in the document. This will include invoice discounts. from the table field | |
| Amount Including VAT | Amount Including VAT | Specifies the sum of amounts, including VAT, on all the lines in the document. This will include invoice discounts. from the table field | |
| Posting Description | Posting Description | Specifies additional posting information for the document. After you post the document, the description can add detail to vendor and customer ledger entries. from the table field | |
| FactBoxes | Control1901138007 | part Page 9093 “Vendor Details FactBox” | — |
| Documents | part Page 1178 “Doc. Attachment List Factbox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Return Order | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 403 “Purchase Order Statistics” |
| Vendor Statistics | View statistical information, such as the value of posted entries, for the sell-to customer on the sales document. | Page 152 “Vendor Statistics” | |
| 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. | ||
| Approvals | View a list of the records that are waiting to be approved. For example, you can see who requested the record to be approved, when it was sent, and when it is due to be approved. | ||
| Comments | View or add comments for the record. | Page 66 “Purch. Comment Sheet” | |
| Documents | Return Shipments | Open the posted return shipments related to this order. | Page 6652 “Posted Return Shipments” |
| Credit Memos | View a list of ongoing credit memos for the order. | ||
| Warehouse | Invt. Put-away/Pick Lines | View items that are inbound or outbound on inventory put-away or inventory pick documents for the purchase return order. | Page 5774 “Warehouse Activity List” |
| Warehouse Shipment Lines | View ongoing warehouse shipments for the document, in advanced warehouse configurations. | Page 7341 “Whse. Shipment Lines” | |
| Warehouse Pick Lines | View ongoing warehouse picks for the document, in advanced warehouse configurations. | Page 5785 “Warehouse Activity Lines” | |
| Processing | Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out. | ||
| Send by Email | Finalize and prepare to email the document. The Send Email window opens prefilled with the vendor’s email address so you can add or edit information. | ||
| Send | Prepare to send the document according to the vendor’s sending profile, such as attached to an email. The Send document to window opens first so you can confirm or select a sending profile. | ||
| Attach as PDF | Create a PDF file and attach it to the document. | ||
| Release | Release | Release the document to the next stage of processing. You must reopen the document before you can make changes to it. | |
| Reopen | Reopen the document to change it after it has been approved. Approved documents have the Released status and must be opened before they can be changed | ||
| Functions | Get Posted Document Lines to Reverse | Copy one or more posted purchase document lines in order to reverse the original order. | |
| Send IC Return Order | Send the document to the intercompany outbox or directly to the intercompany partner if automatic transaction sending is enabled. | ||
| Delete Invoiced Orders | — | Report 6661 “Delete Invd Purch. Ret. Orders” | |
| Warehouse | Create Inventory Put-away/Pick | Create an inventory put-away or inventory pick to handle items on the document according to a basic warehouse configuration that does not require warehouse receipt or shipment documents. | |
| Create Warehouse Shipment | Create a warehouse shipment to start a pick a ship process according to an advanced warehouse configuration. | ||
| Posting | Test Report | View a test report so that you can find and correct any errors before you perform the actual posting of the journal or document. | |
| Post | Finalize the document or journal by posting the amounts and quantities to the related accounts in your company books. | ||
| Post Selected | Finalize the selected documents by posting the amounts and quantities to the related accounts in your company books. | ||
| Preview Posting | Review the different types of entries that will be created when you post the document or journal. | ||
| Post and Print | Finalize print the document or journal. The values and quantities are posted to the related accounts. | ||
| Post Batch | Post several documents at once. A report request window opens where you can specify which documents to post. | ||
| Remove From Job Queue | Remove the scheduled processing of this record from the job queue. | ||
| Request Approval | Send Approval Request | Request approval of the document. | |
| Cancel Approval Request | Cancel the approval request. |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetRecord, OnAfterGetCurrRecord, OnOpenPage
Relations
- card page Page 6640 “Purchase Return Order”
- source table Table 38 “Purchase Header”
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 1535 “Approvals Mgmt.” (2 calls:
SetControlAppearance → CanCancelApprovalForRecord,SetControlAppearance → HasOpenApprovalEntries)
Recent changes
- 2026-08-04 #9549 636017 Move Purchases report action tooltips to report objects (main, BC30, refactor)
Documented on Microsoft Learn
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: "Purchase Return Order List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.