Service Directory > v31.2 > Payroll > Assign_Costing_Allocation
 

Operation: Assign_Costing_Allocation

This service operation will submit requests to replace, add, update or delete costing allocations (distributions) for worker/position/earning and position restrictions criteria. This service does not manage strictly earning-level costing overrides.


@ - A parameter name with this symbol denotes an XML attribute within the document instead of an XML element.


Contents

 

Web Service

 

Request

 

Response

 

Element(s)

 

Request Element: Assign_Costing_Allocation_Request

Specifies the options for the business process, as well as the data for the Costing Allocation
 
Parameter name Type/Value Cardinality Description Validations
@version string [0..1] Web Service version  
Business_Process_Parameters  Business_Process_Parameters  [0..1]  Container for the processing options for a business process. If no options are submitted (or the options are submitted as 'false') then the business process is simply initiated as if it where submitted on-line with approvals, reviews, notifications and to-do's in place. If the Initiator is an Integration System User, any validations you configured on the Initiation step are ignored.   
Costing_Allocation_Data  Costing_Allocation_Data  [1..1]  Specifies what the allocation will be applied to 
Validation Description
Either a Worker or a Position Restriction is required.  Either a Worker or a Position Restriction is required. 
You cannot initiate a Costing Allocation assignment for this Worker, Position Restrictions, Position or Earning criteria because there is a pending assignment that conflicts with this one. Please complete or close any pending assignment event before initiating this action.  You cannot initiate a Costing Allocation assignment for this Worker, Position Restrictions, Position or Earning criteria because there is a pending assignment that conflicts with this one. Please complete or close any pending assignment event before initiating this action. 
Position and Earning costing references are only applicable when the primary costing target is a Worker - this request specifies a Position Restrictions as the primary costing target.  Position and Earning costing references are only applicable when the primary costing target is a Worker - this request specifies a Position Restrictions as the primary costing target. 
Cannot Assign Costing Allocation to a Contingent Worker  Cannot Assign Costing Allocation to a Contingent Worker 
Position Reference is required when Position Required for Costing Allocations is set to True at tenant setup and a Worker level costing allocation is being submitted.  Position Reference is required when Position Required for Costing Allocations is set to True at tenant setup and a Worker level costing allocation is being submitted. 
No worktag dimensions have been enabled for costing allocation; please use the Maintain Worktag Usage task to configure.  No worktag dimensions have been enabled for costing allocation; please use the Maintain Worktag Usage task to configure. 
 
top
 

Response Element: Assign_Costing_Allocation_Response

Contains the Event and Costing data that was created by this request
 
Parameter name Type/Value Cardinality Description Validations
@version string [0..1] Web Service version  
Assign_Costing_Allocation_Event_Reference  Unique_IdentifierObject  [0..1]  The Assign Costing Allocation Event that was created from the web service request.   
Worker_Reference  WorkerObject  [0..1]  Contains reference to the worker, which can then be used to Get Worker Costing Allocations.   
Position_Restriction_Reference  Position_RestrictionsObject  [0..1]  Contains reference to the Position Restrictions, which can then be used to Get Worker Costing Allocations.   
top
 

Business_Process_Parameters

part of: Assign_Costing_Allocation_Request
Container for the processing options for a business process. If no options are submitted (or the options are submitted as 'false') then the business process is simply initiated as if it where submitted on-line with approvals, reviews, notifications and to-do's in place. If the Initiator is an Integration System User, any validations you configured on the Initiation step are ignored.
 
Parameter name Type/Value Cardinality Description Validations
Auto_Complete  boolean  [0..1]  When set to "true" or "1", the business process is automatically processed. This means that all approvals will be automatically approved in the system, all reviews and to-do's will be automatically by-passed, and all notifications will be automatically suppressed.   
Run_Now  boolean  [0..1]  Indicates the transaction should process to completion before the response is generated. Note: All < v12 operations will process with Run_Now = True for backwards compatibility but please review this setting in your environment for performance conditions.   
Comment_Data  Business_Process_Comment_Data  [0..1]  Captures a comment for the Business Process.   
Business_Process_Attachment_Data  Business_Process_Attachment_Data  [0..*]  Element for the attachments pertaining to a Event entered through a web service. 
Validation Description
This Business Process Type has been configured to not accept Event Attachments.   
 
top
 

Business_Process_Comment_Data

part of: Business_Process_Parameters
Captures a comment for the Business Process.
 
Parameter name Type/Value Cardinality Description Validations
Comment  string  [0..1]  Free form comment regarding the business process. 
Validation Description
This Business Process has been configured to disable comment. Please remove the comment or change the setting in the Business Process Policy or tenant setup.   
 
Worker_Reference  WorkerObject  [0..1]  Default the Person making the comment to the processing person if not submitted via the web service.   
top
 

WorkerObject

part of: Business_Process_Comment_Data, Costing_Allocation_Data, Assign_Costing_Allocation_Response
 
Parameter name Type/Value Cardinality Description Validations
@Descriptor  string  [1..1]  Display information used to describe an instance of an object. This 'optional' information is for outbound descriptive purposes only and is not processed on inbound Workday Web Services requests.   
ID  WorkerObjectID  [0..*]  Contains a unique identifier for an instance of an object.   
top
 

WorkerObjectID

part of: WorkerObject
Contains a unique identifier for an instance of an object.
 
Parameter name Type/Value Cardinality Description Validations
#text  string       
@type  WID, Contingent_Worker_ID, Employee_ID  [1..1]  The unique identifier type. Each "ID" for an instance of an object contains a type and a value. A single instance of an object can have multiple "ID" but only a single "ID" per "type".   
top
 

Business_Process_Attachment_Data

part of: Business_Process_Parameters
Element for the attachments pertaining to a Event entered through a web service.
 
Parameter name Type/Value Cardinality Description Validations
File_Name  string (255)   [1..1]  Filename for the attachment.   
Event_Attachment_Description  string  [0..1]  Free form text comment about the attachment.   
Event_Attachment_Category_Reference  Event_Attachment_CategoryObject  [0..1]  Category of attachment. 
Validation Description
This Business Process Type has been configured to not accept Attachment Categories.   
 
File  base64Binary  [0..1]  Binary file contents.   
Content_Type  string (80)   [0..1]  Text attribute identifying Content Type of the Attachment.   
top
 

Event_Attachment_CategoryObject

part of: Business_Process_Attachment_Data
 
Parameter name Type/Value Cardinality Description Validations
@Descriptor  string  [1..1]  Display information used to describe an instance of an object. This 'optional' information is for outbound descriptive purposes only and is not processed on inbound Workday Web Services requests.   
ID  Event_Attachment_CategoryObjectID  [0..*]  Contains a unique identifier for an instance of an object.   
top
 

Event_Attachment_CategoryObjectID

part of: Event_Attachment_CategoryObject
Contains a unique identifier for an instance of an object.
 
Parameter name Type/Value Cardinality Description Validations
#text  string       
@type  WID, Document_Category__Workday_Owned__ID, Document_Category_ID  [1..1]  The unique identifier type. Each "ID" for an instance of an object contains a type and a value. A single instance of an object can have multiple "ID" but only a single "ID" per "type".   
top
 

Costing_Allocation_Data

part of: Assign_Costing_Allocation_Request
Specifies what the allocation will be applied to
 
Parameter name Type/Value Cardinality Description Validations
Worker_Reference [Choice]   WorkerObject  [1..1]  The Worker for which the Costing Allocations should be applied.   
Position_Restriction_Reference [Choice]   Position_ElementObject  [1..1]  The Position Restriction for which the Costing Allocations should be applied. Should only be entered if a Worker is not supplied.   
Position_Reference  Position_ElementObject  [0..1]  A Position can be provided if Costing Allocations are desired at a level with Position. 
Validation Description
Position submitted is not filled as of the effective date.  Position submitted is not filled as of the effective date. 
 
Earning_Reference  Earning__All_Object  [0..1]  An Earning can be provided if Costing Allocations are desired at a level with Earning.   
Position_Element_Effective_As-of_Date  date  [0..1]  The 'Effective As-of Date' is used to determine if the submitted Position Restriction or Position is valid: a Position Restriction must be available on the as-of date; a Position must be filled by the Worker on the as-of date. 
Validation Description
This position is not filled by the worker as of the effective date.  This position is not filled by the worker as of the effective date. 
The position restriction submitted is not valid as of the effective date.  The position restriction submitted is not valid as of the effective date. 
 
