BC Observatoryunofficial, made by waldo
tableextensionInventoryofficial - Microsoftderived - from the source, no model text

Table extension 6637 "ReturnReasonExt"

Base Application · Microsoft.Inventory.Location

Open in Claude6637.mdSource on GitHub

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-30unchanged

Neighbourhood 2 connected objects and pages

Table 14 "Location" (relates to)LocationTable 6635 "Return Reason" (relates to)Return Reason

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

Extends Return Reason.

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
3 Default Location Code Code[10] Specifies the location where items that are returned for the reason in question are always placed. via Page extension 6635 “ReturnReasonsExt” TableRelation Table 14 “Location” (Location where(“Use As In-Transit” = const(false))); DataClassification CustomerContent
4 Inventory Value Zero Boolean Specifies that items that are returned for the reason in question do not increase the inventory value. via Page extension 6635 “ReturnReasonsExt” DataClassification CustomerContent

Relations

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

Evidence 1 sources