Importing SCA files

Can somebody tell me what is the best path to get these specific version of SCA files for my NWDI configuration.
we are running nw2004 .
SAPBUILDT *.SCA
SAPJEE *.SCA
SAPJTECHS *.SCA

Hi,
go to service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by application group -> SAP NetWeaver -> SAP NetWeaver 2004 -> Entry by Component -> Development Infrastructure -> JDI Build Tool 6.40 -> OS Independent.
Download the appropriate SP version and follow note 891223 (personally I prefer to just unzip the archive).
Regards,
Marc

Similar Messages

  • Error while importing sca file in local development

    Hi,
    I am trying to import a sca file (MDMJ71006_0-10006189.SCA) into the local development of my NWDS.
    I right click on local development--> Import SC --> Gave path of SC --> Next (All DCs gets displayed) --> Finish.
    After clicking finish I am getting error like:
    UI job failed with exception: Updating DC model for com.sap.mdm.tech.connector java.lang.NullPointerException
    After this i can see this SC in my local development list but when I update it, the SC gets deleted.
    Can anyone help me import this sca file.
    Thanks
    Arjun

    Hi,
    I am trying to import a sca file (MDMJ71006_0-10006189.SCA) into the local development of my NWDS.
    I right click on local development--> Import SC --> Gave path of SC --> Next (All DCs gets displayed) --> Finish.
    After clicking finish I am getting error like:
    UI job failed with exception: Updating DC model for com.sap.mdm.tech.connector java.lang.NullPointerException
    After this i can see this SC in my local development list but when I update it, the SC gets deleted.
    Can anyone help me import this sca file.
    Thanks
    Arjun

  • Error while importing .SCA files in track

    Hi Folks,
    I tried importing following .SCA files into a nwdi track but it Finished with Errors.
    ENGFACADE
    ENGINEAPI
    FRAMEWORK
    WD-RUNTIME
    By logs i got information that
    'File is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    Note: I am trying to setup nwdi track for CE developments and following this  [Document|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f?quicklink=index&overridelayout=true]
    Following .SCA files are imported successfully
    SAPBUILDT
    SAPJEE
    SAPJTECHS
    Please help me to resolve this issue.
    Thanks in anticipation.
    Mandeep Virk

    Hi John,
    Following are the log details
    20100309050525 Info   :Starting Step CBS-make at 2010-03-09 05:05:25.0359 -6:00
    20100309050526 Info   :wait until CBS queue of buildspace D01_Demo_D is completely processed, before starting the import
    20100309050526 Info   :CBS queue of buildspace D01_Demo_D is completely processed. Starting the import now.
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/base.tools.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/com.sap.base.technology.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/deploy.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.j2ee14.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.lm.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.migration.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcbljcoapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcblvsiapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjeappconfigurationapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjecrossapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebcontainerpublic~api.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebservicesapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebserviceslib.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/webservices.lib.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :=================================================================
    20100309050611 Info   :buildspace = D01_Demo_D   build request id = 23
    20100309050611 Info   :wait until CBS queue of buildspace D01_Demo_D is completely processed, before asking for build results
    20100309050611 Info   :waiting for CBS queue activity
    20100309050641 Info   :build process already running: waiting for another period of 30000 ms
    20100309050641 Info   :CBS queue of buildspace D01_Demo_D is completely processed. Asking for build results now.
    20100309050641 Fatal  :processing of build request is not finished successfully, final status is:FAILED (more details in CBS log )
    20100309050641 Info   :no confirmation of request 23 because the status is not 'succeeded'
    20100309050641 Info   :=================================================================
    20100309050641 Info   :Remove software component ENGFACADE from further processing, because archive import failed
    20100309050641 Info   :Step CBS-make ended with result 'error' at 2010-03-09 05:06:41.0702 -6:00
    - Mandeep Virk

  • Import SCA files in Development Tab of the Transport Studio take more time

    Hi,
    After Check-In files in the Transport Studio, the import of SCA files starts in the development Tab of the Transport Studio.
    The import takes more time. Why this happens?
    Am I missing any configuration? Please specify in detail.
    Thanks in Advance,
    Sathya

    SC: sap.com_SAP-JEE:
    SDM-deploy
    Returncode : Not executed.
    How to check the username, password and url for SDM?
    Log file of Repository-import:
    Info:Starting Step Repository-import at 2009-10-13 22:15:49.0484 +5:00
    Info:Component:sap.com/SAP_JTECHS
    Info:Version  :SAP AG.20060119105400
    Info:3. PR is of type TCSSoftwareComponent
    Info:Component:sap.com/SAP_BUILDT
    Info:Version  :SAP AG.20060411165600
    Info:2. PR is of type TCSSoftwareComponent
    Info:Component:sap.com/SAP-JEE
    Info:Version  :SAP AG.20060119105300
    Info:1. PR is of type TCSSoftwareComponent
    Info:Step Repository-import ended with result 'not needed' at 2009-10-13 22:15:49.0500 +5:00
    Log File of CBS-make :
    Import got failed.
    Info:build process already running: waiting for another period of 30000 ms
    Info:no changes on the CBS request queue (DM0_DEMObp1_D) after a waiting time of 14430000 ms
    Fatal:The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
    Fatal:There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
    Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
         at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:369)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:120)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1736)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2009-10-14 02:16:28.0296 +5:00

  • Problems importing SCA files

    Hi
    I imported several SCA files and I openned their DCs at NWDS but several DCs are missed.
    An example is the DCs with Struts... I addeded its SCA but its DCs haven´t been imported at NWDS.
    STRUTS01_0-10003646.SCA is a pack of DCs to be used as a dependence, isn´t it ?
    so.. how can I add this in order to solve this dependences :
    12/02/2009 11:05:05 /userOut/Development Component (com.sap.ide.eclipse.component.provider.actions.dc.UsedDCFoundHandlerBase) [Thread[ModalContext,5,main]] ERROR: failed to resolve reference "sap.com/struts/lang" for DC "sap.com_SAP-SHRWEB_1:sap.com/crm/isa/web/b2b":Cannot find compartment of used component: sap.com:struts/lang
    Edited by: Michel Dambros Figueiredo - BR on Feb 12, 2009 8:51 PM

    Hi Michel,
                    May i know the business package you are going to implement. As of my knowledge for E-Commerce implementaion we will use this Struts.SCA file as an dependency(means just we need to add the SCA file to the related dependency).
    you will not get Struts.sca file into ur NWDS.
    In ur track just maintain SCA files which is related to ur business package source and add the dependencis for those source files.
    just add
    CUSTCRMPRJ,SHRWEB,SHRAPP,CRMWEB,CRMAPP to the track and remaing all as there depencdencies.
    Regards,
    Anil.

  • Error importing *.SCA file into NWDS:  Import (into source SC) not possible

    All,
    When attempting to import an SCA into a new project in NWDS, an "Import (into source SC) not possible: SCA doesn't contain DC sources" occurs.  Any assistance to fix this issue appreciated.
    Thanks,
    Lee

    You can indeed import SCAs into local development configurations in NWDS (Eclipse). You have to have a pre-existing software component of the same name and vendor which may or may not be empty.
    In the Development Infrastructure perspective in NWDS 7.1, just right-click on the software component you want to overwrite with the import and choose "Import".
    To import SCAs into a CMS track in the NWDI, you have to go to http://<NWDI server>:5<nn instance no>00/devinf/ and import the SCAs from the transport inbox directory of the NWDI server. Don't forget to maintain the SLD if necessary.
    Cheers,
    Thorsten

  • Importing .sca files fails

    Hi,
       I posted this message in NWDS Administrator also. I'm trying to configure NWDI - checking in and importing required SCs.
       In the CMS -transport Studio, the three checked in software components(SAP JEE, JTECHS, BUILDT) do not get imported.
       The CBSmake.log file has this entry:
    Info:Starting Step CBS-make at 2006-03-30 21:24:14.0208 +5:00
    Error:Cannot switch to input mode PRIVILEGED, because another import is running into the same buildspace J2E_SS_D
    Error:or the buildspace was manually switched to PRIVILEGED by the CBS administrator.
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-03-30 22:06:46.0608 +5:00
    How to resolve this issue?
    Thanks
    Sumathi

    Hi,
    Imported failed for the three .scas and the entry in CBS-make.log is:
    Fatal:The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
    Fatal:There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
    Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
         at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:369)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:120)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1440)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1170)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-03-31 18:43:19.0707 +5:00
    Any suggestions to resolve this would greatly help.
    Thanks
    Sumathi

  • Unable to import SCA files in SLD

    Hi,
    We are unable to import EP_BUILDT.sca into the SLD through Administrator or NWDI_CMSADM roles.
    For Administrator user we are getting error that - Unknown error. While checking in logs we found there are some authorizations required. So please let me known which additional authorizations are required, we are using standard Admin user.
    For NWDI_CMSADM - Administration link itself is disabled in SLD app.
    Please advise.
    Regards,
    Ritesh

    Hi Ritesh,
    You user id should have specific roles to be able to access administration link in SLD.
    Below are some of the roles your id should have :-
    LcrClassWriterAll
    LcRClassWriterNR
    LcRClassWriterLD
    refer the link for details of other roles.
    Link: [http://help.sap.com/saphelp_nw70/helpdata/EN/76/d8644233cfc553e10000000a1550b0/content.htm]

  • NWDI import of sca files repository error

    Hi,
    When I am importing SCA files. I am getting following message.Please help me.
    SAP_JTECHS
    20081202184915 Info   :Starting Step Repository-import at 2008-12-02 18:49:15.0396 -5:00
    20081202184915 Info   :Component:sap.com/SAP_JTECHS
    20081202184915 Info   :Version  :SAP AG.20080216073957
    20081202184915 Info   :1. propagation request is of type TCSSoftwareComponent
    20081202184915 Info   :Sources will not be imported for this SC
    20081202184915 Info   :Step Repository-import ended with result 'not needed' at 2008-12-02 18:49:15.0396 -5:00
    SAP_BUILDT
    20081202184221 Info   :Starting Step Repository-import at 2008-12-02 18:42:21.0146 -5:00
    20081202184221 Info   :Component:sap.com/SAP_BUILDT
    20081202184221 Info   :Version  :SAP AG.20080216005300
    20081202184221 Info   :1. propagation request is of type TCSSoftwareComponent
    20081202184221 Info   :Sources will not be imported for this SC
    20081202184221 Info   :Step Repository-import ended with result 'not needed' at 2008-12-02 18:42:21.0146 -5:00
    SAPPCUI_GP
    20081202185133 Info   :Starting Step Repository-import at 2008-12-02 18:51:33.0735 -5:00
    20081202185133 Info   :Component:sap.com/SAPPCUI_GP
    20081202185133 Info   :Version  :MAIN_ERP53PAT_C.20080709102623
    20081202185133 Info   :1. propagation request is of type TCSSoftwareComponent
    20081202185133 Info   :Sources will not be imported for this SC
    20081202185133 Info   :Step Repository-import ended with result 'not needed' at 2008-12-02 18:51:33.0750 -5:00
    SAP_ESS
    20081202185713 Info   :Starting Step Repository-import at 2008-12-02 18:57:13.0511 -5:00
    20081202185713 Info   :Component:sap.com/SAP_ESS
    20081202185713 Info   :Version  :MAIN_ERP53VAL_C.20080605130151
    20081202185713 Info   :1. propagation request is of type TCSSoftwareComponent
    20081202185825 Info   :Propagatable:<a href="http://SAP-PORTALDEV:50000/dtr/system-tools/reports/ResourceDetails?resourceID=ac445ae8331a11ddbdec0030057116fe&path=&command=Show" target="_blank">ac445ae8331a11ddbdec0030057116fe</a> exists allready in the repository. No import necessary.

    Looks OK. This is not the first time you importing these SCs, correct?
    Slava

  • Error while importing ESS.sca file in Development tab.

    Hi,
    we are importing the ESS.sca file development tab. we are getting the below error.
    Fatal   Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailureException received: HTTP protocol error [cause: Parsing of the response body failed [reason: XMLParser: > expected to close empty element (:main:, row:1, col:3541811)]]:
    please give your sugesstions.
    Regards,
    srinivas,

    Hi Srinivas,
    Try this out. I had a similar problem and i did this to make the import successful.
    1)     Go to usr/sap/J2E/JTrans/archives and copy the sca file with version shown like the above screen shot.
    2)     Unzip the entire sca file by renaming it. In the META-INF folder open the SAP_MANIFEST.MF file and the replace the 32 character guid for the field “'pr_dtrwspropagationlistid'”
    3)     Change it to a different value and save it.
    4)     There will be four folders when the sca file was unzipped. Select all the 4 folders and then zip it again to the original name of the sca file.
    5)     Copy this file and then place it in the path usr/sap/J2E/JTrans/archives.
    6)     Now try re-importing the file it should work.
    Hope this helps,
    Regards,
    Nagarajan.

  • SRM 4.0 Business package contains only an .SCA file?

    I am trying to implement the necessary BP into EP 6.0 SP2 so that I can access SRM 4.0 content(EBP 5.0).  In looking at the contents, the zip file only includes a single sca file.  I'm confused on how to import this so that I get all of the Iviews.

    Hi,
    you have to use the SDM-Tool to deploy the SCA-File.
    Greets
    Daniel

  • To see the source code in .sca file

    Hi Experts,
    We have installed EP with NWDI 7.0 2004s SP11 version.
    I have installed NWDS 7.0.08 in mysystem.
    I have been provided with a .sca file which contains the applications which are developed.
    Now I have to see the source code of those applications in NWDS thru NWDI or by any other means.
    Thanks & regards
    Vardhan

    Hi Pascal,
    I have already unzipped it and I got the folders like Build archives, Deploy archives, Meta inf, source archives.
    Deploy archives consists of .sda files what you have said in your post.
    Source archives folder has a .sc file.
    I deployed that .sca file through sdm, but it is not available in the software components under CMS inorder to import it into track.
    But that software component is available under my SLD--> installed systems products.
    My objective is to see the source code in that .sca file.
    What do you mean by double post and tripple post?
    Best Regards
    Harshavardhan

  • ESS sca file content is not able to see in EP PCD

    Hi,
    we got .sca file relating to ESS  and we deployed that but the content is not yet come to the portal content dircetory. Do anyone of you having the idea about this type of file and how to get the content into the portal.
    what this .sca file will do relating to the ESS?
    is it again we need to import the ESS businesspackage on the portal side or both are same(.sca file of ESS and the BP)?
    can anybody help me!
    Regards,
    sireesha.

    Hi Sireesha,
    Which version of ESS you are deploying?
    As you have mentioned .sca file I am assuming this is based on WebDynpro version (?)
    ESS50.x : You can directly import the business package
              from portal
              System Administration>Transport>Import
              by copying the business package contents
              under the following directory
              \usr\sap\XXX\SYS\global\pcd\Import
              (Server Side Import best practice)
    ESS60.x : You can deploy through SDM
              After successful completion if you don't see
              the contents just restart the server.
    Hope this helps.
    Regards
    -Venkat Malempati

  • How to get Source Code out of SCA File

    I have a SCA file comprising SAP Ecommerce 5 solution. What I want to achieve is to get all the source code out of it including the original directory structure. Unzipping it doesn't give me the required results and requires a lot of manual work creating directories and more unzipping.
    I tried importing it into a Local SC in NWDS but it complains that " Import (into source SC) not possible: SCA doesn't contain DC sources".
    I don't have access to NWDI at this point.

    Hi,
    For getting the source code of the Business Package Content, follow the steps below:
    1. Make sure Source Archive is available for the Business Package.
    2. Create a NWDI Track, and include all dependencies (check SAP Note : 1080927 - Creating CMS Tracks for common Application Types )
    3. Once you have track in place, you can import the Track into NWDS
    4. In Development Configurations perspective of the NWDS you can see the track.
    5. Now create Project from Inactive Workspace to start modifying the code.
    Check the link for general links
    http://wiki.sdn.sap.com/wiki/display/JDI/NWDIRelatedNotesandLinks
    Hope this helps.
    Cheers-
    Pramod

  • Import export file from hands-on training session

    I have download the required files from the Forms hands-on training session and want to install the database. After a succesfull ftp upload of the export file (binary method) to a HP-UX system, I import the file as indicated in section 7 of the installation instructions.
    I then receive several kind of the following messages:
    Import: Release 8.0.5.0.0 - Production on Mon Aug 14 19:38:29 2000
    (c) Copyright 1998 Oracle Corporation. All rights reserved.
    Connected to: Oracle8 Enterprise Edition Release 8.0.5.0.0 - Production
    PL/SQL Release 8.0.5.0.0 - Production
    Export file created by EXPORT:V08.01.05 via conventional path
    IMP-00008: unrecognized statement in the export file:
    AD 6U
    IMP-00008: unrecognized statement in the export file:
    %G6BYI2m"<9lza`k)@Q'UQIf5{$>8@?`c=@
    IMP-00008: unrecognized statement in the export file:
    9
    IMP-00008: unrecognized statement in the export file:
    Kz`
    IMP-00008: unrecognized statement in the export file:
    Is it because of the import against a 8.0.5 database or is perhaps the export file corrupt?
    I hope you can help me.
    Best regards,
    Erika van der Aar
    E-mail: [email protected]

    Hi,
    Please go through the below blog:
    How to Export/Import and activate .sca files in SAP Composition Environment - CE local development
    Hope this helps!!!
    BR,
    Anurag

Maybe you are looking for