---
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
---
# How ERP Customization Mining determines candidate score and potential
# How ERP Customization Mining determines candidate score and potential {#ariaid-title1}
* Release version: Yokohama
*
* Updated January 30, 2025
*
*  2 minutes to read
Summarize
 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 How ERP Customization Mining determines candidate score and potential
ERP Customization Mining (ERP-CM) evaluates legacy ERP candidates to determine their suitability for replatforming onto the ServiceNow AI Platform.
It generates a candidate potential score that ranks each ERP application based on how well its tables and fields align with ServiceNow's ERP models and data extraction capabilities.
Show full answer Show less
## How Candidate Scores Are Determined
Each candidate is associated with an ERP module that guides the evaluation. ERP-CM analyzes remote tables (populated by scripts from external sources) and extraction tables (large data sets obtained via scheduled queries and transformed for use on the platform) related to this module. Scores reflect the candidate's compatibility with existing ERP models and the amount of customization required to integrate the application.
## Key Metrics Used in Scoring
* **ERP Models:** Counts how many ERP models provide remote or extraction tables used by the candidate.
* **Similar Candidates:** Measures similarity to other candidates using table and model similarity, adjustable via system properties.
* **Supported Table Score:** Ratio of custom application tables supported by any ERP model versus total custom tables (excluding technical and ServiceNow cluster tables).
* **Supported Table Usage:** Proportion of supported tables actually utilized by the custom app.
* **Unsupported Model Penalty:** Penalty for unsupported operations on ERP model tables, scaled between 0 and 1 using a sigmoid function.
* **Unsupported Table Extensions:** Counts custom app tables suggested as extensions to ERP models.
* **Model Inaccuracy:** Counts supported model tables not used by the app, also scaled with a sigmoid function.
## Interpreting Scores and Next Steps
A high candidate potential score indicates strong alignment with existing ERP models, enabling immediate use of remote and extraction tables in replatforming without extensive customization. A low score suggests the application uses few supported tables, implying more effort to adapt the candidate for ServiceNow.
**Important:** Administrators must configure ERP system connections in ERP Canvas before leveraging ERP-CM capabilities.
ERP Customization Mining (ERP-CM) generates a score to rank the potential for replatforming legacy ERP (Enterprise Resource Planning) candidates onto the ServiceNow AI Platform.
Every candidate has an ERP module specified in the candidate details in ERP-CM. The ERP module is used to evaluate the potential score of the candidate for replatforming, as well as the remote tables and extraction tables the model contains.
* Remote tables get their records from running an associated script against an external data source.{#erpcm-potential-and-recommendations__erpc-remote-extraction-difference-ul-remote}
* Extraction tables retrieve large amounts of data using a scheduled query, and use transform tables to process data for use on the ServiceNow AI Platform.{#erpcm-potential-and-recommendations__erpc-remote-extraction-difference-ul-extr}
{#erpcm-potential-and-recommendations__ul_yj4_5fn_xyb}
Note:
Admins must first configure the connection to the ERP system in ERP Canvas. 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.").
## High and low scores for candidate potential {#erpcm-potential-and-recommendations__section_d2s_sss_3yb}
ERP-CM evaluates candidates based on how well their tables and fields are supported by the ServiceNow AI Platform.
* A high potential indicates that ERP-CM can immediately use remote tables and extraction tables that match the ERP model for the application candidate without making additional changes.{#erpcm-potential-and-recommendations__high-score-def}
* A low potential indicates that the application candidate matches few of the remote tables and extraction tables in the ERP models in ERP Canvas.{#erpcm-potential-and-recommendations__low-score-def}
{#erpcm-potential-and-recommendations__ul_l3p_mlk_wyb}
## How scores are calculated {#erpcm-potential-and-recommendations__section_btf_plk_wyb}
The candidate potential score is calculated using the following metrics:
* ERP models: The number of ERP models that the candidate uses remote tables and extraction tables from.
* Similar candidates: The number of candidates with a similarity score above the threshold, which accounts for both table-based similarity and model-based similarity. The threshold can be adjusted in the System Properties
\[sys_properties\] table, and the default OR condition can be changed to AND.
* Supported table score: The ratio of the number of custom app tables that are supported by any ERP model relative to the number of custom app tables.
Note:
Tables from either the Technical or ServiceNow table clusters are ignored from these computations.
* Supported table usage: The ratio of tables supported by the relevant ERP models that are used by the custom app.
* Unsupported model penalty: A penalty for the number of unsupported operations on tables in ERP models. The number of unsupported operations is passed through a sigmoid function, so it ranges from 0.0 and 1.0.
* Unsupported table extensions: The number of custom app tables that are also suggested as model extensions.
* Model inaccuracy: The number of tables supported by relevant ERP models that aren't used by custom apps, and are passed through a sigmoid function.
{#erpcm-potential-and-recommendations__ul_bzs_qlk_wyb}