---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Managing ERP development pipelines in ERP Canvas

# Managing ERP development pipelines in ERP Canvas {#ariaid-title1}

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

Move your ERP (Enterprise Resource Planning) systems, ERP models, tables, operations, and flows from a development instance to a production environment when they're ready.  
Changes that you could promote from a development instance to a production instance include adding:

* Fields to tables
* Tables or BAPIs (Business Application Programming Interface) to ERP models
* Table joins and fields to link tables
* Read and update operations
* Flows built with the Use ERP Data action to query and update the system of record
{#manage-erp-tables-pipelines__ul_iqh_nyr_dyb}  
Note:  
You should do your development on a non-production instance. If you make changes on a production instance, and then promote changes from a non-production instance to the production instance, any changes you previously made on the production instance are overwritten.  
There are several ways to move changes to your production instance on the ServiceNow AI Platform:

1. Use System Update Sets to transfer changes from a development instance to a non-production and then production instance. For more information, see [System update sets](https://servicenow-prod.fluidtopics.net/ZQ_8X~7qlkF6pxE1QX5AvA "An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.").
2. Add the changes to the ServiceNow Store and use the Share with others option to install the updates on the production instance. For more information, see [Publish an application to an Update Set](https://servicenow-prod.fluidtopics.net/zngIeHhDcdvFzySWGB70ew "Publishing an application creates an update set containing the current version of all application configuration records.").

{#manage-erp-tables-pipelines__ol_urm_xvr_dyb}For more information on ways to publish your ERP updates, see [Application sharing](https://servicenow-prod.fluidtopics.net/WVhVgBTo~JwieNDZgRl~lg "Administrators can share applications that are complete and are ready for use on other instances.").