tableInventoryofficial - Microsoftderived - from the source, no model text

Table 6025 "Invt. Order Tracking"

Base Application · Microsoft.Inventory.Counting.Tracking

Across versions

  1. BC23not present
  2. BC24added
  3. BC25-27unchanged
  4. BC288 fields changed
  5. BC29-30unchanged

Neighbourhood 1 connected objects and pages

Page 6029 "Invt. Order Tracking Lines" (pages and codeunits on it)Invt. Order Tracking Lines

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.Inventory.Counting.Tracking · captioned “Phys. Invt. Tracking” · BC24-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Phys. Invt. Tracking
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 Serial No. Δ BC28 Code[50] Specifies the serial number. DataClassification SystemMetadata
2 Lot No. Δ BC28 Code[50] Specifies the lot number. DataClassification SystemMetadata
3 Package No. Δ BC28 Code[50] Specifies the lot number. DataClassification SystemMetadata
4 Expiration Date Δ BC28 Date Specifies the expiration date. DataClassification SystemMetadata
10 Qty. Recorded (Base) Δ BC28 Decimal — DataClassification SystemMetadata
11 Qty. Expected (Base) Δ BC28 Decimal Specifies the expected base quantity. via Page 6029 “Invt. Order Tracking Lines” DataClassification SystemMetadata
20 Qty. To Transfer Δ BC28 Decimal — DataClassification SystemMetadata
21 Outstanding Quantity Δ BC28 Decimal — DataClassification SystemMetadata
22 Open Boolean — DataClassification SystemMetadata
23 Line No. Integer — DataClassification SystemMetadata

Keys

  • Key1: Serial No., Lot No., Package No. (clustered)
  • Key2: Open

Pages and codeunits on this table

Ask your agent

Procedure bodies are not stored here (D10). 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: "Invt. Order Tracking"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources