SLD - Solman wrong assignement in SMSY

[Former Member]

Hello,

we add a new ERP 6.0 (Doublestack) System to SLD, but by starting the job LandscapeFetch the Solution Manager make a wrong assignement in transaktion SMSY.

The new ERP 6.0 System is now below the Netweaver JAVA Components and there is no Abap, but why?

I can´t find a solution, any help ?

thanks

Steven

[stuart_campbell]

Hi

Check the following notes - recommend to have latest LANDSCAPE_FETCH code

SV-SMG-SYS 1361991 2 39 SMSY: Incorrect database host names for Java systems

SV-SMG-SYS 1392489 1 52 SMSY: Übernahme eines Einzelsystems aus dem SLD

SV-SMG-SYS 1360590 3 36 SMSY: systems are created more than once

SV-SMG-SYS 1301106 11 49 SMSY: Enhancements and errors in Enhancement Package 1

SV-SMG-SYS 1319149 2 49 SMSY: Transferring the product information from SLD

SV-SMG-SYS 1376733 2 32 SMSY: Indicator NO_ABAP_INCLUDED cleared

SV-SMG-SYS 1303097 4 51 SMSY: Capitalized instance names from SLD

SV-SMG-SYS 1342337 1 38 Instances remain inactive

SV-SMG-SYS 1370396 1 37 JAVA installation number is not transferred from the SLD

SV-SMG-SYS 1350401 1 37 Incorrect leading product version set (data source SLD)

SV-SMG-SYS 1283307 24 33 SMSY: Product version cannot be determined correctly

SV-SMG-SYS 1335225 5 35 LANDSCAPE FETCH job: Termination with SCDT_LIS_IF 011

SV-SMG-SYS 1296512 4 39 SMSY: Product version transferred from deleted system

As mention before - pre-existing entries in SMSY with different data sources can cause problems - once a data source

has been decided upon creation you need to stick to it - or delete the system a re-create it via a different data source - deletion however can cause loss of existing customizing and inconsistencies if existing customizing has already been set up - changing data source after configuration has taken place is not recommended

Duplicates in SMSY or SLD can also mix import lines and target objects - both should be as consistent as possible before

a landscape fetch from SLD - you may even need to compare SLD with SMSY for any pre-existing entries

Best wishes

Stuart

[Former Member]

Hi,

SLD via Data Supplier.

Data Source SLD

all other System are OK and are in the section ERP Systems

regards

Steven

[Former Member]

Hello,

the Leading Product Version of the new System is Netweaver 7.0 and this is wrong we have a ERP 6.0.

Why does the Solution Manager (SMSY) add a ERP 6.0 System as a Netweaver System ?

regards

Steven

[Former Member]

Hi,

Not sure abt the exact reason, these are the resons i can think of.

1)Someway the data from SLD is not properly reaching the SMSY for the particular system Check the SLD data for the particular SID again.

2) Some duplicate entry with wrong product version, already present in SMSY and has been updated by SLD.

Anyways,you can change the leading product version manually to point to the correct product version.

Your <SID>->Header Data->Installed product versions->Change the Leadign product version->by checking the correct product.

Note:(If your Product is missing->select it from the free selection).

Hope this helps.

Thanks,

Jagan

[Former Member]

Hi,

Please confirm the following:

how did you add the system to SLD, is it through SLD data suppliers?.

Please check the entries of the EP system under technical systems.

Also, check the data source of the system created in SMSY.

Thanks,

Jagan