Replace_Existing_Costing_Allocation_Intervals  boolean  [0..1]  When this indicator is selected, all existing Costing Allocation Intervals for the selected criteria (Worker, Position, Earning) are removed and replaced with the newly submitted Costing Allocation Interval data. This indicator is typically only used during implementation to migrate data to a production tenant.   
Costing_Allocation_Interval_Data  Costing_Allocation_Interval_Data  [0..*]  Specifies an Allocation for a given date range 
Validation Description
Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with another proposed Costing Allocation Interval.  Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with another proposed Costing Allocation Interval. 
Allocation percentage must total 100%.  Allocation percentage must total 100%. 
Update Keys may not be specified when "Replace Existing Costing Allocation Intervals" is enabled - Allocation Intervals can only be added, not updated.  Update Keys may not be specified when "Replace Existing Costing Allocation Intervals" is enabled - Allocation Intervals can only be added, not updated. 
The Costing Allocation Interval Update Keys submitted do not correspond with an existing Costing Override.  The Costing Allocation Interval Update Keys submitted do not correspond with an existing Costing Override. 
The Costing Override ID must be unique within the Workday system - the ID submitted corresponds with an existing Costing Override.  The Costing Override ID must be unique within the Workday system - the ID submitted corresponds with an existing Costing Override. 
The Costing Override ID must be unique within the Workday system - the ID submitted conflicts with another Costing Allocation Interval proposed in this request.   
Start Date is required when adding a new Costing Allocation Interval.  Start Date is required when adding a new Costing Allocation Interval. 
Costing Allocation Details are required when adding a new Costing Allocation Interval.  Costing Allocation Details are required when adding a new Costing Allocation Interval. 
Costing Allocation Interval data may not be submitted when the requested action is Delete.  Costing Allocation Interval data may not be submitted when the requested action is Delete. 
Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with an existing Costing Allocation Interval.  Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with an existing Costing Allocation Interval. 
End Date must be after or on Start Date  End Date must be after or on Start Date 
 
Validation Description
Either a Worker or a Position Restriction is required.  Either a Worker or a Position Restriction is required. 
You cannot initiate a Costing Allocation assignment for this Worker, Position Restrictions, Position or Earning criteria because there is a pending assignment that conflicts with this one. Please complete or close any pending assignment event before initiating this action.  You cannot initiate a Costing Allocation assignment for this Worker, Position Restrictions, Position or Earning criteria because there is a pending assignment that conflicts with this one. Please complete or close any pending assignment event before initiating this action. 
Position and Earning costing references are only applicable when the primary costing target is a Worker - this request specifies a Position Restrictions as the primary costing target.  Position and Earning costing references are only applicable when the primary costing target is a Worker - this request specifies a Position Restrictions as the primary costing target. 
Cannot Assign Costing Allocation to a Contingent Worker  Cannot Assign Costing Allocation to a Contingent Worker 
Position Reference is required when Position Required for Costing Allocations is set to True at tenant setup and a Worker level costing allocation is being submitted.  Position Reference is required when Position Required for Costing Allocations is set to True at tenant setup and a Worker level costing allocation is being submitted. 
No worktag dimensions have been enabled for costing allocation; please use the Maintain Worktag Usage task to configure.  No worktag dimensions have been enabled for costing allocation; please use the Maintain Worktag Usage task to configure. 
top
 

Position_ElementObject

part of: Costing_Allocation_Data, Costing_Allocation_Data
 
Parameter name Type/Value Cardinality Description Validations
@Descriptor  string  [1..1]  Display information used to describe an instance of an object. This 'optional' information is for outbound descriptive purposes only and is not processed on inbound Workday Web Services requests.   
ID  Position_ElementObjectID  [0..*]  Contains a unique identifier for an instance of an object.   
top
 

Position_ElementObjectID

part of: Position_ElementObject
Contains a unique identifier for an instance of an object.
 
Parameter name Type/Value Cardinality Description Validations
#text  string       
@type  WID, Position_ID  [1..1]  The unique identifier type. Each "ID" for an instance of an object contains a type and a value. A single instance of an object can have multiple "ID" but only a single "ID" per "type".   
top
 

Earning__All_Object

part of: Costing_Allocation_Data
 
Parameter name Type/Value Cardinality Description Validations
@Descriptor  string  [1..1]  Display information used to describe an instance of an object. This 'optional' information is for outbound descriptive purposes only and is not processed on inbound Workday Web Services requests.   
ID  Earning__All_ObjectID  [0..*]  Contains a unique identifier for an instance of an object.   
top
 

Earning__All_ObjectID

part of: Earning__All_Object
Contains a unique identifier for an instance of an object.
 
Parameter name Type/Value Cardinality Description Validations
#text  string       
@type  WID, Earning_Code, Workday_Earning_Code  [1..1]  The unique identifier type. Each "ID" for an instance of an object contains a type and a value. A single instance of an object can have multiple "ID" but only a single "ID" per "type".   
top
 

Costing_Allocation_Interval_Data

part of: Costing_Allocation_Data
Specifies an allocation for a given date range
 
Parameter name Type/Value Cardinality Description Validations
Costing_Interval_Update_Key  Costing_Interval_Update_Key  [0..*]  Submit only when updating or deleting an existing Costing Allocation Interval. One key (Costing Override ID or Start Date) is required.   
Costing_Override_ID  string  [0..1]  A unique identifier for the Costing Allocation Interval within Workday. You can optionally submit this for a new instance, but If left blank Workday will automatically generate an appropriate ID.   
Start_Date  date  [0..1]  Start date for the allocation. 
Validation Description
Select a unique Start Date. [SD] is already in use.   
 
End_Date  date  [0..1]  End date for the allocation.   
Costing_Allocation_Detail_Data  Costing_Allocation_Detail_Replacement_Data  [0..*]  Details of the allocation, (e.g., one or many sets of allocation dimensions with a specific distribution percentage). Note that individual allocation details can not be edited because they do not have a discrete key - rather, the entire set of desired allocation details (totaling 100% distribution) must be submitted, which then replaces the existing details. 
Validation Description
Each distribution worktag for an Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Allocation Detail includes a costing dimension more than once.  Each distribution worktag for an Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Allocation Detail includes a costing dimension more than once. 
Each Allocation Detail within a Costing Allocation Interval date range should use a unique combination of distribution worktags - the set of worktags assigned for this Allocation Detail matches that used by another Allocation Detail.   
Each Costing Allocation Detail within a Costing Allocation Interval must have its own unique ordering  Each Costing Allocation Detail within a Costing Allocation Interval must have its own unique ordering 
The override worktags entered do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task.  The override worktags entered do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task. 
Salary Over the Cap sub-allocation percentage must total 100%.  Salary Over the Cap sub-allocation percentage must total 100%. 
Salary Over the Cap Allocation Details may only be entered if Salary Over the Cap is enabled in the Edit Tenant Setup - Payroll and if Grant is a Payroll Costing Allocation worktag.  Salary Over the Cap Allocation Details may only be entered if Salary Over the Cap is enabled in the Edit Tenant Setup - Payroll and if Grant is a Payroll Costing Allocation worktag. 
Salary Over the Cap Allocation data lines should not be loaded unless the original allocation line includes a valid grant of Salary Over the Cap type.  Salary Over the Cap Allocation data lines should not be loaded unless the original allocation line includes a valid grant of Salary Over the Cap type. 
 
Validation Description
Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with another proposed Costing Allocation Interval.  Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with another proposed Costing Allocation Interval. 
Allocation percentage must total 100%.  Allocation percentage must total 100%. 
Update Keys may not be specified when "Replace Existing Costing Allocation Intervals" is enabled - Allocation Intervals can only be added, not updated.  Update Keys may not be specified when "Replace Existing Costing Allocation Intervals" is enabled - Allocation Intervals can only be added, not updated. 
The Costing Allocation Interval Update Keys submitted do not correspond with an existing Costing Override.  The Costing Allocation Interval Update Keys submitted do not correspond with an existing Costing Override. 
The Costing Override ID must be unique within the Workday system - the ID submitted corresponds with an existing Costing Override.  The Costing Override ID must be unique within the Workday system - the ID submitted corresponds with an existing Costing Override. 
The Costing Override ID must be unique within the Workday system - the ID submitted conflicts with another Costing Allocation Interval proposed in this request.   
Start Date is required when adding a new Costing Allocation Interval.  Start Date is required when adding a new Costing Allocation Interval. 
Costing Allocation Details are required when adding a new Costing Allocation Interval.  Costing Allocation Details are required when adding a new Costing Allocation Interval. 
Costing Allocation Interval data may not be submitted when the requested action is Delete.  Costing Allocation Interval data may not be submitted when the requested action is Delete. 
Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with an existing Costing Allocation Interval.  Costing Allocation Interval date ranges must not overlap - the date range submitted conflicts with an existing Costing Allocation Interval. 
End Date must be after or on Start Date  End Date must be after or on Start Date 
top
 

