Details and Examples: Resource Fields Data Set

The 'Resource Fields' data set contains all fields and properties assigned to the resource, and its position in the Resource Tree available in the application by the end of extraction period.

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.

Resource Fields are exported in the Daily Extract file for which 'Resource Fields' is selected as the entity. Any resource properties and fields available in Oracle Field Service (for example, 'Resource ID', 'Status', 'Resource Parent'.) 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 'providers' root element that contains 'provider' elements. 'provider' elements are sets of 'Field' elements whose attributes are names of fields and custom properties defined for the resource and whose contents are their corresponding values.

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

Field	Label	Description
Capacity Bucket	provider.pcapacity_bucket	ID of capacity bucket for the resource.
Child Resource ID	provider_children.child_id	ID of subordinated (child) resource (from resource tree)
Date format (Resource)	provider.pdate_fid	ID of date format for the resource
Email address	provider.email	Email address for the resource
Initial Ratio for Activity Duration	provider.pinitial_ratio	Initial ratio for activity duration for the resource the activity belongs to.
Message Language	provider.planguage	Language for the resource.
Organization	provider.organization_id	ID of organization for the resource
Parent Resource ID	provider_children.parent_id	ID of parent resource for the resource (from resource tree)
Resource External ID	provider.external_id	External system identifier for the resource
Resource ID	provider.pid	Unique internal identifier of the resource.
Resource Name	provider.pname	Name (text identifier) of the resource
Resource Owner Name	provider_owner.pname	Parent resource name for the resource
Resource Parent	provider.parent	ID of parent resource for the resource
Resource Phone	provider.pphone	Phone number of the resource
Resource status	provider.pactive	Resource status (active or inactive).
Resource type	provider.ptype	Resource type ID for the resource
Routing profile	provider.p_rprid	ID of routing plan assigned to the resource
Subordination Level	provider_children.distance	Depth of parent-child resource relations (from resource tree)
Time Zone (Resource)	provider.time_zone	ID of time zone assigned to the resource
Time format (Resource)	provider.ptime_fid	ID of time format for the resource
Working days to start impacting duration estimations	provider.skip_days_for_stats	Integer number of days which must be skipped for natural learning statistics

Note: No changes to this data set.

Resource 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.

This table provides the Resource custom properties that can be configured:

Type	Configurable
String	Yes
Integer	Yes
Enumeration	Yes
File	No

In this example, data is extracted in a file for the following Resource Tree:

This figure shows an expanded list of resources in the Resource Tree.

Image shows resources in the Resource Tree.

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

Unique internal identifier of the resource, for example, Resource ID
Name of the resource, for example, Resource Name
Type of the resource, for example, Resource Type, with the following values
- 1: Mobile Worker
- 2: Organization
- 3: Bucket
flag of the resource status, for example, Is Resource Active, with the following values
- 1: Resource is active
- 0: Resource is inactive
unique identifier of the bucket or organization to which the resource belongs, for example, Owner ID
name of the bucket or organization to which the resource belongs, for example, Owner Name
integer that defines the subordination level, for example, Subordination

Data in the ResourcePosition is collected for the following resources:

Resource 1 named Sunrise Enterprise, of organization type (in our example the type corresponds to 3)
Resource 10000 named Planning, of organization type (in our example the type corresponds to 3)
Resource 11000 named Coast Beach, of a 'Bucket type' (in our example the type corresponds to 2)
Resource 10001 named BARRAGAN, James of a 'Mobile Worker' type (in our example the type corresponds to 1)

In our example BARRAGAN, James belongs to Coast Beach, Coast Beach is a child resource of Planning and Planning belongs to Sunrise Enterprise.

This way all resources are active and:

Resource 10000 (Planning) belong to Resource 1 (Sunrise Enterprise) only and the subordination level is 1
Resource 11000 (Coast Beach) belongs to Resource 10000 (Planning) with subordination level 1 and belongs to Resource 1 (Sunrise Enterprise) with subordination level 2
Resource 10001 (BARRAGAN, James) belongs to Resource 11000 (Coast Beach) with subordination level 1, belongs to Resource 10000 (Planning) with subordination level 2 and belongs to Resource 1 (Sunrise Enterprise) with subordination level 3

<?xml version="1.0" encoding="UTF-8"?>
<providers>
  <provider>
    <Field name=”Resource ID”>10000</Field>
    <Field name=”Resource Name”>Planning</Field>
    <Field name=”Resource Type”>3</Field>
    <Field name=”Is Resource Active”>1</Field>
    <Field name=”Owner ID”>1</Field>
    <Field name=”Owner Name”>Sunrise Enterprise</Field>
    <Field name=”Subordination”>1</Field>
  </provider>
     <provider>
    <Field name=”Resource ID”>11000</Field>
    <Field name=”Resource Name”>Coast Beach</Field>
    <Field name=”Resource Type”>2</Field>
    <Field name=”Is Resource Active”>1</Field>
    <Field name=”Owner ID”>10000</Field>
    <Field name=”Owner Name”>Planning</Field>
    <Field name=”Subordination”>1</Field>
  </provider>
  <provider>
    <Field name=”Resource ID”>11000</Field>
    <Field name=”Resource Name”>Coast Beach</Field>
<Field name=”Resource Type”>2</Field>    <Field name=”Is Resource Active”>1</Field>
    <Field name=”Owner ID”>1</Field>
    <Field name=”Owner Name”>Sunrise Enterprise</Field>
    <Field name=”Subordination”>2</Field>
  </provider>
  <provider>
    <Field name=”Resource ID”>10001</Field>
    <Field name=”Resource Name”>BARRAGAN, James</Field>
    <Field name=”Resource Type”>1</Field>
    <Field name=”Is Resource Active”>1</Field>
    <Field name=”Owner ID”>11000</Field>
    <Field name=”Owner Name”>Coast Beach</Field>
    <Field name=”Subordination”>1</Field>
  </provider>
  <provider>
    <Field name=”Resource ID”>10001</Field>
    <Field name=”Resource Name”>BARRAGAN, James</Field>
    <Field name=”Resource Type”>1</Field>
    <Field name=”Is Resource Active”>1</Field>
    <Field name=”Owner ID”>10000</Field>
    <Field name=”Owner Name”>Planning</Field>
    <Field name=”Subordination”>2</Field>
  </provider>
<provider>
    <Field name=”Resource ID”>10001</Field>
    <Field name=”Resource Name”>BARRAGAN, James</Field>
    <Field name=”Resource Type”>1</Field>
    <Field name=”Is Resource Active”>1</Field>
    <Field name=”Owner ID”>1</Field>
    <Field name=”Owner Name”>Sunrise Enterprise</Field>
    <Field name=”Subordination”>2</Field>
  </provider>
</providers>Resource Location Fields