--- 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 --- # ERP Canvas Use ERP Data action details for flows # ERP Canvas Use ERP Data action details for flows {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of ERP Canvas Use ERP Data action details for flows The Use ERP Data action in Workflow Studio allows ServiceNow customers to test and incorporate ERP (Enterprise Resource Planning) data into the ServiceNow AI Platform. After creating and managing ERP models in ERP Canvas, this action enables reading or updating ERP system data directly within ServiceNow flows, streamlining integration and automation. Show full answer Show less ## Key Features * **Integration with ERP Canvas Models:** Select existing ERP models and their defined read or update operations to perform ERP data interactions. * **Dynamic Inputs:** Provide mandatory and optional fields for the ERP operation using dynamic templates or data pills, ensuring flexibility and precise control over input parameters. * **Connected ERP System Reference:** Specify the name of the connected ERP system to target the appropriate backend environment. * **Action Outputs:** Receive detailed runtime status, error messages, and response data from the ERP system to use in subsequent flow steps, facilitating error handling and data processing. * **Role-Based Access:** Requires appropriate delegated development roles or user role assignments to access and use the action, ensuring secure operation within ServiceNow. ## Key Outcomes * Empowers building ServiceNow flows that seamlessly interact with ERP data, enhancing automation and data consistency across systems. * Enables testing of ERP model inputs and outputs within Workflow Studio before deploying production flows, ensuring accuracy and reliability. * Provides structured error reporting and action status feedback to improve troubleshooting and flow resilience. * Facilitates use of dynamic and configurable parameters aligned with ERP Canvas model definitions, promoting reusability and maintainability. After you're done creating and managing your model in ERP Canvas, go to Workflow Studio and use the Use ERP Data action to test your model's inputs and outputs. You can then build a flow with the action to incorporate ERP (Enterprise Resource Planning) data into the ServiceNow AI Platform. For information on using the Use ERP Data action to retrieve ERP data, see [Building flows to read or update the ERP system](https://servicenow-prod.fluidtopics.net/NdbNUiPnlKTbiurxTBkbMA "After you configure an operation in ERP Canvas, you can build a flow in Workflow Studio to specify details for querying the ERP (Enterprise Resource Planning) system. For example, build a flow that filters by Order ID."). ## Roles and availability {#erp-canvas-flow-reference-2__section-subscription-roles} Available as part of ERP Canvas. Role requirements{#erp-canvas-flow-reference-2__action-fd-roles} : This action requires roles granted by delegated development or assigned to the user. For more information, see [User access to Workflow Studio flows](https://www.servicenow.com/docs/access?context=user-access-flow-designer&version=yokohama&pubname=yokohama-build-workflows&ft:locale=en-US). ## Inputs {#erp-canvas-flow-reference-2__section-inputs} Provide a value for each input that your action needs. To add dynamic values, you can also select data pills using the pill picker.{#erp-canvas-flow-reference-2__inputs-description} ModelName : Data type: Dynamic Choice Name of the ERP model that contains the read or update operation. The model must already be created, and have the read or update operation defined in ERP Canvas. For more information, see [Managing how models read and update the ERP system](https://servicenow-prod.fluidtopics.net/QgXLFIZNnf9wfUZebaVqQQ "After you create an ERP (Enterprise Resource Planning) model in ERP Canvas, you can specify how it reads and updates the ERP system using parameters."). ModelOperation : Data type: Dynamic Choice Whether to Read or Update the ERP system. The read or update entity must already be defined in ERP Canvas. For more information, see [Add a read, update, or create entity to a model in ERP Canvas](https://servicenow-prod.fluidtopics.net/D95uvrIJ22NNM_wEBVYGew "Specify the operation entity, which is the table or BAPI (Business Application Programming Interface) that ERP Canvas uses for read, update, or create operations."). Mandatory Field(s) : Data type: Dynamic Template Fields that are required for the operation. Fields must already be defined as required input parameters when you manage the model in ERP Canvas. For more information, see [Manage input parameters for an ERP Canvas model operation](https://servicenow-prod.fluidtopics.net/8F4AIpMBTqhyaUWPuO8XEA "Specify how fields on the ERP (Enterprise Resource Planning) system map to input parameters and their values to define the inputs for an operation that reads or updates the system of record from ERP Canvas."). Optional Field(s) : Data type: Dynamic Template Fields that are optional for the operation. Fields must already be defined as optional input parameters when you managed the model. For more information, see [Manage input parameters for an ERP Canvas model operation](https://servicenow-prod.fluidtopics.net/8F4AIpMBTqhyaUWPuO8XEA "Specify how fields on the ERP (Enterprise Resource Planning) system map to input parameters and their values to define the inputs for an operation that reads or updates the system of record from ERP Canvas."). System : Data type: Reference Name of the connected ERP system. For more information, see [Working with ERP systems in ERP Canvas](https://servicenow-prod.fluidtopics.net/vSzZr5oM2tSX~5KAaE2a8Q "An ERP (Enterprise Resource Planning) system represents a connection to a section of your ERP system of record. For example, sales orders or vendor invoices."). ## Outputs {#erp-canvas-flow-reference-2__section-outputs} You can use these outputs as inputs for other items.{#erp-canvas-flow-reference-2__outputs-description} Action status : Data type: Object Data pill that contains the current runtime details about the action. The Action Status object consists of a code and a message. Don't Treat As Error : Data type: True/False Option to report the Action Status as an error or a success when returned to a flow. Error Message : Data type: String String data pill containing the error message produced by the action, step, or system operation. Response : Data type: Dynamic Object Requested data that's returned from the ERP system. For more information, see [Choose output parameters for an ERP model](https://servicenow-prod.fluidtopics.net/OX_LJNB6x0Te4D7FgWIe_g "Specify output parameters for an ERP (Enterprise Resource Planning) system read or update operation in ERP Canvas to define how fields and parameters are mapped from the ERP system to the ServiceNow AI Platform. Output parameters also define how returned data is stored on the ServiceNow AI Platform.").