Skip to Content
author's profile photo Former Member
Former Member

ECC6 EHP4 SPS7 - CTSOBJLISTV could not be activated

While implementing ECC6 EHP4/NW701 Support Package Stack 7 we are getting the following error on Support Package SAPKNA7016

View CTSOBJLISTV could not be activated

(E- Table contains more than 3 long string fields )

Table CTSOBJLIST was activated (error in the dependencies)

Table CTSOBJLISTT was activated (error in the dependencies)

Table SI_RQ_CONTENT was activated (error in the dependencies)

Table CTS_FILEOBJECT was activated with warnings

(W- Field name FILE is reserved (Do not use structure as include in DB table) )

We have made no changes to this object.

The Support package note (822379) indicates SAPKB70108 shouild be incluided in the que along with SAPKB70105 - SAPKB70107 but SAPKB70108 is not available at service marketplace.

Has anyone seen and overcome this problem?

Thanks in advance.

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 16, 2010 at 06:09 PM

    Additional Information:

    We activated ctsobjlist table and tried to activate the view ctsobjlistv which would not activate due to 4 long string fields.

    We deleted the fourth string field called "additional info" and were able to activate the view with a warning.

    SPAM was able to continue.

    Question: What is the recomended way of handling this type of problem?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Since I was in a sandbox we were able to do something that is really not recommended. We deleted one of the Long String fields getting us down to the limit of three.

      I have since applied the note to increase the number of long string fields allowed across my landscape and do not expect to see this problem when we go to DEV.

      I was very disappointed that this was not referenced in the Support Package note we try to review before applying support package stacks.

  • author's profile photo Former Member
    Former Member
    Posted on Sep 18, 2010 at 03:44 PM

    We ran into the same issue our Development System. We fixed it using note 1354957.

    For some reason we did not get this same error in our Sandbox system.

    Note 1354957 has correction 1243983 which explains the fix for report RADTBCHK.

    We exported report RADTBCHK from our Sandbox and imported into Development and we were able to continue.

    Another option would be to apply the fix in correction 1243983 manually in report RADTBCHK.

    Hope this helps....

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 12, 2010 at 01:54 PM

    Hello!

    I'm importing SPS 7 in NW 7.0 with EhP1 (it was in SPS 3)

    I get the same error: CTSOBJLISTV could not be activated

    I read note "1354957 - Tables with more than 3 long string fields" and the support package SAPKB70105 that have this correction is in the queue but is next to the PI_BASIS SP 4 that have this error.

    Now, how can I solve this issue?

    Best regards,

    Filipe

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 02, 2011 at 09:19 PM

    I did get the same error when applying SP stack 8 to CRM and it failed on DDIC Activation. I applied your solution by implementing the note changes manually (Note 1354957). The problem was solved and the SP import continued normally. Thanks a lot.

    Muriel

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Apr 21, 2011 at 07:43 AM

    Today I ran onto the same activation error for view CTSOBJLISTV with an SP for SAP_BS_FND. I am applying CRM 7.0 EHP1 SPS 3 to SPS 8. Implementation of SAPNote 1354957 solved the activation error and the queue runs again (import proper).

    Thanks,

    Rob.

    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.