Troubleshooting: Strategic Sourcing Supplier Connector
Integration Error Messages in Workday
Error Message | Cause | Solution |
|---|---|---|
Validation Error Details: Addresses should be present
Field: /data/attributes/addresses. | You don’t have an address for a supplier in Workday but Strategic Sourcing requires an address for the supplier. |
|
Validation Error: An error was encountered while attempting to copy [Supplier Name] to WSS
500 Internal Server Error. | There are duplicate reference IDs for data on the same supplier. These are commonly duplicate Address reference IDs. |
|
Validation Error: Invalid Number: the number is not recognized. Verify the country phone number. | Phone validations have been configured in your Workday tenant, in the Global tab of your tenant setup. | Ensure no extra spaces and additional characters are in the Phone Number field on the supplier in Strategic Sourcing. |
Validation Error Details: tax_ids should be present
Field: /data/attributes/tax_ids | The Tax ID is configured as required in the Strategic Sourcing Supplier Profile, but the supplier in Workday doesn't have a tax ID. | You can add a tax ID to the supplier in Workday, or:
|
Validation Error: An unexpected error occurred while updating the supplier group configuration in WSS, some configuration may not have been updated. Detail Processing error occurred. The task submitted is not authorized.
Warning: This external value on the To WSS map is an invalid WSS custom field name: Example Web Address. | The To WSS and From WSS values should be mapped to your Strategic Sourcing custom fields. |
|
Validation Error: Default Payment Type Reference is required. | Selection options for the Accepted Payment Types custom field in Strategic Sourcing don't match the selection options for reference IDs that are in Workday. |
|
Validation Error: An unexpected error occurred while updating the address components configuration in Scout, some configuration may not have been updated.
Detail: error from returned HTTP status: 400 {"error": "invalid_grant"} | Values set within the integration attributes for any of these fields are invalid:
| Review and update API tokens if necessary and re-test the integration.
You must have the non-expired flag enabled. |
Detail: error from returned HTTP status: 401 Unauthorized or HTTP status: 403 Forbidden {"message": "forbidden"} | Your credentials have become invalid. This can happen when:
| Create a new personal API token in Strategic Sourcing when you have the Company Admin role. Input the new token information.
Input the token information without the prefixes. Including the prefixes for the WSS API tokens will result in a 401 Unauthorized or 403 Forbidden error. |
Validation Error: Name has already been taken | Strategic Sourcing doesn't allow duplicate supplier names. |
|
Validation Error: Last name must not be empty | In Workday, some supplier contact countries do not require last names, but the Strategic Sourcing Connector requires them. |
|
Validation Error: postal_code Postal code must be 4 digits followed by 2 letters.
Validation Error: postal_code Postal code must be 5 digits | You can receive this error if you have suppliers in Egypt or Costa Rica. | Correct the postal codes of your suppliers. You can also:
|
Validation Error: postal_code must be 3 or 5 digits. | You can receive this error if you have suppliers with addresses in Taiwan. | Correct the postal codes of your suppliers. You can also:
|
Validation Error: Processing error occurred. The task submitted is not authorized.
Http Response Status: 500 | The Supplier Connector security group in Workday doesn't have all of the correct Domain Security Policy permissions. | In Workday:
|
Validation Error: error from returned HTTP status: 403 {"error":"permission denied","code":"S22"}
Http Response Status: 403 | The Supplier Connector security group in Workday doesn't have all of the correct Domain Security Policy permissions. | In Workday:
|
Error from returned HTTP status: 422 {"errors":[{"source":{"pointer":"/data/attributes/deselected_option_ids"},"title":"Validation Error","detail":"deselected_option_ids Option name is selected"}]} - Error occurs when classification are set as inactive | A classification that is present on a supplier is made inactive. | Remove the classification from suppliers in Workday before inactivating the classification. |
Error: HTTP status: 422 {"errors":[{"source":{"pointer":"/data/attributes/base"},"title":"Validation Error","detail":"Cannot delete record because dependent supplier companies exist"}]}error from returned HTTP status: 422 {"errors":[{"source":{"pointer":"/data/attributes/supplier_classification_fields.external_id"},"title":"Validation Error","detail":"supplier_classification_fields.external_id has already been taken"} | You updated reference IDs for in-use supplier classifications in Workday. | Revert the reference IDs to the previous IDs synched to Strategic Sourcing. |
Processing error occurred. Duplicate insert on index: Supplier-External Sourceable ID-External Sourceable ID | You create a new supplier in Strategic Sourcing that already exists as an inactive supplier in Workday and attempt to update the External ID of the new supplier.
You update the External ID of a supplier through the Strategic Sourcing Data Importer. | Suppliers that have an Inactive status in Workday can still be added to Strategic Sourcing events. To enable suppliers with an Inactive status in the integration for Strategic Sourcing users, update Supplier Status on the integration system. See Workday Supplier Status in Strategic Sourcing. |
Error: Postal code must be # of digits.
Error: postal_code is not valid for this region | A postal code is missing or the postal code validations on the Submit Supplier EIB have been turned off. The integration system specifies what format the postal code must be in. These error messages vary by supplier based on the postal code requirement for their region. | Strategic Sourcing validates postal codes. In Workday, turn on postal code validations on the Submit Supplier EIB . |
An error has occurred while processing [Supplier Name]: You must include a supplier contact email, which must be a Work type email | The only email type for a supplier contact is set to Home or the supplier contact doesn't have an email address. |
|
Validation Error Details: bic Bank Identification Code (BIC) incorrectly formatted. Refer to SWIFT guidelines for correct format
Field: /data/attributes/bank_accounts/0/bic | The BIC is in an incorrect format. | Correct the BIC or remove the incorrect code to send the supplier to Strategic Sourcing. If you remove the code, you must temporarily update your settings in Strategic Sourcing:
|
Message Summary: Patching Address Component Rules for Country | Maintain Localization Settings is enabled in Workday for various countries. This is most commonly seen on the City prompt in Workday. | Temporarily disable localization settings and re-run the Supplier Connector. This will allow the supplier to pass into Workday and localization settings can then be re-enabled after the sync. Localization settings is a tenant setting and may affect other areas of Workday. If possible localization settings should stay disabled, so the suppliers can pass from Strategic Sourcing to Workday without issue.
|
Validation error occurred. 1 or more of the addresses you've selected are currently in use on an active supplier remit-to connection. To update or delete an address either remove it from the remit-to connection, or deactivate the remit-to connection. | An address that you are attempting to update or delete in Strategic Sourcing is currently used on a remit-to connection on the supplier. |
|
A supplier classification wasn't transferred.
The classification has fields with duplicate names or matches another classification with the same name for the same country in Workday.
Access the
Maintain Supplier Classifications
task in Workday to review where there may be duplicates in the Classification Name
column.My Workday Supplier Statuses don't populate on Supplier Profiles in Strategic Sourcing.
The External ID fields in Strategic Sourcing are incorrect or not present.
- In Strategic Sourcing, access theSuppliersdataset inReports.
- Confirm theExternal IDfield is populated.
- (Optional) Initiate a full sync of the Supplier Connector populate theExternal IDfield.
My integration system is configured to enable the Supplier Event business process, but suppliers are not passing through the business process once they have synched to Workday.
Supplier Event
business process, but suppliers are not passing through the business process once they have synched to Workday.The
Supplier Event
business process requires information from the supplier that isn't gathered in Strategic Sourcing.Access the
Maintain Custom Validations
task to update validations for your suppliers when sending From Strategic Sourcing.Suppliers are not syncing from Workday Supplier Accounts to Strategic Sourcing.
This error can have multiple causes.
Attempt to identify any issues by viewing multiple items:
- Access the integration system. Select the related action. Select the integration event where the supplier should have attempted to sync and see if there is an error related to that supplier in theOutput FilesandMessagestabs.
- In Workday, access the supplier and view theProcess Historytab.
- In Strategic Sourcing, access of the supplier. View the most recent data in theHistory Log.
If you are unable to sync with the supplier after viewing all items, submit a Product Support Case on Community.