LMDB to SMSY Synchronization ???

Hi ,
We are in SM 7.1 SP 03. I have attached a new remote SLD (SL1) to LMDB and performed full sync. After the sync SL1 data is showing correctly in LMDB.However this data is not being populated in SMSY ! I was hoping after 5 mins. LMDB data will be
synchronized automatically to SMSY. This is not happening. I ran the report AI_LMDBS_DISPLAY_SYNC_LOGS and no sync logs are present.That suggests LMDB > SMSY sync never happened. Am I missing something?
Also tried SMSY_SETUP and ran the LANDSCAPE FETCH job manually but no luck so far
How to sync LMDB with SMSY ?
Your help is much appreciated.
Regards
VIvek
P.S: Already referred https://websmp110.sap-ag.de/~sapidb/011000358700000146522011E.

Hello,
First you state you are on SP03, so you should not be using the Guide for SP01
https://websmp101.sap-ag.de/~sapidb/011000358700001228392011E/Setup_Guide_LMDB_SP2_3.pdf
If you refer to page 14, you can see that SMSY is now going to be automatically updated from the LMDB.
Manual changes should not be made in SMSY, execpt to product system and logical component
The idea is that the datasupplier will feed the data pulled from the system itself to the SLD and the SLD will update LMDB, and LMDB will maintain SMSY.
The habit of making changes in SMSY needs to be broken in 7.1
I am not sure what all you might have done up to this point, but you may want to consider removing the systems that are not updating from LMDB and SMSY, then resync from SLD using report RLMDB_SYNC_TECHNICAL_SYSTEM, see page 22 of same guide above.
Also consider:
If multiple SLDs are connected to LMDB, one technical system must be registered on only one SLD, otherwise inconsistencies may arise in LMDB.
Hope this information helps
Paul

Similar Messages

Synchronization error between LMDB and SMSY

Hello Experts
I have a sync error between LMDB and SMSY entries. I want your help to make this synchronization to Solution Manager 7.1 SP07.
Thank you very much for your help
Juan Carlos Salazar R

Solman Setup - Configuration Lost
To try to solve the synchronization error
I have been running a Report for get some information and as a consequence all the information into the solman configuration was lost. I mean everything, all the clock (the date of modification) are in zero, and all the status are grey.
Someone know How to bring this information back; without performing a backup or to perform a setup again.
The report is the RLMDB_SYNC_TECHNICAL_SYSTEM

LMDB to SMSY sync disabled.

Hi Guys,
We are getting an warning message in LMDB Administration
" NT 601 Consumer Synchronization from LMDB to SMSY ( Cl_LMDBS_Notification) is disabled"
I have checked the job SAP_LMDB_NOTIFY_LDB* there also i find the same message.
I have ran the smsy_setup transaction as well but no luck,
I ran the report Al_LMDB_DISPLAY_SYNC_LOGS but i can not find any logs there as well.
I have checked the note 1670464 but there is no information related to this error message.
Please advice how to proceed.
Regards
Abhishek

Hi,
Found solution in report RLMDB_TRIGGER_DOWNSTREAM_SYNC.
Regards
Abhishek

SLD is not sync to LMDB nor SMSY

Hi All,
we are running on SOLMAN 7.1 SP03 and CIM & CR Content are upgraded to latest version. Full sync completed sucessfully and incremental sync as well. However, why certain entries (JAVA) in SLD is not sync to LMDB and SMSY? I've deleted it from SLD and trigger from source system but to no avail.
Btw, may i know is LANDSCAPE_FETCH still useful in SOLMAN7.1 or it has been replaced by LMBD_##0001 job?
Your kind advise is very much appreciated,
Thanks,
Nicholas Chang

