Details and Examples: Service Request Fields Data Set

Details of fields and custom properties for all service requests created in the application during the extraction period can be extracted.

Important: This information only applies to Oracle Field Service environments. You can verify whether you've Oracle Field Service or Oracle Fusion Field Service, by signing in and checking on the About page.

Service Request Fields are exported in the Daily Extract file for which 'Service Request Fields' is selected as the entity. Any properties and fields used to define service requests in Oracle Field Service (for example, 'Request type', 'Text', 'User ID'.) can be included in the Daily Extract by adding them to the file structure.

Depending on the requirements of the company, the list of exported properties and fields can be changed at any time by removing or adding certain fields.

Data can be retrieved as one or more XML files consisting of 'service_requests' root element which contains 'service_request' elements. 'service_request' elements are sets of 'Field' elements whose attributes are names of the fields and custom properties defined for service requests and whose contents are their corresponding values.

This table provides the label and description for those fields that can be configured:

Field Label Description

Activity ID

support_request.sr_aid

Unique internal identifier of the activity to which the service request was assigned.

Created

support_request.srcreated

Date and time when the service request was created.

Inventory ID

support_request.sr_invid

Unique internal identifier of the inventory to which the service request was assigned.

Resource ID

support_request.sr_pid

Unique internal identifier of the resource to which the service request was assigned.

Service Request Date

support_request.srdate

Date of the service request.

Service Request ID

support_request.srid

Unique internal identifier of the service request.

Service Request Properties

support_request.properties

List of custom service request properties with values.

Service Request Type

support_request.srtype

Type of service request.

User ID

support_request.sr_uid

Unique internal identifier of the user who initiated the service request.

Note: No changes for this data set.

Service request custom properties (except file properties) can be configured and extracted to the Property fields data set. File properties are extracted according to configuration defined in the Property File Fields data set.

Custom properties
Type Configurable

String

Yes

Integer

Yes

Enumeration

Yes

File

No

Example: Service Request Fields file

The following data is collected. Provide a meaningful name to the report.

  • Date and time of the service request, for example, SR Date&Time

  • Unique internal identifier of the resource to which the service request was assigned, for example, SR Resource ID

  • Unique internal identifier of the activity to which the service request was assigned, for example, SR Activity ID

  • Unique internal identifier of the inventory to which the service request was assigned, for example, SR Inventory ID

In the example, a custom property, Importance, corresponds to the importance of the request and has the following values.
  • 1: Critical

  • 2: Average

  • 3: Minor

Details for two service requests: critical request generated at 14:29:15 of November 20, 2013 on Resource 56879 and minor request generated at 17:35:23 of the same date on Inventory 45687.

<?xml version="1.0" encoding="UTF-8"?>
<support_requests>
   <support_request>
      <Field name=”SR Date&Time;”>14:29:15 20-11-2013</Field>
      <Field name=”SR Activity ID”/>
      <Field name=”SR Resource ID”>56879</Field>
      <Field name=”SR Inventory ID”/>
      <Field name=”Importance”>1</Field>
   </support_request>
   <support_request>
      <Field name=”SR Date&Time;”>17:35:23 20-11-2013</Field>
      <Field name=”SR Activity ID”/>
      <Field name=”SR Resource ID”/>
      <Field name=”SR Inventory ID”>45687</Field>
      <Field name=”Importance”>3</Field>
   </support_request>
</support_requests>