Page 9304 "Sales Return Order List"
Base Application · Microsoft.Sales.Document
Across versions
- BC23-30present
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Sales.Document · captioned “Sales Return Orders” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Sales Return Orders |
| SourceTable | Sales Header |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | SalesReturnOrder |
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. |
| Sell-to Customer No. | Sell-to Customer No. | Specifies the number of the customer. | |
| Sell-to Customer Name | Sell-to Customer Name | Specifies the name of the customer. | |
| External Document No. | External Document No. | Specifies a document number that refers to the customer’s or vendor’s numbering system. from the table field | |
| Sell-to Post Code | Sell-to Post Code | Specifies the postal code of the customer’s main address. from the table field | |
| Sell-to Country/Region Code | Sell-to Country/Region Code | Specifies the country/region code of the customer’s main address. from the table field | |
| Sell-to Contact | Sell-to Contact | Specifies the name of the contact person at the customer’s main address. from the table field | |
| Bill-to Customer No. | Bill-to Customer No. | Specifies the number of the customer that you send or sent the invoice or credit memo to. from the table field | |
| Bill-to Name | Bill-to Name | Specifies the name of the customer that you send or sent the invoice or credit memo to. from the table field | |
| Bill-to Post Code | Bill-to Post Code | Specifies the postal code of the customer’s billing address. from the table field | |
| Bill-to Country/Region Code | Bill-to Country/Region Code | Specifies the country/region code of the customer’s billing address. from the table field | |
| Bill-to Contact | Bill-to Contact | Specifies the name of the contact person at the customer’s billing address. 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 placed when they are received. This field acts as the default location for new lines. You can update the location code for individual lines as needed. | |
| Salesperson Code | Salesperson Code | Specifies which salesperson is associated with the shipment. | |
| 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 document is open, waiting to be approved, has been invoiced for prepayment, or has been 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 sales return order must be paid. | |
| Payment Discount % | Payment Discount % | Specifies the payment discount percentage that is granted if the customer pays on or before the date entered in the Pmt. Discount Date field. The discount percentage is specified in the Payment Terms Code field. from the table field | |
| Shipping Agent Code | Shipping Agent Code | Specifies the code for the shipping agent who is transporting the items. from the table field | |
| Shipping Agent Service Code | Shipping Agent Service Code | Specifies the code for the service, such as a one-day delivery, that is offered by the shipping agent. from the table field | |
| Package Tracking No. | Package Tracking No. | Specifies the shipping agent’s package number. from the table field | |
| Shipment Date | Shipment 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. from the table field | |
| Shipping Advice | Shipping Advice | Specifies if the customer accepts partial shipment of orders. from the table field | |
| Completely Shipped | Completely Shipped | Specifies if all the items on the order have been shipped or, in the case of inbound items, completely received. | |
| Job Queue Status | Job Queue Status | Specifies the status of a job queue entry or task that handles the posting of sales return orders. | |
| Campaign No. | Campaign No. | Specifies the campaign number that the document is linked to. | |
| 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 | |
| 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 | Documents | part Page 1178 “Doc. Attachment List Factbox” | — |
| Control1902018507 | part Page 9082 “Customer Statistics FactBox” | — | |
| Control1900316107 | part Page 9084 “Customer Details FactBox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Return Order | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 402 “Sales Order Statistics” |
| Customer Statistics | View statistical information, such as the value of posted entries, for the sell-to customer on the sales document. | Page 151 “Customer 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 67 “Sales Comment Sheet” | |
| Documents | Return Receipts | View a list of posted return receipts for the order. | Page 6662 “Posted Return Receipts” |
| 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 sales return order. | Page 5774 “Warehouse Activity List” |
| Whse. Receipt Lines | View ongoing warehouse receipts for the document, in advanced warehouse configurations. | Page 7342 “Whse. Receipt Lines” | |
| Warehouse Put-away Lines | View ongoing warehouse put-aways 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. | ||
| 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 sales document lines in order to reverse the original order. | |
| Send IC Return Order Cnfmn. | Send the document to the intercompany outbox or directly to the intercompany partner if automatic transaction sending is enabled. | ||
| Delete Invoiced Orders | — | Report 6651 “Delete Invd Sales Ret. Orders” | |
| Request Approval | Send Approval Request | Request approval of the document. | |
| Cancel Approval Request | Cancel the approval request. | ||
| 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 Whse. Receipt | Create a warehouse receipt to start a receive and put-away 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. | ||
| Preview Posting | Review the different types of entries that will be created when you post the document or journal. | ||
| Post and Print | Finalize and prepare to print the document or journal. The values and quantities are posted to the related accounts. A report request window where you can specify what to include on the print-out. | ||
| Post and Email | Post the sales document and attach it to an email addressed to the customer. | ||
| 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. |
Events published
OnAfterPostingSetSelectionFilter(var SalesHeaderToPost: Record "Sales Header"; CurrPageSalesHeader: Record "Sales Header")(integration)
Procedures
2 local procedures, no public ones.
Triggers
OnAfterGetCurrRecord, OnAfterGetRecord, OnOpenPage
Relations
- card page Page 6630 “Sales Return Order”
- source table Table 36 “Sales 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)
Documented on Microsoft Learn
- Analyze data in lists with Copilot (preview)
- Analyze list page and query data using data analysis
- Process sales returns or cancellations
- Process sales return orders
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: "Sales Return Order List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.