Parent Company Task Code Upload

This integration uploads parent company task codes into child companies based on the Parent Company Mapping Rule.

Connector Overview

Component

Detail

Company Type

Buyer

Version Type

BULK-FULL-V1.0

Format

CSV

Prerequisites

Company plug-ins must be turned on for Integration – Parent Company Task Code Upload

User role permission must be turned on for Upload Data and Download Data.

Predecessor

Legal Entities (if enabled for buyer)

Business Units

Cost Centers

Related Connectors

Standard Cost Centers Upload

Task Code Upload

File Formatting

Header

Component

Required?

Definition/Use

Notes

Value

Type

Yes

Upload File Type

If you have a custom connector name for a standard connector, you may use the exact same custom name for the Type header; otherwise, you must use the standard name shown in the Value field.

Parent Company Task Code Upload

Transaction

No

Transaction Type

Transaction Type. The valid type names are:

  • True: If any record errors, the entire upload fails.

  • False: Only records in error fail. Remaining records are committed successfully.

If this field is not included in the header, the default value will be True.

Number Format

No

Determines the Number Format to be used in the file.

The valid values are:

  • “#,##9.99" (Example: "1,234,567.99”)

  • “#.##9,99" (Example: "1.234.567,99”)

  • “#'##9.99" (Example: "1'234'567.99”)

  • “# ##9,99" (Example: "1 234 567,99”)

The quotes are required even if the value does not have a comma in it. If this field is not included in the header the default value will be "#,##9.99" (Example: "1,234,567.99").

Date Format

No

Determines the date format to be used in the file.

The valid values are:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

If this field is not included in the header, the default value will be MM/DD/YYYY.

Language

No

Determines the language to be used for values in the file, such as drop-down lists and radio buttons. Column headers will always default to the upload user's preferred language.

The valid language values are:

Arabic (Standard Arabic)
Chinese (Simplified)
Chinese (Traditional)
Dutch (Netherlands)
English (United Kingdom)
English (United States)
French (Canada)
French (France)
German (Germany)
Hebrew (Israel)
Hungarian (Hungary)
Italian (Italy)
Japanese (Japan)
Korean (Korea)
Mongolian (Mongolia)
Polish (Poland)
Portuguese (Brazil)
Portuguese (European)
Russian (Russia)
Spanish (Mexico)
Swedish (Sweden)

Comments

No

Upload Comments

This is a comment field containing notes about the upload file.

Immediately following the Header section of the upload is one blank line.

Detail

Column Header Name

Data Type

Length

Required?

Value(s)/Format

Description/Use/Field Rules

Task Code

Text

100

Yes

Valid SAP Fieldglass Task Code

Value that uniquely describes the child company task code.

Task Name

Text

100

Yes, for Add only.

Value that uniquely describes the child company task code in more recognizable terms than the Task Code.

Description

Text

1000

No

Optional long text description of the child company task code.

Billable Flag

Text

3

No

Valid values are:

  • Yes

  • No

Flag that indicates whether or not the task is billable.

If left blank, the Billable Flag will default to Yes.

Capitalized Flag

Text

3

No

Valid values are:

  • Yes

  • No

Task Code Adjustment

Text

100

No

Adjustment Code that is present for the specific task code

Include in Tenure

Text

3

Conditional

Valid values are:

  • Yes

  • No

Flag to indicate if task code should be included in tenure calculation.

The 'Track tenure by time worked' configuration must be enabled.

If field left blank or invalid value is entered, this field will default to 'No'.

General Ledger Account Name

Text

100

Yes, for Adds and Updates only

General Ledger Account associated to the task.

In certain configurations of Fieldglass, Task Codes may be associated to multiple General Ledger Accounts. In order to accomplish this through the upload, multiple GL Accounts may be included in this field separated by a tilde (~).

(i.e. 100~200~300)

Original Code

Text

400

No

Identifies original code for the task code. Multiple task codes may have the same Original Code.

[c] Task Custom Field[x]

Dependent upon Custom Field Type

Dependent upon Custom Field Type

Dependent upon Custom Field Type

Any custom field associated with the Task Code module. The custom field name should be prefixed with ‘[c]’. For example, custom field name: ‘TC Custom Field 1’ should be ‘[c] TC Custom Field 1’.

Valid values of the custom field are configured during the setup of the Fieldglass system.

When Custom Field Type = Segmented Pick List and the Autopopulate Segment rule on the Pick List = Yes, if a segment value is left blank on the upload, the value is auto populated on the document if there is only one possible value based on the previous segment values. If there is more than one possible value, an error message displays.

Do not include this field if it is not being used.

Unique Identifier

  • Task Code field

Configuration Considerations

#

Item

Notes

1

Task Name

Task names appear throughout the application. If possible, utilize a consistent and useful naming convention to ensure uniqueness throughout your organization and meaningfulness to the users.