pageWarehouseofficial - Microsoftderived - from the source, no model text

Page 7340 "Posted Whse. Shipment List"

Base Application · Microsoft.Warehouse.History

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-26unchanged
  4. BC27declaration changed
  5. BC28-30unchanged

Neighbourhood 6 connected objects and pages

Table 7322 "Posted Whse. Shipment Header" (relates to)Posted Whse. Shipment HeaderPage 7337 "Posted Whse. Shipment" (pages and codeunits on it)Posted Whse. ShipmentTable 7322 "Posted Whse. Shipment Header" (pages and codeunits on it)Posted Whse. Shipment HeaderCodeunit 7302 "WMS Management" (calls)WMS ManagementPicking and Shipping in Basic Warehouse Configurations (Learn pages)Picking and Shipping in Basi…Ship items (Learn pages)Ship 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 · captioned “Posted Warehouse Shipments” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Posted Warehouse Shipments
SourceTable Posted Whse. Shipment Header
PageType List
UsageCategory History
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 were 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
No. Series No. Series Specifies the number series from which entry or record numbers are assigned to new entries or records. 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
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
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. 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 Comments View or add comments for the record. Page 5776 “Warehouse Comment Sheet”
Line Card View or change detailed information about the record on the document or journal line.

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

Evidence 3 sources