View and work with candidate details in ERP Semantic Mining

  • Release version: Zurich
  • Updated July 31, 2025
  • 3 minutes to read
  • View and edit candidate details and recommended actions in ERP Semantic Mining. Analyze ERP (Enterprise Resource Planning) system scan results, linked ERP models, usage, and similar candidates.

    Before you begin

    Role required: sn_erp_mining.erp_user

    Important:
    Starting with the Zurich release, ERP Semantic Mining is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

    Procedure

    1. Navigate to All > ERP Foundation > ERP Semantic Mining.
    2. In the side panel, select the candidates icon .
    3. View and edit basic candidate details by selecting the candidate Name in the list.

      Alternatively, you can select a candidate directly on the ERP Semantic Mining home page. For more information, see Browse an overview of candidates in ERP Semantic Mining.

      The Details tab of the candidate is where you can review and update any basic details, as well as work with comments, attachments, and the Activity stream.
      Table 1. Basic candidate details
      Field Description
      Name Record number of the potential candidate, which is automatically generated.
      Status Status of the candidate, either Draft or Potential.

      When you evaluate a draft candidate and decide the candidate is good to replatform, you can change the status from Draft to Potential.

      ERP application Name of the ERP application on the ERP system.
      ERP module Functional business area of the ERP system, such as Sales.
      Short description Brief description of the candidate, what the application does.
      Long text Additional information about the candidate.
    4. Work with the next steps by selecting the Recommendations tab.
    5. View details about tables relevant to the candidate and the ERP system scan details by selecting the ERP scan results tab.
      For a description of the field values, see ERP Semantic Mining candidate scan results field descriptions.
    6. Check and note which ERP models are ERP Semantic Mining identified as being related to the candidate by selecting the Models tab.
      Table 2. Models tab details
      Field Description
      Model type ERP model relevant to the candidate. This model can be a standard ERP model (which you work with in Zero Copy Connector for ERP), a workflow, or a custom business area.
      Relevant for implementation Whether the ERP model is required for replatforming.
      Module ERP business area for the model on the system of record, such as Sales.
      Table names Names of the tables in the ERP model on the ERP system.
      Updated Date and time the list was most recently updated.
      You can note which ERP models to work with in Zero Copy Connector for ERP.
    7. Optional: Check the number of system users that use the candidate application by selecting the Usage tab.
    8. Research candidates related to the current candidate and their tables by selecting the Similar candidates tab.

      Similar candidates are helpful when planning how to best replatform a legacy app. When you replatform a custom app from the system of record, you don't have to replicate the old app exactly. Use the replatforming process to design a better app. For example, an app that addresses the needs of multiple similar candidates in a single, new app built using low-code tools on the ServiceNow AI Platform.

      For a description of the field values, see ERP Semantic Mining similar candidates field descriptions.

    9. Select the Save button and save any changes you made to the candidate details.

    What to do next

    After you work with the candidate details and identify similar candidates, you can:
    Note:

    If you delete a candidate from ERP Semantic Mining, the candidate automatically reappears the next time the ERP system is scanned. Instead of deleting candidates, use the Save as potential candidate feature to organize your candidates.