Skip to Content

How to avoid “Data Separation” in SMSY on solman SP08


Today i was trying to discover the root cause of a SMSY data migration in step 5.3 of System Preparation of Solman_setup, we start working with our solution manager around 4.0 release or less (i didn’t know solman on that ages), that days my company colleges usually create managed system information manually in smsy, servers, data base host, product systems, etc… Then, when we star on the first setup of Solution Manager VAR scenario we use data providers as SLD, RFC and create the information from that data providers or from SAP marketplace license data.

After that the current situation is a mix of old manually data, old sap marketplace data, and new LMDB data fron SLD data sources in solution manager 7.1 that make us that situation:


Well, after that huge number of errors we have to start with a single system to investigate the cause of the problem, the first system is:

A72AMZ01  – 0020209397 A72 Netweaver 7.2 – No relevant product instance found for product SAP BI ACCELERATOR

>>> You can go Directly to the Trick without reading the initial problem <<<

Lest go to search that system in solution manager, remember that on solution manager 7.1 SMSY is “recommend” to not be used, so we search the system trough “Solution Manager Administrations”, “Solution Manager Configuration” workcenters and LMDB but the system is not missing in each of that option, obviously not in LMDB because the system can be migrated on the before picture.


Well, beside SAP recommendations i try to search for the system in SMSY, but I get a nice surprise because we use “data separation” in solution manager. If you use Data separation you will be asked to select with customer data you are looking for, but as you can see on “migration problems” you don’t know the customer from the affected system, so you can’t find the system in SMSY as not as you select without customer assignment or public.


We have a liter sigh, because we can search the customer name with the installation number from the “smsy migration list”, the installation number is “0020209397”. So with that i try to search the lost system in “Solution Manager Administration” and “Landscape browser” 7.1 work centers without success.


That’s coming really hard to search a first system of a list of more that 300 with migration problems 😕 , so after that situation i decide to try surfing trough debug to find a solution that allow me to see that system on SMSY, and discover the problem:

The Trick to disable “data separation” in SMSY with debuggin

Go to function module “SMSY_SHLP_BP_SPC_FOR_USER” that is used in search help when the system ask you to select one customer, navigate to line 78 and create a breakpoint.


The key is the internal table “shlp-selopt”, after the breakpoint is set, go back to SMSY and trough debug tools change values from that internal table.

When the select customer screen appears you have to input ALL_CUSNRS in entry field. (if you don’t do that, that trick don¡t work)



After to remove the “X” value from the low parameter in the internal table shlp-selopt you will be able to see all systems in SMSY.


Then, after that you can just open product system from the select object option inside SMSY

( You will have to repeat the debug edit any time you move in SMSY)


The customer is: 13416, so, now we can just select that customer on SMSY start and try to discover the problem with the migration of product system that have a “SAP BI ACCELERATOR 7.0” for that system, on the migration log from SMSY we can read something like that: “No relevant product instance found for product SAP BI ACCELERATOR“, so lest go in SMSY in “Product Instance Selection”.

( Yes, you can go to view V_AIINSNRS to discoer the customer number, but if I do that yo will not be able to see that trick working to use SMSY 😉 )


Humm, is that the problem ?

Lest go to try to solve that updating the flag. You are able to update that flag in SMSY without any problem in Solution Manager SP08.


Now lest go to check again the migration tool from solman_setup step 5. After the “Calculate Candidates” i see that it is not enough to select the relevant instance, it is necessary to assign a technical system. So, lets go to fix all errors after technical system assign type ( i get a lot of errors on the mapping of the SMSY technical system, like “Cannot map SMSY system type ‘THIRDPARTY’ to an LMDB system type” ). That part make me come back to SMSY technical system assignment more or less 5 times as i get the correct one.


When you solve all warnings in “SMSY“, then you will be able to see that on “SMSY Migration Tool“.


Final Words and lesson of my own experience to remember on future solman upgrades:

1.- If it’s possible, try to do not upgrade the Solution Manager, a Flesh Installation will make you live easy.

2.- Never create system information manually.

3.- If any customer have wrong information in sap service marketplace, cal your customer to fix that before download it to solution manager.

4.- If you update AISUSER, V_AISAPCUSTNOS and V_AIINSNRS with all your customer information you will fill your Solution Manager of wrong Data.

I listen from some friends that on SP10 it’s not possible to edit anymore system information on SMSY, so i can’t test that in SP10. But, what will hapen when I upgrade my Solution Manager to SP10 ?

Who I can delete all that wrong system data from the solution manager if i can see it ?

Hope that post can be useful to someone with a similar situation.

Best regards,


