Page 7339 "Warehouse Shipment List"
Base Application · Microsoft.Warehouse.Document
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 9 connected objects and pages
Base Application · Microsoft.Warehouse.Document · captioned “Warehouse Shipments” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Warehouse Shipments |
| SourceTable | Warehouse Shipment Header |
| PageType | List |
| UsageCategory | Lists |
| ApplicationArea | Warehouse |
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. from the table field |
| Location Code | Location Code | Specifies the code of the location from which the items are being shipped. 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 | |
| Sorting Method | Sorting Method | Specifies the method by which the shipments are sorted. from the table field | |
| Status | Status | Specifies the status of the shipment and is filled in by the program. from the table field | |
| Zone Code | Zone Code | Specifies the code of the zone on this shipment header. from the table field | |
| Bin Code | Bin Code | Specifies the bin where the items are picked or put away. from the table field | |
| Document Status | Document Status | Specifies the progress level of warehouse handling on lines in the warehouse shipment. from the table field | |
| Posting Date | Posting Date | Specifies a posting date. If you enter a date, the posting date of the source documents is updated during posting. from the table field | |
| Assignment Date | Assignment Date | Specifies the date when the user was assigned the activity. 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 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. | |
| 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 Picked | Completely Picked | Specifies whether all items on the warehouse shipment have been completely picked. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Shipment | Comments | View or add comments for the record. | Page 5776 “Warehouse Comment Sheet” |
| Pick Lines | View the related picks. | Page 5785 “Warehouse Activity Lines” | |
| Registered Pick Lines | View the list of warehouse picks that have been made for the order. | Page 7364 “Registered Whse. Act.-Lines” | |
| Posted Warehouse Shipments | View the quantity that has been posted as shipped. | Page 7340 “Posted Whse. Shipment List” | |
| Functions | 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 for additional warehouse activity. | ||
| Posting | Post Shipment | Post the items as shipped. Related pick documents are registered automatically. | |
| 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. |
Procedures
4 local procedures, no public ones.
Triggers
OnOpenPage
Relations
- card page Page 7335 “Warehouse Shipment”
- source table Table 7320 “Warehouse Shipment Header”
Pages and codeunits on this table
- Table 7320 “Warehouse Shipment Header” (lookup page)
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 5764 “Whse.-Post Shipment (Yes/No)” (3 calls:
PostShipmentYesNo → (object),ShowPreview → MessageIfPostingPreviewMultipleDocuments,ShowPreview → Preview) - Codeunit 5765 “Whse.-Post Shipment + Print” (1 call:
PostShipmentPrintYesNo → (object)) - Codeunit 7302 “WMS Management” (1 call:
OnOpenPage → GetWarehouseEmployeeLocationFilter)
Called by
- Codeunit 5752 “Get Source Doc. Outbound” (1 call:
OpenWarehouseShipmentPage → (object))
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: "Warehouse Shipment List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.