Job Posting PMO Assisted Workflow Upload

This integration uploads job postings without all required native fields using Program Office assistance.

Within the UI, if the creator of a Job Posting has the Feature Access flag Program Office will assist with Requisition creation checked on their user profile (i.e. PMO Assisted Workflow), they’re prompted to complete a subset of native fields when creating a Job Posting. The Job Posting PMO Assisted Workflow Upload mirrors this functionality.

Connector Overview

Component

Detail

Company Type

Buyer

MSP Partner

Version Type

API-A-V1.0

Format

CSV

Prerequisites

Company Details setting must be turned on for Integration – Job Posting PMO Assisted Workflow Upload.

User role permission must be turned on for upload data and download data.

Predecessors

Job Posting Templates

Business Units

Cost Centers

Sites

User

Related Connectors

Job Posting Template Upload

Job Posting 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.

Job Posting PMO Assisted Workflow Upload

Send Notification?

No

Determines whether normal messaging workflow should be followed.

This flag is used to control sending notifications to users.

Valid values are:

  • True: Messages will be sent as configured.

  • False: No messages will be sent.

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

Submit

No

Determines the status of in which the job postings will be saved.

Valid values are:

  • True: Job Postings will be considered completed and submitted to the next step in the Job Posting Workflow configured in SAP Fieldglass.

  • False: Job Postings will be saved in Draft status.

If this field is left blank, it will default to True.

Number Format

No

Determines the number format to be used in the file.

This is an optional header value. Determines the number format used in the company.

The valid number format 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".

Date Format

No

Determines the date format to be used in the file.

The valid date format 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 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)

Submit

No Determines the status in which the job postings will be saved.

Transaction Type. The valid values are:

  • True: Job Posting will be considered completed and submitted to the next step in the job posting workflow configured in SAP Fieldglass.

  • False: The job postings will be saved in draft status.

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

External Job Posting Id

Text

100

Yes

Unique Identifier

Any unique identifier of this job posting (as it pertains to this file). When this file is uploaded, SAP Fieldglass automatically assigns each job posting with the next application-generated identifier.

Template ID

Text

16

Yes, if Template Name is not entered.

Example:

  • xxxxJT00001234

System generated template identifier.

Template Name

Text

100

Yes, if Template ID is not entered.

Job Posting Template names are defined in the SAP Fieldglass application.

The name of the job posting template upon which this job posting is based. Job posting template names are defined in the SAP Fieldglass application.

Start Date

Date

Yes

Example:

  • 01/01/2013

Date on which the contract begins.

End Date

Date

Yes

Example:

  • 01/31/2013

Date on which the contract ends.

Is travel required for position?

Text

3

Yes

Valid values are:

  • Yes

  • No

Indicates whether travel time is required for the position. This field defaults to No. If Yes is entered, you can optionally enter the percentage of travel time in the Travel Time’ field.

Travel Time

Number

Conditional

Valid values are:

  • 0 - 100

The percentage of travel required for this position. Only enter data if Is travel required for position? is set to Yes.

Title

Text

100

Yes

SAP Fieldglass recommends the Title field to be the same as the Template Name.

The title of the position requested for this job posting.

SAP Fieldglass recommends that the value of the Title field be the same as the template name. This allows for easy tracking and reporting purposes.

Job Description

Text

10000

No

A description of the position requested on this job posting.

If this field is left blank, the job description from the job posting template becomes the default description for this job posting.

Number of Positions

Number

Conditional

Example:

  • 1

The number of positions requested for this job posting.

If field is left blank and Is Named Job Posting? is Yes/True, it will default to 1.

Site Code

Text

100

Yes

Valid SAP Fieldglass Site Code

The code of the site in which this job posting is located. The site code aids suppliers in knowing where the work occurs, so that appropriate candidates within that locale are submitted. This field also assists suppliers in determining which supplier account manager fulfills the job posting.

The job posting owner must have access to this site in order to create the job posting.

Site names must be defined in the SAP Fieldglass application.

When the buyer is using the Users have access to all Business Unit/Cost Centers and Sites plug-in, the site gets automatically associated to the job posting owner and all those users who can act as a coordinator on upload.

Purchase Unit

Text

100

Conditional

Valid Purchase Unit Code

Purchase Unit associated to the Job Posting.

Location Code

Text

100

Yes

Valid SAP Fieldglass Location Code(s).

Example:

  • loc1~loc2~loc3

The code of the location in which this job posting is located. The Location Code aids suppliers in knowing where the work occurs, so that appropriate candidates within that locale are submitted.

Location name must be defined in the SAP Fieldglass application.

Multiple locations are separated by a tilde (~) and at least one sub-configuration for company configuration Use multiple locations must be enabled.

Primary Location Code

Text

100

Conditional

Valid SAP Fieldglass location code

Indicates primary location code

Enable at least one sub-configuration for the company configuration Use multiple locations.

If the selected primary location isn't listed in the 'Location Code' column, the application displays an error message.

If the 'Primary Location Code' column is blank for records with multiple locations or even a single location, the application displays an error message.

Business Unit Code

Text

200

Yes

Valid SAP Fieldglass Business Unit Codes

The business unit in which this job posting belongs. Business unit codes must be defined in the SAP Fieldglass application, and the job posting owner must have access to this business unit code.

When the buyer is using the Users have access to all Business Unit/Cost Centers and Sites plug-in, the business unit gets automatically associated to the job posting owner and all those users who can act as a coordinator on upload.

Cost Center Code

Text

200

Yes

Valid Cost Center Code

The code of the cost center to which this Job Posting is assigned. The Cost Center Code typically identifies to what cost center (or total estimated budget) this job posting applies, and is used for accounting purposes.

Cost Center Codes must be defined in the SAP Fieldglass application. The job posting owner must have access to this cost center in order to create the job posting.

The Cost Center Code is not directly related to the business unit or the site.

When buyer is using the Users have access to all Business Unit/Cost Centers and Sites plug-in, the cost center gets automatically associated to job posting owner and all those users who can act as coordinator on upload.

If entered cost center code is inactive, the system displays an error message.

General Ledger Account Name

Text

100

This is dependent upon the company configuration and is required if the company has General Ledger account functionality enabled.

General Ledger Account Name

General Ledger (G/L) accounts created in the SAP Fieldglass system.

This field is mutually exclusive with Segmented Object Detail field.

Currency

Text

100

Yes

Example values are:

  • USD

  • CAD

  • GBP

Valid three-character currency code associated with the Cost Center listed in the Cost Center Code field. Only one currency code can be given.

Currency must be associated with the buyer prior to using in this upload.

Legal Entity

Text

100

Conditional

Valid SAP Fieldglass Legal Entity

Legal Entity code associated to job posting.

Company configuration Use legal entity must be turned on for Contingent.

Owner Username

Text

100

Yes

Valid SAP Fieldglass Username

The SAP Fieldglass username of the individual who owns this specific job posting. The owner receives notifications and work items about the job posting. This username must be defined in the SAP Fieldglass application.

Creator Username

Text

10

Yes

Valid SAP Fieldglass Username

The valid SAP Fieldglass username of the individual who creates this specific job posting. The creator of the job posting can be different from the owner of the job posting. This user must be loaded into SAP Fieldglass prior to this file upload.

[c]Job Posting Custom Field 1

Dependent on custom field configuration

No

Dependent on Custom Field type.

Any custom field associated with a job posting. The custom field name should be prefixed with ‘[c]’.

For example, custom field name: 'Job Posting Custom Field 1' will be ‘[c] Job Posting Custom Field 1’.

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

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 not in use.

Unique Identifier

  • External Job Posting ID field

Configuration Considerations

#

Item

Notes

1

External Job Posting ID

A consistent format should be used for the values populated in the External Job Posting ID field. As the actual Job Posting ID is generated by SAP Fieldglass, the External Job Posting ID will be referenced in related uploads of job seekers and work orders related to this Job Posting. As such, it is often a good idea to apply a counter to the end of the ID and increment it by some constant number for each new row.

By applying this consistent counter, you should be able to upload job seekers and worker orders through their respective connectors in the same order, at a later time and with greater ease.

2

Send Notifications?

If False, normal notifications related to the creations, submission, and distribution of job postings will not occur. 

3

Business Unit Code

Site Code

Cost Center Code

If Legal Entity functionality is enabled and utilized by a client, then specific validations may be performed against these core values on the upload. If these values do not match the required validation, then this can cause an error in the upload. Buyers using Legal Entity will need to ensure that their specific validation setups are reflected in their upload values.

Assumptions/Tips

  • All Job Postings that are created through an upload will automatically be in the Full-Serve workflow regardless of the Job Posting Template and User flags.

  • For Rates 2.0:

    • For Job Posting step 'Setup' and actions 'Complete Later' or 'Continue', rates are refreshed; however, Calculated Rates with Rate Rule does not refresh. If action is 'Submit', the system refreshes job posting rates including when Calculated Rates with Rate Rule has 'Use Rule to Calculate Rate at' = Job Posting or Job Posting through Work Order Revision.

    • For other steps when a Job Posting is uploaded, new rates and rate components will refresh from the lookups, and the system will display errors, if applicable. Calculated Rates that use a Rate Rule will not be calculated at this stage; these will be calculated farther in the process. Supplier rates will refresh if the Job Posting uses Supplier Distribution Lookups. Otherwise, the Job Posting values will be distributed to Suppliers.

  • Regarding leading and dependent custom fields:

    • When leading and dependent custom fields have been set up and a buyer downloads a blank upload template for this connector from the user interface, leading and dependent custom fields are automatically added as individual columns.

  • The system reads the value of the leading custom field and validates the first dependent custom field. This process continues for all dependent custom fields in the defined sequence until it is completed.