Skip to Content
Author's profile photo Daniel Lippmann

How to configure Solution Manager 7.2 SPS05 for LMDB upload (VAR) (new: updated for SPS06)

In this blog post, I will explain the steps needed for updating system data in Support Portal using the Support Hub user. If you’re managing different customers, additional things have to be configured.

It took a lot of research and debugging… For further details, you can refer to

  1. Create Support Hub S user as described in SOLMAN_SETUP.
  2. Configure Solution Manager:
    1. SOLMAN_SETUP has to be green.
    2. Copy RFC
      1. Select created SAP-SUPPORT_PORTAL RFC:
      2. Check S user (has to be Support Hub user):
      3. Copy RFC, name it SM_SP_<customer_number>_H:

      4. Change S user / password:

        Unlike in the old RFCs, it’s not possible to check the password, the return code is always HTTP 200.
    3. Test upload in LMDB:

      Note: You can ignore HTTP 500 error codes.


  1. If Maintenance Planner can’t open the system, just delete it in SMP and manually update the system from LMDB.
  2. If no other customer numbers are updated, check if the BaDi is active:
  3. Sometimes, the system isn’t uploaded correctly, if this is the case, try to resynchronize it from SLD with report RLMDB_SYNC_TECHNICAL_SYSTEM (check the “Delete before resynchr.” checkbox).
  4. If automatic system update is disabled, add parameter UPLOAD_SYSDATA_GLOBAL_SETTING = X in AGS_WORK_CUSTOM.
  5. When you want to check for upload problems, use SLG1 with AI_LMDB / UPLOAD:
  6. Using report RLMDB_UPLOAD_FEATURE_STATUS, you can check the configuration status:
  7. You should check the joblog of SM:UPLOAD SYSTEM DATA on a regular base, you will find helpful information there why the upload is failing (e. g. manual entered systems or systems without product version aren’t uploaded). A CX_SISE_EXCEPTION can be caused by systems with addon product versions but no main product version.

Please note that you have to implement note 2558077 in SPS06. Furthermore, I advise everyone to have the managed system setup updated. We also had problems with outdated system data – we solved it by resetting RZ70 settings and executing smdsetup:

smdsetup.[sh|bat] managingconf hostname:"sapms://<FQDN>" port:"81<message server J2EE>"

User name and password doesn’t have to be provided as of 7.1 SPS05.

Hint: After upgrading Solution Manager, you should use the same ports for J2EE (except system numbers of course).

If you have problems, feel free to contact me!

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Reza Ejersbo
      Reza Ejersbo

      Hello Daniel,


      Thanks for good Information,

      When I try to Upload to SAP Support Portal

      I get this massages:

      System data is uploaded successfully to SAP Backend. - Display Help

      An exception of type CX_SISE_EXCEPTION has occurred.


      Any Idea why?




      Author's profile photo Michael Spitzer
      Michael Spitzer

      did you manage to solve this ?

      Author's profile photo Jianhua Zhou
      Jianhua Zhou


      Author's profile photo Hafiz Nasir
      Hafiz Nasir

      i am facing this issue can you please help

      Author's profile photo Daniel Lippmann
      Daniel Lippmann
      Blog Post Author

      Have you put AI_SC_GET_NEW_CUSTOMERS to 'X' in DNO_CUST04? And have you tried to add a new entry in AISUSER transaction with username, customer number and S-user without S?

      Also check, it has valuable hints.

      Author's profile photo Hafiz Nasir
      Hafiz Nasir

      yes i add  AI_SC_GET_NEW_CUSTOMERS to 'X' in DNO_CUST04
      also i tried new entry in AISUSER and get this error


      Does Not exsit in AISAPCUSTNOS (check entry)

      Author's profile photo Daniel Lippmann
      Daniel Lippmann
      Blog Post Author

      Can you ignore the message by pressing ENTER? And is AISUSER with customer number?

      Author's profile photo Hafiz Nasir
      Hafiz Nasir

      Data Cannot be save in AISUSER only contact no save no customer Number

      Author's profile photo Daniel Lippmann
      Daniel Lippmann
      Blog Post Author

      I found it in the note: maintain V_AISAPCUSTNOS in SM30 manually with all custnos. When you do so, you can maintain AISUSER by entering custno and S user. Remember to enter S user without S and trailing zeros.

      Then you can continue with the creation of the RFCs as copy of the other RFCs.

      When standard jobs have run, you have a F4 value help for S users.