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

Page 6270 "Service Order Archives"

Base Application · Microsoft.Service.Archive

Across versions

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

Neighbourhood 2 connected objects and pages

Table 6010 "Service Header Archive" (relates to)Service Header ArchivePage 6271 "Service Order Archive" (pages and codeunits on it)Service Order 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 · BC25-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Service Order Archives
SourceTable Service Header Archive
PageType List
UsageCategory History
ApplicationArea Service

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
ServiceOrderArchives No. No. Specifies the number of the involved entry or record, according to the specified number series. from the table field
Version No. Version No. Specifies the version number of the archived document. from the table field
Date Archived Date Archived Specifies the date when the document was archived. from the table field
Time Archived Time Archived Specifies what time the document was archived. from the table field
Archived By Archived By Specifies the user ID of the person who archived this document. from the table field
Interaction Exist Interaction Exist Specifies that the archived document is linked to an interaction log entry. from the table field
Status Status Specifies the service order status, which reflects the repair or maintenance status of all service items on the service order. from the table field
Order Date Order Date Specifies the date when the order was created. from the table field
Order Time Order Time Specifies the time when the service order was created. from the table field
Customer No. Customer No. Specifies the number of the customer who owns the items in the service document. from the table field
Ship-to Code Ship-to Code Specifies a code for an alternate shipment address if you want to ship to another address than the one that has been entered automatically. This field is also used in case of drop shipment. from the table field
Name Name Specifies the name of the customer to whom the items on the document will be shipped. from the table field
External Document No. External Document No. Specifies a document number that refers to the customer’s numbering system.
Location Code Location Code Specifies the code of the location (for example, warehouse or distribution center) of the items specified on the service item lines. from the table field
Response Date Response Date Specifies the estimated date when work on the order should start, that is, when the service order status changes from Pending, to In Process. from the table field
Response Time Response Time Specifies the estimated time when work on the order starts, that is, when the service order status changes from Pending, to In Process. from the table field
Priority Priority Specifies the priority of the service order. from the table field
Release Status Release Status Specifies if items in the Service Lines window are ready to be handled in warehouse activities. from the table field
Shortcut Dimension 1 Code Shortcut Dimension 1 Code Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
Shortcut Dimension 2 Code Shortcut Dimension 2 Code Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
Assigned User ID Assigned User ID Specifies the ID of the user who is responsible for the document. from the table field
Notify Customer Notify Customer Specifies how the customer wants to receive notifications about service completion. from the table field
Service Order Type Service Order Type Specifies the type of this service order. from the table field
Contract No. Contract No. Specifies the number of the contract associated with the order. from the table field
Document Date Document Date Specifies the date when the related document was created. from the table field
Payment Terms Code Payment Terms Code Specifies a formula that calculates the payment due date, payment discount date, and payment discount amount. from the table field
Due Date Due Date Specifies when the invoice is due. from the table field
Payment Discount % Payment Discount % Specifies the percentage of payment discount given, if the customer pays by the date entered in the Pmt. Discount Date field. from the table field
Payment Method Code Payment Method Code Specifies how to make payment, such as with bank transfer, cash, or check. from the table field
Shipping Advice Shipping Advice Specifies information about whether the customer will accept a partial shipment of the order. from the table field
Warning Status Warning Status Specifies the response time warning status for the order. from the table field
Allocated Hours Allocated Hours Specifies the number of hours allocated to the items in this service order. from the table field
Expected Finishing Date Expected Finishing Date Specifies the date when service on the order is expected to be finished. from the table field
Starting Date Starting Date Specifies the starting date of the service, that is, the date when the order status changes from Pending, to In Process for the first time. from the table field
Finishing Date Finishing Date Specifies the finishing date of the service, that is, the date when the Status field changes to Finished. from the table field
Service Time (Hours) Service Time (Hours) Specifies the total time in hours that the service specified in the order has taken.
Your Reference Your Reference Specifies a customer reference, which will be used when printing service documents. from the table field

Actions

Group Action ToolTip Runs
Version Dimensions View dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.
Comments View comments for the record. Page 6266 “Service Archive Comment Sheet”

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: "page", object_name: "Service Order Archives"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources