pageWarehouseofficial - Microsoftderived - from the source, no model text

Page 7330 "Posted Whse. Receipt"

Base Application · Microsoft.Warehouse.History

Across versions

  1. BC23-30present

Neighbourhood 4 connected objects and pages

Table 7318 "Posted Whse. Receipt Header" (relates to)Posted Whse. Receipt HeaderPage 7333 "Posted Whse. Receipt List" (pages and codeunits on it)Posted Whse. Receipt ListCodeunit 7302 "WMS Management" (calls)WMS ManagementReceive items (Learn pages)Receive items

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Warehouse.History · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Posted Whse. Receipt
SourceTable Posted Whse. 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 where the items were received. from the table field
Zone Code Zone Code Specifies the code of the zone on this posted receipt 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 status of the posted warehouse receipt. from the table field
Posting Date Posting Date Specifies the posting date of the 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
Whse. Receipt No. Whse. Receipt No. Specifies the number of the warehouse receipt that the posted warehouse receipt concerns. 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 PostedWhseRcptLines part Page 7331 “Posted Whse. Receipt Subform” —

Actions

Group Action ToolTip Runs
Receipt List View all warehouse documents of this type that exist.
Comments View or add comments for the record. Page 5776 “Warehouse Comment Sheet”
Put-away Lines View the related put-aways. Page 5785 “Warehouse Activity Lines”
Registered Put-away Lines View the list of completed put-away activities. Page 7364 “Registered Whse. Act.-Lines”
Functions Create Put-away Create warehouse put-away for the received items.
Processing Print Prepare to print the document. A report request window for the document opens where you can specify what to include on the print-out.
Reporting Put-away List — Report 5751 “Put-away List”

Triggers

OnOpenPage

Relations

Pages and codeunits on this table

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.

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. Receipt"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources