Page 5893 "Phys. Invt. Item Track. List"

Base Application · Microsoft.Inventory.Counting.Tracking · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Phys. Invt. Item Track. List
SourceTable	Reservation Entry
PageType	List

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
Control40	Item No.	Item No.	Specifies the value from the same field on the physical inventory tracking line.
	Variant Code	Variant Code	Specifies the variant of the item on the line. from the table field
	Location Code	Location Code	Specifies the location of the traced item.
	Serial No.	Serial No.	Specifies the serial number of the item that is being handled on the document line. from the table field
	Lot No.	Lot No.	Specifies the lot number of the item that is being handled on the document line.
	Package No.	Package No.	Specifies the package number of the item that is being handled on the document line.
	Expiration Date	Expiration Date	Specifies the expiration date of the item that is being handled on the document line. from the table field
	Positive	Positive	Specifies that the difference is positive. from the table field
	Quantity	Quantity	Specifies the quantity of the record. from the table field
	Qty. per Unit of Measure	Qty. per Unit of Measure	Specifies how many of the base unit of measure are contained in one unit of the item. from the table field
	Quantity (Base)	Quantity (Base)	Specifies the quantity on the line, expressed in base units of measure.
	Qty. to Handle (Base)	Qty. to Handle (Base)	Specifies the quantity of item, in the base unit of measure, to be handled in a warehouse activity.
	Qty. to Invoice (Base)	Qty. to Invoice (Base)	Specifies the quantity, in the base unit of measure, that remains to be invoiced. It is calculated as Quantity - Qty. Invoiced.
	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
	Expected Receipt Date	Expected Receipt Date	Specifies the date you expect the items to be available in your warehouse. If you leave the field blank, it will be calculated as follows: Planned Receipt Date + Safety Lead Time + Inbound Warehouse Handling Time = Expected Receipt Date.
	Description	Description	Specifies a description of the record.
	Reservation Status	Reservation Status	Specifies the status of the reservation. from the table field
	Created By	Created By	Specifies the user who created the traced record. from the table field
	Creation Date	Creation Date	Specifies when the traced record was created.
	Entry No.	Entry No.	Specifies the number that is assigned to the entry.

Actions

Group	Action	ToolTip	Runs
Item Tracking Information	Serial No. Information Card	Show Serial No. Information Card	Page 6509 “Serial No. Information List”
	Lot No. Information Card	Show Lot No. Information Card	Page 6508 “Lot No. Information List”

Relations

source table Table 337 “Reservation Entry”

Called by

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.

Table 5876 “Phys. Invt. Order Line” (1 call: ShowItemTrackingLines → (object))

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: "Phys. Invt. Item Track. List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.