BC Observatoryunofficial, made by waldo
tableextensionSales & Receivablesofficial - Microsoftderived - from the source, no model text

Table extension 6466 "Serv. Ship-To Address"

Base Application · Microsoft.Sales.Customer

Open in Claude6466.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Table 222 "Ship-to Address" (relates to)Ship-to AddressTable 5957 "Service Zone" (relates to)Service Zone

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

Extends Ship-to Address.

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
5900 Service Zone Code Code[10] Specifies the code for the service zone in which the ship-to address is located. via Page extension 6466 “Serv. Ship-to Address” TableRelation Table 5957 “Service Zone” (Service Zone); 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: "Serv. Ship-To Address"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources