SAP Knowledge Base Article - Public

3425858 - Standard Data Fields for Career Site Builder Job Distribution - Recruiting Marketing

Symptom

If a customer wishes to use CSB XML Feeds to distribute job postings to job boards/external vendors, there are a basic number of data fields to create job feeds. 
The feed options are based on the source templates developed in collaboration with the vendors based on the fields that they require. 
For these source options there are standard fields that are required in order to map effectively and then there are fields that are strongly recommended for best practice.  

This KBA provides these lists.

Environment

SAP SuccessFactors Recruiting Marketing

Resolution

Best Practice Job Fields & Alignments in Field Mapping to support XML Feeds

System Defaults

XML Field Nodes          (Will be adjusted by feed)

Defined

Notes

title

External Job Title

 

date

Position RMK Create Date

Format: Fri, 13 07 2012 00:00:00 GMT

referencenumber

RMK Specific ID

This is the same ID that appears on the unique job URL

ID

RCM Internal ID (Req ID)

Includes job locale - Format: “-en_US” or “-de_DE”

url

Career Site Job Apply URL

Landing page from vendor

company

Company Name in Command Center

May also appear under “publisher”

city

Primary Job City

Must be a physical, proper city name (not “REMOTE” or “Multiple Locations”)

state

Primary Job State (ISO CODE)

Required (US/CA/AU) 2 Digit Country Code in US & CA – 3 Digit in AU

postalcode

Primary Job Postal Code

Needed for proper accurate radial search by primary physical location

country

Primary Job Country (ISO CODE)

Required 2 Digit Country Code

location

Combined Job Location

Format: City, State, Country

description

RCM Job Description with header and footer

Combines ATS Description, Qualifications, Company Details, etc. into 1 field

locale

Job Locale

Language version (multi-language jobs will appears with unique locales)

brand (when required)

Brand Identifier Code

This is not the official brand name, only branding template label

 

Required Mapping

XML Field Nodes         (Will be adjusted by feed)

Defined

Proper Alignment/Use

Notes

department

RCM Category

Job Function or Primary Job Category

Used for vendor job classification and search categorization

dept

RCM Department

Specialization or Department

Secondary departmental mapping 

businessunit

RCM Business Unit

Brand Name or Divisional Label

Used in order to display to vendors the secondary brand name for advertising

facility

RCM  Facility

Physical Location Name or Address

Alternative for brand name if businessunit field filled

 

Additional Fields (not required but nice to have)

XML Field Nodes         (Will be adjusted by feed)

Defined

Proper Alignment/Use

Notes

shifttype

RCM Job Type

Permanent/Temporary/Etc

 

shift

RCM Shift

Full Time/Part Time/Etc

 

productservice

RCM Product Service

Supplemental department alignment

Can be leveraged for salary range if required

compensation

RCM Compensation

Currency Based

Not generally shared

travel

RCM Travel

Percentage

Not generally shared

adcode

RCM Adcode

Filtering Code. Picklist. Can be used for exclusion code, req id, other

Identifying job coding

recruiterid

Recruiter Alias

If passing recruiter info to vendor

Not generally shared

customfield1

Additional RCM Data

Custom Realigning Field

Misc fields for general use when other fields don’t align to be populated.

customfield2

Additional RCM Data

Custom Realigning Field

customfield3

Additional RCM Data

Custom Realigning Field

customfield4

Additional RCM Data

Custom Realigning Field

customfield5

Additional RCM Data

Custom Realigning Field

 

The feeds themselves are able to be generated by the SAP Professional Services team or by implementation partners with access to the Career Site Builder backend system (Command Center).  In certain scenarios the SAP PS team can moderately adjust source templates to adapt to non-standard field mapping. For example, naming conventions of the fields can be adapted to match the customer's schema. However, for feed and system efficiency it is strongly recommended to maintain the best practice process of field mapping and not altering the field naming conventions unless required for vendor connections.  Most vendors can accept the field labels that are provided and adapt the job collection to align to their import values. 

See Also

2361686:  XML Feeds - Recruiting Marketing

Keywords

mapping , KBA , LOD-SF-RMK-MED , RMK Media Requests and Feeds , How To

Product

SAP SuccessFactors Recruiting all versions