---
sourceDocument: Yokohama Finance and Supply Chain
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/source-to-pay-operations

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Finance and Supply Chain

ft:clusterId :

    - stpop

bundleId :

    - stpop

workflow :

    - Employee


---

# Restructured Supplier Task table

# Restructured Supplier Task table {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The Supplier Task table architecture has been restructured in the Washington DC and Yokohama releases.

In releases before the Washington DC release, the Supplier Task \[sn_slm_task\] table extended the Task \[task\] table.

Starting with the Washington DC release, the Supplier Task \[sn_slm_task\] table extends the Service Task \[sn_spend_sdc_service_task\] table.
Figure 1. Supplier Task table structure  
After you upgrade to the Washington DC release, the fix script `glidefix_script_reparent_sn_slm_task.xml` runs to reparent the Supplier Task table on instances with huge count of records (in millions). Therefore, it's advisable to run the upgrade during a period of low interaction.  
Note:  
This is a mandatory one-time fix script run on instances upgrading directly to Washington DC from Vancouver or older versions.