Costing_Interval_Update_Key

part of: Costing_Allocation_Interval_Data
Submit only when updating or deleting an existing Costing Allocation Interval. One key (Costing Override ID or Start Date) is required.
 
Parameter name Type/Value Cardinality Description Validations
@Delete  boolean  [1..1]  Select Yes (Y) to delete the existing Costing Allocation Interval identified by the submitted key value.   
Costing_Override_ID_Update_Key [Choice]   string  [1..1]  The existing Costing Allocation Interval to be updated may be identified using either its Costing Override ID or its Start Date.   
Start_Date_Update_Key [Choice]   date  [1..1]  The existing Costing Allocation Interval to be updated may be identified using either its Costing Override ID or its Start Date.   
top
 

Costing_Allocation_Detail_Replacement_Data

part of: Costing_Allocation_Interval_Data
Details of the allocation, (e.g., a set of allocation dimensions and percentages)
 
Parameter name Type/Value Cardinality Description Validations
Order  string  [1..1]  Orders the allocation detail (e.g., 'a', 'b', 'c', ...). Note that during general ledger costing, any rounding issues resulting from the distributions are reconciled in the last allocation detail.   
Default_from_Organization_Assignment [Choice]   boolean  [1..1]  Select Yes (Y) to indicate that the corresponding percentage should be allocated using the worker's (or position's) default organizational assignments with no overrides. Workday detects if this Request represents a sub-event embedded within a higher-level business process, and if so searches for a possible Assign Organization sub-event which contains proposed assignments. 
Validation Description
You can only assign one default org for each costing override.  You can only assign one default org for each costing override. 
 
Costing_Override_Worktag_Reference [Choice]   Tenanted_Payroll_WorktagObject  [1..*]  The costing dimension value(s) to use for the override (e.g., cost center reference, fund reference, etc.).   
Distribution_Percent  decimal (9, 6) >0   [1..1]  The percentage for the given allocation detail, represented as a decimal value (e.g., .5).   
Salary_Over_the_Cap_Costing_Allocation_Detail_Data  Salary_Over_the_Cap_Costing_Allocation_Detail_Data  [0..*]  Details of the Salary over the Cap allocation, (e.g., a set of allocation dimensions and percentages) 
Validation Description
Each Salary Over the Cap sub-allocation within an Allocation Detail should use a unique combination of distribution worktags - the set of worktags assigned for this Salary Over the Cap sub-allocation matches that used by another Salary Over the Cap sub-allocation.  Each Salary Over the Cap sub-allocation within an Allocation Detail should use a unique combination of distribution worktags - the set of worktags assigned for this Salary Over the Cap sub-allocation matches that used by another Salary Over the Cap sub-allocation. 
A Grant may not exist in the override worktags entered for the Salary Over the Cap sub-allocation.  A Grant may not exist in the override worktags entered for the Salary Over the Cap sub-allocation. 
Each distribution worktag for a Salary Over the Cap Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Salary Over the Cap Allocation Detail includes a costing dimension more than once.  Each distribution worktag for a Salary Over the Cap Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Salary Over the Cap Allocation Detail includes a costing dimension more than once. 
Each Salary Over the Cap Allocation Detail within an Allocation Detail must have its own unique ordering.  Each Salary Over the Cap Allocation Detail within an Allocation Detail must have its own unique ordering. 
The override worktags entered for the Salary Over the Cap sub-allocation do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task.  The override worktags entered for the Salary Over the Cap sub-allocation do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task. 
 