Hi All,
i would like to thanks for helping. At last i manage to solve part of the problem.
I just dislike LMDB which is really complicate our life.
I can see my java portal, SID EPP in SMSY assigned under technical system -> Java. after full sync from SLD to LMDB.
Therefore, i've to assign EPP to product system -> SAP NW7, but i can't do it in SMSY and need to do it in LMDB and Landscape verification tool, and i can only assign exactly one Product Instance for it, unlike in SMSY, we can select others product instance as relevant.
In order to assign extra product instance, we need to go to Managed System Configuration and click on Edit Technical System Software and add it in section "Maintain Assigned Software".
We need to go numerous places merely to assign one Product System. Perhaps this is the new thing we need to adapt and master it.
At the moment, i still having problem to assign enable XSS software components to my portal where i get an error when try to add it using LMDB -> under software component version. Fyi, i've added ERP Portal content as one of the product instance.
Also, i notice Landscape verification tools is not sync with the changes i make in LMDB, any ideas beside running lvsm_load job?
Thanks all for the help.
Cheers,
Thanks,
Nicholas Chang.

SLD to SMSY synchronization - Which product version do we have to choose ?

Hello,
We do have a CPP system running on SAP ECC 6.0 version.
1. In SLD, we do have the list of all "Software Components" used in CDP.
We do not have the "PRODUCT VERSION" of the managed system.
2. With job SAP_SLD_DATA_COLLECT (RZ70), all data are sent from CDP (managed system) to SLD.
3. With LANDSCAPE FETCH job, all data are synchronized between SLD and SMSY.
Now, how can we choose the right "PRODUCT VERSION" to set in SMSY ?
As far as there is not "PRODUCT VERSION" defined in SLD, do we have to set manually a PRODUCT in SMSY ?
Is there any guide or OSS Notes which describe, step by step, the full workflow process synchronization
from (1) Managed System to (2) SLD to (3) SMSY ?
Thanks
Best regards
PC

Hi,
As I have observed, when the data sync happens between SLD and SM system, the product versions are also assigned.
Sometimes, the product assigned through SLD sync may not be correct or may be irrelevant to your scenario,
In that case, you should always manually edit and assign the correct product version in SMSY, to avoid any conflicts arising in further setup of EWA, SMD setup etc.
For ECC 6.0, you can goto SMSY>systems>search for SAP ECC-->your system CPP/CDP should already be present under SAP ECC through SLD landscape fetch job.
Select that system, and in the header data tab u can see the Installed product versions.
There you can always change the relevant products for your systems.
Hope this helps.

Product system not in LMDB only in SMSY

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

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 Jansi Rani Murugesan 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

SMSY - How to maintain "System Name"

Hi experts,
in transaction SMSY, if you go to a Product System, in register "System Data in SAP Support Portal" there is a field "System Name".
And as far as I know, this is the field, which is displayed in SMP after synchronize right?
But where can I maintain this field?
I didn't find this in LMDB.
Kind regards

Hi Christian,
See this link is usefully
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and
Landscape Verification work in SOLMAN7…
Regards,
Deva

LMDB Configurations on Solman 7.1

Dear Experts
I wanted to no how to do verfication of lmdb in solution manager 7.1 sp plzz help me in this if any one have a steps or screenshot so send me
Kindly guide me on how to do it
Thanks & Regards,
Ishant chaturvedi

Hi Ishant,
Please check:
Landscape Verification
http://scn.sap.com/docs/DOC-8793
Landscape Management Database (LMDB)
http://help.sap.com/saphelp_sm71_sp01/helpdata/en/3a/0f2676ccb4413b9fee695e126cde24/content.htm
How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
http://scn.sap.com/community/it-management/alm/solution-manager/blog/2011/12/17/sapadmin-how-to-assign-product-system-in-solman-71-how-lmdb-sld-smsy-and-landscape-verification-work-in-solman71
Thanks
Vikram

Problem while adding SAP Netweaver 7.3 As Java in Solution Manager 7.1

Hi All,
We are facing strange problem while configuring managed system- SAP Netweaver 7.3 As Java in Solution manager 7.1 SP3. We added this system in SLD of solution manager and synchronized it with LMDB. As a result this As Java system is present under Technical systems in SMSY. Now we are assigning Product system to it with Landscape verification tool. But the problem is when we try to save after assigning Product version as SAP Netweaver and Product as SAP Netweaver 7.3. It always gives below error:
Fatal error trying to update Technical System (UPDATE_TSYSTEMS). Update could not be executed.
Product instance 54 not found
Product instance number error keep on changing depend upon what usage i select like ADS 7.3, Application Server Java 7.3 etc.
Please suggest if someone has faced this issue.
Thanks
Sunny

