tableInventoryofficial - Microsoftderived - from the source, no model textobsolete - removed

Table 5887 "Pstd. Exp. Phys. Invt. Track"

Base Application · Microsoft.Inventory.Counting.Tracking

Across versionsobsolete removed since 27.0

  1. BC23present
  2. BC24declaration changed
  3. BC25unchanged
  4. BC26declaration changed
  5. BC27declaration changed
  6. BC281 fields changed
  7. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 5879 "Pstd. Phys. Invt. Order Hdr" (relates to)Pstd. Phys. Invt. Order HdrTable 5880 "Pstd. Phys. Invt. Order Line" (relates to)Pstd. Phys. Invt. Order Line

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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Pstd. Exp. Phys. Invt. Track
DataClassification CustomerContent
ObsoleteState Removed
ObsoleteTag 27.0
ObsoleteReason Replaced by table Posted.Exp.Invt.Order.Tracking.

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 Order No Code[20] — TableRelation Table 5879 “Pstd. Phys. Invt. Order Hdr” (Pstd. Phys. Invt. Order Hdr)
2 Order Line No. Integer — TableRelation Table 5880 “Pstd. Phys. Invt. Order Line” (“Pstd. Phys. Invt. Order Line”.“Line No.” where(“Document No.” = field(“Order No”)))
3 Serial No. Code[50] —
4 Lot No. Code[50] —
30 Quantity (Base) Δ BC28 Decimal —

Keys

  • Key1: Order No, Order Line No., Serial No., Lot No. (clustered)

Relations

Deprecations

  • object: Removed 27.0 (#if not CLEANSCHEMA27), “Replaced by table Posted.Exp.Invt.Order.Tracking.”

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

Evidence 1 sources