Validation Description
Each distribution worktag for an Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Allocation Detail includes a costing dimension more than once.  Each distribution worktag for an Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Allocation Detail includes a costing dimension more than once. 
Each Allocation Detail within a Costing Allocation Interval date range should use a unique combination of distribution worktags - the set of worktags assigned for this Allocation Detail matches that used by another Allocation Detail.   
Each Costing Allocation Detail within a Costing Allocation Interval must have its own unique ordering  Each Costing Allocation Detail within a Costing Allocation Interval must have its own unique ordering 
The override worktags entered do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task.  The override worktags entered do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task. 
Salary Over the Cap sub-allocation percentage must total 100%.  Salary Over the Cap sub-allocation percentage must total 100%. 
Salary Over the Cap Allocation Details may only be entered if Salary Over the Cap is enabled in the Edit Tenant Setup - Payroll and if Grant is a Payroll Costing Allocation worktag.  Salary Over the Cap Allocation Details may only be entered if Salary Over the Cap is enabled in the Edit Tenant Setup - Payroll and if Grant is a Payroll Costing Allocation worktag. 
Salary Over the Cap Allocation data lines should not be loaded unless the original allocation line includes a valid grant of Salary Over the Cap type.  Salary Over the Cap Allocation data lines should not be loaded unless the original allocation line includes a valid grant of Salary Over the Cap type. 
top
 

Tenanted_Payroll_WorktagObject

part of: Costing_Allocation_Detail_Replacement_Data, Salary_Over_the_Cap_Costing_Allocation_Detail_Data
 
Parameter name Type/Value Cardinality Description Validations
@Descriptor  string  [1..1]  Display information used to describe an instance of an object. This 'optional' information is for outbound descriptive purposes only and is not processed on inbound Workday Web Services requests.   
ID  Tenanted_Payroll_WorktagObjectID  [0..*]  Contains a unique identifier for an instance of an object.   
top
 

Tenanted_Payroll_WorktagObjectID

part of: Tenanted_Payroll_WorktagObject
Contains a unique identifier for an instance of an object.
 
Parameter name Type/Value Cardinality Description Validations
#text  string       
@type  WID, Business_Unit_ID, Company_Reference_ID, Contingent_Worker_ID, Cost_Center_Reference_ID, Custom_Organization_Reference_ID, Custom_Worktag_06_ID, Custom_Worktag_07_ID, Custom_Worktag_08_ID, Custom_Worktag_09_ID, Custom_Worktag_1_ID, Custom_Worktag_10_ID, Custom_Worktag_11_ID, Custom_Worktag_12_ID, Custom_Worktag_13_ID, Custom_Worktag_14_ID, Custom_Worktag_15_ID, Custom_Worktag_2_ID, Custom_Worktag_3_ID, Custom_Worktag_4_ID, Custom_Worktag_5_ID, Employee_ID, FLSA_Workweek_Calendar_Event_ID, Fund_ID, Gift_Reference_ID, Grant_ID, Holiday_Calendar_Event_ID, Job_Profile_ID, Location_ID, Object_Class_ID, Organization_Reference_ID, Payroll_ID, Position_ID, Program_ID, Project_ID, Project_Plan_ID, Region_Reference_ID, Run_Category_ID, Withholding_Order_Case_ID, Workers_Compensation_ID  [1..1]  The unique identifier type. Each "ID" for an instance of an object contains a type and a value. A single instance of an object can have multiple "ID" but only a single "ID" per "type".   
@parent_id  string  [1..1]  Contains a unique identifier for an instance of a parent object   
@parent_type  WID, FLSA_Workweek_Calendar_ID, Holiday_Calendar_ID  [1..1]  The unique identifier type of a parent object   
top
 

Salary_Over_the_Cap_Costing_Allocation_Detail_Data

part of: Costing_Allocation_Detail_Replacement_Data
Details of the Salary over the Cap allocation, (e.g., a set of allocation dimensions and percentages)
 
