Skip to Content

#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1

Hi All,

Many questions have created lately on forum Solution Manager surrounding the LMDB, MOPZ, SMSY, Product System and etc on SOLMAN 7.1. Therefore, I took the initiative and decided to write my first blog in my life so far, on how to assign Product System in SOLMAN 7.1 and how LMDB, SLD, SMSY and Landscape Verification work inter-related in SOLMAN7.1, to share with our fellow #sapadmin, as this is the important first step in order to proceed to utilize and operate most of the SOLMAN functionalities such as MOPZ, EWA, Diagnostics Configuration and etc. We can’t proceed further if stuck here. talk about product version and product instance information need to be maintained manually for all technical system running on Netweaver prior to 7.02 but the wiki didn’t provide any guide on how to assigned, get it visible and working.

LMDB technology was brought into SOLMAN 7.1, works inter-related with SMSY, SLD and even Landscape Verification step a leg in, which complicate the effort to maintain your company system landscape.

In our scenario, BJP is our BI-JAVA. We’ve fetched the system information to SLD, and entry appeared in SMSY once SLD has sync it with LMDB ( when periodic job SAP_LMDB_LDB_0000000001 completed, which runs on every 10 minutes)

In SMSY, if your perform a search,  you’ll see BJP appears in Databases and Technical Systems but not Product Systems.

*BJP is used as example here.

Now we need to go assign Product System to BJP. Highlight BJP and right click -> change and below screen will prompt out. Click on “check” button and it’ll bring you to Technical System Editor.

You can change your landscape pattern here – either as HUB or SIDECAR.

As you can see, Product Versions and Product Systems tab is empty.

Next you need to go to Software and assigned Product Instances by clicking the Add button:

Navigate to “Proposals fitting to SCs” tab and add the correct product instance carefully, else it’ll lead to inconsistency and issues in MOPZ and Diagnostics configuration, when you don’t want to spend and waste time troubleshooting later.

Select the correct Product instance and click “Add”:

Next, go to “Proposals fitting to unassigned SCs” to check if there’s any software components, eg: Add-On and etc which doesn’t fit into the Product Instance Selected. Read the “Note” and “What to do” on how to fit those software components in.

What you’ll see when Product Instance is added:

Here, you need to ensure relevant software components has the “Product Assigned”

Save your entry and go back to the main screen, and product Version assigned.

How about “Product System”? We don’t find any feature to add in the product system. And there’s no information on any notes nor guides that talk about this explicitly. As product system is important to MOPZ and Diagnostic Configuration, we can’t proceed further without product system assigned for our Instance.

How about try our luck in Managed System Configuration?

When you click on “Display Product Systems”, it just bring you back to SMSY, and still we can’t find the feature to add “Product System”.

Don’t worry, trick to assign “Product System” is in Landscape Verification Tool. Click on “Goto Landscape Verification Tool” or go to transaction code LVSM. Click “Yes” for data synchronization and wait for it to complete, alternative, you can go to transaction code LVSM_LOAD to check the status.

Next, you need to manually create “Product System” as you won’t find “BJP” here:

Click “Add Product Systems”

*Please pay attention to the Product Selected, otherwise, you’ll have problem generate STACK XML for EHP upgrade and maintenance. Many questions had raised in Solution Manager Forum surrounding this topic.

Always select the base as main product, for example:

For ERP EHP1, 2 or 5, select Product SAP ERP

For NW7 EHP1, or 2, select Product SAP NETWEAVER

For SCM7 EHP1, select Product SAP SCM7 and etc………

Click Next and assign “BJP” as technical system.

Select the relevant Product Instance. Bear in mind that you can only select ONE Product Instance here! Otherwise you’ll hit into error and fails to save.

Next and Finish.

Remember to “SAVE” your configuration. Click the SAVE button.

Click OK

You will see “BJP” now:

Go to SMSY and search for “BJP” and you’ll see Product Version is assigned and you are free to maintain additional Product Versions or Product Instance if relevant.


I hope this blog will help #sapadmin who encounters problem and unclear about SOLMAN7.1 Landscape Management technology. I’ve spent long hour and greased my elbow to get this working just for MOPZ usage for my upgrade. Previously, generate Stack XML in SOLMAN version<7.1 took me few minutes, but not  longer simple in SOLMAN 7.1. To ensure a smooth operation in near future, i strongly advise your SOLMAN7.1 is patched to latest support packages, apply the master note and ensure system preparation, basic configuration are performed and completed successfully. Also, update your SAP CIM and SAP CR contents to latest level available, or at minimum 1.6.16 for CIM before SLD -> LMDB synchorization.

