on 09-24-2008 9:23 PM
Hello Friends,
Our landscape is ECC 6.0 & EP 7.0 & NWDI 7.0.
We are implementing ESS. We used ESS BP 1.0. However for some reason we went ahead and used ESS 100 instead of ESS 600. We did some WebDynpro changes and checked in the changes to NWDI.
ESS 100 in NWDI is looking for EP 640 component and we have 1 broken DC reach in ESS 100 and PCUI_GP 100 SCs. so the central build in CBS is failing. Hence we can't move the changes in landscape through NWDI.
So we deployed the changed DCs manually through SDM.
Now we are thinking of creating a new track with ESS and PCUI_GP 600 in NWDI and redo all the changes in it. Is this the best approach ?
If we want to deploy ESS 600 on portal, is it going to overwrite ESS 100 ?
Can both the version reside together ?
Thanks
Shobhan
Hi Shoban,
So now you know the correct verion that is ESS600. I think that you can create a new track based on ESS600 Business package. So now create another track for all custom modifidations based on SAP Provided code.
So that overall you will have two tracks one is Standard SAP provided code track say we call it as BASE track and another one is for your custom modifications say we call it as ESS600CUSTOM track.
So you will use the ESS600CUSTOM track for all your custom modifications and you will have BASE track for future verifications.
Thanks
Krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shoban,
If you think that ESS100 is not the correct version , then it's a good idea to undeploy the wrong version and deploy the correct version.
I explained the procedure how to undeploy your wrong version of ESS Software Componensts.
The Software Deployment Manager (SDM) is a tool with which you can undploy ESS100 SCA files.
First launch the SDM tool. To start SDM GUI, execute the following script file in the /sap//SDM/program directory:
RemoteGui.bat for Windows hosts.
Now logon to SDM:
1. Choose SDM Gui ® Login
2. Enter the SDM Server password.
3. In the User Description (Optional) field you can enter a description of the user who is logging on. Any users
who are then prevented from accessing the SDM can see this description.
4. Specify the SDM server hostname and port.
5. Choose Login.
Once you log in to SDM , Choose the Undeployment tab page to undeploy SDAs you have previously deployed with SDM and do not need anymore.
If you want to undeploy an SDA on which other SDAs depend, then you have to undeploy all of them beforehand.
Thanks
Krishna
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.