Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2023-06-23
Troubleshooting: Supplier Contracts Strategic Sourcing Integrations

Troubleshooting: Supplier Contracts Strategic Sourcing Integrations

I don’t see anything to select in the Financial Company or Hierarchy field in Workday Strategic Sourcing (WSS).

Only users (including implementers) that have the correct security role assignment are able to view selectable options for these fields.
    Process: Supplier Contract - Create/Edit
     domain.
  1. Ensure that your Single Sign-On (SSO) configuration is complete.
  2. Check that your WSS tenant authenticates using Workday SSO.
  3. Initiate SSO authentication by clicking on the
    Workday Strategic Sourcing
     worklet tile. You can add it as an optional worklet.
  4. Review the security section above to verify role assignments for users in various domains. Your user must have
    View
     privileges.
  5. Access the
    Create Supplier Contract
     task and verify that you can see a set of companies\hierarchies.

My integration skipped some of my WSS contracts.

WSS Contract isn't eligible.
Verify that your credentials used to run the Integration have access to view the contract in WSS. We recommend that you configure your integration to run using administrator credentials.

Integration fails with a processing error occurred. The task submitted isn’t authorized.

The user has incorrect security permissions.
Check that the user running the integration has the right permissions to
Submit Supplier Contract
 and
Submit Supplier Contract Amendment
 web services. Also, check that the user has integration permissions on the
Process: Supplier Contract - View
 domain.

Workday creates multiple amendments for contracts in Workday, even when there are no tangible changes against the WSS contract.

You haven't configured your launch parameters correctly.
  1. On the
    Last Successful Run
     field, select
    Determine Value at Runtime
     as the value type.
  2. Select one of these options as the
    Determine Value at Runtime
     value:
    • As Of Entry Date/Time of Last Completed Integration Event
    • As Of Entry DateTime of Last Completed or Completed with Warnings Integration Event.
  3. On the Current Entry Date/Time field, select
    Determine Value at Runtime
     as the value type.
  4. Select
    Current Moment (Date/Time)
     as the
    Determine Value at Runtime
     value.

I have multiple users access WSS and some are experiencing errors between Workday and WSS.

Cause
Solution
The user can't access WSS using the Workday Strategic Sourcing tile on their dashboard.
Enable the
Workday Strategic Sourcing
 domain and verify that the user belongs to one of the security groups listed in the domain security policy. Then, add the Workday Strategic Sourcing worklet tile to your dashboard.
Your Contracts Integration user doesn't have the right permissions to access supplier contract amendment web services.
Access the related actions menu of the
Supplier Contract Event
, business process and select
Business Process Policy -> Edit
 to review security groups assigned to the
Submit Supplier Contract
 initiating action.
You can also edit the business process policy in the related action menu of the
Supplier Contract Amendment Event
, to review security groups assigned to initiating action Submit Supplier Contract Amendment web service.
Your WSS contract creation user doesn't belong to the appropriate security groups.
Access the
Process Supplier Contract
 domain and into domain security policy to review security group assignments.
Your user doesn't belong to one of the
Self-Service: Account
 domain security groups listed in security policy.
The user must be in 1 of the security groups that have
View
 privileges in the Report/Task Permissions of this domain.
Run the
Test Domain Permissions for User
 task and check if the user belongs to this security domain. If not, configure this domain to include users who need access to SSO.
Does the user running the connector have integration permissions?
Access the
Process: Supplier Contract - View
 domain and verify that the user has
Integration
 permissions. We require this, because the Connector internally uses Get Supplier Contracts web service to determine whether to create (or) update an existing contract.

I'm receiving a Can't retrieve attachments from Workday Strategic Sourcing Contract; Skipping Workday Strategic Sourcing Contract Number error message:

The contract document attempting to sync to Workday likely has a special character in its name.
Check the name of the contract and rename if necessary.

I can't retrieve attachments from a WSS Contract or my deployment is skipping the WSS Contract Number.

The contract you're attempting to sync with Workday likely has a special character in the name.
Rename any contracts that contain special characters.

Is your Scout Supplier Connector Integration syncing inactive and holding suppliers into Strategic Sourcing?

The contract you're attempting to sync with Workday likely has a special character in the name.
You can verify this in the
Integration Attributes
 section of the integration system. You can find additional instructions for how to change the attributes on
Workday Supplier Status in Strategic Sourcing
 in Community. Strategic Sourcing doesn't prevent a user from adding an inactive supplier to a contract. However, contract with an inactive status, it won’t transfer into Workday.