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

Table 5936 "Service Document Register"

Base Application · Microsoft.Service.Document

Across versions

  1. BC23present
  2. BC245 fields added
  3. BC25-27unchanged
  4. BC283 fields changed
  5. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Page 5968 "Service Document Registers" (pages and codeunits on it, 3 links)Service Document RegistersCodeunit 5999 "Service Experience Tier" (event subscribers)Service Experience TierTable 5965 "Service Contract Header" (referenced by, 4 links)Service Contract Header

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

Properties

Property Value
Caption Service Document Register
DataClassification CustomerContent

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 Source Document Type Enum “Service Source Document Type” — enum Enum 5938 “Service Source Document Type”
2 Source Document No. Δ BC28 Code[20] Specifies the number of the service order or service contract.
3 Destination Document Type Δ BC28 Enum “Service Destination Document Type” Specifies the type of document created from the service order or contract specified in the Source Document No. enum Enum 5937 “Service Destination Document Type”
4 Destination Document No. Δ BC28 Code[20] Specifies the number of the invoice or credit memo, based on the contents of the Destination Document Type field.
32 Invoice Period + BC24 Enum “Service Contract Header Invoice Period” — enum Enum 5997 “Service Contract Header Invoice Period”
33 Last Invoice Date + BC24 Date —
34 Next Invoice Date + BC24 Date —
98 Next Invoice Period Start + BC24 Date —
99 Next Invoice Period End + BC24 Date —

Keys

  • Key1: Source Document Type, Source Document No., Destination Document Type, Destination Document No. (clustered)
  • Key2: Destination Document Type, Destination Document No.

Trigger event subscribers

Procedures

  • InsertServiceSalesDocument(ServDocType: Enum "Service Source Document Type"; ServDocNo: Code[20]; SalesDocType: Enum "Service Destination Document Type"; SalesDocNo: Code[20])
  • PostServiceSalesDocument(SalesDocType: Enum "Service Destination Document Type"; SalesDocNo: Code[20]; InvoiceNo: Code[20])
  • ServiceDocument(SalesDocType: Option Quote,"Order",Invoice,"Credit Memo","Blanket Order"; SalesDocNo: Code[20]; var ServTable: Integer; var ServDocNo: Code[20]): Boolean

Relations

Referenced by

4 fields in 1 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

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: "Service Document Register"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources