Table 6502 "Item Tracking Code"

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

Properties

Property	Value
Caption	Item Tracking Code
DataClassification	CustomerContent

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation	Notes
1	Code Δ BC28	Code[10]	Specifies the code of the record.	NotBlank
2	Description Δ BC28	Text[100]	Specifies a description of the item tracking code.
3	Warranty Date Formula Δ BC28	DateFormula	Specifies the formula that calculates the warranty date entered in the Warranty Date field on item tracking line.
5	Man. Warranty Date Entry Reqd. Δ BC28	Boolean	Specifies that a warranty date must be entered manually.
6	Man. Expir. Date Entry Reqd. Δ BC28	Boolean	Specifies that items that use this item tracking code must have an expiration date, and that you must enter the expiration date manually. The date formula specified in the Expiration Calculation field on the item card will be ignored.
8	Strict Expiration Posting Δ BC28 Δ BC29	Boolean	Specifies if the expiration date is considered when you sell items. For example, you cannot post a sales order for an item that has passed its expiration date. For tracked items, this setting also uses the First-Expired-First-Out (FEFO) method to determine which items to pick, regardless of the Pick…
9	Use Expiration Dates Δ BC28	Boolean	Specifies that items that use this item tracking code can have an expiration date. This will enable checks for expiration dates, which can affect performance for documents with many Item Tracking Lines.
11	SN Specific Tracking Δ BC28	Boolean	Specifies that when handling an outbound unit of the item in question, you must always specify which existing serial number to handle.
13	SN Info. Inbound Must Exist Δ BC28	Boolean	Specifies that serial numbers on inbound document lines must have an information record in the Serial No. Information Card.
14	SN Info. Outbound Must Exist Δ BC28	Boolean	Specifies that serial numbers on outbound document lines must have an information record in the Serial No. Information Card.
15	SN Warehouse Tracking Δ BC28	Boolean	Specifies that warehouse document lines require serial numbers.
21	SN Purchase Inbound Tracking Δ BC28	Boolean	Specifies that inbound purchase document lines require serial numbers.
22	SN Purchase Outbound Tracking Δ BC28	Boolean	Specifies that outbound purchase document lines require serial numbers.
23	SN Sales Inbound Tracking Δ BC28	Boolean	Specifies that inbound sales document lines require serial numbers.
24	SN Sales Outbound Tracking Δ BC28	Boolean	Specifies that outbound sales document lines require serial numbers.
25	SN Pos. Adjmt. Inb. Tracking Δ BC28	Boolean	Specifies that inbound item journal lines of type positive entry require serial numbers.
26	SN Pos. Adjmt. Outb. Tracking Δ BC28	Boolean	Specifies that outbound item journal lines of type positive entry require serial numbers.
27	SN Neg. Adjmt. Inb. Tracking Δ BC28	Boolean	Specifies that inbound item journal lines of type negative entry require serial numbers.
28	SN Neg. Adjmt. Outb. Tracking Δ BC28	Boolean	Specifies that outbound item journal lines of type negative entry require serial numbers.
29	SN Transfer Tracking Δ BC28	Boolean	Specifies that transfer order lines require serial numbers.
34	Create SN Info on Posting Δ BC28	Boolean	Specifies that if the Serial No. Information card is missing for the document line, the card will be created during posting.
41	Lot Specific Tracking Δ BC28	Boolean	Specifies that when handling an outbound unit, always specify which existing lot number to handle.
43	Lot Info. Inbound Must Exist Δ BC28	Boolean	Specifies that lot numbers on inbound document lines must have an information record in the Lot No. Information Card.
44	Lot Info. Outbound Must Exist Δ BC28	Boolean	Specifies that lot numbers on outbound document lines must have an information record in the Lot No. Information Card.
45	Lot Warehouse Tracking Δ BC28	Boolean	Specifies that warehouse document lines require a lot number.
51	Lot Purchase Inbound Tracking Δ BC28	Boolean	Specifies that inbound purchase document lines require a lot number.
52	Lot Purchase Outbound Tracking Δ BC28	Boolean	Specifies that outbound purchase document lines require a lot number.
53	Lot Sales Inbound Tracking Δ BC28	Boolean	Specifies that inbound sales document lines require a lot number.
54	Lot Sales Outbound Tracking Δ BC28	Boolean	Specifies that outbound sales document lines require a lot number.
55	Lot Pos. Adjmt. Inb. Tracking Δ BC28	Boolean	Specifies that inbound item journal lines of type positive entry require a lot number.
56	Lot Pos. Adjmt. Outb. Tracking Δ BC28	Boolean	Specifies that outbound item journal lines of type positive entry require a lot number.
57	Lot Neg. Adjmt. Inb. Tracking Δ BC28	Boolean	Specifies that inbound item journal lines of type negative entry require a lot number.
58	Lot Neg. Adjmt. Outb. Tracking Δ BC28	Boolean	Specifies that outbound item journal lines of type negative entry require a lot number.
59	Lot Transfer Tracking Δ BC28	Boolean	Specifies that transfer order lines require a lot number.
64	Create Lot No. Info on posting Δ BC28	Boolean	Specifies that if the Lot No. Information card is missing for the document line, the card will be created during posting.
70	Package Specific Tracking Δ BC28	Boolean	Specifies that when handling an outbound unit, always specify which existing package number to handle.
71	Package Warehouse Tracking Δ BC28	Boolean	Specifies that warehouse document lines require a package number.
73	Package Info. Inb. Must Exist Δ BC28	Boolean	Specifies that package numbers on inbound document lines must have an information record in the Package No. Information Card.
74	Package Info. Outb. Must Exist Δ BC28	Boolean	Specifies that package numbers on outbound document lines must have an information record in the Package No. Information Card.
75	Package Purchase Inb. Tracking Δ BC28	Boolean	Specifies that inbound purchase document lines require a package number.
76	Package Purch. Outb. Tracking Δ BC28	Boolean	Specifies that outbound purchase document lines require a package number.
77	Package Sales Inbound Tracking Δ BC28	Boolean	Specifies that inbound sales document lines require a package number.
78	Package Sales Outb. Tracking Δ BC28	Boolean	Specifies that outbound sales document lines require a package number.
79	Package Pos. Inb. Tracking Δ BC28	Boolean	Specifies that inbound item journal lines of type positive entry require a package number.
80	Package Pos. Outb. Tracking Δ BC28	Boolean	Specifies that outbound item journal lines of type positive entry require a package number.
81	Package Neg. Inb. Tracking Δ BC28	Boolean	Specifies that inbound item journal lines of type negative entry require a package number.
82	Package Neg. Outb. Tracking Δ BC28	Boolean	Specifies that outbound item journal lines of type negative entry require a package number.
83	Package Transfer Tracking Δ BC28	Boolean	Specifies that transfer order lines require a package number.

Keys

Key1: Code (clustered)

Events published

OnAfterIsSpecific(ItemTrackingCode: Record "Item Tracking Code"; var Specific: Boolean) (integration)
- subscribers: Codeunit 6516 “Package Management” ItemTrackingCodeIsSpecific
OnAfterIsSpecificTrackingChanged(ItemTrackingCode: Record "Item Tracking Code"; ItemTrackingCode2: Record "Item Tracking Code"; var TrackingChanged: Boolean) (integration)
- subscribers: Codeunit 6516 “Package Management” ItemTrackingCodeIsSameSpecificTracking
OnAfterIsWarehouseTracking(ItemTrackingCode: Record "Item Tracking Code"; var WarehouseTracking: Boolean) (integration)
- subscribers: Codeunit 6516 “Package Management” ItemTrackingCodeIsWarehouseTracking
OnAfterIsWarehouseTrackingChanged(ItemTrackingCode: Record "Item Tracking Code"; ItemTrackingCode2: Record "Item Tracking Code"; var TrackingChanged: Boolean) (integration)
- subscribers: Codeunit 6516 “Package Management” ItemTrackingCodeIsSameWarehouseTracking
OnValidateSNSpecificTrackingOnAfterSet(var ItemTrackingCode: Record "Item Tracking Code") + BC26 (integration)
- subscribers: Codeunit 935 “Asm. Item Tracking Mgt.” OnValidateSNSpecificTrackingOnAfterSet, Codeunit 99000891 “Mfg. Item Tracking Mgt.” OnValidateSNSpecificTrackingOnAfterSet
OnValidateLotSpecificTrackingOnAfterSet(var ItemTrackingCode: Record "Item Tracking Code") + BC26 (integration)
- subscribers: Codeunit 935 “Asm. Item Tracking Mgt.” OnValidateLotSpecificTrackingOnAfterSet, Codeunit 99000891 “Mfg. Item Tracking Mgt.” OnValidateLotSpecificTrackingOnAfterSet
OnValidatePackageSpecificTrackingOnAfterSet(var ItemTrackingCode: Record "Item Tracking Code") + BC26 (integration)
- subscribers: Codeunit 935 “Asm. Item Tracking Mgt.” OnValidatePackageSpecificTrackingOnAfterSet, Codeunit 99000891 “Mfg. Item Tracking Mgt.” OnValidatePackageSpecificTrackingOnAfterSet

Procedures

TestSetSpecific(CurrentFieldName: Text[100])
TestRemoveSpecific(CurrentFieldName: Text)
IsSpecific(): Boolean
IsSpecificTrackingChanged(ItemTrackingCode2: Record "Item Tracking Code"): Boolean
IsWarehouseTracking(): Boolean
IsWarehouseTrackingChanged(ItemTrackingCode2: Record "Item Tracking Code"): Boolean

Plus 6 local procedures.

Triggers

OnDelete

Relations

drill-down page Page 6502 “Item Tracking Codes”
lookup page Page 6502 “Item Tracking Codes”

Referenced by

2 fields in 2 objects relate to this table (TableRelation or CalcFormula).

Table 1382 “Item Templ.”: Item Tracking Code
Table 27 “Item”: Item Tracking Code

Pages and codeunits on this table

Page 6502 “Item Tracking Codes” (source table)
Page 6512 “Item Tracking Code Card” (source table)

Extended by

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.

Page 31 “Item List” (1 call: EnsureRelatedItemsHaveNoExpirationDate → (object))

Recent changes

2026-08-12 #10150 [Bug 617189] Clarify strict expiration posting tooltip (main, BC30, fix)

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