Page 7337 "Posted Whse. Shipment"
Base Application · Microsoft.Warehouse.History
Across versions
- BC23-30present
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Warehouse.History · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Posted Whse. Shipment |
| SourceTable | Posted Whse. Shipment Header |
| PageType | Document |
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 |
|---|---|---|---|
| General | No. | No. | Specifies the number of the involved entry or record, according to the specified number series. from the table field |
| Whse. Shipment No. | Whse. Shipment No. | Specifies the number of the warehouse shipment that the posted warehouse shipment originates from. from the table field | |
| Location Code | Location Code | Specifies the code of the location from which the items were shipped. from the table field | |
| Zone Code | Zone Code | Specifies the code of the zone on this posted 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 | |
| Posting Date | Posting Date | Specifies the posting date of the posted warehouse shipment. 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 | |
| Assignment Date | Assignment Date | Specifies the date when the user was assigned the activity. from the table field | |
| Assignment Time | Assignment Time | Specifies the time when the user was assigned the activity. from the table field | |
| Content | WhseShptLines | part Page 7338 “Posted Whse. Shipment Subform” | — |
| Shipping | 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 |
| 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. 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 | |
| Shipment Method Code | Shipment Method Code | Specifies the delivery conditions of the related shipment, such as free on board (FOB). from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Shipment | List | View all warehouse documents of this type that exist. | |
| Comments | View or add comments for the record. | Page 5776 “Warehouse Comment Sheet” | |
| 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. |
Triggers
OnOpenPage
Relations
- source table Table 7322 “Posted Whse. Shipment Header”
Pages and codeunits on this table
- Page 7340 “Posted Whse. Shipment List” (card 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 7302 “WMS Management” (1 call:
OnOpenPage → GetWarehouseEmployeeLocationFilter)
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: "Posted Whse. Shipment"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.