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

Table 6014 "Service Order Allocat. Archive"

Base Application · Microsoft.Service.Archive

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-27unchanged
  4. BC2815 fields changed
  5. BC29-30unchanged

Neighbourhood 8 connected objects and pages

Table 152 "Resource Group" (relates to)Resource GroupTable 156 "Resource" (relates to)ResourceTable 231 "Reason Code" (relates to)Reason CodeTable 5940 "Service Item" (relates to)Service ItemTable 6011 "Service Item Line Archive" (relates to)Service Item Line ArchivePage 6273 "Service Order Allocat. Archive" (pages and codeunits on it, 3 links)Service Order Allocat. ArchiveCodeunit 5999 "Service Experience Tier" (event subscribers)Service Experience TierTable 6010 "Service Header Archive" (referenced by, 2 links)Service Header Archive

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.Archive · captioned “Service Order Allocation Archive” · BC25-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Service Order Allocation Archive
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 Entry No. Δ BC28 Integer Specifies the number of the entry, as assigned from the specified number series when the entry was created.
2 Status Δ BC28 Option Specifies the status of the entry, such as active, non-active, or cancelled. OptionCaption: Nonactive,Active,Finished,Canceled,Reallocation Needed
3 Document No. Δ BC28 Code[20] Specifies the number of the service order associated with this entry.
4 Allocation Date Δ BC28 Date Specifies the date when the resource allocation should start.
5 Resource No. Δ BC28 Code[20] Specifies the number of the resource allocated to the service task in this entry. TableRelation Table 156 “Resource”
6 Resource Group No. Δ BC28 Code[20] Specifies the number of the resource group allocated to the service task in this entry. TableRelation Table 152 “Resource Group” (Resource Group)
7 Service Item Line No. Δ BC28 Integer Specifies the number of the service item line linked to this entry. TableRelation Table 6011 “Service Item Line Archive” (“Service Item Line Archive”.“Line No.” where(“Document Type” = field(“Document Type”), “Document No.” = field(“Document No.”), “Doc. No. Occurrence” = field(“Doc. No. Occurrence”), “Version No.” = field(“Version No.”)))
8 Allocated Hours Δ BC28 Decimal Specifies the hours allocated to the resource or resource group for the service task in this entry.
9 Starting Time Δ BC28 Time Specifies the time when you want the allocation to start.
10 Finishing Time Δ BC28 Time Specifies the time when you want the allocation to finish.
11 Description Δ BC28 Text[100] Specifies a description for the service order allocation.
12 Reason Code Δ BC28 Code[10] Specifies the reason code, a supplementary source code that enables you to trace the entry. TableRelation Table 231 “Reason Code” (Reason Code)
13 Service Item No. Δ BC28 Code[20] Specifies the number of the service item. TableRelation Table 5940 “Service Item” (“Service Item”.“No.”)
14 Posted Boolean —
16 Service Item Serial No. Δ BC28 Code[50] Specifies the serial number of the service item in this entry.
18 Service Started Boolean —
19 Document Type Δ BC28 Enum “Service Document Type” Specifies the type of the document (Order or Quote) from which the allocation entry was created. enum Enum 5900 “Service Document Type”
5047 Version No. Integer —
5048 Doc. No. Occurrence Integer —

Keys

  • Key1: Document Type, Document No., Doc. No. Occurrence, Version No., Entry No. (clustered)
  • Key2: Document Type, Document No., Doc. No. Occurrence, Version No., Allocation Date, Resource No., Status, Resource Group No.

Trigger event subscribers

Relations

Referenced by

2 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 Order Allocat. Archive"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources