Product system not in LMDB only in SMSY

[hasanajsh]

Hi Solman experts,

I have a question regarding Solman products in LMDB and SMSY.

After updating Solman 7.1 from SP08 to SP10, in Managed Systems Configuration, Assign Product step I get the following errors:

(I am using ABC as SID)

ABC00001~JAVA: part of product system ABC, which is not in LMDB but only in SMSY

ABC~ABAP: part of product system ABC, which is not in LMDB but only in SMSY

In SMSY i see that under ABC there is both ABAP and JAVA whereas under ABC00001 there is only Java (in Products system).

The Diagnosis of Solman for this error is:

Diagnosis

The technical system ABC00001~JAVA is assigned to product system ABC, which was created in transaction SMSY and has not yet been migrated into the Landscape Management Database (LMDB).

The technical system ABC~ABAP is assigned to product system ABC, which was created in transaction SMSY and has not yet been migrated into the Landscape Management Database (LMDB).

System Response

Procedure

If the product system information in transaction SMSY is still required for your system landscape maintenance, migrate it to LMDB. You can do this in the SAP Solution Manager: Configuration work center under System Preparation -> Prepare Landscape Description -> Migrate SMSY Data into LMDB -> Migrate Product Systems. (For more information, refer to the help text in the UI.)

If the product system information in transaction SMSY is no longer required for your system landscape maintenance, delete the product system information in SMSY.

Could anybody who had the same experience share their opinion on this case. This LMDB<>SMSY change is very confusing at this step. Would be more meaningful to execute the optional migrate from SMSY step or delete the product. the second seems a little bit meaningless in this case.

Thanks in advance.

Regards

[Former Member · Accepted solution]

hi,

make sure you completed all the steps in solman_setup -> system preparation and BASIS configuration, before proceed to managed system config

specially on solman_setup -> system prepartion-> 2.4 migrate smsy to lmdb

Thanks

Jansi

[hasanajsh · Accepted solution]

Hi Jansi,

Thanks for your suggestion.

I've completed those parts but skipped the Migrate step. The reason is that, as I said it was a SP08 to SP10 update, and the info in that step says that it necessary for the manually created Products in SMSY in the previous release of Solman.

The strange thing is that I had only the ABC Product before update and after the update the Solman itself made some changes adding this 00000 and adding one product more. If I migrate now, I think I will have 2 Products. ABC and ABC00000.

This whole situation is very confusing in fact. Anyway, I will give a try executing that step. Will let you know about the outcome.

Kind regards

[nthsol · Accepted solution]

Hi Shkëlzen,

we also had the situation that SolMan added some 0 to the SID.

I assumed this was the case because the Product system with that same SID was already existant in LMDB and LMDB needs an unique identifier for the system. So that LMDB does not confuse the systems.

I imagine there are some old System landscapes that have the same SID used several times.

What we did to resolve this:

1. clear both product systems. (delete the assignment between Product and technical system)
2. navigate to the technical system and make sure this is the newest data from SLD.
3. map the technical system once again to the product system.
4. delete the product system that is not used any more.

regards,

Niklas

[hasanajsh · Accepted solution]

Hi Niklas,

Thanks for your answer.

I want to clear something about your solution, regarding 3 and 4.

When you say "map the technical system once again to the product system", which product system do you mean. The ABC which is in SMSY only or the newly created one, with 00000. Actually, the first one would have the same problem, as it is in SMSY only. Basically, I guess you are saying: that system (ABC) should be deleted (step 4), but we need to get read of this assignments to be able too. Is my understanding of your solution right?

Regards

[nthsol · Accepted solution]

Hi,

to be honest I personally would suggest to create a completely new product system (ABC00001) and delete the other to make sure there is only one and to avoid future confusion.

If you don't want to create a new one you would need to delete the products one by one from the assigned technical system

At the end you have a product system that has no assignment to anything. To no Logical Component and to not Technical system.

I would also suggest to delete all erroneous entries that are existent from the old SolMan version (Solman 7.01) coming from SMSY. To avoid any "old" settings that may cause any error

I hope you are not using transaction SMSY but LMDB

(url for LMDB = https://<HOST FQDN>:<HTTP Port>/sap/bc/webdynpro/sap/lmdb_wda_expl_oif?WDCONFIGURATIONID=LMDB_WDA_EXPL_OIF_CFG&sap-language=EN )

Regards,

Niklas

[hasanajsh · Accepted solution]

Hi Niklas,

As I said (and the error indicates too) one of the Product Systems (ABC) is not in the LMDB, but only in SMSY. How can it be edited in LMDB if it is not there?

Regards

[nthsol · Accepted solution]

Hm, that is strange some how.

I am a little confused right now.

You have mentioned that the conversion from SolMan 7.01 (SMSY) to SolMan 7.1 (LMDB) was done before and the system worked good.

Now you have updated from SPS 08 to SPS 10 and this created the new Product system, right?

What is it what you do to check the system ABC and ABC00000 if they are not in LMDB?

Regards,

Niklas

[hasanajsh · Accepted solution]

Hi Niklas,

I guess there is some misunderstanding. There was no conversion from 7.01.

ABC00000 is in LMDB and SMSY whereas ABC is in SMSY only, not in LMDB.

Regards

[nthsol · Accepted solution]

Hi Shkëlzen,

then that could be the reason why you have some system(s) in SMSY and LMDB.

As far as I understood you need to migrate all your Landscape from SMSY to LMDB by using the step "2.4 migrate smsy to lmdb" as mentioned by at http://scn.sap.com/message/15079962#15079962

It might happen that this transformation creates double system entries in LMDB by adding the 0000x to the SID. But this is only an visual "defect".

Once you have done the conversion from SMSY to LMDB you should get this issue resolved.

The conversion report took me more than 48 hours to complete. This is totally normal. You can execute some database statistics updates and/or check/optimize the profile parameters and hope the conversion runs faster.

Hope this helps,

Niklas

[hasanajsh · Accepted solution]

Hi Niklas,

Executing that step immediately imported the system to LMDB and the issue was resolved. (I do now know why it was so faster than your system ).

the confusing part is that the documentation regarding that steps considers older systems and I was very sure it would not be relevant for an SPS8 to 10 update.

Thank you for your inputs.

Best regards