Skip to Content


The purpose of this document is to list steps to undeploy Software/ Development component on NetWeaver Java release 7.0x(7.00, 7.01, 7.02).

Use Case

Custom Software/ Development components have been deployed in system. During system upgrade, SUM or other upgrade tool could not continue upgrade saying these custom Software/ Development components can not be handled by upgrade tool. Under this situation, you can follow this document to manually undeploy custom Software/ Development components before upgrading.

NOTE: Undeployment as such is not supported and should be used only in cases where the SAP Basis admin is well versed with the system landscape and the repercussions of this activity very well. If unknowingly a component is deployed, the best option would be to restore the system to the previous state it was before the deployment was triggered. Hence, you should always take a full offline backup before commencing deployment.


Check out all Development Components that belong to the Software Components that need to be undeployed together.

1. Access http://<hostname>:<port>/sap/monitoring/SystemInfo, then click link “all components…“.

2. Suppose want to undeploy Software Component DI_CBS, DI_CMS, DI_DTR.

    Note: Undeployment of SAP standard Software/ Development components is very risky operation.

             This document only use these Software/ Development components as example.

             Please do not do such undeployment in real system.


3. Check “Development Components” section for all entries that has “Software Component” with value DI_CBS, DI_CMS DI_DTR.




1. Create xml file to list all Development Components identified in Step1 with format like below. Make sure no extra space and exact upper/lower case.



<DevelopmentComponentLine name=”dev_comp1_name” vendor=”vendor1_name”></DevelopmentComponentLine>

<DevelopmentComponentLine name=”dev_comp2_name” vendor=”vendor2_name”></DevelopmentComponentLine>




For example:



<DevelopmentComponentLine name=”tc.CBS.Appl” vendor=””></DevelopmentComponentLine>

<DevelopmentComponentLine name=”tc.CBS.CommonPart” vendor=””></DevelopmentComponentLine>




2. Stop SDM node, then modify it to standalone mode.


3. Undeploy Development Components using command: sdm undeploy “list=<xml file location>” “undeploydb=yes”


    If undeployment successfully finished, “Return code: 0” message show up as below image.

    If any error happen, error detail can be seen in newest sdmlog*.log in usr/sap/<SID>/<xx>/SDM/program/log.


4. Once undeployment successfully finished, set SDM back to integrated mode and start it manually.




Access http://<hostname>:<port>/sap/monitoring/SystemInfo again, and confirm indeed Software/ Development components that want to undeployed are not show there anymore.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Tom Xing

    Hi Amy,

    Nice post!

    Follows a question 🙂

    Afaik, undeployment on AS Java is hardly suggested.

    Consider this situation: Software Component A has dependency on SC B, and nothing depends on A.

    Is there going to be an error if we undeploy B directly, while A is still in the system?

    Or is there a way to check dependency, to make the undeployment a bit “safer”?

    BR, Tom

    1. Amy Lv Post author

      Hi Tom,

      Good question!

      Undeployment will check dependency of Development component. For your situation, If undeploy B , error will occur saying A is not selected to undeploy. Example error log:


      Info: Select development component A for undeployment

      Error: Deployment A cannot be undeployed:

      Error: Deployment B is not selected


      This error log can be seen in newest sdmlog*.log in usr/sap/<SID>/<xx>/SDM/program/log




Leave a Reply