Page 99000822 "Order Tracking"

Base Application · Microsoft.Foundation.Navigate · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Order Tracking
SourceTable	Order Tracking Entry
PageType	Worksheet

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	Item No.	`CurrItemNo`	Specifies the number of the item related to the order.
	Starting Date	`StartingDate`	Specifies the starting date for the time period for which you want to track the order.
	Ending Date	`EndingDate`	Specifies the end date.
	Quantity	`CurrQuantity + DerivedTrackingQty`	Specifies the outstanding quantity on the line from which you opened the window.
	Untracked Quantity	`CurrUntrackedQuantity + DerivedTrackingQty`	Specifies the amount of the quantity not directly related to a countering demand or supply by order tracking or reservations.
Control16	Entry No.	Entry No.	Specifies the number of the entry, as assigned from the specified number series when the entry was created. from the table field
	Name	Name	Specifies the name of the line that the items are tracked from. from the table field
	Demanded by	Demanded by	Specifies the source of the demand that the supply is tracked from. from the table field
	Supplied by	Supplied by	Specifies the source of the supply that fills the demand you track from, such as, a production order line. from the table field
	Warning	Warning	Specifies there is a date conflict in the order tracking entries for this line. from the table field
	Starting Date	Starting Date	Specifies the starting date of the line that the items are tracked from. from the table field
	Ending Date	Ending Date	Specifies the ending date of the line that the items are tracked from. from the table field
	Quantity	Quantity	Specifies the quantity, in the base unit of measure, of the item that has been tracked in this entry. 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
	Expected Receipt Date	Expected Receipt Date	Specifies the date when the tracked items are expected to enter the inventory. from the table field
	Item No.	Item No.	Specifies the number of the item that has been tracked in this entry. from the table field

Actions

Group	Action	ToolTip	Runs
Processing	Untracked Qty.	View the part of the tracked quantity that is not directly related to a demand or supply.
	Show	View the order tracking details.

Procedures

SetReqLine(var CurrentReqLine: Record "Requisition Line")
SetPlanningComponent(var CurrentPlanningComponent: Record "Planning Component")
SetItemLedgEntry(var CurrentItemLedgEntry: Record "Item Ledger Entry")
SetMultipleItemLedgEntries(var TempItemLedgEntry: Record "Item Ledger Entry" temporary; SourceType: Integer; SourceSubtype: Integer; SourceID: Code[20]; SourceBatchName: Code[10]; SourceProdOrderLine: Integer; SourceRefNo: Integer)
SetVariantRec(SourceRecordVar: Variant; NewItemNo: Code[20]; NewQuantity: Decimal; NewStartingDate: Date; NewEndingDate: Date)

Plus 3 local procedures.

Triggers

OnAfterGetRecord, OnFindRecord, OnInit, OnNextRecord, OnOpenPage

Relations

source table Table 99000799 “Order Tracking Entry”

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 99000778 “OrderTrackingManagement” (10 calls: OnFindRecord → FindRecord, OnNextRecord → GetNextRecord, OnOpenPage → FindRecords, …)
Codeunit 99000845 “Reservation Management” (2 calls: LookupLine → LookupLine, LookupName → LookupDocument)
Codeunit 99000856 “Planning Transparency” (1 call: SetReqLine → SetCurrReqLine)

Documented on Microsoft Learn

Track Relations Between Demand and Supply

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