Reference: Contract Header Data Mapping from Contract Lifecycle Management to Workday Procurement
This table shows how fields from supplier contracts created in Contract Lifecycle Management (CLM) will be mapped onto corresponding procurement contracts in Workday.
Other workflow fields in CLM won’t sync to Workday Procurement.
CLM Field | Workday Procurement Field | Location of Field on Workday Contract |
|---|---|---|
Title
| Contract Name
| Contract Information section |
Contract Description
| Contract Overview
| Contract Overview section |
Contract Type
| Contract Type
| Contract Information section |
Company
| Company
| Contract Information section |
Supplier
| Supplier
| Contract Information section |
Start Date
| Start Date
| Terms and Amounts section |
Upcoming Expiration Date
| End Date
| Terms and Amounts section |
Final Spend
| Total Contract Amount
| Terms and Amounts section |
Currency
| Currency
| Terms and Amounts section |
Contract Specialist
| Contract Information section
By default, Workday uses the assignment rules you’ve configured in the Maintain Supplier Contract CLM Assignment Rules task to determine the Contract Specialist field. See Maintain Supplier Contract CLM Assignment Rules.When there are no matching assignment rules, Workday sets the contract submitter from CLM as both the Contract Specialist and Buyer for the contract in Workday. You can update both fields in Workday, but these fields don't appear in CLM. | |
Buyer
| Contract Information section
By default, Workday uses the assignment rules you’ve configured in the Maintain Supplier Contract CLM Assignment Rules task to determine the Buyer . See Maintain Supplier Contract CLM Assignment Rules.When there are no matching assignment rules, Workday sets the contract submitter from CLM as both the Contract Specialist and Buyer for the contract in Workday. You can update both fields in Workday, but these fields don't appear in CLM. | |
Doc ID
| CLM Document ID
| Supplier contract header |