Manages vendor response data within an event-driven integration process, ensuring seamless updates after third-party payroll processing is completed.

Table Specific Information

Select

The Workday driver requires filtering on Id in order to perform the query.

For example:

SELECT * FROM EventDrivenIntegrationVendorResponse WHERE Id = '12345'

Workday Resource Information

Updates a specific vendor response instance of Event-Driven Integration with the specified data after the third-party payroll system completes processing of the worker changes. The third-party payroll system updates the overall status of the processing and payroll error messages and warnings, if any.

Secured by: Set Up: Payroll Interface (Update Vendor Response for Event-Driven Integration)+TG

Scope: Payroll Interface

Aggregate Fields

The driver represents the following fields as aggregates containing JSON text. Each of them conforms to their respective schema. Fields marked with an asterisk are required and must be included if their parent object is. Fields marked with a hyphen are read-only and must not be included when calling stored procedures or when performing an INSERT or UPDATE.

This information is derived from the Workday REST API specification which does not explicitly list all business rules and validations that apply to each object. More fields may be required than what is listed here.

ErrorMessageSet_Errors_Aggregate

[{
  diagnosis: Text /* An explanation for the root cause of the error. */
  functionalArea: Text /* The functional area that was impacted by the error reported. Examples: Position, Compensation, Personal data. */
  group: [{
      groupData: [{
          name: Text /* The name of the reported field attribute. Examples: Amount, Currency, Status. */
          value: Text /* The value of the reported field attribute. Examples: 2000, USD, Active. */
      }]
      groupName: Text /* The group category holding the data being provided by the third-party payroll system. Examples: Allowance, Address. */
      groupValue: Text /* The specific name of the type of data being provided by the third-party payroll system. Examples: Car Allowance, Home Address. */
  }]
  messageCategory: Text /* The category for where the error occurred. Examples: Worker Data, Organization, Supervisory, Staffing. */
  messageNumber: Text /* An integer number identifying the error reported. */
  procedure: Text /* The steps to fix the error. */
  recordType: Text /* The type of error being recorded. Examples: Data error, Configuration error. */
 *severity: { /* The Workday ID or reference ID of the severity level for the error message. The reference ID uses the referenceIdType=sampleRefId format. Examples: CRITICAL, ERROR, WARNING, INFO. */
     -descriptor: Text /* A description of the instance */
     -href: Text /* A link to the instance */
     *id: Text /* wid / id / reference id */
  }
 *vendorErrorMessage: Text /* Required detailed error message that explains what occurred in the third-party payroll system while processing the worker changes sent through event-driven integration. */
  who: Text /* Lists the names, positions, or roles of the concerned audience for handling the error resolution. */
}]

Columns

Name	Type	ReadOnly	Description
Id [KEY]	String	False	The unique Workday identifier (WID) required for the Event-Driven Integration. Workday provides this identifier to the third-party payroll vendor during the initial file delivery, ensuring accurate tracking and processing of worker data.
ErrorMessageSet_Errors_Aggregate	String	False	A structured dataset that contains detailed payroll messages and exceptions returned by the payroll vendor. These messages relate to worker changes sent via the Event-Driven Integration, allowing users to identify and address specific issues.
OverallStatus_Descriptor	String	False	A human-readable description of the current status of the integration instance, providing context on the state or outcome of the process.
OverallStatus_Href	String	False	A URL link that directs users to the specific integration instance within Workday, enabling quick access for review and troubleshooting.
OverallStatus_Id	String	False	The unique identifier associated with the integration instance, which can be a WID, internal Id, or reference I, used for tracking and referencing within the system.
Relaunchable	Bool	False	Indicates whether users can resend worker changes to the payroll vendor after correcting errors. If true, the 'Resend to Payroll' button is available on the 'Review Event-Driven Integration for Third-Party Payroll' step. If false, resubmitting changes is disabled because errors cannot be resolved by user actions.
SetLsrd	Bool	False	Specifies whether Workday updates the Last Successful Run Date (LSRD) for the worker. If true, only changes made after the Event-Driven Integration are included in the next batch PECI integration. If false, the original data is resent during the next transmission through either the event-driven integration or the Payroll Effective Change Interface integration.
SkipReview	Bool	False	Determines whether the 'Review Event-Driven Integration for Third-Party Payroll' step is displayed on the 'Maintain Local Payroll Data' task. If true, this review step is bypassed, streamlining the process. If false, users must review the integration before proceeding.
SkipReviewReason	String	False	Provides the reason why users should or should not complete the 'Maintain Local Payroll Data' step after the 'Review Event-Driven Integration for Third-Party Payroll' step. This field is applicable when the Hire business process is configured with these steps in sequence, offering guidance for accurate payroll data maintenance.