Job Posting Update Upload

This integration uploads job posting edits.

The Job Posting Update Upload mimics the UI feature to edit the job posting by only changing the title, description and other determined fields without creating a revision. The upload allows the users to do the same edits you can do in the UI to multiple job posting records at the same time.

Connector Overview

Component	Detail
Company Type	Buyer
Version Type	API-V1.0
Format	CSV
Prerequisites	Company plug-ins must be turned on for Integration – Job Posting Update Upload. User role permission must be turned on for Upload Data and Download Data.
Predecessors	N/A
Related Connectors	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 Update Upload
Transaction	No	Only applicable for the API-V1.0 version. Transaction Type	Transaction Type. The valid type names are: True: If any record errors, the entire upload fails. False: Only records that are in error fail. Remaining records are committed successfully. If this field is not included in the header, the default value will be True.
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)
Number Format	No	Determines the number format to be used in the file.	This is an optional header value. It 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.
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

Field Header Name	Data Type	Length	Required?	Value(s)/Format	Description/Use/Field Rules
Job Posting ID	Text	16	Yes, if Job Posting External ID is blank.	Example: FGFGJP00000010	The SAP Fieldglass Job Posting ID is used to identify the job posting that needs to be edited.
External Job Posting ID	Text	100	Yes, if Job Posting ID is blank.	User entered value.	The external job posting ID that is used to identify the job posting that originates in an external system. If more than one job posting has same external reference ID, an error is displayed.
New External Job Posting ID	Text	100	No	User entered value.	External job positng ID for when the job posting originates in SAP Fieldglass, then is sent to an external system that creates this ID that then can be used to match to the SAP Fieldglass Job Posting ID.
Job Posting Title	Text	100	No	Example: Business Analyst	Any title appropriate for a Job Posting. The Job Posting Template rule Creator can change JP Title needs to be enabled. If the rule is not enabled in the corresponding Job Posting Template, the upload will show an error. This value can be edited in any status of the Job Posting.
Job Posting Description	Text	10000	No	Example: Self-starter with strong Business analysis experience and relevant data analysis experience.	Any description appropriate for a Job Posting. The Job Posting Template rule Creator can change JP External Description needs to be enabled. If the rule is not enabled in the corresponding Job Posting Template, the upload will show an error. This value can be edited in any status of the Job Posting.
Owner Username	Text	100	No	Valid username from SAP Fieldglass with proper permissions.	Username of the new Job Posting Owner. The user should be a valid user of the corresponding buyer company. If user is invalid, an error will be shown This value can be edited in any status of the Job Posting. If the Enhanced Legal Entity Validation configuration is enabled for the company, the system validates if the owner has visibility to the job posting legal entity, business unit, cost center, and site codes. If even one of these is not associated to the owner, the system displays an error message.
Reassign Pending Work Items Owner	Text	3	No	Valid values are: Yes No	Indicates if pending work items should be reassigned to new owner. This value is only used when the Owner user is changed in the same record. If the value is left blank, it will be defaulted as a No.
Coordinator Username	Text	100	No	Valid username from SAP Fieldglass with proper permissions	User name of the new Job Posting Coordinator. The user should be a valid coordinator user of the corresponding buyer company. If user is invalid, an error will be shown. This value can be edited in any status of the Job Posting. If the 'Enhanced Legal Entity Validation' configuration is enabled for the company, the system validates if the coordinator username has access to the job posting business unit and legal entity and has the 'Coordinator' user profile flag enabled. If not, the system displays an error message.
Reassign Pending Work Item Coordinator	Text	3		Valid values are: Yes No	This value is only used when the Coordinator user is changed in the same record. If the value is left blank it will be defaulted as a No.
Distributor Username	Text	100	No	Valid username from SAP Fieldglass with proper permissions.	User name of the new Job Posting Distributor. The user name should be validated depending on the Job Posting Template Distribution Rule. The upload will show an error if the user is invalid. This value can only be changed if Distribution Rule are enabled in the job posting template. If the rule is not set in the Job Posting Template, the upload will show an error. This value can be edited in any status of the Job Posting. If the Enhanced Legal Entity Validation is enabled for the company, the system validates if the distributor username has access to the job posting business unit and the legal entity and has the 'Distributor' user profile flag enabled. If not, the system displays an error message.
Reassign Pending Work Item Distributor	Text	3		Valid values are: Yes No	This value is only used when the Distributor user is changed in the same record. If the value is left blank it will be defaulted as a No.
Project Code	Text	100	No	Valid project code from SAP Fieldglass.	Project code of the new project for the Job Posting. The Project code value should correspond to an existing and valid project of the buyer company. If the value is invalid, the upload will show an error. Pass value [Blank] (not case sensitive) to remove previously selected project and leave it blank. Company configuration 'Project' needs to be selected for the corresponding company. If this configuration is not enabled, the upload should show an error. This value can be edited in any status of the Job Posting.
Number of Positions	Number		No	Valid values are: 0-99999	Numeric value that is equal to or greater than the total number of hired positions for this job posting. Field can only be edited for Job Postings in Submitted or Halted status. Field cannot be edited for a Named Job Posting. Field cannot be edited for Shift Manager Job Postings. User Role Permission 'Edit Job Posting Number of Positions after Creation' needs to be enabled.
Maximum Submission	Number		No	Valid values are: 1-9999	The number of job seekers a supplier can submit against this particular job posting. If Company Edit Configuration/Maximum number of submittals per Supplier / Lock default values is selected, then the upload will show an error if a value is passed for this field. If the Lock default values is not selected then the value can be updated in any status.
Disallow Approval of Time Sheet/Expense Sheet/Invoice when Job Posting Estimated Spend is exceeded	Text	3	Conditional	Valid values are: Yes No	This field indicates whether the approval of time sheet, expense sheets, and invoices will be disallowed when the job posting estimated spend is exceeded when Shift Manager is enabled. Company configuration Use Shift Manager must be enabled. The value in this column will be ignored and will default to what is on the template if the field was locked during creation of the job posting template ID. If this field is blank or missing, it will default to No.
Creator can add and remove Rate Codes or Rate Schedules	Text	3	No	Valid values are: Yes No	Rule to allow changes on Pay Rates. This value can only be edited if the Job Posting is in a ‘Submitted’, ‘Halted’, or ‘Closed’ status. If the Job Posting is in any other status, the upload will show an error.
[c] job posting custom field 1	Dependent on custom field configuration	Dependent on custom field configuration	Dependent on custom field configuration	Dependent on custom field configuration.	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

Job Posting ID field

Configuration Considerations

#	Item	Notes
1	Job Posting Title	The Job Posting Template rule Creator can change JP Title needs to be enabled. If the rule is not enabled in the corresponding JPT, then the upload will show an error.
2	Job Posting Description	The Job Posting Template rule Creator can change JP External Description needs to be enabled. If the rule is not enabled in the corresponding Job Posting Template, then the upload will show an error.
3	Distributor	User name of the new Job Posting distributor. The user name should be validated depending on the Job Posting Template Distribution Rule. The upload will show an error if the user is invalid.
4	Change Project	Company configuration Project needs to be selected for the corresponding company. If this configuration is not enabled, then the upload should show an error.

Assumptions/Tips

When the company configuration Distribution selected by distributor before approval is enabled along with the sub-configuration Submit JP to Suppliers before any approvals (Editor selects Suppliers in Program Office Assisted Workflow), the distribution logic will send job postings to Level 1 suppliers at job posting submit. It will then send job postings to remaining distribution levels based on the distribution time(s) specified in their job posting distribution list (job posting no longer needs to be approved to send to remaining distribution levels).
If the Number of Positions is changed in this upload, the Maximum Submissions per Supplier will be automatically recalculated.
Custom fields with defined values cannot be changed with this connector. Please use the Custom Field Update Upload connector.
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.