tableextensionService Managementofficial - Microsoftderived - from the source, no model text

Table extension 6451 "Serv. Customer Templ."

Base Application · Microsoft.Service.Customer

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC261 fields added
  4. BC27-30unchanged

Neighbourhood 2 connected objects and pages

Table 1381 "Customer Templ." (relates to)Customer Templ.Table 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.Service.Customer · BC25-30 · source at ea08af5e · facts from BC29

Extends Customer Templ..

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 that is assigned to the customer. via Page extension 6492 “Serv. Customer Templ. Card” TableRelation Table 5957 “Service Zone” (Service Zone); DataClassification CustomerContent
5930 Combine Service Shipments + BC26 Boolean Specifies if several orders delivered to the customer can appear on the same service invoice. via Page extension 6492 “Serv. Customer Templ. Card” 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. Customer Templ."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources