Page 6511 "Posted Item Tracking Lines"

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

Properties

Property	Value
Caption	Posted Item Tracking Lines
SourceTable	Item Ledger 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
Control1	Serial No.	Serial No.	Specifies a serial number if the posted item carries such a number. from the table field
	Lot No.	Lot No.	Specifies a lot number if the posted item carries such a number. from the table field
	Package No.	Package No.	Specifies a package number if the posted item carries such a number. from the table field
	Quantity	Quantity	Specifies the number of units of the item in the item entry. from the table field
	Shipped Qty. Not Returned	Shipped Qty. Not Returned	Specifies the quantity for this item ledger entry that was shipped and has not yet been returned. from the table field
	Warranty Date	Warranty Date	Specifies the last day of warranty for the item on the line. from the table field
	Expiration Date	Expiration Date	Specifies the last date that the item on the line can be used. from the table field

Triggers

OnOpenPage

Relations

source table Table 32 “Item Ledger 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.

Codeunit 6503 “Item Tracking Doc. Management” (3 calls: ShowItemTrackingForInvoiceLine → (object), ShowItemTrackingForJobPlanningLine → (object), ShowItemTrackingForShptRcptLine → (object))
Codeunit 99000891 “Mfg. Item Tracking Mgt.” (1 call: ShowItemTrackingForProdOrderComp → (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: "Posted Item Tracking Lines"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.