Skip to Content

Error: transaction type SMIN has already been included in the categorization schema - SAP_SOLUTION_MANAGER_TEMPLATE

Hi,

during the setup of the IT Service Management I get the error:

***

Error: transaction type SMIN has already been included in the categorization schema - SAP_SOLUTION_MANAGER_TEMPLATE

***

To solve the problem I followed the Note 1956609 - ITSM 'Activate Categorization Scheme' returns "Error: transaction type SMIN has already been included in the categorization schema - SAP_SOLUTION_MANAGER_TEMPLATE." - Solution Manager 7.10.

But when I got to step 5. I cannot find the transaction types.

  1. Run transaction sm_crm and select role SOLMANPRO if/when prompted
  2. Browse to 'service operation'
  3. Browse to ' categorization schema'
  4. Search and select SAP_SOLUTION_MANAGER_TEMPLATE, click New Version button
  5. Select the transaction types which should be removed for usage and press 'Delete' button.
  6. Save and Change Status from 'Draft' to 'Released'. The new version will be activated according to your defined timestamp

Thanks in advance for any help on this issue,

Beni

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Jul 19, 2016 at 10:38 AM

    Hello Beni,

    There are many reasons why you get such error message.

    Let me explain those scenarios below, so that you can get better idea of how categorization schema work.

    1. My first advice will be, never work with any SAP standard transaction eg: SMIN,SMPR etc.

    The reason is, in future if there is any update from SAP all the standard transaction types gets updated.

    So, try using customized transaction types.

    Similarly, you create a new categorization schema by copying from standard SAP schema.

    Note: Never keep the valid to date of any schema up to the year 2999. It creates error when you want to create a new categorization schema.


    2. In case if you are going to create a new schema, first we need to make the active schema (Schema 1) as inactive. This can be done by the following steps

    (a) Create a new version (Schema 2) of existing schema and delete all the transactions in it. By doing like this, you can avoid an error " Transaction SMIN or ZMIN already exists in some other schema"

    (b) Now, make the version as active by releasing it. This schema will have no transaction types assigned to it.

    (c) Select the versioned schema (Schema 2) and then click new button. This prompts for creation of new schema (Schema 3) from the versioned one.

    (d) For the newly created schema, add all the transaction types, keep the valid to date in near future say for one year and release it.

    So finally the third schema will the current schema...

    Hope these points clarifies you.

    Let me know in case if you need more help.

    Cheers,

    Vignesh

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Beni,

      I don't think running the activity twice is the issue. This error was because the standard template schema was already activated.

      After you removed the SMIN from application area of this template schema, did you try running this step again in SOLMAN_SETUP? Please see if executing it again helps.

      Alternatively, it can also be run via SPRO --> IMG: Solution Manager --> IT Service Management --> Multilevel Categorisation --> Configuration example

      Also, apart from this, what is the error that you face currently when trying to add ZMIN in the application area?

      Regards

      Shubhra

  • Posted on Jul 20, 2016 at 03:45 PM

    Hello Beni,

    Here is my blog which clarifies most of the queries related to Categorization Schema,

    How it works- Categorization Schema...!! Challenges faced when creating new schema from existing schema

    Let me know if you need more help from me...😊

    Cheers,

    Vignesh

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 26, 2016 at 12:39 PM

    Hi,

    the answer from SAP is to ignore the error and to continue the setup.

    Thanks a lot for your help, I learned a lot about the issue.

    Beni

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.