Hi Sunny,
You can refer to my first blog on this topic:
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
Try to select only one product instance in LMDB and saved. After that, you can add more product instance in SMSY.
Hope it helps.
Cheers,
Nicholas Chang

Best Practice to Export Solman Customer Data to a new one

Hi Solman experts,
We are facing a new project to move a huge Solution Manager VAR Scenario to a new one server, the biggest problems is system landscape from customer data (LMDB) and incident management customer data (ITSM), also mopz, ewa and sap service delivery that has request from customers to SAP and is Stored in solution Manager.
The information that we have to export to a new Solution Manager is:
Customers: +300 aprox.
Systems: +900 aprox.
- Solution Manager Configuration "Managed system Setup" for around +900 productive systems.
- Customer data in LMDB and SMSY ( product systems, tech.systems, logical components, solutions, etc... ).
- VAR Scenario data from: ITSM (with communication with SAP).
- VAR Scenario data from: Mopz, ewa, Sap engagement and service delivery, Solution Documentation.
We decided to do that to user a flesh installation of Solution Manager SP11 with better system resources, better than migrate our existing one.
What do you think that is the best way to migrate customer data from a SAP Solution Manager SP08 to a new server with SAP Solution Manager SP11 ?
Thanks,
Lluis

Hi forum,
Have you check anytime that SAP package ? AGS_SISE_MASS
you can check it runing that webdynpro app:
http://<server>/sap/bc/webdynpro/sap/wd_sise_mass_conf
Related SAP Support Notes:
http://service.sap.com/sap/support/notes/2009401
http://service.sap.com/sap/support/notes/1728717
http://service.sap.com/sap/support/notes/1636012
Regards,
Lluis

Dump while Select files - Confirm Target step in MOPZ

