|
External Job Posting ID |
Text |
100 |
Yes |
|
An external job posting identifier used by the client for tracking purposes. |
|
Creator Username |
Text |
100 |
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.
If the 'Enhanced Legal Entity Validation' configuration is enabled for the company and if the Creator Username is not the same as the Owner Username, then system must validate if the creator and owner both have visibility to the job posting legal entity, business unit, cost center and site codes. If even one of them is not associated to either the creator or the owner, the system displays an error message. |
|
Template ID |
Text |
16 |
Yes, if Template Name is not entered. |
Example:
|
System generated template identifier.
If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have the legal entity and business unit visibility to the template, otherwise the system displays an error message. |
|
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.
If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have the legal entity and business unit visibility to the template, otherwise the system displays an error message. |
|
Buyer reference |
Text |
100 |
No |
|
Used to set buyer reference value on the job posting. |
|
Title |
Text |
100 |
Yes |
Example:
|
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. |
|
Number of Positions |
Number |
|
Conditional |
Example:
|
The number of positions requested for this job posting.
If this field is left blank and Is Named Job Posting? is Yes or True, this field defaults to 1. |
|
Job Description |
Text |
10000 |
No |
|
A description of the position requested on this job posting.
If this field is left null/blank, the job description from the job posting template becomes the default description for this job posting.
Use the following HTML tags to format text in supported fields:
<strong>Your text</strong>
<em>Your text</em>
<span style="text-decoration: underline;">Your text</span>
<ul>
<li>Bullet Item 1</li>
<li>Bullet Item 2</li>
</ul>
These will render as bold text, italics, underlined text, and bullets, respectively.
Remember:
-
Tags must be opened and closed (for example., <strong> ... </strong>)
-
Tags can be combined: <strong><em>Bold and italic</em></strong>
-
Plain text fields do not render HTML — only use in fields that support rich text
|
|
Are workers project-based? |
Text |
3 |
No |
Valid values are:
|
Indicates if workers are project based.
If this field is left blank, it uses the value from the Contingent Type. |
|
Currency |
Text |
100 |
Yes |
Valid SAP Currency Code.
Examples are:
|
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. |
|
Business Unit Code |
Text |
100 |
No |
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 configuration, the business unit is automatically associated to the job posting owner and all those users who can act as a coordinator on upload.
If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have visibility access to the business unit code, and the business unit code must have visibility to the job posting legal entity.
If the entered business unit code is not associated with either the creator or the owner, the system displays an error message.
If the entered business unit code does not have visibility to the job posting legal entity, the system displays an error message.
If field is left blank, the value is defaulted to the job posting owner's business unit. |
|
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 codes 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 configuration, the site is automatically associated to the job posting owner and all those users who can act as a coordinator on upload.
If 'Enhanced Legal Entity Validation' configuration is enabled for the Company, the creator and owner must have visibility access to the site code and the site code must have visibility to the job posting legal entity.
If the site code is not associated with either the creator or the owner, the system displays an error message.
If the site code does not have visibility to the job posting legal entity, the system displays an error message. |
|
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:
|
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 codes must be defined in the SAP Fieldglass application.
Multiple codes are separated by a tilde (~) when at least one sub-configuration for company configuration Use multiple locations is 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. |
|
Start Date |
Date |
|
Yes |
Example:
|
Date on which the contract begins. |
|
End Date |
Date |
|
Yes |
Example:
|
Date on which the contract ends. |
|
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.
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. |
|
Coordinator Username |
Text |
100 |
Conditional
This is only a required value for buyers utilizing MSP services within SAP Fieldglass |
Valid SAP Fieldglass Coordinator Username |
The SAP Fieldglass username of the individual who coordinates this specific job posting. The coordinator can be responsible for defining and reviewing a job posting, as well as on-boarding activities, such as setting up security badges for new employees. Typically, the coordinator is assigned to the buyer’s MSP.
The Coordinator Username must be defined in the SAP Fieldglass application. Leave the Coordinator Username blank if no coordinator exists.
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. |
|
Distributor Username |
Text |
100 |
No |
Valid job posting distributor username. |
Sets distributor on the job posting if Distribution Type is 'Distributor selects Suppliers before any approvals or Distributor selects Suppliers after final approval'.
If the Enhanced Legal Entity Validation configuration 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. |
|
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 configuration, the cost center is automatically associated to job posting owner and all those users who can act as coordinator on upload.
If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have visibility access to the cost center code and the cost center code must have visibility to the job posting legal entity.
If the cost center code is not associated with either the creator or the owner, the system displays an error message.
If entered cost center code does not have visibility to the job posting legal entity, the system displays an error message.
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.
When the Allows Unknown Cost Center Validation and GLA allocation on Job Postings and Statements of Work is required company configurations are enabled, the software supports unknown cost center functionality. It also suppresses SOD or GLA allocation for unknown cost centers. |
|
Segmented Object Detail |
Text |
2000 |
Conditional |
Examples:
-
IS|Admin|12001
-
IS-Admin-12001
-
IS;Admin;12001
-
IS:Admin:12001
|
Multiple accounting strings that can be assigned to a worker.
Segments are separated by delimiter on the segmented object. Valid delimiters are colon (:), semi-colon (;), pipe (|) and dash (-).
Required if 'Segmented object detail' set.
If the buyer company has Segmented object detail based allocation is required company configuration enabled, then the field must be associated to a Pick List which has the first segment as Active Legal Entity.
This field is mutually exclusive with GL Account fields.
When the Allows Unknown Cost Center Validation and Segmented object detail based allocation is required company configurations are enabled for Contingent cost centers, the software supports unknown cost center functionality. It also suppresses SOD or GLA allocation for unknown cost centers. |
|
Estimated Expense % |
Decimal |
|
No |
Example:
|
The estimated expense percentage of the total estimated cost for this job posting. Example: 1.25% should be entered as 1.25, not .0125. |
|
Estimated Additional Spend % |
Decimal |
|
No |
Example:
|
Percentage of the total number of hours per week. This is used by SAP Fieldglass to calculate the total estimated cost for this job posting. Example: 1.25% should be entered as 1.25 not .0125. |
|
Job Seeker Rate can be increased |
Text |
3 |
Yes |
Valid values are:
|
This field indicates whether the bill rate can be increased in the work order.
If this field is set to No, the bill rate that is presented in the job seeker must be less than or equal to the bill rate presented in the job. The Job Seeker Bill Rate cannot be greater than the Job Posting Bill Rate.
If this field is set to Yes, then the bill rate that is presented in the job seeker can be greater than the bill rate presented in the job posting.
If company configuration Enable Rates 2.0 is enabled, this rule no longer controls whether the user can enter zero because that is now controlled by the job posting template rule 'Creator can edit Rate values on Job Posting'. |
|
Allow Job Seeker Submissions Below Minimum Requested Pay Rate |
Text |
3 |
No |
Valid values are:
|
You can view this column only if Enable Rates 2.0 is on and Service Type is Temp.
When enabled, this rule allows suppliers to submit job seekers below the minimum requested pay rate. This rule applies only to rates that use a pay-rate based rate component group.
If left blank, this field borrows the value set on this rule on your job posting template.
If you have locked or hidden the rule Allow Job Seeker Submissions Below Minimum Requested Pay Rate on the contingent type, then any value you enter here will be ignored. |
|
Allow Deductions to be Submitted on Time Sheet |
Text |
3 |
Conditional |
Valid values are:
|
Determines whether the workers can submit deductions on their time sheets
Company configuration Deduction must be enabled.
This field defaults to the value from the job posting template if company configuration Deduction is locked or in case of company configuration is not locked and this field is left blank. |
|
Respond by Date |
Date |
|
No |
Example:
|
The respond by date identifies the time in which the suppliers must respond to the job posting with job seekers.
If this field is null/blank, the Job Posting Start Date is taken as the Respond by Date. |
|
Hours per Week |
Decimal |
|
Yes, if Hours per Week value is not defined for the site or in the buyer’s company configuration. |
Example:
|
The standard number of hours per week for this position on this job posting.
This is required if the Hours per Week value is not defined for the site or in the buyer’s company configuration. |
|
Days for Estimated Spend |
Decimal |
|
Conditional, if Job Posting Template rule Hours/Days for Committed Spend is set to ‘Creator enters’ AND committed spend rate UOM is set to ‘Days’ |
Example:
|
Indicates days per estimated spend. |
|
Hours for Estimated Spend |
Decimal |
|
Conditional, if Job Posting Template rule Hours/Days for Committed Spend is set to ‘Creator enters’ AND committed spend rate UOM is set to ‘Days’. |
Example:
|
Indicates hours per estimated spend. |
|
Is Named Job Posting? |
Text |
5 |
No |
Valid values are:
|
Indicates if job posting has a named worker associated with it.
If field is left blank, it defaults to No. |
|
Workforce ID |
Text |
16 |
Conditional |
Valid SAP Fieldglass Worker ID
Example:
|
Indicates worker named to job posting.
Required if Is Named Job Posting? is set to Yes or True. |
|
Hours per Day |
Decimal |
|
Yes |
Example:
|
The standard number of hours per day for this position on this job posting. |
|
Travel Time |
Decimal |
|
No |
Example:
1.25% should be entered as 1.25, not .0125. |
The percentage of travel required for this position on this job posting. |
|
Maximum Submission |
Number |
|
No |
Example:
|
The number of job seekers a supplier can submit against this particular job posting.
If left blank, each supplier may submit an unlimited number of job seekers in response to the job posting. |
|
Flat Adjustment |
Number |
|
No |
Example:
|
Flat adjustment amount applied to the job posting estimated spend.
Flat adjustment value can be positive or negative. Users can enter the value for flat adjustment from -99999999 to 999999999. |
|
Comments |
Text |
2000 |
No |
|
Any comments added to this job posting. |
|
Address 1 |
Text |
600 |
No |
Example:
|
Address of work location. |
|
Address 2 |
Text |
600 |
No |
Example:
|
Address of work location. |
|
City |
Text |
50 |
No |
Example:
|
City of work location. |
|
State/ Province |
Text |
50 |
No |
Example:
|
State/province of work location. |
|
Country/Region |
Text |
3 |
No |
Example:
|
Country/region of work location. |
|
ZIP/Postal Code |
Text |
20 |
No |
Example:
|
Postal code of work location. |
|
Site Tax |
Decimal |
|
No |
Example:
|
Percentage of site tax for work location. Example: 1.25% should be entered as 1.25, not .0125. |
|
Suppliers |
Text |
10000 |
No |
Valid Supplier Code or Codes
Examples:
|
Use this field to control supplier distribution of job postings. Only valid supplier codes from the template distribution list can be used. If code is specified as [ALL], then all suppliers in the template distribution list receive the job posting. Codes should be delimited by “~”.
The field values are dependent upon the distribution rule on the job posting template. |
|
Time Sheet Type |
Text |
16 |
No |
Valid values are:
-
Standard (or Hourly)
-
Time-In/Time-Out
-
No Time Sheets
|
This flag indicates how time and expenses should be recorded for workers. |
|
Enable CATS Time Sheet |
Text |
3 |
Conditional |
Valid values are:
|
Indicates if CATS time sheets are used.
Applicable only for Time sheet type ‘Standard’ / ‘Hourly’.
Company configuration ‘Rate schedule’ must be enabled.
If locked on Job Posting Template, entry is ignored. |
|
Time Sheet Frequency |
Text |
16 |
Yes, for Adds only |
Valid values are:
-
Weekly
-
Biweekly or Bi-Weekly
-
Semimonthly
-
Monthly
-
8 Day Time Sheet
|
Indicates how often time sheets are generated.
Allowed values for time sheet frequency depends on the company configuration and locked value if any. |
|
Start Day of Week |
Text |
9 |
No |
Valid values are:
-
Sunday
-
Monday
-
Tuesday
-
Wednesday
-
Thursday
-
Friday
-
Saturday
|
Start day of the time sheet if Time Sheet Frequency is Biweekly, Bi-Weekly, or Monthly.
These can be entered if the Start Day value is not locked. |
|
Adjustment Group |
Text |
100 |
Conditional |
Valid SAP Fieldglass Adjustment Group Code
or
Blank |
Sets an adjustment group for a job posting.
If job posting template flag Creator can change adjustment group = Yes, changes can be made to the adjustment group via this upload.
Company configuration Adjustment groups must be enabled. |
|
When Job Posting is distributed to Suppliers, use Rate values from |
Text |
100 |
Conditional |
Valid values are:
|
Identifies the rate value when job postings are distributed to suppliers.
Company configuration Rates 2.0 must be enabled.
In order to choose anything but Supplier Distribution Lookups, the user must have these Job Posting permissions:
Financial
View Rates During Creation
AND
Job Posting Template must have enabled 'Creator can edit Rate values on Job Posting' in order for the 'Job Posting' value to be accepted.
If this field is left blank and if Contingent Type is not locked, this field defaults to:
-
Supplier Distribution Lookups when 'On Job Posting, calculate Estimated Spend using' configuration is set to 'Estimated Spend values from lookups'.
-
Rates Lookup when 'On Job Posting, calculate Estimated Spend using' configuration is NOT set to 'Estimated Spend values from lookups'.
If Contingent Type has locked the field, it sets to the selection from the Contingent Type.
Job Posting is a valid entry when the Job Posting Template has enabled 'Creator can edit Rate values on Job Posting'. |
|
Refresh rate components from lookup |
Text |
100 |
No |
If left blank, the value from the Contingent Type is picked. |
Company configuration Enable Rates 2.0 must be enabled in order to view/use this.
You must have the following Job Posting permissions:
-
Financial: View Rates During Creation
-
When Job Posting is distributed to Suppliers, use Rate values from is set to Job Posting
|
|
Rate Schedule Code |
Text |
100 |
Conditional |
Valid Rate Schedule Code |
Sets the rate schedule on the job posting.
Company configuration 'Rate schedule' must be enabled and 'Can Change Rate' rule is enabled on the job posting. |
|
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.
If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have visibility access to the Legal Entity Code. If the entered Legal Entity code is not associated with either the creator or the owner, the system displays an error message.
If the legal entity entered in the Legal Entity field is not associated to the job posting template, the system displays an error message. |
|
Default Shift Schedule |
Text |
100 |
Conditional |
Valid SAP Fieldglass Shift Codes |
Indicates default shift schedule. Company configuration Enable Shift Manager must be enabled. |
|
Disallow Approval of Time Sheet/Expense Sheet/Invoice when Job Posting Estimated Spend is exceeded |
Text |
3 |
Conditional |
Valid values are:
|
This field indicates whether the approval of time sheet, expense sheets, and invoices are disallowed when the job posting estimated spend is exceeded when Shift Manager is enabled.
The value in this column is ignored and defaults to what is on the template if the field was locked during creation on the job posting template ID.
Company configuration Enable Shift Manager must be enabled. |
|
Is this a Rebillable Resource? |
Text |
3 |
No |
Valid values are:
|
Allows job posting to be flagged to enable the rebillable resource. |
|
Rebillable Margin |
Decimal |
|
Conditional |
Example:
|
This field reflects the numerical value of the re-billable markup percentage.
All values entered are in percentage. For example, 1.25% should be entered as 1.25, not .0125.
If the field Is this a Rebillable Resource? is Yes, the percent value is accepted. |
|
Project code |
Text |
100 |
No |
Valid project code created in SAP Fieldglass that is active. |
Project code associated to the job posting. Used to set the currency conversion factor on the job posting while creating a job posting from a project. |
|
Comparator Rate |
Decimal |
|
Conditional |
Example:
|
Comparator rate indicates what a permanent worker's equivalent rate would be. All values are in percentage. For example, 1.25% should be entered as 1.25, not .0125.
Company configuration 'Germany Rate Automation' must be enabled. The Collective Bargaining Agreement (CBA) rate change flag must also be enabled on the business unit of the job posting.
If company configuration 'Rates 2.0' is enabled, this field is ignored. |
|
Parity Management Type |
Text |
100 |
Dependent on site configuration. |
Valid Parity Management Type |
United Kingdom (UK) pay parity type.
If parent and all children configurations are enabled, the Parity Management Type is taken from user selection.
If parent and only one child configuration is enabled, the child configuration value defaults as Job Posting Parity Management Type.
Company configuration Manage Pay Parity must be enabled. This is the only configuration necessary for the parent company. For a child company, configurations Manage Parity via Automated Milestones and Manage Parity via Automated Status Change can be enabled.
If company configuration Rates 2.0 is enabled, this field is ignored. |
|
Allow Suppliers and Workers to Edit CATS Time Information? |
Text |
3 |
Conditional |
Valid values are:
|
Indicates if suppliers or workers can edit other workers' CATS time sheet information.
The time sheet must be in draft or rejected status to be edited.
Job Posting Template rule 'Enable SAP CATS Time Sheet' must = Yes. If rule locked on Job Posting Template, this field can not be changed.
If this field is blank or missing, the default value is No. |
|
[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. |
|
[Min] Rate Category/ Rate UOM |
Decimal |
|
No |
Example:
[Min] OT/Hr
11.25 |
Minimum requested rate for the job posting.
If the rate is a factor, enter the factor in this field. (For example, if 1.25%, then enter 1.25.). This is not applicable for Rates 2.0.
If the rate is a calculated rate, enter the word Calculated.
If field left blank, rate is taken from job posting template.
If company configuration Rates 2.0 is enabled, the system runs the rate lookups then the system validates the entry in the upload against the default value to determine whether the entered value is acceptable. If the entered value does not pass validations, the system creates an error. Also see Assumption section for additional Rates 2.0 information. |
|
[Max] Rate Category/ Rate UOM |
Decimal |
|
No |
Example:
[Max] OT/Hr
15.25 |
Maximum requested rate for the Job Posting.
If the rate is a factor, enter the factor in this field. (For example, if 1.25%, enter 1.25.)
If the rate is a calculated rate, enter the word Calculated.
If this field left blank, rate is taken from job posting template.
If company configuration Rates 2.0 is enabled, the system runs the rate lookups then the system validates the entry in the upload against the default value to determine whether the entered value is acceptable. If the entered value does not pass validations, the system creates an error. Also see Assumption section for additional Rates 2.0 information. |
|
[RC] Rate Category/UOM |
Text |
100 |
No |
Valid SAP Fieldglass Rate Code
Example:
[RC] ST/Hr
B1 |
To change a rate code or to add a new rate, this header must be manually added.
If a new rate code is provided for an existing rate category and UOM combination, then the existing rate code is replaced with this new value. |
|
[Committed Spend Flag] RateCategory/UOM |
Text |
3 |
No |
Valid values are:
|
Sets ‘Use in committed spend calculation’ flag value on the newly added rates or can be used to change the value on rates carried from the job template.
If company configuration Rates 2.0 is enabled, the system ignores this field if the rate that it applies to is a Calculated Rate with Calculation Type = Rate Rule, and the rate is not flagged to be included in spend. |
|
[min] [pr] Rate Category/Interval |
Decimal |
|
No |
Example:
|
Time Sheet Allotment Min Pay Rate.
If company configuration Rates 2.0 is enabled, this field is ignored. |
|
[max] [pr] Rate Category/Interval |
Decimal |
|
No |
Example:
|
Time Sheet Allotment Max Pay Rate.
If company configuration Rates 2.0 is enabled, this field is ignored. |
|
[min] [br] Rate Category/Interval |
Decimal |
|
No |
Example:
|
Time Sheet Allotment Min Bill Rate.
If company configuration Rates 2.0 is enabled, this field is ignored. |
|
[max] [br] Rate Category/Interval |
Decimal |
|
No |
Example:
|
Time Sheet Allotment Max Bill Rate.
If company configuration Rates 2.0 is enabled, this field is ignored. |
|
[drc] Rate Category/ Rate UOM |
Decimal |
|
No |
Example:
[drc] OT2/Hr
Weekend_factor |
Removes an existing rate code on the job posting. |
|
[factor] Rate Category/ Rate UOM |
Decimal |
|
Conditional |
Example:
[factor] OT/HR
1.125 |
Rate factor. Minimum Value = 0.001, Maximum Value = 1000.
Company configuration Rates 2.0 must be enabled.
If the rate does not use a factor, the system ignores any value you enter in this column for that row. If the rate uses a factor and you customize the column with a specific rate category or rate unit of measure, make sure the column name matches a valid factor-based calculated rate on the job posting template. If the column name does not match a valid rate or is not valid for the rate code you are adding, the system displays an error. |