Parameter name Type/Value Cardinality Description Validations
SOC_Order  string  [1..1]  Orders the allocation detail (e.g., 'a', 'b', 'c', ...). Note that during general ledger costing, any rounding issues resulting from the distributions are reconciled in the last allocation detail.   
SOC_Default_from_Organization_Assignment [Choice]   boolean  [1..1]  Select Yes (Y) to indicate that the corresponding percentage should be allocated using the worker's (or position's) default organizational assignments with no overrides. Workday detects if this Request represents a sub-event embedded within a higher-level business process, and if so searches for a possible Assign Organization sub-event which contains proposed assignments.   
SOC_Override_Worktag_Reference [Choice]   Tenanted_Payroll_WorktagObject  [1..*]  The costing dimension value(s) to use for the override (e.g., cost center reference, fund reference, etc.).   
SOC_Distribution_Percent  decimal (9, 6) >0   [1..1]  The percentage for the given allocation detail, represented as a decimal value (e.g., .5).   
Validation Description
Each Salary Over the Cap sub-allocation within an Allocation Detail should use a unique combination of distribution worktags - the set of worktags assigned for this Salary Over the Cap sub-allocation matches that used by another Salary Over the Cap sub-allocation.  Each Salary Over the Cap sub-allocation within an Allocation Detail should use a unique combination of distribution worktags - the set of worktags assigned for this Salary Over the Cap sub-allocation matches that used by another Salary Over the Cap sub-allocation. 
A Grant may not exist in the override worktags entered for the Salary Over the Cap sub-allocation.  A Grant may not exist in the override worktags entered for the Salary Over the Cap sub-allocation. 
Each distribution worktag for a Salary Over the Cap Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Salary Over the Cap Allocation Detail includes a costing dimension more than once.  Each distribution worktag for a Salary Over the Cap Allocation Detail must belong to a unique costing dimension - the set of worktags assigned for this Salary Over the Cap Allocation Detail includes a costing dimension more than once. 
Each Salary Over the Cap Allocation Detail within an Allocation Detail must have its own unique ordering.  Each Salary Over the Cap Allocation Detail within an Allocation Detail must have its own unique ordering. 
The override worktags entered for the Salary Over the Cap sub-allocation do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task.  The override worktags entered for the Salary Over the Cap sub-allocation do not satisfy the set of required allocation dimensions that have been established in the Maintain Worktag Usage task. 
top
 

Unique_IdentifierObject

part of: Assign_Costing_Allocation_Response
 
Parameter name Type/Value Cardinality Description Validations
@Descriptor  string  [1..1]  Display information used to describe an instance of an object. This 'optional' information is for outbound descriptive purposes only and is not processed on inbound Workday Web Services requests.   
ID  Unique_IdentifierObjectID  [0..*]  Contains a unique identifier for an instance of an object.   
top
 

Unique_IdentifierObjectID

part of: Unique_IdentifierObject
Contains a unique identifier for an instance of an object.
 
Parameter name Type/Value Cardinality Description Validations
#text  string       
@type  IID, WID  [1..1]  The unique identifier type. Each "ID" for an instance of an object contains a type and a value. A single instance of an object can have multiple "ID" but only a single "ID" per "type".   
top
 

Position_RestrictionsObject

part of: Assign_Costing_Allocation_Response
 
Parameter name Type/Value Cardinality Description Validations
@Descriptor  string  [1..1]  Display information used to describe an instance of an object. This 'optional' information is for outbound descriptive purposes only and is not processed on inbound Workday Web Services requests.   
ID  Position_RestrictionsObjectID  [0..*]  Contains a unique identifier for an instance of an object.   
top
 

Position_RestrictionsObjectID

part of: Position_RestrictionsObject
Contains a unique identifier for an instance of an object.
 
Parameter name Type/Value Cardinality Description Validations
#text  string       
@type  WID, Position_ID  [1..1]  The unique identifier type. Each "ID" for an instance of an object contains a type and a value. A single instance of an object can have multiple "ID" but only a single "ID" per "type".   
top
 

WorkerReferenceEnumeration

part of: WorkerObjectID
Base Type
string
top
 

Event_Attachment_CategoryReferenceEnumeration

part of: Event_Attachment_CategoryObjectID
Base Type
string
top
 

Position_ElementReferenceEnumeration

part of: Position_ElementObjectID
Base Type
string
top
 

Earning__All_ReferenceEnumeration

part of: Earning__All_ObjectID
Base Type
string
top
 

Tenanted_Payroll_WorktagReferenceEnumeration

part of: Tenanted_Payroll_WorktagObjectID
Base Type
string
top
 

Base Type
string

top
 

Unique_IdentifierReferenceEnumeration

part of: Unique_IdentifierObjectID
Base Type
string
top
 

Position_RestrictionsReferenceEnumeration

part of: Position_RestrictionsObjectID
Base Type
string
top