Page 9314 "Warehouse Movements"
Base Application · Microsoft.Warehouse.Activity
Across versions
- BC23-26present
- BC27declaration changed
- BC28-30unchanged
Neighbourhood 5 connected objects and pages
Base Application · Microsoft.Warehouse.Activity · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Warehouse Movements |
| SourceTable | Warehouse Activity 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 |
| Source Document | Source Document | Specifies the type of document that the line relates to. from the table field | |
| Source No. | Source No. | Specifies the number of the source document that the entry originates from. from the table field | |
| Type | Type | Specifies the type of activity, such as Put-away, that the warehouse performs on the lines that are attached to the header. from the table field | |
| Location Code | Location Code | Specifies the code for the location where the warehouse activity takes place. from the table field | |
| Destination Type | Destination Type | Specifies information about the type of destination, such as customer or vendor, associated with the warehouse activity. from the table field | |
| Destination No. | Destination No. | Specifies the number or the code of the customer or vendor that the line is linked to. from the table field | |
| 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 | |
| Assigned User ID | Assigned User ID | Specifies the ID of the user who is responsible for the document. from the table field | |
| No. of Lines | No. of Lines | Specifies the number of lines in the warehouse activity document. from the table field | |
| Sorting Method | Sorting Method | Specifies the method by which the lines are sorted on the warehouse header, such as Item or Document. from the table field | |
| Assignment Date | Assignment Date | Specifies the date when the user was assigned the activity. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Movement | Comments | View or add comments for the record. | Page 5776 “Warehouse Comment Sheet” |
| Registered Movements | View any quantities that have already been moved. | Page 5797 “Registered Whse. Activity List” | |
| Processing | Register Movement | Register the movement of items between bins in an advanced warehouse configuration. | |
| Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out. | |||
| Assign to me | Assigns this movement document to the current user. |
Procedures
2 local procedures, no public ones.
Triggers
OnOpenPage
Relations
- card page Page 7315 “Warehouse Movement”
- source table Table 5766 “Warehouse Activity 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 7302 “WMS Management” (1 call:
OnOpenPage → GetWarehouseEmployeeLocationFilter) - Codeunit 7306 “Whse.-Act.-Register (Yes/No)” (1 call:
RegisterActivityYesNo → (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 Movements"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.