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

Table extension 6102 "E-Doc. Location"

EDocument · Microsoft.Inventory.Location

Open in Claude6102.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 2 connected objects and pages

Table 14 "Location" (relates to)LocationTable 60 "Document Sending Profile" (relates to)Document Sending Profile

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.

EDocument · Microsoft.Inventory.Location · BC29-30 · source at ea08af5e · facts from BC29

Extends Location.

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
6100 Transfer Doc. Sending Profile Code[20] Specifies the document sending profile that is used for transfer shipment documents. TableRelation Table 60 “Document Sending Profile” (Document Sending Profile); 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: "E-Doc. Location"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources