Page tree
Skip to end of metadata
Go to start of metadata

OTHER SOURCES OF INFORMATION: Content Activation Wiki - Content Activation Guide - How to implement SAP Notes for content activation



Universally current. Valid for SAP Solution Manager 7.1 and SAP Solution Manager 7.2 in general.

First Things First: Did you Implement the Relevant SAP Notes?

If you want to perform Content Activation from SAP Solution Manager 7.1 to 7.2 with as little trouble as possible, you must strictly follow the note implementation instructions given in KBA 2599354. There is no cutting corners here. Any issues during note implementation will return to haunt you later in the Content Activation process.


 Universally current. Valid for SAP Solution Manager 7.2 in general.

Problems with Guided Procedure “Solution Documentation Content Activation”? Some general points. 

The remainder of this Wiki presents some 'hot topics' and frequently encountered issues in both the preparatory guided procedure (aka "GP1", mostly run on SAP Solution Manager 7.1 systems) as well as the actual content activation guided procedure (aka "GP2") which needs to be completed in SAP Solution Manager 7.2 before you can start working with the new Solution Manager release.

However, if none of the items listed below work for you - and specifically do not address the problem you are dealing with in the GP2 content activation guided procedure (SAP Solution Manager Configuration, transaction SOLMAN_SETUP > Related Links > Post-upgrade Activities > Solution Documentation Content Activation) - SAP Note 2446977 tells you how to run a few simple checks in your content activation environment, and if this fails to pin down the problem, too, the Note also provides instructions how to get help from SAP by creating an effective incident pre-filled with the kind of information SAP needs to provide you the best possible assistance.


 Current 30 January 2018. Valid for SAP Solution Manager 7.2 SP03-06.

How to Handle Unreasonable Memory Recommendations in Activity "Check Readiness for Activation"

In the all important Content Activation Guide, at the beginning of the first chapter "Process Overview and Technical Preparation" we give some recommendations for system memory settings required for a stable run of the content activation guided procedure ("GP2") on your SAP Solution Manager 7.2 system, incl. parameter abap/heap_area_nondia.

While actually running the GP2 guided procedure an error message may appear in the log of activity "Check Readiness for Activation" which suggests that you increase the value of abap/heap_area_nondia to a level that you feel is unrealistically high.

If this happens, ignore the error message and rather follow the instructions of SAP Note 2500932.


 Current 16 January 2018. Valid for SAP Solution Manager 7.2 SP03-06 - if you use the "history" option.

How to Repair an Incomplete or Faulty "History" of 7.2 Solution Elements

If you are using the "history" option in the SAP Solution Manager 7.2 solution documentation application, you will likely find that after content activation wrong or no history data has been stored for some solution elements.

This is due to a program error in SAP Solution Manager 7.2 SP03-06.

If you discover inconsistencies in the history of your solution elements after performing content activationSAP Note 2589168 gives you instructions on how to fix the problem.

If you have become aware of the risk of inconsistent history data before starting the content activation process - for example, by reading this FAQ item - you have the chance to avoid the problem by implementing the correction instructions of SAP Note 2589168


 Current 01 December 2017. Valid for SAP Solution Manager 7.1 SP05-16 and SAP Solution Manager 7.2 all SPs - if you used projects and solutions in 7.1.

Does my Solution Manager Connect Properly to its Managed Systems?

Faulty RFC connections between your SAP Solution Manager and its managed systems can be annoying because they may cause errors and at the very least slow down content activation, especially if your Solution Manager runs more than a handful of managed systems. SAP is therefore providing you with a report that lets you conveniently check the integrity of RFC connections between the Solution Manager system and its remote systems. This report is called RMIG_GP1_CHECK_RFC. 

To check RFC connections execute report RMIG_GP1_CHECK_RFC using transaction SA38

      • during the course of the preparatory guided procedure ("GP1", transaction PREPARE_ACTIVATION in SAP Solution Manager 7.1) for content activation after completing Step 2 and before commencing Step 3 of that guided procedure
      • before starting to work with the content activation guided procedure "GP2" (transaction SOLMAN_SETUP > Post-Upgrade Activities > Solution Documentation Content Activation) in SAP Solution Manager 7.2.


      • checks whether the RFC connections are functional, and also
      • lists which of your 7.1 projects and solutions use which RFC connections. 

 If you are interested in using report RMIG_GP1_CHECK_RFC, implement SAP Note 2572583 on your SAP Solution Manager 7.1 and 7.2 systems. 


 Current 21 September 2017. Valid for SAP Solution Manager 7.2 all SPs

Handling of "in scope/out of scope" Flag in SOLAR01/SOLAR02 during Content Activation

In the solution documentation transactions SOLAR01 and SOLAR02 of SAP Solution Manager 7.1 you could work with the "scope" flag to set content in scope or out of scope for a specific project.

Please be aware that this flag is not considered by content activation. All elements of a SOLAR project will be activated, regardless of their scope flag setting. If you have used the scoping functionality in SAP Solution Manager 7.1, this means that you will have to either manually clean up elements which have been set "out of scope" in SAP Solution Manager 7.1 as they will be visible in SAP Solution Manager 7.2 after content activation no matter how their scope had been flagged in 7.1, or you use a workaround to save "out of scope" flags in 7.2. 


 Current 20 September 2017. Valid for SAP Solution Manager 7.2 all SPs - if you have used Test Management in 7.1.

How to Recover Remote Test Cases Missing after Content Activation?

During content activation test documents will be created for remote manual test cases. This can only work, if system access to all managed system where those remote test cases reside is available at the time of content activation. If any of those systems cannot be accessed, a warning is written into the log of the consistency check in PREPARE_ACTIVATION, plus an (empty) test document placeholder is created in the new 7.2 solution.

So, if you are confronted with empty test documents in your 7.2 solution after content activation, you need to take measures to fill the empty test documents with the missing remote manual test cases. If you don't do this, you might see exception "No document version exists for the specified context” in the 7.2 Solution Documentation application (transaction /ui2/flp → tile "Solution Documentation") because for the missing remote manual test cases, too, placeholders are used in the new solution (KW documents with test case ID as LOIO).

To recover missing remote test cases to delete all trouble making placeholders (if you decide that you do not need the affected 7.1 remote test cases in 7.2), follow SAP Note 2535824.


 Current 01 September 2017. Valid for SAP Solution Manager 7.2 all SPs - if you have used Change Request Management or IT Service Management in 7.1.

Convert IBase Elements so that ChaRM and ITSM Keep Working Properly in 7.2

Prior to SAP Solution Manager 7.1 SP05 systems were stored as text items in IBase. Starting with SP05, IBase configuration items replaced text elements as the standard container for system information. Conversion of pre-existing text items into new configuration items was also supported since SP05, but one could also choose to keep using both text and configuration items in parallel. 

Because in SAP Solution Manager 7.2 CRM transactions cannot work with text items any longer, you must carry out the transformation from text to configuration elements at the latest during the content activation process. To do so, follow the instructions of knowledge base articles 2012029 and 2010187.


 Current 23 August 2017. Valid for SAP Solution Manager 7.2 all SPs - if you have used Business Process Operations (in particular BP Monitoring and BP Analytics) in 7.1.

Why Can't I Create an Operations Branch for my BPO Objects during Content Activation?

The reality is that the guided procedures which help you to go through content activation simply do not support the creation of the operations branch which is - for example - touted at the end of chapter 2 of the Content Activation Guide as the best practice technique to run BPO in SAP Solution Manager 7.2. 

So as a workaround, assign during content activation your 7.1 solutions containing BPO objects to the production branch and after you are done with content activation, go to the Solution Administration application in 7.2 (transaction /ui2/flp → tile "Solution Administration") and create the operations branch as a child of the production branch. 


 Current 24 May 2017. Valid for SAP Solution Manager 7.1 all SPs - if you have used maintenance projects in 7.1.

How to Handle 7.1 Maintenance Projects Related to 7.1 Solutions during Content Activation?

7.1 Solutions with Active Check-in-Check-out Mechanism Need to be Checked-in before Content Activation

If a maintenance project is assigned to a 7.1 solution and that solution has some of its contents checked-out into the maintenance project, you must check that content back into the solution because otherwise it will be left behind during content activation. It is possible that in the future a preparatory check will be implemented to warn you about solutions in this state, or that the check-in will be automatically carried out, but until this happens you must make sure you do not lose data during content activation by explicitly going through your 7.1 solutions and triggering check-in, if required.

Do not Forget Configuration Structures Indirectly Assigned to 7.1 Solutions

One of the conceptual weaknesses in 7.1 solution documentation was that configuration structures could not be directly assigned to 7.1 solutions. Instead, it was common to employ a workaround by assigning those configuration structures to maintenance projects which in turn were assigned to a solution. However, as maintenance projects are currently not regarded as relevant for content activation in the guided procedure algorithms which support your content activation process, you need to use yet another workaround to bring those configuration structures into 7.2, as follows.
Copy the configuration structures from your auxiliary maintenance projects into other (newly created) projects of other types for which content activation is by default performed, for example, standalone maintenance projects. Make sure that the target 7.2 solution for those projects is the same as for the 7.1 solutions to which the configuration structures actually belong.

How to Activate 'Native' Solution Documentation Contents Residing in 7.1 Maintenance Projects

Above we have discussed how to deal with configuration structures that have been offloaded from a 7.1 solution into a 7.1 maintenance project. But what happens with other, ‘native’ contents possibly present in maintenance projects? Even those contents are currently out-of-scope for content activation into 7.2 as long as a maintenance project is assigned to a 7.1 solution. To get around this, check-in all contents which belong to the 7.1 solution associated with a maintenance project, undock the maintenance project from the 7.1 solution and set the maintenance project in-scope for content activation. Alternatively, you can also copy all native contents from a maintenance project tied in with a 7.1 solution into another, independent project and mark that project as in-scope for content activation.


Current 22 May 2017. Valid for SAP Solution Manager 7.2 all SPs - if you have used Change Request Management (ChaRM) in 7.1.

How to View ChaRM Data Created in SAP Solution Manager 7.1 in SAP Solution Manager 7.2?

ChaRM transactions created in 7.1 are NOT activated for full use in SAP Solution Manager 7.2 either because you have chosen them not to be activated, or because the 7.1 ChaRM transactions were 'inactive' in 7.1 in the first place, for example, because they belonged to closed change cycles.

SAP's Knowledge Base Article 2474918 describes how you can view legacy 7.1 ChaRM transactions in SAP Solution Manager 7.2. Note that the recommendations given there, of course, do NOT apply to 7.1 ChaRM transactions that have been content-activated into 7.2. 7.1 ChaRM transactions that have been subjected to the usual content activation process are transformed into fully viable 7.2 ChaRM transactions.


 Current 11 April 2017. Valid for SAP Solution Manager 7.2 all SPs - if you have used multiple projects in 7.1 solution documentation

What to do about Redundant Document Types in 7.2 Solution Documentation?

Here is how you can consolidate them.

In SAP Solution Manager 7.1 it was not unusual that different people were responsible for different 7.1 projects and that semantically comparable but formally different document types were used in various 7.1 projects.

After content activation, the contents of those 7.1 projects including their document types will nearly always end up with just one 7.2 solution. It is, therefore, possible that in your 7.2 solution redundant document types are present and you would like to resolve those redundancies.

There is no easy mass-fix to the issue of redundant document types because only you, not SAP, can judge which document types in your 7.2 solution are equivalent and can be consolidated into one document type.

The solution is to first remove the redundant document types in 7.2 application Solution Administration (tile "Solution Administration" or transaction SOLADM). After you have done so, the documents stripped of their document type will remain intact but are in display-only mode. Hence, if you are actually working with those documents at a later stage i.e you want to change them, you first need to assign a new, consolidated document type before you can make any changes. This way, over time all relevant documents of old (redundant) type will be changed over to a new document type.

There is no explicit tool to assist you, for example, in communicating within your organization which document types have to be replaced. You need to manage this process yourself.


 Current 31 March 2017. Valid for SAP Solution Manager 7.2 all SPs - if you have used projects in 7.1.

What are the Empty Folders Doing in the Configuration Library after Content Activation?

As part of the content activation process, empty folders are created on scenario level for 7.1 projects so that possible configuration library contents present in sub-structures of those scenarios find a proper place in the 7.2 configuration library.

When no such contents are found, the folders remain empty and you can simply delete them if they disturb you.


 Current 31 March 2017. Valid for SAP Solution Manager 7.2 all SPs.

Can "Solution Transfer" be Used to Bring 7.1 Solutions into 7.2 Outside of Content Activation ...

Why would anyone want to do this in the first place? Possible scenarios include

      • 7.1 solutions have been overlooked and left behind during preparation for content activation (preparatory guided procedure) in the 7.1 system,
      • the 7.1 solution resides in a system which is not subject to upgrade onto 7.2 at all,
      • 7.2 has been newly installed (instead of a 7.1 to 7.2 upgrade) and 7.1 solution documentation content can only to be brought into 7.2 by means of a transport.

Whatever the motivation, the short answer to the headline question is a No. The solution transfer function (transaction SOLUTION_TRANSFER) in SAP Solution Manager 7.1 cannot be used to bring a 7.1 solution into a 7.2 system.

However, you can use the following workaround, with the limitation that business process monitoring/analytics data cannot be transferred in this manner:

      • copy your 7.1 solution into a 7.1 project using "Copy Projects and Solutions" in Related Links of the 7.1 Implementation/Upgrade Work Center (transaction SOLMAN_WORKCENTER),
      • for the newly created 7.1 project use function "Transport Project" in transaction SOLAR_PROJECT_ADMIN to create a transport,
      • improve the data quality of the transport by following the instructions given in SAP Note 2391886,
      • implement the enhanced transport in your SAP Solution Manager 7.2,
      • select the auxiliary 7.1 project carrying the 7.1 solution content as in-scope for content activation in Step 1 of the preparation guided procedure and execute content activation.

... and are there other tools to transfer existing Solution Documentation content from 7.1 into a fresh 7.2 installation?

Theoretically and technically it is possible to use SAP CAL for this purpose, as explained in the SAP Solution Manager Media Center. However, this scenario is currently not fully supported by SAP, has some major limitations and is therefore not recommended.


If you need to preserve your existing 7.1 solution documentation content, the only officially recommended procedure is an upgrade of an existing SAP Solution Manager system.


 Current 30 March 2017. Valid for SAP Solution Manager 7.2 SP03-04 - if you have used Change Request Management in 7.1.

What to do about long running ChaRM Content Activation?

If you have used ChaRM in 7.1 extensively and a lot of ChaRM-related reporting data may have piled up, it is possible that activity “Activate ChaRM Content” in the content activation guided procedure will have an unusually long run time. To estimate the run time, get the row count of table /TMWFLOW/REP71KR (using transaction SE16), divide the number of rows by 15 million and multiply the result with 1 hour. Example: /TMWFLOW/REP71KR contains 90 million rows. Division by 15 million comes to 6, meaning that “Activate ChaRM Content” will run for about 6 hours. If you work on a HANA system, you can halve the estimated run time i.e. in our example the run time would be reduced to 3 hours.

If the estimated run time is too long for you, implement SAP Note 2417302 (if you have not already implicitly done so by applying composite Note 2397667). This Note separates the activation of ChaRM reporting data from the main activation taking place in “Activate ChaRM Content”, thereby dramatically reducing the run time of the activity. This means that you can complete content activation and return to the near-full operational use of ChaRM in 7.2 a lot quicker, but also that you need to wait for a background job called CM_MIGRATE_REPORTING_TABLES to finish to be able to use the reporting features in the Administration Cockpit. Monitor the progress of job CM_MIGRATE_REPORTING_TABLES using transactions SM37 or SLG1 (object =/TMWFLOW/CMSCV, sub object = 72MIGRATION) to find out when ChaRM reporting is back online. Re-start job CM_MIGRATE_REPORTING_TABLES, if it gets stuck for whatever reason.

As of SP05 separating out the potentially long-running activation of ChaRM reporting into an asynchronous background job will be standard procedure. There will be no need to implement an SAP Note.

 Current 28 March 2017. Valid for SAP Solution Manager 7.2 all SPs.

I have activated my solution documentation content - but my 7.2 solution is empty!

In the Solution Documentation application of SAP Solution Manager 7.2, are you looking at the right branch? Usually, your content arrives in the maintenance branch, and if you have accidentally selected to view the production branch, you will not see any content. Either switch to the maintenance branch or release the content from the maintenance branch to make it visible in the production branch.


 Current 14 March 2017. Valid for SAP Solution Manager 7.2 SP03-05 - if the "Readiness Check" (see below) in the content activation guided procedure is very slow.

The "Readiness Check" is taking too much time - how can it be made faster?

In SAP Solution Manager 7.2 SP03 and SP04 Step 2 of the content activation guided procedure contains two activities called "Check Readiness of Production Branches" and "Check Readiness of non-Production Branches". In SP05 these have been combined into one activity called "Check Readiness for Activation".

If any of those activities disturb you because they use up too much time, apply SAP Note 2439747 to improve performance.


 Current 28 February 2017. Valid for SAP Solution Manager 7.2 all SPs - if you used TBOMs (technical bills of material) in 7.1.

How are TBOMs handled during Content Activation?

Case 1: You have used dynamic TBOMs in 7.1

Dynamic TBOMs are taken care of by the content activation process i.e. after completion of content activation they will show up in 7.2. in the expected place and shape. This means you do not have to worry about content activation of dynamic TBOMs. However, do make sure that you have assigned role SAP_SM_BPCA_TBOM_ALL to the user running content activation!

Case 2: You have used semi-dynamic or static TBOMs in 7.1

Semi-dynamic or static TBOMs, whose creation is in contrast to dynamic TBOMs automatic and not manual, are not processed as part of content activation. You have to re-create semi-dynamic and static TBOMs after content activation is finished by calling the Solution Manager launch pad in 7.2: Test Suite > Administration - Change Impact Analysis > TBOM Utilities - Generate TBOMs where you can schedule the creation of semi-dynamic and static TBOMs for branches. Those TBOMs are assigned to executables in the Executable Library of Solution Documentation.

You can find more information regarding TBOMs in the Test Suite Wiki, in the section "Change Impact Analysis with BPCA and SEA".

Current 07 December 2016. Valid for SAP Solution Manager 7.2 all SPs - if you used projects and solutions in 7.1.

Be Careful with Languages when bringing 7.1 Project and Solution Content into 7.2

Case 1: All 7.1 projects and solutions that require content activation use the same master language

Make sure that your 7.2 solution uses the same master language.

Case 2: The 7.1 projects and solutions that require content activation are in more than one language

The master language of your 7.2 solution should be one of the master languages of the old 7.1 solutions and projects. The languages which you have not chosen as the master language of the 7.2 solution must be created as content languages in the 7.2 solution.

If this information reaches you too late, i.e. if your content activation guided procedure can no longer be reset, the languages in 7.2 are mixed up and need to be straightened out, open a ticket at component SV-SMG-IMP-BIM.


 Current 12 December 2016. Valid for SAP Solution Manager 7.2 all SPs - if you used Test Management or Projects/Solutions (with solution documentation) in 7.1.

Cannot Understand what Step 3 in the Preparation Guided Procedure is all about?

You are not alone. It has intuitively not been clear to many users what needs to be done in Step 3 or why it is even required. Therefore we have rewritten chapter 3.3 of the Content Activation Guide. Note that this is only relevant if you used Solution Documentation or Test Management in 7.1.


 Current 08 March 2017. Valid for SAP Solution Manager 7.2 all SPs - if you used Test Management or Projects/Solutions (with solution documentation) in 7.1.

No RFC Connection to a Managed System in Step 3 of the Preparation Guided Procedure

This issue can arise if you have worked with Test Management in 7.1.

When performing the consistency check in Step 3 of the preparatory guided procedure (transaction PREPARE_ACTIVATION), you get an error that, for example, reads like this:

“System not found for SAP_ERP_EP_SER_VPACK_SUCC0001 in PRODUCTION with site GLOBAL and role Quality Assurance System”.

In other words, the error message is of the following format:

“System not found for <Logical Component Group> in <branch> with site <site name, mostly GLOBAL> and role <system role>”.

What this means is that due to the way you have set up Step 1 and 2 of the preparatory guided procedure, access to a system (supposedly) contained in the Logical Component Group (LCG) mentioned in the error message is expected, but the system is not or not properly assigned to the LCG or the RFC connection into the system simply does not exist or does not work.

Why is this important? In Step 3 of the preparatory guided procedure (read chapter 3.3. in the Content Activation Guide) you bring data which is distributed throughout managed systems into your new 7.2 infrastructure or at least you are using that data to properly structure the content of our 7.2 infrastructure. If a managed system has been identified to hold such data, but cannot be reached through an RFC call, data cannot be brought into 7.2. This can result in manual test cases being lost during content activation.

Check for simple things first  Before getting into the rather complex error handling procedure described below, make sure that the error message is not trivially set off by a missing or broken RFC connections into relevant managed systems. An easy way to check the status of managed systems is through the SAP Solution Manager Configuration application (transaction SOLMAN_SETUP).

Step by Step Error Resolution

How to find affected manual tests

The error message mentioned above tells you which

        • project/solution,
        • LCG,
        • branch/site and
        • system role

are involved. With this information in hand, you can try to derive the manual test cases which are affected by your 7.1 project or solution as follows:

Step 1: Determine the 7.1 logical components related to the LCG

In transaction PREPARE_ACTIVATION go to Step 2 and select “LCG Overview”. In the list that comes up, look for the LCG you are interested in. The 7.1 logical components are written next to it.

Step 2: Determine the manual test cases in your 7.1 project or solution

Start transaction SOLAR_EVAL. If you are working with a

7.1 project, open the tree along the path “Project > Configuration > Assignments > Test Cases”

7.1 solution, open the tree along the path "Solution > Assignments > Test Cases”.

When clicking "Test Cases" enter your project or solution in the report selection screen. Then fill field "Source Component" in the report input screen that comes up with the 7.1 logical components from Step 1 and execute the report.

The report produces the list of manual test cases for your project or solution, with a small caveat. For projects, transaction SOLAR_EVAL can only find test cases assigned to structure elements within the business blueprint scope of the selected project, but not in structure elements outside the business blueprint scope. Watch this Wiki for a new auxiliary report that will close this gap.

How to resolve the RFC error messages 

After having identified the relevant 7.1 logical components and their manual test cases, you can now deal with the root causes underlying the error message brought up by the consistency check. You have the following options.

Option 1: You do not really need the 7.1 project/solution containing the problematic manual test cases in 7.2 >> drop the project from activation scope

Going through Steps 1 and 2 (above) you may find that the 7.1 project or solution which contains the manual test cases that have triggered error messages is actually outdated and no longer needed in 7.2. In this case, you can save yourself the trouble of working through the various rescue options for manual test cases below, by removing the project/solution from the content activation scope in Step 1 of transaction PREPARE_ACTIVATION. After you have done that, redo your revised LCG planning in Step 2 of PREPARE_ACTIVATION, before once more proceeding to the "Consistency Check" in Step 3 of PREPARE_ACTIVATION.

Running "Consistency Check" after having scaled down the activation scope should confirm that the initial error message does not reoccur.

Option 2: You have no use for some 7.1 manual test cases in 7.2 >> simply discard them

Content activation is a process that lends itself to housekeeping, also in the area of manual test cases. So once you have established which manual test cases are causing problems in terms of content activation, you should carefully consider, whether those test cases remain relevant in 7.2 or you can delete them. Deletion is obviously a lot less time-consuming than the other error handling options discussed below.

So if you are sure that you can drop some 7.1 manual test cases as they have become obsolete in 7.2, delete them from your project/solution e.g. using transaction SOLAR02/SOLMAN_DIRECTORY, if you are still operating in SAP Solution Manager 7.1. If you have already moved onto SAP Solution Manager 7.2 watch this space for an announcement of an auxiliary deletion report suitable for 7.2.

After you are done with deletions from affected 7.1 projects or solutions, run “Initialize list” in Step 1 of transaction PREPARE_ACTIVATION, and re-enter LCG planning in Step 2.

Then proceed again with Step 3 in transaction PREPARE_ACTIVATION and execute the "Consistency Check". The error messages observed previously should not re-occur.

Option 3: You know the test case (managed) system, it was embedded in 7.1 logical components, but was missing in the LCG >> fix by assigning the test case system to the LCG

If you know the managed system in which your test cases are stored and that system is already part of your 7.1 logical components, you can resolve the situation quite easily within transaction PREPARE_ACTIVATION. The procedure depends on whether the system is already contained in your 7.2 LCGs, or not:

  • If the system is not yet assigned to your logical component groups, go to “LCG Overview” in Step 2 of PREPARE_ACTIVATION and add the system to the LCG mentioned in the error message.
  • If the system is already contained in your logical component groups planning in PREPARE_ACTIVATION, go to Step 3 of PREPARE_ACTIVATION and select a branch and system role consistent with those shown in the error message.

Then return to Step 3 in PREPARE_ACTIVATION and execute the "Consistency Check" again. The error message hopefully does not appear again.

Option 4: You know the test case system, but it was not embedded in 7.1 logical components >> Go back to start

If your test case system had not been part of 7.1 logical components, the procedure in Step 1 and 2 above will not work for you. However, if you know the managed system in which your test cases are stored anyways, and you are still on SAP Solution Manager 7.1 you can address the problem as follows.

First, assign the test case system to a suitable 7.1 logical component so that the preparatory guided procedure has a chance of knowing the system for 7.2 LCG planning. Then execute “Reset” in Step 2 of PREPARE_ACTIVATION and re-enter LCG planning.

Finally go back to step 3 in PREPARE_ACTIVATION and execute the "Consistency Check" again. If you are lucky, the error message will have vanished. Otherwise, it is now more likely to fall into the error category handled through Option 3.


 Current 07 December 2016. Valid for SAP Solution Manager 7.2 all SPs - if you used implementation projects 7.1.

How are Configuration Structures Handled during Content Activation?

If you have used configuration units in 7.1 projects or solutions you can find those after activation into 7.2 in the configuration library underneath the folder node that represents the original 7.1 project or solution.

Case 1: What a 7.1 scenario structure (= scenario + processes + mater data + org units + steps) turns into in 7.2

One configuration unit is created per node. Assignments recorded on the "Configuration" and "Business Functions" tabs in 7.1 appear as assignments in the 7.2 configuration units.

The hierarchical structure that may have existed in 7.1 (scenario > process > steps etc.) is not preserved in 7.2 All configuration units have equal rank.

Case 2: What a 7.1 configuration structure turns into in 7.2

One configuration unit is created per node. Assignments recorded in 7.1 tabs appear as assignments in the 7.2 configuration units.

The hierarchical structure that may have existed in 7.1 is preserved in 7.2.


  Current 07 December 2016. Valid universally.

How do I Select which Projects and Solutions Should be Activated?

An important step at the start of the content activation is the selection of projects and solutions ('scoping') which will be activated. As some important decisions have to be made on which projects to bring into 7.2 and which one to leave behind ... what is the best way to efficiently arrive at these decisions?

A simple selection strategy to analyze all existing projects and solutions (also taking the information from the overview report into account) and to assign each and every one one of them to one of the following three categories:

      • NEEDED: This project or solution will be activated
      • NOT NEEDED: This project or solution will not be activated but will be left behind
      • UNCLEAR: It is unclear whether the project or solution should be in scope for activation

For the first two categories, the procedure is straightforward. All NEEDED projects are to be selected for activation and should be moved to a separate "Activation" branch which should be created as a child branch of the production branch. All projects and solutions which are NOT NEEDED are not to be selected for activation.

For UNCLEAR projects and solutions SAP recommends a selection for activation. During the activation procedure, a separate branch should be created (as a child branch of the "Activation" branch) and all UNCLEAR projects and solutions should be moved into this separate branch. This will keep the content of these projects and solutions available for further use, but at the same time will keep the new solution documentation clean by separating the projects and solutions from the more important content.


 Current 07 December 2016. Valid universally. 

What Happens to KW Documents during Content Activation?

All Knowledge Warehouse documents which are attached to a structure element will be activated, including their version history. Documents NOT attached to a structure element ("orphans") will not be activated and will not be accessible anymore after activation. You can run report SOLMAN_UNUSED_DOCUMENTS to find unassigned KW documents in your 7.1 system.


 Current 07 December 2016. Valid universally.

What Happens to Shortcuts Used in Solution Documentation during Content Activation?

During content activation preparation (transaction PREPARE_ACTIVATION) you can determine how to handle shortcuts. If you decide to resolve external shortcuts, the content which the shortcut points to will be activated, even if the project of that "shortcutted" content is not set in scope for content activation. 
Internal shortcuts (within the same project) will be fully resolved as different occurrences referring to the same original.


 Current 07 December 2016. Valid universally.

What happens to direct document URLs during Content Activation?

URLs pointing to documents remain unchanged during content activation.


 Current 07 December 2016. Valid universally.

What about Authorizations?

We need to distinguish between authorizations for the content activation procedure and authorizations for the new Solution Documentation environment. The authorizations needed for the content activation procedure are described in the Content Activation Guide. The new authorization concept for Solution Documentation in SAP Solution Manager 7.2 is described in the Security Guide.


 Current 07 December 2016. Valid universally.

Which version of ST-PI is Needed for Content Activation?

SAP always recommends having the latest version of ST-PI on your managed systems. For content activation, it is strongly recommended to have at least ST-PI 2008_1_7xx SP12 or ST-PI 740 SP02 installed in your systems.

If lower versions of ST-PI are installed on managed systems, content activation will still function, but the automated generation of the libraries in the new Process Management capability of SAP Solution Manager 7.2 will not work properly.








  • No labels