Skip to Content
author's profile photo
Former Member

MetaData Comparision & Source Code Comparision

Hi Experts,

i am new to NWDI & NWDS, We are going to upgrade to EHP5, so i created a new track with upgraded ess/mss software components,

now the issue is how do i move old custom developed changes to new track, according to my research "i found that we have to perform meta data comparision or source comparision between two tracks and edit the new track code accordingly", please let me know if it is true.

If it is true please let me know in detail how to perform meta data comparation and source comparation between two tracks.

Actually where do we find source code of a track, please help me out!, thanks inadvance,



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Posted on May 03, 2011 at 09:05 AM


    Can you please clarify me on following details.

    1) Have you performed your customer specific modifications inside the Standard ESS SC itself by importing the ESS track.

    2) OR you have developed all together a different custom DCs which are not part of the standard ESS SC to achieve your customer specific requirements?

    Always remember one thumb rule.

    We never make modifications in the standard SAP delivered products.

    If you need to make customizations, then we make a copy of the standard delivery and in that copy we achieve the customer specific requirements.

    Why do we follow this practice is because, During the time of upgrade all the standard objects are overwritten by the latest patches that will be applied.

    This means that if you have made modifications directly inside the standard SAP delivered packages like ESS/MSS and

    then if you upgrade the ESS/MSS Software Components (SCs) to the latest patch, then all your custom changes will be lost as the SC of the latest patch will overwrite the old SC.

    For your question regarding how to find the source code of a track, please read the below instructions.

    1) Track is used for modifying the Source Code of Developments (DCs) that are present inside Software Components (SCs).

    2) A Track contains the SC that needs to be modified.

    3) when you import the development configuration in Developer studio using "Import Development Configuration from SLD" option you are actually importing those SCs for modifications into your developer studio via Track.

    4) So, for Example of you want to access the source code of the standard SC delivered by SAP like ESS/MSS, then you need to define the product in SLD that will be containing the ESS/MSS SC inside it.

    5) After that you need to Create a track inside CMS Landscape configurator that will incorporate your ESS/MSS SCs

    6) This very track you import into your developer studio for modifications.

    I hope you get a clear picture now.

    Please revert if you need any further clarifications.


    Shreyas Pandya

    Add comment
    10|10000 characters needed characters exceeded