Page 142 "Posted Sales Shipments"
Base Application · Microsoft.Sales.History
Across versions
- BC23present
- BC24declaration changed
- BC25-26unchanged
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 9 connected objects and pages
Base Application · Microsoft.Sales.History · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Posted Sales Shipments |
| SourceTable | Sales Shipment Header |
| 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 | 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. | — | |
| Sell-to Customer Name | Sell-to Customer Name | Specifies the name of the customer. | |
| Sell-to Post Code | Sell-to Post Code | Specifies the postal code of the customer’s main address. | |
| 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. | — | |
| 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. | |
| 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. | |
| 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. | |
| Ship-to Contact | Ship-to Contact | Specifies the name of the contact person at the address that the items are shipped to. | |
| Posting Date | Posting Date | Specifies the date on which the shipment was posted. | |
| Salesperson Code | Salesperson Code | Specifies which salesperson is associated with the shipment. | |
| 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 | |
| Currency Code | Currency Code | Specifies the currency code of the shipment. from the table field | |
| Location Code | Location Code | Specifies the location from which the items were shipped. from the table field | |
| No. Printed | No. Printed | Specifies how many times the document has been printed. from the table field | |
| Document Date | Document Date | Specifies the date when the related document was created. from the table field | |
| Requested Delivery Date | Requested Delivery Date | Specifies the date that the customer has asked for the order to be delivered. 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 | |
| Shipping Agent Code | Shipping Agent Code | Specifies the code for the shipping agent who is transporting the items. | |
| 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. | |
| 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 | |
| External Document No. | External Document No. | Specifies the number that the customer uses in their own system to refer to this sales document. from the table field | |
| FactBoxes | Documents | part Page 1178 “Doc. Attachment List Factbox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Shipment | Statistics | View statistical information, such as the value of posted entries, for the record. | Page 396 “Sales Shipment Statistics” |
| Comments | View or add comments for the record. | Page 67 “Sales Comment Sheet” | |
| 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” | |
| Print Certificate of Supply | Print the certificate of supply that you must send to your customer for signature as confirmation of receipt. | ||
| Functions | Track Package | Open the shipping agent’s tracking page to track the package. | |
| 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 | Prepare to send the document according to the customer’s sending profile, such as attached to an email. The Send document to window opens where you can confirm or select a sending profile. | ||
| Send by Email | Prepare to send the document by email. The Send Email window opens prefilled for the customer where you can add or change information before you send the email. | ||
| Attach as PDF | Create a PDF file and attach it to the document. | ||
| 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 information from the shipping agent. You can only edit a few fields because the document has already been posted. |
Events published
OnBeforePrintRecords(SalesShptHeaderRec: Record "Sales Shipment Header"; var SalesShptHeaderToPrint: Record "Sales Shipment Header")(integration)
Triggers
OnOpenPage
Relations
- card page Page 130 “Posted Sales Shipment”
- source table Table 110 “Sales Shipment Header”
Pages and codeunits on this table
- Table 110 “Sales Shipment Header” (drill-down page)
- Table 110 “Sales Shipment Header” (lookup page)
Extended by
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 1630 “Office Management” (1 call:
OnOpenPage → IsAvailable)
Documented on Microsoft Learn
- Edit posted sales and purchase documents
- How to work with VAT on sales and purchases
- Track packages
- Posting sales documents
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 Shipments"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.