Refer to Note 669669 – Updating the SAP Component Repository in the SLD on how to update.

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

    I love the fact that you stepped up and created a blog around LMDB, SLD, SMSY and Landscape Verification.

    I’m sure this blog will be useful for many.

    You have put a lot of effort into your first blog as well! Keep up the good work and continue to blog and be active on SCN, you won’t regret it.

    SDN reference page: Landscape Management Database (LMDB)

    SDN Wiki pages:

    Kind regards


  • Hello Nicolaus,

    what is the procedure for the registration of SAP EHP4/5 systems (double stack ERP systems)?
    a)     two SMSY-entries (SAP ERP 6.0 and SAP EHP4/5)
    b)      one SMSY-entry (SAP ERP 6.0)
    c)     one SMSY-entry (SAP EHP4/5)

    Via LVSM only SAP ERP 6.0 can be choosed.

    Thank you!

    • Hi Alex,

      perhaps you can be more specific on the question. If i read it correctly, you would like to maintain EHP4/5 system. Therefore, you can do this in SMSY and assign SAP ERP as main product, and include EHP4/5 for SAP ERP subsequently,  mark as active. Also, you can assigned the JAVA instance as extended ID to your Abap stack by checking application server Java Product instance.

      Nicholas Chang

      • Hello Alex

        A) is the closest answer. If you want to be completely correct it should be D) other

        You should have:
        SAP ERP 6.0
        EHP4 for ERP 6.0 / NW 7.01

        As active product version for a Dual Stack (ERP 6.0 EHP4 + Netweaver 7.0 EHP1 AS Java)

        You can see a ERP 6.0 EHP4 config in the Solution Manager landscape setup guide which you find through -> Media Library -> Solution Manager Landscape Setup Guide (last updated 25.08.2011)

        Product version assignment can still be performed in transaction SMSY in Solution Manager 7.1.

        Kind regards


    • Hi Alex,

      perhaps you can be more specific on the question. If i read it correctly, you would like to maintain EHP4/5 system. Therefore, you can do this in SMSY and assign SAP ERP as main product, and include EHP4/5 for SAP ERP subsequently,  mark as active. Also, you can assigned the JAVA instance as extended ID to your Abap stack by checking application server Java Product instance.

      Nicholas Chang

  • Hi Nicholas,

    Excellect blog!
    Quck question.  We just upgraded our production Solman to 7.1 Stack 3.  Before I can do the system preparation or basic configuration wizards I have to provide a detailed workplan with timings and screen shots of how long everything will take.  Until I get approval I can’t do the step to create the LMDB.

    Should SLD still be working?  The SLD server shows started with the expected technical systems, but LVSM_LOAD doesn’t find anything.

    Best regards,

    • Hi Russ,

      Thanks. Your SLD is running but is not configure to communicate with SOLMAN. You will do the linkage in Basic Configuration -> Prepare Landscape. At this point, you’ll tell Solman where’s your SLD.

      Just ensure you update SLD CR and CIM to latest before LMDB sync.

      Hope it helps,

      Nicholas Chang

  • Hi Derek,

    First of all, you need to send your JAVA instance data to SLD (either solman or if you have any Productive SLD) in VA -> SLD data supplier and point it to your SLD.

    Secondly, you need to ensure SLD <-> LMDB sync is completed during solman_setup -> system preparation -> outsides system discovery.

    Ensure the data is fetched and you should able to see it in SOLMAN -> SMSY.


    Nicholas Chang

  • Hello Derek

    The message in your dev_w is not relevant to your AS Java not started issue.

    You should check out the logging that concerns your AS Java startup in the work directory. dev_server0, std_server0.out to check why your AS Java server node has not started up properly.

    Kind regards


  • Nicholas, great writeup.  We’re fighting with exactly the same problems right now – first system upgrades to managed systems since going to SM7.1.  – I think I hit all of your steps on my own yesterday, just not in such a nicely defined sequence.. πŸ™‚    Your absolutely most succinct and accurate statement was in one of your earlier posts – “it’s making my life hell”..

    SAP – this is NOT an improvement.  What used to be accomplished in minutes in SMSY is now an horribly convoluted process frought with pitfalls.  There is nothing in this mess that makes things faster, easier, more accurate.  Add to this now the propensity of the system to create more and more extended sids if the smallest detail doesn’t match existing systems, and this thing turns into a permanent cleanup work cycle.  Not impressed.

    Now to figure out why all of our Java instances stopped sending data to central SLD at the same time while still showing “data sucessfully sent”…  doh!.

    • Hi Jason,

      There’s no LMDB in SOLMAN EHP1. and much simple where you just need to ensure you java SID is in SLD and run the lanscape_fetch in solman abap.


      Nicholas Chang

  • Hi, Nicholas.

    The blog is informative. However, do you have any insight on how to setup a PI domain in the LMDB? I have been struggling with making my PI domains showup in the PI monitoring in the solman 7.1. Unfortunately, I have not found any blog yet on how to setup/troubleshoot a PI domain. The standard SAP doc is dreadful as usual.

    By the way, the PI is running on its own SLD but is already synced into the Solman local SLD. I am just eye balling the entries and the PI domain config between the 2 SLD’s are identical. The LMDB job is already run. Now I don’t know where to begin troubleshooting.



    • Hi Jonathan,

      I haven’t touch on any PI monitoring with SOLMAN 7.1 yet. What exactly is the error when you run PI monitoring setup? Do explain more as some experienced sapadmin might help on this.

  • Hi Chang,

    as well form my side thank you very much for this great Blog!

    It was very helpfully for me but I stuck at step “Don’t worry, trick to assign “Product System” is in Landscape Verification Tool.“.

    At transaction LVSM I have one error “No detected product instances available for technical system DPO”.

    Error Message:

    In this case, it was not possible to determine the possible product instances for technical system DPO. This could have the following causes:

    • The connection to the SAP support system failed. If this is the case, there will be other error messages that you can use to correct the error.
      –> Connection is working fine and no additional error message
    • The SAP support system is not able to assign a product instance to the software component versions. This indicates that the software component versions that are assigned to this technical system in the system landscape of the Solution Manager have errors. Perhaps you entered the relevant software component versions manually. Check the relevant data.
      –> nothing manually added
    • Only one user of the Landscape Verification Tool can query the SAP support system at a time. This error message can therefore also occur if the program is being used by two different users who are simultaneously executing this query. This error is of a temporary nature; in this case, simply repeat the check again later.
      –> only one user

    So, I am not able to go on as documented at your Blog.

    Any idea? Many thanks in advance!



    PS. I absolute agree with you in this point “I’ve spent long hour and greased my elbow to get this working just for MOPZ usage for my upgrade.” under Conclusion.

    I am SAP Consulting for PI and not for Solution Manager and I only need to have update services for PI available to fix all Bugs at DVD download version!

    • Hi Jochen,

      What’s your solman version? Is it 7.1 SP05? For SP05, you first need to assign your product instance in SMSY.

      If you merely want to approve your SPs download but not generate the XML file, you can do as below without using MOPZ.

      Go to SE37 -> /TMWFLOW/MO_UI_BASKET_AUTHORIZ -> Process -> SAP-OSS -> Execute.


      Nicholas Chang

      • Hi Nicholas,

        first of all many thanks for reply!

        In the meantime I was able to fix that issue.

        The problem was mainly related to the lower CR content level at the Solution Manager (version 7.1). After update to the highest available level at local SLD and restart the whole SM System I could add the Product System with the Landscape Verification Tool. Previously I had to wait after Job “SAP_LMDB_LDB_0000000001” was successfully executed, the (full) synchronization between SLD and LMDB.

        Now, the Product System is available in LMDB and I was able to perform the MOPZ successfully.



  • Hello Nicholas

    Really nice work !

    Any hints regarding Business Objects (Monitoring and configuration) and EWA for Business Objects with Solman 7.1?



    • Hi Marian

      You would need to ensure the correct definition of your BOBJ in Solution Manager (LMDB ).

      Once that is in place, you would need to have host agent / diagnostics agent ~ in other words, you need to setup diagnostics for your BOBJ system in order to be able to insert it into Technical Monitoring and in order to generate EWA reports for it.

      Best regards


      • Hi Tom

        The correct definition of the BOBJ in LMDB is exactly the thing that concerns me.

        Because when when performing a check using LVSM, I get some errors and a SAP Note – 1610201 is mentioned.
        Unfortunately when searching the mentioned SAP Note I get the message:
        The requested SAP Note is either in reworking or is released internally only”
        And one question: we have recently upgraded to SPS7 and can’t find the option “Proposals fitting to unassigned SCs” . Is this normal?



        • Hi Marian

          The requested SAP Note is either in reworking or is released internally only

          Two options: wait until SAP has updated the note or create a customer message and state you urgently need the note to be available.

          “And one question: we have recently upgraded to SPS7 and can’t find the option “Proposals fitting to unassigned SCs” . Is this normal?”

          That seems strange as normally SPS7 is mostly about bug fixing. I have to check what version my test Solution Manager is on (might be SPS6 still). My customers are not yet running SPS7 either. Going for the latest version often has risks in regards to undiscovered bugs. I might install the latest SPS on a test system (sandbox) but I won’t patch the productive Solution Manager immediately (only after a good number of central note versions are out).

          Best regards


          PS: You might find my latest blog post an interesting read:


        • Hello,

          I am on SP7 and I think I see the same as you. There is no proposal option for the Product Instances for BOBJ. Moreover, the automatically installed Product Instances are not recognized by “Verification Check” and reports them as errors.

          Seems LMDB needs some bug fixing in next patch πŸ™‚


  • Hi all,

    Nice blog!

    Any idea which field will set the system to ‘production’ in transaction SMSY?

    I have noticed in your screen shots above, that this is not set either, and we cannot see any corresponding field in LMDB.

    Any suggestions?


  • Hi Nicholas,

    Need your little feedback regarding the LMDB-SLD-SMSY in Solman 7.1

    I have to configure EWA in SM71, for that I have to first perform “Managed Systems Configuaration”. I was doing that manually i.e. “Create System in Managed System Config” but I realized that’s not the correct way and I started digging around

    To my realization read one of your comments on some other post and came to this blog post. Well, now I have pushed the system information of Satellite System (AS-ABAP) to Solman SLD via RZ70 and system got added to SLD.

    Next I waited for the *LMDB* job to complete and sync the SLD to LMDB and there after the system appeared in SMSY & LMDB with all the required information.

    That was cool!

    But, as per your post above, in SMSY the system appeared in Databases|Product Systems but not in Technical Systems.

    I am confused now!

    Rather it should be appearing in TS but not in PS, so that later on TS can be assigned to PS.

    Also, if I see in the “Managed Systems Configuration” there the technical system has been defined in its entirety with all the information like Product Version, Product Instance, Software Components etc.

    But in SMSY system is not appearing in Technical Systems!

    Can you please let me know, if this is Ok?



    • Hi Chang,

      Excellent blog !!! i appreciate your effect for putting and sharing with us your experience .we are currently on Solman 7.0 EHP1 just have downloaded the installation media.

      i was looking for configuration steps for LMDB-SLD for sure your blog gona help me in that.


    • Hi Akshay,

      FYI, the blog was written 1-2 years ago with solman 7.1 earlier release. I believe the bug fixes had included in the later and newest SPS.

      Yes, the SID should appear in product system and you are fine to proceed.


      Nicholas Chang

      • Hi Nicholas,

        Yep totally agree with that.

        Yesterday I struggled hard to get that in place and it went all Green with some hustling.

        Now the satellite system is added in Managed systems configuration with all columns with green LED.

        Just a germ of curiosity left, which is that in SMSY in the system doesn’t appears in Technical System, it appears only in Product Systems.

        I guess with the evolution of LMDB/SLD fetching that’s not required as everything has been defined perfectly in Managed Systems Configuration.

        Right now speeding up RTCCTOOL checks. Looks like I am closing in πŸ˜†

        Solution Manager ain’t a regular ride πŸ˜›

        However appreciate your meticulous blog.



        • Hi all,

          I have the same problem than Lisa Deady, do you know how to declare a system in production like in SMSY, in the LMDB ? in your second screenshot, there is the checkbox for this in SMSY.



  • Synchronization from SLD to LMDB is working fine, but data is not written to Software ==> Product Instance section tab. What could be the problem ? Normally it should gather automatically but pushed me to select manually lots of component ???

    • Kemal – usually Product tab is not populated by LMDB.  You need to create a Product System, then assign a technical system to it (both java and abap if it’s dual stack).  If all goes well you can use the Select by Proposal in the Assign Product Instance tab to allow the system to give you the right product pieces.  As of SP10 it’s actually been working relatively well, with only systems that weren’t defined correctly in the first place causing us any grief.

      • We are getting below error, while doing the upgrade.. but in solman properly set everything and system have components. still stack file is not generating properly. anyone guide me..

        Validation of deployment queue completed with error: The stack does not match the system. Probably the system was changed after the stack was generated. Synchronize the system with SAP Solution Manager and then generate a new stack. Software feature SAP NETWEAVER 7.3: Mobile with ID 0120031469090000254034 is found on the system but not in the list of expected system software features in the stack. Software feature SAP NETWEAVER 7.3: Advanced Adapter Engine Extnd with ID 0120031469090000254075 is found on the system but not in the list of expected system software features in the stack.