Job Posting Upload

Create a variant of the Job Posting Upload for Employee Central transmissions, which is used to map in the Position API data received to the job posting template.

For information on creating a variant, see https://help.sap.com/viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/8a2506aa422f4f9198d1678a552f2751.html?q=variant.

For information on working with column transforms, see https://help.sap.com/viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/5cc0fc50a7b646de869906756ea12a76.html?q=%22transform%20column%22.

To view the SAP SuccessFactors Employee Central Position Management API for employee position management, go to https://api.sap.com/api/ECPositionManagement/schemaInformation published on SAP site.

Connector Properties

Property

Value

Comments/ Notes

Official Connector Name

Job Posting

  

Real Time vs. Batch

Real Time

  

Transfer Method

API

  

File Type

    

Frequency

Real Time

  

Field Layout/ Data Mapping

See Detail section below.

  

Bulk vs. API (Processing Framework – Upload only)

API

  

Record Inclusion Logic (Upload)

Per Position ID

  

Variant Integration Connector Name

Requisition Upload EC

Required variant connector name.

Variant Code

EC

  

Header

Header information defaults within the connector settings.

Detail

  • Add an entry for "General Ledger Account Name" if GLAs are enabled for the buyer.

  • Owner transform could append the buyer code if usernames append the buyer code.

Use Upload Column Transform to map defaults for the following fields and to map the SAP SuccessFactors fields to the SAP Fieldglass fields as per the following table.

  • Number of Positions = 1

  • Coordinator Username = [buyer]@FG_HELP

  • Creator Username = [buyer]@FG_HELP

  • Job Seeker Rate can be increased = Yes

  • Hours per Week = 40

  • Hours per Day = 8

To enable SAP Fieldglass to correctly receive data from SAP SuccessFactors, refer to the mapping table below. You’ll need to configure the connector using Upload Column Transform in the Configuration Manager. To complete the setup:

  1. Navigate to the Upload Column Transform page.

  2. Choose Add Native Fields.

  3. Choose the Standard Column Name that corresponds to the SAP Fieldglass Field Header Name listed in the first column of the table below.

  4. In the File Column Name field, enter the corresponding SAP SuccessFactors Mapping (Entity) from the second column of the table.

  5. Choose Update to save the changes.

SAP Fieldglass Field Header Name

SAP SuccessFactors Mapping (Entity)

Required

Value/ Format

Description/ Use/ Field Rules

Template Match Criteria

Template Name

externalName_[language]

(for example, externalName_en_US)

+ ' | ' +

jobLevel

(Position)

Yes

Examples:

Administrative Assistant | EntryAssistant Administratif | Niveau

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

Language for template name is derived off of the job posting owner user profile (owner username). Direct Match lands on page 2 (augment) of the job posting submission page. No match lands on page to create a job posting.

Title

Same as SAP Fieldglass template.

Yes

  

The title of the position requested for this job posting.

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

  

Job Description

description

(Position)

No

  

Description of the position requested on this job posting.

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

  

Business Unit Code

businessUnit

(Position)

Yes

ACE_CORP

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.

  

Site Code

location

(Position)

Yes

AU_SYD

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.

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.

  

Location Code

location

(Position)

Yes

AU_SYD

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.

  

Start Date

effectiveStartDate

(Position)

Yes

2013-04-11T00:00:00

Date on which the contract begins.

End Date

effectiveEndDate

(Position)

Yes

2013-05-11T00:00:00

Date on which the contract ends.

Owner Username

Owner

(Position)

Yes

  

SAP Fieldglass username of the person 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.

Match on SAP Fieldglass user. Owners default language drives matching logic against the job posting template. A separate template is set up in SAP Fieldglass for each language.

Cost Center Code

costCenter

(Position)

Yes

35106

Code of the cost center this job posting is assigned to. 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 isn't directly related to the business unit or the site.

  

Hours per Week

standardHours

(Position)

Yes

  

Standard number of hours per week for this position on this job posting.

Yes, if some Hours per Week value isn't set on site or in buyer’s company configuration.

  

Comments

comment

(Position)

No

ACC-MGR

    

Job Code

jobcode

(Position)

Yes

ACC-MGR

    

[c] Job Code

jobcode

(Position)

No

Manager

  

[c] Job Level

jobLevel

(Position)

No

Salary Grade 13

    

[c] Pay Grade

payGrade

(Position)

No

Employee

    

[c] Employee Class

employeeClass

(Position)

No

      

c] Position ID

Code

(Position)

No

    

Added for application visibility.