You must be Logged on to comment or reply to a post.
  • Hello Luis,


    The VAR configuration in Solution Manager is definitely causing some particular  challenges at the time of upgrade.

    If the landscape master data in Solution Manager is wrong, you have to take care about it possibly before upgrading.


    The first step is to "clean" the SAP Marketplace data :

    1. Ensure that all Customer Numbers are properly registered on the SAP Support Portal and if possible managed by one unique CCC Number.
    2. Ensure that the installation numbers and system definition/roles are properly maintained
    3. Clean S-Users (declaration + authorizations) attached to the installations

    This is a time-consuming activity, but it has to be done anyhow.

    Then, the "upgrade" of that master data and the future maintenance effort will be dramatically facilitated. I recommend to leverage those jobs : AI_SC_GET_SAP_CUSTOMER_NUMBERS (customer numbers) ; REFRESH_ADMIN_DATA_FROM_SUPPORT (installation numbers and

    Also make sure the SLD CIM Model and CR Content is up-to-date before synchronizing SLD and LMDB with LANDSCAPE_FETCH.

    Hope this will help.

    Regards, Sebastien

    • Thanks for your Reply Sebastien,

      1. I try to request unique CCC management to SAP but I'm still waiting for an answers, is there any special requirement ? That option with reduce the remote access to each customer information, now we have to do that manually to more than 200 customers.

      About the downloading process from sap marketplace, our problem is the amount of managed systems, and the pass from 701 to 71, we have a lot of systems in SMSY that need to be migrated to 7.1, also we have some customers with systems loaded from a SLD data supplier and other created manually on a old release before 701.

      Only for curiosity, many systems do you manage with a single solution Manager ? your run it with both data suppliers, SLD and SAP marketplace ?

      About the maintenance of data from marketplace it sure that will reduce the effort to the VAR scenario, but it's really hard to get customers information up-todate because they are changing their system infrastructure continuously; i think that a solution for that could be that SAP provide a tool like SLD to update sap marketplace system information from RZ70.

      Thanks for your comments Sebastien,


      • Hello Luis,

        I can imagine that so many customer numbers to manage and data inconsistencies to clean up can become a nightmare.

        In my case, the VAR scenario was used to manage less than 50 customer numbers, and about 3000 S-Users. Installation numbers were downloaded from Marketplace and SID got generated. Choice was made not to update from SLD in the first place (clean-up to be made).

        I agree that using both SLD and SAP Marketplace is tricky. Once the initial registration is made, probably the best is to maintain only SLD, and let SolMan updating Marketplace.



        • I'm agree with you Sebastien, but think about that:

          Initial setup of VAR:  Download Data from Market

          After the initial Setup: Maintain Data from SLD and update from solman to marketplace

          What happen if new names come to be added to Solman ?

          You download it from marketplace ?

          While SLD data supliers are active ?

          Now we use a mix from market and sld, looking the best way to manage that. And survive with duplicated host on SLD, LMDB, SMSY, bla, bla bla...



  • Hi Luis,

    I'm facing a problem in that data separation. I've created a message to SAP and the answer is like below. Do you have any idea for this issue?



    Dear customer,

    I have analyzed your issue.

    Unfortunately this is related to your usage of the

    obsolete 'Customer Key' (KONZS key field) in SMSY.

    This is not supported by SAP!

    This will NOT work in the future with LMDB and other Solution Manager


    For example the logical component Z_KALYON_BPC10

    that you have created, does NOT have the KONZS field filled and is

    therefore not visible with your customer selection 313.

    Is it possible for you to switch off this obsolete and unsupported


    This was developed for internal purposes only and is no longer in use

    for SAP Solution Manager 7.1.

    Sorry for the bad news, but you will have to migrate or update

    the SMSY systems which contain a customer key.

    Best regards,

      • Hi Luis,

        I Can't see the Logical Component that is created in Managed System Configuration (ex: Z_KALYON_BPC10) in SMSY.

        And because of this problem I can't manage EWA conf for this systems.



        • I see Tutku,

          Do that IIke:

          1.- Go to SMSY

          2.- Select your product system

          3.- Select the "Where is used" option to see object references, you will se the logical component.

          4.- click on the logical component and you will be able to edit the logical component

          5.- add the BP of the customer in your logical component and save

          6.- go-to solman_directory and now you will be able to add your logical component on the solution.

          * That's another bug on SMSY<->LMDB use until SMSY disappear.



      • Hi again,

        And I tried to deactivate Data Separation with Tcode SA_CUSTOMER_SEP_ADM but can't because of error "Namespace separation is only relevant if data is separated".

        And I inserted a break point as you wrote above, but in selection list there is no ALL_CUSNRS, so your solution is not fit mine.



        • Try what i answers before, i think that your problem is that: "you can't see your logical component because when you have data separation activated SMSY filter objects with customer's BP"; you can try also selection "without solution assignment" when SMSY promps your for customer, then you can add the correct BP to your solution.

          You can use ALL_CUSNRS beside is not in the selection list.

          Hope that help you,