Hi All,
I'm getting dump while trying to confirm files in mopz. This is in the step confirm target.
Please see this link, issue exactly what we have but the notes cannot be implemented which is in this link Maintenance Optimizer: "Value loss during allocation"
Kindly have a look on below dump
Category               ABAP Programming Error
Runtime Errors         CONVT_DATA_LOSS
Except.                CX_SY_CONVERSION_DATA_LOSS
ABAP Program           CL_MO_SMP_ADAPTER=============CP
Application Component SV-SMG-MAI
Date and Time          16.12.2011 00:32:20
     Short text
          Value loss during allocation.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "CL_MO_SMP_ADAPTER=============CP" had to be
           terminated because it has
          come across a statement that unfortunately cannot be executed.
     What can you do?
          Note down which actions and inputs caused the error.
          To process the problem further, contact you SAP system
          administrator.
          Using Transaction ST22 for ABAP Dump Analysis, you can look
          at and manage termination messages, and you can also
          keep them for a long time.
     Error analysis
          An exception occurred that is explained in detail below.
          The exception, which is assigned to class 'CX_SY_CONVERSION_DATA_LOSS', was not
           caught in
          procedure "GET_2ND_CHECK_RESULT" "(METHOD)", nor was it propagated by a RAISING
           clause.
          Since the caller of the procedure could not have anticipated that the
          exception would occur, the current program is terminated.
          The reason for the exception is:
          Value "01200314695000002461|01200314694900013074:01200314694900009502|" was
           allocated in a field which is not long enough.
          Therefore the target field could not store all information of
           "01200314695000002461     01200314694900013074:01200314694900009502     ".
     How to correct the error
          Probably the only way to eliminate the error is to correct the program.
          If the error occures in a non-modified SAP program, you may be able to
          find an interim solution in an SAP Note.
          If you have access to SAP Notes, carry out a search with the following
          keywords:
          "CONVT_DATA_LOSS" "CX_SY_CONVERSION_DATA_LOSS"
          "CL_MO_SMP_ADAPTER=============CP" or "CL_MO_SMP_ADAPTER=============CM00A"
          "GET_2ND_CHECK_RESULT"
          If you cannot solve the problem yourself and want to send an error
          notification to SAP, include the following information:
          1. The description of the current problem (short dump)
             To save the description, choose "System->List->Save->Local File
          (Unconverted)".
          2. Corresponding system log
             Display the system log by calling transaction SM21.
             Restrict the time interval to 10 minutes before and five minutes
          after the short dump. Then choose "System->List->Save->Local File
          (Unconverted)".
          3. If the problem occurs in a problem of your own or a modified SAP
          program: The source code of the program
             In the editor, choose "Utilities->More
          Utilities->Upload/Download->Download".
          4. Details about the conditions under which the error occurred or which
          actions and input led to the error.
          The exception must either be prevented, caught within proedure
          "GET_2ND_CHECK_RESULT" "(METHOD)", or its possible occurrence must be declared
           in the
          RAISING clause of the procedure.
          To prevent the exception, note the following:
     System environment
          SAP Release..... 702
          SAP Basis Level. 0004
          Application server... "OMEGASOL"
          Network address...... "172.16.1.13"
          Operating system..... "Windows NT"
          Release.............. "6.0"
          Hardware type........ "4x AMD64 Level"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 5
          Shortdump setting.... "full"
          Database server... "OMEGASOL"
          Database type..... "DB6"
          Database name..... "OS1"
          Database user ID.. "SAPOS1"
          Terminal.......... "124.123.157.231"
          Char.set.... "C"
          SAP kernel....... 720
          created (date)... "Aug 5 2010 02:21:12"
          create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
          Database version. "DB6_81 "
          Patch level. 59
          Patch text.. " "
          Database............. "DB6 08.02., DB6 09."
          SAP database version. 720
          Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
           NT 6.0, Windows NT 6.1"
          Memory consumption
          Roll.... 0
          EM...... 33518336
          Heap.... 0
          Page.... 81920
          MM Used. 32855760
          MM Free. 658336
     User and Transaction
          Client.............. 100
          User................ "OS1_USER"
          Language key........ "E"
          Transaction......... " "
          Transaction ID...... "344F27E12581F11B97DA920465FA5E5A"
          EPP Whole Context ID.... "920465FA5E5A1ED189E9DA9C282A77DA"
          EPP Connection ID....... "920465FA5E5A1ED189E9DAF1CA0A37DA"
          EPP Caller Counter...... 1
          Program............. "CL_MO_SMP_ADAPTER=============CP"
          Screen.............. "SAPMHTTP 0010"
          Screen Line......... 2
          Debugger Active..... "none"
     Server-Side Connection Information
          Information on Caller of "HTTP" Connection:
          Plug-in Type.......... "HTTP"
          Caller IP............. "124.123.157.231"
          Caller Port........... 8000
          Universal Resource ID. "/sap/bc/webdynpro/sap/wda_mopz_plan"
          Program............. "CL_MO_SMP_ADAPTER=============CP"
          Screen.............. "SAPMHTTP 0010"
          Screen Line......... 2
          Information on Caller ofr "HTTP" Connection:
          Plug-in Type.......... "HTTP"
          Caller IP............. "124.123.157.231"
          Caller Port........... 8000
          Universal Resource Id. "/sap/bc/webdynpro/sap/wda_mopz_plan"
     Information on where terminated
          Termination occurred in the ABAP program "CL_MO_SMP_ADAPTER=============CP" -
           in "GET_2ND_CHECK_RESULT".
          The main program was "SAPMHTTP ".
          In the source code you have the termination point in line 19
          of the (Include) program "CL_MO_SMP_ADAPTER=============CM00A".
          The termination is caused because exception "CX_SY_CONVERSION_DATA_LOSS"
           occurred in
          procedure "GET_2ND_CHECK_RESULT" "(METHOD)", but it was neither handled locally
           nor declared
          in the RAISING clause of its signature.
          The procedure is in program "CL_MO_SMP_ADAPTER=============CP "; its source
           code begins in line
          1 of the (Include program "CL_MO_SMP_ADAPTER=============CM00A ".
     Source Code Extract
     Line     SourceCde
         1     method GET_2ND_CHECK_RESULT.
         2       DATA ls_buffer TYPE smp_buffer.
         3       CLEAR ev_status.
         4       DATA lv_crm_id TYPE crmt_object_guid.
         5     mo_controller->crm_adapter->get_crm_id(
         6     IMPORTING ev_crm_id = lv_crm_id
         7     ).
         8       SELECT * FROM smp_buffer INTO ls_buffer WHERE crm_id EQ lv_crm_id AND action EQ mopzp_c_ac
         9         ev_status = ls_buffer-action_lock.
        10       ENDSELECT.
        11
        12       IF ev_status EQ 2.
        13         DATA lt_errors TYPE mopzp_t_errors.
        14
        15
        16         IF ls_buffer-data IS NOT INITIAL.
        17           DATA lt_start TYPE mopzp_tt_system_constellation.
        18           DATA lt_target TYPE mopzp_tt_system_constellation.
     >>>>>           call TRANSFORMATION id SOURCE XML ls_buffer-data RESULT system_base = lt_start
        20           system_goal = lt_target
        21           stacklist = et_targets
        22           errors = lt_errors.
        23           et_target_constellation = lt_target.
        24           et_start_constellation = lt_start.
        25           on_errors( lt_errors ).
        26         ENDIF.
        27
        28         IF ls_buffer-error IS NOT INITIAL.
        29           CLEAR lt_errors.
        30           CALL TRANSFORMATION id SOURCE XML ls_buffer-error
        31           RESULT errors = lt_errors.
        32           on_errors( lt_errors ).
        33         ENDIF.
        34       ELSEIF ev_status EQ 0.
        35         check_target_constellation_asc( ).
        36       ENDIF.
        37     endmethod.
Thanks in advance
Uday

Hi,
yes, upgrade to latest level is a good move to eliminate all possible bugs. Also, you can read my blog on assigning to correct product system in solman 7.1
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
hope it helps,
Cheers,
Nicholas Chang

Managed System configuration in Solman 7.1 sp11??

Hi All,
I have done new installation of solman 7.1 and upgraded to sp11.
I did system preparation and basis configuration in solman_setup.
I have one query how to add ERP production system to SLD and how to do managed system configuration for that.
I want to add ERP Production system and Managed configuration for that and MOPZ,EWA configuration ERP Production system.
Please help me in this...
Here i attached screen shot for your reference.
Presently in managed system Only Solman system is visible.
Thank in Advance
Chandra

Hi,
Please chekc th ebelow guide
Step By Step Process to configure SLD, MOPZ & EWA in Solution Manager 7.1 SP 8
https://websmp104.sap-ag.de/~iron/fm/011000358700000209862011E/012002523100005267752014WRK2?TMP=1407918324257#bkm_show1_…
go to Configuration of SAP Solution Manager
Normally y this demo and guide will be available http://service.sap.com/rkt-solman
#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
Normally after addition in SLD ,system will adding the system in LMDB ,then added in smsy automatically. check the Job LMDB*
Update the CR content in SLD , check th below note fpor the smae.
Note 669669 - Updating the SAP Component Repository in the SLD
LMDB FQA:
Landscape Management Database (LMDB) – FAQ
Product system Editor in LMDB:
New in SP05: Product System Editor in the Landscape Management Database of SAP Solution Manager 7.1
Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki
Rg,
Karthik

SolMan 7.1: SAP_BASIS does not fulfill the prerequisites

Hello experts,
in the phase "configuration of managed systems", step 2 I get the following error:
Error
SAP_BASIS does not fulfill the prerequisites (installed: 700 SP0000, expected: 700 SP0001)
Action
Please check SAP Note 1483508 for more information
Check Context
Managed systems prerequisite | ABAP Managed system prerequisite | SYSTEM =ET4~ABAP
Info
SAP_BASIS fulfills the prerequisites (702 SP0000)
Check Context
Managed systems prerequisite | ABAP Managed system prerequisite | SYSTEM =ET4~ABAP
Info
The definition of Technical System 'ET4~ABAP' is correct
Check Context
Managed systems definition | Managed System Definition Status | SYSTEM =ET4~ABAP
The note doesn't help me at all. I have the following releases:
Managed system: SAP_BASIS 702 0007 SAPKB70207
Solman: SAP_BASIS 702 0008 SAPKB70208
No one of both systems is SAP_BASIS 700, does anybody have an idea how to solve this?
Note 1572183 - Authorizations for SAP Solution Manager RFC user is already implemented in managed system.
Thank you and best regards, Basti

Hi Basti,
May be the issue with the system details not update in the solution manager LMDB and SMSY.
Better goto the solution manager system -> LMDB -> Resynchronize the SLD detaisl for ET4 system. so it will fetch the latest details from SLD( also check in the SLD, ET4 having latest update and check the last update details) and update in the ET4 system, also check the job LMDB* . it will fetch all the details and updated in LMDB.
After syn also system is not update, try the below option
Goto SE38 and run the report RLMDB_SYNC_TECHNICAL_SYSTEM.and follow the below document
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/f6/a41e0402664451b9c4640ff4513527/content.htm
After ET4 system update, run the managed system setup it will solve the issue
Rg,
Karthik

Solman 7.1 LVSM Product system has no technical system assigned

Hi All,
As reference of blog #sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1SAPNetworkWeblogs%2528SAPNetworkWeblogs%2529
I have created product instance from LSVM and now I have problem to add "product system" for Enterprise portal (using NW 7.3) to the landscape, as its throw me an error "Product system has no technical system assigned".
From the display help its mentioned:
*Diagnosis*
Product system is not assigned a technical system in the system landscape of the Solution Manager.
*System Response*
Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly assigned, many important functions are not available to you, or are only available on a restricted basis.
*Procedure*
Assign one or more technical systems to your product system . SAP recommends that you use the corresponding wizard of the Landscape Verification Tool. To start the wizard, choose the button Change Technical System Assignments next to the message. The user interface of the wizard contains detailed information about its usage.
I'm not sure with sentence of Assign one or more technical systems to your product system and which wizard are this referring to ?
I have also checked from the wiki:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/MaintenanceofProductintheSystemLandscape#MaintenanceofProductintheSystemLandscape-EnterprisePortal
And its only supported for NW 7.0 not 7.3.
Is there anyone had this issues ?
It's feels like I'm the only one stuck in this.
Thanks in advanced.
Raff

Hi Sunny,
Many thanks for your reply.
I have followed the guide you mentioned, now I can see 2 EPD Error from LVSM.
1. Product system EPD has no technical system assigned (new)
2. Technical system EPD is not assigned to a product system
For number 1. if I clicked on Change Technical System Assignments I can see EPD there, but when I want to add the EPD by clicking > I've got this error message " Newly linked technical system EPD has already been locked by user" I've tried to remove the lock from sm12 but nothing happen.
For number 2. if I clicked on Change Product System Assignments, there is an error messages "Technical system EPD was updated in parallel session"
I believe the number 1. coming because I create it from SMSY, but the number 2. is still there in the first place.
Cheers,
Raff

RPT_MOPZ_COPY_STACK_XML shows SC version differs

Hi All,
I am using the report/program RPT_MOPZ_COPY_STACK_XML to copy the stack xml file I used from a previous upgraded system. System is identical. However, report shows "Software Component Version MDM_CONNECTOR710.711[01200615320200018572] differs between <System1> and <System2>".
However, this is not the case when checked, it's strange that this particular component has the same version between the two systems, but the report says they differs in version.
Please refer to screenshots below.
Could anyone advise to resolve this or any workaround? Thanks.
Regards,
Philip

Hello,
Are you sure that the versions are the same?
If the MDM CONNECTOR 710.711 differs in Support Package level or patch level, the check will be wrong. What is the complete entry in LMDB or SMSY for this software component in the two systems?
Best regards,
Miguel Ariño

LMDB to SMSY Synchronization ???

Similar Messages

Maybe you are looking for