Page 5768 "Warehouse Receipt"
Base Application · Microsoft.Warehouse.Document
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Warehouse.Document · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Warehouse Receipt |
| SourceTable | Warehouse Receipt 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 |
| Location Code | Location Code | Specifies the code of the location in which the items are being received. from the table field | |
| BinFields | Zone Code | Zone Code | Specifies the zone in which the items are being received if you are using directed put-away and pick. from the table field |
| Bin Code | Bin Code | Specifies the bin where the items are picked or put away. from the table field | |
| General | Document Status | Document Status | Specifies the status of the warehouse receipt. from the table field |
| Posting Date | Posting Date | Specifies the posting date of the warehouse receipt. from the table field | |
| Vendor Shipment No. | Vendor Shipment No. | Specifies the vendor’s shipment number. It is inserted in the corresponding field on the source document during posting. 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 | |
| Sorting Method | Sorting Method | Specifies the method by which the receipts are sorted. from the table field | |
| Content | WhseReceiptLines | part Page 5769 “Whse. Receipt Subform” | — |
| FactBoxes | Control1901796907 | part Page 9109 “Item Warehouse FactBox” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Receipt | Comments | View or add comments for the record. | Page 5776 “Warehouse Comment Sheet” |
| Posted Whse. Receipts | View the quantity that has been posted as received. | Page 7333 “Posted Whse. Receipt List” | |
| Functions | Use Filters to Get Src. Docs. | Retrieve the released source document lines that define which items to receive or ship. | |
| Get Source Documents | Open the list of released source documents, such as purchase orders, to select the document to receive items for. | ||
| Autofill Qty. to Receive | Have the system enter the outstanding quantity in the Qty. to Receive field. | ||
| Delete Qty. to Receive | Have the system clear the value in the Qty. To Receive field. | ||
| Calculate Cross-Dock | Open the Cross-Dock Opportunities window to see details about the lines requesting the item, such as type of document, quantity requested, and due date. This information might help you to decide how much to cross-dock, where to place the items in the cross-dock area, or how to group them. | ||
| Posting | Post Receipt | Post the items as received. A put-away document is created 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. | ||
| Post and Print Put-away | Post the items as received and print the put-away document. | ||
| 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. |
Procedures
10 local procedures, no public ones.
Triggers
OnOpenPage, OnAfterGetCurrRecord
Relations
- source table Table 7316 “Warehouse Receipt Header”
Pages and codeunits on this table
- Page 7332 “Warehouse Receipts” (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)
Called by
- Codeunit 5751 “Get Source Doc. Inbound” (1 call:
OpenWarehouseReceiptPage → (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 Receipt"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.