SDM deploy af atleast one item aborted

Hi,
We are not able to deploy ear file on server and getting exception "Deploy of atleast one item aborted". Till now we have tried below solutions for fixing the same:
Restart SDM both from MMC and Console.
Changed SDM password.
Enable/Disable SDM from JCMON.
Restart J2EE server.
Changed NWDS workspace and deploy fresh ISA application.
Tried to deploy from SDM GUI.
After all these attempts we are still not able to deploy. Attached is SDM Log file for this problem.
Looking forward for valuable thoughts on this......
Dec 31, 2014 2:10:46 AM Info: Start file transfer to E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear Dec 31, 2014 2:10:47 AM Info: File transfer of E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear finished for 296 ms. Total file size is 30508322 bytes. Dec 31, 2014 2:10:47 AM Info: The SDM client uses an old SDM client API. Dec 31, 2014 2:10:47 AM Info: -------------------------- Starting deployment ------------------------ Dec 31, 2014 2:10:47 AM Info: Error handling strategy: OnErrorStop Dec 31, 2014 2:10:47 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop Dec 31, 2014 2:10:47 AM Info: Update strategy: UpdateAllVersions Dec 31, 2014 2:10:47 AM Info: Starting deployment prerequisites: Dec 31, 2014 2:10:47 AM Info: Loading selected archives... Dec 31, 2014 2:10:47 AM Info: Loading archive 'E:\usr\sap\CRQ\JC00\SDM\program\temp\temp3728619115795722000Saltestapp_ear.ear' Dec 31, 2014 2:10:47 AM Info: Selected archives successfully loaded. Dec 31, 2014 2:10:47 AM Info: Actions per selected component: Dec 31, 2014 2:10:47 AM Info: Initial deployment: Selected development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0' will be deployed. Dec 31, 2014 2:10:47 AM Info: Ending deployment prerequisites. All items are correct. Dec 31, 2014 2:10:47 AM Info: Saved current Engine state. Dec 31, 2014 2:10:47 AM Info: Starting: Initial deployment: Selected development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0' will be deployed. Dec 31, 2014 2:10:47 AM Info: SDA to be deployed: E:\usr\sap\CRQ\JC00\SDM\root\origin\sap.com\Saltestapp_ear\localhost\0\2014.12.31.02.10.28\temp3728619115795722000Saltestapp_ear.ear Dec 31, 2014 2:10:47 AM Info: Software type of SDA: J2EE Dec 31, 2014 2:10:47 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) ***** Dec 31, 2014 2:10:54 AM Info: Begin of log messages of the target system: 14/12/31 02:10:47 - *********************************************************** 14/12/31 02:10:48 - Start updating EAR file... 14/12/31 02:10:48 - start-up mode is lazy 14/12/31 02:10:51 - EAR file updated successfully for 2806ms. 14/12/31 02:10:51 - Start deploying ... 14/12/31 02:10:54 - EAR file uploaded to server for 2892ms. 14/12/31 02:10:54 - ERROR: Not deployed. Deploy Service returned ERROR: com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:732) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:714) at com.sap.engine.services.rmi_p4.Call.getResultStream(Call.java:200) at com.sap.engine.services.deploy.DeployService_Stub.deploy(DeployService_Stub.java:507) at com.sap.engine.deploy.manager.DeployManagerImpl.deployUpdateAction(DeployManagerImpl.java:709) at com.sap.engine.deploy.manager.DeployManagerImpl.deploy(DeployManagerImpl.java:513) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performDeployment(EngineApplOnlineDeployerImpl.java:188) at com.sap.sdm.serverext.servertype.inqmy.extern.EngineDeployerImpl.deploy(EngineDeployerImpl.java:96) at com.sap.sdm.serverext.servertype.inqmy.EngineProcessor.executeAction(EngineProcessor.java:224) at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:60) at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:186) at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:48) at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:83) at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:60) at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:127) at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:73) at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:59) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:128) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:97) at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:68) at com.sap.sdm.apiimpl.local.DeployProcessorImpl.deploy(DeployProcessorImpl.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:331) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.requestRemoteCall(RemoteProxyServerImpl.java:127) at com.sap.sdm.is.cs.remoteproxy.server.impl.RemoteProxyServerImpl.process(RemoteProxyServerImpl.java:38) at com.sap.sdm.apiimpl.remote.server.ApiClientRoleCmdProcessor.process(ApiClientRoleCmdProcessor.java:84) at com.sap.sdm.is.cs.session.server.SessionCmdProcessor.process(SessionCmdProcessor.java:67) at com.sap.sdm.is.cs.cmd.server.CmdServer.execCommand(CmdServer.java:76) at com.sap.sdm.client_server.launch.ServerLauncher$ConnectionHandlerImpl.handle(ServerLauncher.java:286) at com.sap.sdm.is.cs.ncserver.NetCommServer.serve(NetCommServer.java:43) at com.sap.sdm.is.cs.ncwrapper.impl.ServiceWrapper.serve(ServiceWrapper.java:39) at com.sap.bc.cts.tp.net.Worker.run(Worker.java:50) at java.lang.Thread.run(Thread.java:683) Caused by: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1292) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1811) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1695) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1288) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:336) at com.sap.engine.services.rmi_p4.Call.getResultStream(Call.java:195) ... 32 more Caused by: java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1070) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:376) at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:998) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:331) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:837) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1326) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1364) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1336) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1280) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1068) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:285) at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:332) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137) 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:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) For detailed information see the log file of the Deploy Service. 14/12/31 02:10:54 - *********************************************************** Dec 31, 2014 2:10:54 AM Info: End of log messages of the target system. Dec 31, 2014 2:10:54 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) ***** Dec 31, 2014 2:10:54 AM Error: Aborted: development component 'Saltestapp_ear'/'sap.com'/'localhost'/'2014.12.31.02.10.28'/'0': Caught exception during application deployment from SAP J2EE Engine's deploy service: com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC) Dec 31, 2014 2:10:54 AM Info: Starting to save the repository Dec 31, 2014 2:10:54 AM Info: Finished saving the repository for 74 ms. Dec 31, 2014 2:10:54 AM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process. Dec 31, 2014 2:10:54 AM Error: ---------------- At least one of the Deployments failed ---------------
Kind Regards,
Vishal Sobti

Hi Vihsal,
Can you please try to kill this from Operating System level. One more question, are you deploying this first time? Reason of asking this question is your below error code.
"ERROR: Not deployed. Deploy Service returned ERROR: com.sap.engine.services.rmi_p4.MarshalException: Exception when trying to read the original exception.; nested exception is: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.microsoft.sqlserver.jdbc.StreamError at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException"
Could you please also confirm about the database please.
Please try the below step as well if not done yet
Go to SDM Directory and enter the below
sdm jstartup "mode=integrated"
Thanks,
Hamendra

Similar Messages

Deployment exception : The deployment of at least one item aborted

Hello Everybody,
I am getting error in deploying any applications on WAS server.
It gives me following error.
just one application . other applications is OK
Help, anyone?
2009-6-26 17:47:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[005]Deployment aborted
Settings
SDM host : JT-PLDEV
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/perplpe/LOCALS1/Temp/temp57144FI_SEARCH_BXD.ear
Result
=> deployment aborted : file:/C:/DOCUME1/perplpe/LOCALS1/Temp/temp57144FI_SEARCH_BXD.ear
Aborted: development component 'FI_SEARCH_BXD'/'local'/'LOKAL'/'0.2009.06.26.17.47.22'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application local/FI_SEARCH_BXD.. Reason: Exception during generation of components of application local/FI_SEARCH_BXD in container webdynpro.; nested exception is:      com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/FI_SEARCH_BXD in container webdynpro. (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
2009-6-26 17:35:20 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[004]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[/usr/sap/TD1/JC00/SDM/program/log/sdmcl20090626093509.log]/>
<!PATTERN[sdmcl20090626093509.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 26, 2009 5:35:09 PM Info: -
Starting deployment -
Error handling strategy: OnErrorStop
Prerequisite error handling strategy: OnPrerequisiteErrorStop
Update strategy: UpdateAllVersions
Starting deployment prerequisites:
Loading selected archives...
Loading archive '/usr/sap/TD1/JC00/SDM/program/temp/temp57143FI_SEARCH_BXD.ear'
Selected archives successfully loaded.
Actions per selected component:
Update: Selected development component 'FI_SEARCH_BXD'/'local'/'LOKAL'/'0.2009.06.26.17.35.09'/'0' updates currently deployed development component 'FI_SEARCH_BXD'/'local'/'LOKAL'/'0.2009.06.26.17.17.23'/'0'.
Ending deployment prerequisites. All items are correct.
Saved current Engine state.
Starting: Update: Selected development component 'FI_SEARCH_BXD'/'local'/'LOKAL'/'0.2009.06.26.17.35.09'/'0' updates currently deployed development component 'FI_SEARCH_BXD'/'local'/'LOKAL'/'0.2009.06.26.17.17.23'/'0'.
SDA to be deployed: /usr/sap/TD1/JC00/SDM/root/origin/local/FI_SEARCH_BXD/LOKAL/0/0.2009.06.26.17.35.09/temp57143FI_SEARCH_BXD.ear
Software type of SDA: J2EE
Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Begin of log messages of the target system:
09/06/26 17:35:12 - ***********************************************************
Start updating EAR file...
start-up mode is lazy
- EAR file updated successfully for 237ms.
- Start updating...
- EAR file uploaded to server for 823ms.
- ERROR: Not updated. Deploy Service returned ERROR:
                     java.rmi.RemoteException: Cannot deploy application local/FI_SEARCH_BXD..
                     Reason: Exception during generation of components of application local/FI_SEARCH_BXD in container webdynpro.; nested exception is:
                          com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/FI_SEARCH_BXD in container webdynpro.
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:683)
                          at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
                          at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
                          at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
                          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(AccessController.java:219)
                          at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
                          at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
                     Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/FI_SEARCH_BXD in container webdynpro.
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:406)
                          at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                          at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3186)
                          at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:671)
                          ... 10 more
                     Caused by: java.lang.NullPointerException
                          at com.sap.engine.services.webdynpro.util.Procedures.switchio(Procedures.java:40)
                          at com.sap.engine.services.webdynpro.ArchiveParser.extractEntry(ArchiveParser.java:127)
                          at com.sap.engine.services.webdynpro.ArchiveParser.process(ArchiveParser.java:101)
                          at com.sap.engine.services.webdynpro.PApplication.process(PApplication.java:170)
                          at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:949)
                          at com.sap.engine.services.webdynpro.WebDynproContainer.makeUpdate(WebDynproContainer.java:1281)
                          at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
                          ... 16 more
                     For detailed information see the log file of the Deploy Service.
09/06/26 17:35:15 - ***********************************************************
Jun 26, 2009 5:35:15 PM Info: End of log messages of the target system.
Jun 26, 2009 5:35:15 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jun 26, 2009 5:35:15 PM Error: Aborted: development component 'FI_SEARCH_BXD'/'local'/'LOKAL'/'0.2009.06.26.17.35.09'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application local/FI_SEARCH_BXD..
Reason: Exception during generation of components of application local/FI_SEARCH_BXD in container webdynpro.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application local/FI_SEARCH_BXD in container webdynpro.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Jun 26, 2009 5:35:15 PM Info: Starting to save the repository
Jun 26, 2009 5:35:17 PM Info: Finished saving the repository
Jun 26, 2009 5:35:17 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Jun 26, 2009 5:35:17 PM Error: -
At least one of the Deployments failed -
Edited by: Gavin Zheng on Jun 26, 2009 6:16 PM
Edited by: Gavin Zheng on Jun 26, 2009 6:16 PM
Edited by: Gavin Zheng on Jun 26, 2009 6:17 PM

Hi,
1) Please check if J2EE engine is up or not. Please make sure that its up and running.
2) Please close the project, NWDS and then again open NWDS, project. Deploy the application.
3) Contact your BASIS consultant and explain the problem to him. Many time, BASIS consultant do carry out some BASIS activities and at that time you get this type of error.
4) If nothing works out, get your Portal restarted.
Regards,
Gary

SDM Deploy Error

Hello! I'm deploying a J2EE project and the J2EE Server gives me the following error :
18-may-2005 14:02:06 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[005]Deployment aborted
Settings
SDM host : linux2
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
Result
=> deployment aborted : file:/C:/DOCUME1/ADMINI1/CONFIG~1/Temp/temp31738Isicres_J2EE.ear
Aborted: development component 'Isicres_J2EE'/'sap.com'/'localhost'/'2005.05.18.13.59.43':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application sap.com/Isicres_J2EE.. Reason: null; nested exception is: java.lang.NullPointerException (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
I haven't idea to solve this problem!! any help, please?
Thank you

Hi Carlos,
You can find the root exception in the defaultTrace.trc file under /usr/sap/<SID>/<INSTANCE>/j2ee/cluster/server<N>/log.
Hope it helps,
Vladimir

Error " TR should have atleast one line item "

Hi,
While trying to create TO for the TR , system through the error " TR should have atleast one line item "
but the TR have the line item.
pls trhu some light. actually it properly working in development server but not working in production.

Hi
Thos error message does not make any sense if what you are saying is true in that the TR does have one line item.
The only thing I can think of is Has the stock situation changed since the TR was created.
Do you in fact have any stock?
Check the TR in LB02 to make sure it is OK
I hope that this helps
Frenchy

SAP SDM Deployment failed

Hello everybody i have a problem with my SAP ERP Installation the Error is :
An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog: SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/CENTRAL/AS/callSdmViaSapinst.log for more information. (in script unknown, line 0:
And here are my logfile , i hope you can help me for a solution. I have restart the SAP System and start it again and click retry but nothing happen, the same error comes again.
Jan 19, 2010 7:34:14 AM Info: Initial deployment: Selected development component 'tc/kmc/bc.uwl.ui/wd_pp'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'1' will be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.portal.nav.ws.NavigationWSEar'/'sap.com'/'SAP AG'/'7.0014.20071210113331.0000'/'2' will not be deployed because containing software component 'EP-PSERV'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210193159''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'3' will not update currently deployed development component 'caf/eu/gp/ui/gpconf'/'sap.com'/'MAIN_APL70VAL_C'/'1534144'/'2'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'3' will not update currently deployed development component 'caf/eu/gp/croom/content'/'sap.com'/'MAIN_APL70VAL_C'/'1498043'/'1'.
Jan 19, 2010 7:34:14 AM Info: No action: Selected development component 'com.sap.prt.ws.container'/'sap.com'/'SAP AG'/'7.0010.20061109164817.0000'/'2' will not be deployed because containing software component 'EPBC2'/'sap.com'/'SAP AG'/'1000.7.00.14.0.20071210152356''/'2' will not be deployed.
Jan 19, 2010 7:34:14 AM Info: Ending deployment prerequisites. All items are correct.
Jan 19, 2010 7:35:49 AM Info: Saved current Engine state.
Jan 19, 2010 7:35:49 AM Info: Starting: Initial deployment: Selected development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3' will be deployed.
Jan 19, 2010 7:35:49 AM Info: SDA to be deployed: C:\usr\sap\DRC\DVEBMGS00\SDM\root\origin\sap.com\caf\eu\gp\ws\msosrv\MAIN_APL70VAL_C\3\963790\sap.com_cafeugpwsmsosrv.sda
Jan 19, 2010 7:35:49 AM Info: Software type of SDA: J2EE
Jan 19, 2010 7:35:49 AM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Info: Begin of log messages of the target system:
10/01/19 07:35:50 - ***********************************************************
10/01/19 07:35:51 - Start updating EAR file...
10/01/19 07:35:51 - start-up mode is lazy
10/01/19 07:35:51 - EAR file updated successfully for 47ms.
10/01/19 07:35:51 - Start deploying ...
10/01/19 07:35:51 - EAR file uploaded to server for 32ms.
10/01/19 07:35:56 - ERROR: NOT deployed. The Deploy Service returned the following error:
                     For detailed information see the log file of the Deploy Service.
                     Exception is:
                     com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
                          at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
                          at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
                          at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
                          at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
                          at java.lang.Thread.run(Thread.java:534)
10/01/19 07:35:56 - ***********************************************************
Jan 19, 2010 7:35:56 AM Info: End of log messages of the target system.
Jan 19, 2010 7:35:56 AM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Jan 19, 2010 7:35:56 AM Error: Aborted: development component 'caf/eu/gp/ws/msosrv'/'sap.com'/'MAIN_APL70VAL_C'/'963790'/'3', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.14.0.20071210153525''/'3':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: ERROR: NOT deployed. The Deploy Service returned the following error: com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
Exception is:
com.sap.engine.services.rmi_p4.P4ConnectionException: Possible problem: no available running server node. Check your running servers.
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:700)
     at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:688)
     at com.sap.engine.services.rmi_p4.Parser.newRequest(Parser.java:180)
     at com.sap.engine.services.rmi_p4.Connection.run(Connection.java:427)
     at java.lang.Thread.run(Thread.java:534)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Jan 19, 2010 7:35:56 AM Info: Starting to save the repository
Jan 19, 2010 7:35:57 AM Info: Finished saving the repository

Hi,
Check below thread:
/message/441671#441671 [original link is broken]
Thanks
Sunny

Invoice verification:-- complete atleast one line of ACCOUNTINGDATA

Sap Gurus,
During invoice verification an error is coming.... " complete atleast one line of accounting data for item 000003".
In PO account assignment is cost center and item category is services.
service line item is having 3 parts.
1st and 3rd is linked with cost center 25020 and 3rd one to 25030. 2nd is linked with cost center 25030.

Hi Chintan
thanks for the Prompt reply. But where can we see the Account assignment from. Is it referring to the account assignment field in PO. The same Account assignment (Cost Center) has been entered in the PO line item as well.
Thanks
Nitin

"A script is already running" while attempting to run more than one item

We upgrade recently to ODT 11.2.0.3.20. Since then, attempting to run more than one item from the Solution Explorer (by selecting the items, right-clicking, and selecting "Run") results in a popup error of "Oracle Developer Tools. A script is already running". If many items are selected it results in many error messages and only a random few of the items are actually executed on the server. Also, choosing "Run On" now results in it prompting for the target database for each item selected (rather than once for all items selected like it used to). This all used to work fine in the earlier release we were using. Has anyone else run into this? Any fixes? We used to use multi-select and "Run" or "Run On" to deploy multiple items at once, but this no longer works -- doing one at a time works, but if you have hundreds of items to run, this quickly becomes unusable.
Thanks for any insight.
- Josh

cshay wrote:
I don't believe that the intention was for you to be able to run a bunch of scripts one after the other. Often there are dependencies between scripts anyway and so you you have to order them. Because we're generally deploying a large set of stored procedures (and not just one-time scripts) the order doesn't really matter -- even if a stored procedure gets created before one it depends on, once all the SPs are on the server, the ones that are "invalid" will compile correctly once you execute them.
I think a lot of people are creating master scripts that references child scripts using the "@" sql plus syntax.... have you tried that?
I'll give that a try as a work around. Only issue I have with that solution is every time we add or remove something from the solution, we also have to update the script.
We are doing a lot of enhancements to our script generation in the coming year. Keep an eye out for a beta to test.
Like I said, this used to work fine in the older versions of ODT. It seems like the new version is attempting to execute multiple items at once on the same connection simultaneously, thus resulting in the "A script is already running" error. The old version used to be smart enough to execute them one at a time -- so something changed in a more recent version to completely break "Run" and "Run On" when you have more than one item highlighted (even just highlighting 2 items and choosing "Run" runs the first item, but then gives the error for the second item).
Christian- Josh

SDM Deployment fails - Dependency caf/core/ear missing

crosspost from: SDM Deployment fails - Dependency caf/core/ear missing
deploying a DC from NWDS into SDM the following Exception is thrown:
07.01.2008 16:20:38 /userOut/daView_category (eclipse.UserOutLocation) [ThreadDeploy Thread,5,main] INFO:
002Additional log information about the deployment
<!LOGHEADERSTART/>
<!HELPManual modification of the header may cause parsing problem!/>
<!LOGGINGVERSIONhttp://1.5.3.7185 - 630/>
<!NAME[/usr/sap/IT1/DVEBMGS00/SDM/program/log/sdmcl20080107151422.log]/>
<!PATTERNhttp://sdmcl20080107151422.log/>
<!FORMATTERcom.sap.tc.logging.TraceFormatter(%24d %s: %m)/>
<!ENCODINGUTF8/>
<!LOGHEADEREND/>
Jan 7, 2008 4:14:22 PM Info:
Starting deployment
Jan 7, 2008 4:14:22 PM Info: Error handling strategy: OnErrorStop
Jan 7, 2008 4:14:22 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Jan 7, 2008 4:14:22 PM Info: Update strategy: UpdateAllVersions
Jan 7, 2008 4:14:22 PM Info: Starting deployment prerequisites:
Jan 7, 2008 4:14:23 PM Info: Loading selected archives...
Jan 7, 2008 4:14:23 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23425innobis.dewkbtmetadata.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23426innobis.dewkbtear.ear'
Jan 7, 2008 4:14:24 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23427innobis.dewkbtdictionary.sda'
Jan 7, 2008 4:14:25 PM Info: Loading archive '/usr/sap/IT1/DVEBMGS00/SDM/program/temp/temp23428innobis.dewkbtpermissions.ear'
Jan 7, 2008 4:14:26 PM Info: Selected archives successfully loaded.
Jan 7, 2008 4:14:26 PM Error: Unresolved dependencies found for the following SDAs:
1.: development component 'wkbt/ear'/'innobis.de'/'NetWeaver Developer Studio'/'20080107144202'/'0'
dependency:
name: 'caf/core/ear'
vendor: 'sap.com'
There is no component either in SDM repository or in Deployment batch that resolves the dependency.
Deployment will be aborted.
Jan 7, 2008 4:14:26 PM Error: Prerequisites were aborted.
Jan 7, 2008 4:14:27 PM Error: Error while creating deployment actions.
system:
sap.com/SAP-JEECOR 7.00 SP10 (1000.7.00.10.0.20061026144500)
sap.com/SAP-JEE 7.00 SP10 (1000.7.00.10.0.20061026144500)
I checked http://<srv>/sap/monitoring/ComponentInfo
the missing 'caf/core/ear' is not listed, however several other CAFs are:
sap.com caf/core null (964250) SAP AG MAIN_APL70VAL_C 20061212133926 sap.com/CAF
sap.com caf/core/dict null (964586) SAP AG MAIN_APL70VAL_C 20061212131613 sap.com/CAF
sap.com caf/core/gp/facade/backgroundco/ear null (964227) SAP AG MAIN_APL70VAL_C 20061212134201 sap.com/CAF
sap.com caf/core/metadata null (963689) SAP AG MAIN_APL70VAL_C 20061212133653 sap.com/CAF
etc....
Is it possible to deploy this missing caf-ear component supplementary?
I have the strange feelings caf/core/ear is something 7.1 CE only related....
thanks for any hint!
kai

Kai, I didn't mean to offend you. But good forum practice is to avoid duplicate posts.
Regards,
\-- Vladimir

Error in SDM-deploy Step

<h5>Good Morning Gentleman,</h5>
<h5>"When i'm trying to import a transport order to our productive system the import fails in step SDM-deploy with the following error:</h5>
<h5>20120228122646 Info   :Starting Step SDM-deploy at 2012-02-28 12:26:46.0143 +0:00
20120228122646 Info   :start deployment of archives:http://sapsps.sonaesierra.com:50004
20120228122646 Fatal :caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.:The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'j2ee_admin' could not be connected to the specified host 'sapsps.sonaesierra.com'and port '50004'.
     at com.sap.cms.tcs.beans.deployer.DeployConnector.openConnection(DeployConnector.java:160)
     at com.sap.cms.tcs.beans.TCSDeployBean.performDirectDeployment(TCSDeployBean.java:194)
     at com.sap.cms.tcs.beans.TCSDeployObjectImpl0_0.performDirectDeployment(TCSDeployObjectImpl0_0.java:1342)
     at com.sap.cms.tcs.beans.TCSDeploy_Stub.performDirectDeployment(TCSDeploy_Stub.java:1296)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:331)
     at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
     at $Proxy225.performDirectDeployment(Unknown Source)
     at com.sap.cms.tcs.core.SDMDeployTask.processImport(SDMDeployTask.java:302)
     at com.sap.cms.tcs.core.SDMDeployTask.process(SDMDeployTask.java:366)
     at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
     at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
     at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)
     at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
     at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)
     at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)
     at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1640)
     at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1637)
     at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)
     at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:1042)
     at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)
     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:420)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     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:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
20120228122646 Info   :Step SDM-deploy ended with result 'fatal error' ,stopping execution at 2012-02-28 12:26:46.0306 +0:00"</h5>
<h5>I'm new to NWDI and related subjects. I've already checked:</h5>
<h5>1. Port 50004 is available in the productive system</h5>
<h5>2. J2EE Visual Administrator in productive is accessible by j2ee_admin</h5>
<h5>3. j2ee_admin isn't locked in productive system</h5>
<h5>What more should i check? What could be the reason behind this error?</h5>
<h5>Thank you.</h5>
<h5>Best Regards,</h5>
<h5>Pedro Gaspar</h5>

Good Morning Kumar,
If i tell you what happened you're going to laugh... But i'll tell you anyway.
After watching your post i went to the CMS Landscape Configurator in order to look into the configuration. I noticed that the Selected Tool for deployment in the Productive Runtime system was configured as Deploy Controller (this is a NW 7.01 and as far as i've read before... in this version it's advisable to configure it as you told me in your post - SDM Deploy, thanks for that).
So i tried to change it, but nothing happened, i've tried a second time, but the changes wouldn't take effect and no message was generated. I've spent a few hours trying to understand what was happening... So i told to myself, let me try it with another browser (was using Firefox 3.6.27, changed to IE 9.0.8112) and when trying to change the runtime system configuration a message outputs... "... More than one name server configured in SLD"
Immediately searched and got SAP note 1118009 - SLD name-server configuration error in CMS. After executing note steps i was able to change the runtime system tool for deployment, and i could finish the transport.
The difference a message and the browser version can do in your life
Thanks for your reply, which helped me solve the problem.
Best Regards,
Pedro Gaspar

Getting an error " Atleast one entry could not be found in object buffer"

Hi All,
I m facing an peculiar problem while executing a custom Function Module.I have written a custom FM to create a service request and fetch the obj ID and return it back.When i tested the same in debugging mode everything is working fine. But when i execute it directly, It is giving me an error saying " Atleast one entry could not be found in object buffer" at the bottom of the screen and return parameters are not displayed.
Any pointers on this would be of great help.
Thanks,
Eureka

Hi Phani,
PFB the source code. Please look in to this at your convenient time..
FUNCTION ZSERVICE_TICKET_INC_EDIORDERS.
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(ZPROCESS_TYPE) TYPE CRMT_PROCESS_TYPE
*" EXPORTING
*"     REFERENCE(ZOBJECT_ID) TYPE CRMT_OBJECT_ID_DB
* PARAMETER QUANTITY TYPE CRMT_SCHEDLIN_QUAN.
* DATA DECLARATION FOR LOCAL VARIABLES
DATA : lv_header_guid        TYPE                   GUID_32,
         lv_header_guid16      type                   guid_16,
         lv_item_guid          TYPE                   guid_32,
         lv_sched_guid         TYPE                   guid_32,
         lt_header_guid16      type                   CRMT_OBJECT_GUID_TAB,
         wa_header_guid16      like line of           lt_header_guid16.
DATA: itab_header           TYPE STANDARD TABLE OF bapibus20001_header_ins,
         itab_created_process TYPE STANDARD TABLE OF bapibus20001_header_ins,
         itab_objects_to_save TYPE STANDARD TABLE OF bapibus20001_guid_dis,
         itab_partner          TYPE STANDARD TABLE OF bapibus20001_partner_ins,
         itab_input_fields     TYPE STANDARD TABLE OF bapibus20001_input_fields,
         itab_return           TYPE STANDARD TABLE OF bapiret2,
         lt_orderadm_h         type                   CRMT_ORDERADM_H_WRKT.
* DATA DECLARATION WORKAREAS
DATA:   wa_header             TYPE                   bapibus20001_header_ins,
         wa_partner            TYPE                   bapibus20001_partner_ins,
*         wa_item               TYPE                   bapibus20001_item,
*         WA_SCHEDLIN_I         TYPE                   BAPIBUS20001_SCHEDLIN,
         ls_inputfields        TYPE                   bapibus20001_input_fields,
         wa_objects_to_save    LIKE                   LINE OF itab_objects_to_save.
*         wa_pricing            TYPE                   bapibus20001_pricing,
*         wa_sales              TYPE                   bapibus20001_sales,
*         wa_shipping           TYPE                   bapibus20001_shipping,
*         wa_product_i          TYPE                   bapibus20001_product.
*         wa_schedlin_i    LIKE LINE OF lt_schedlin_i,
*         wa_schedlines   LIKE LINE OF lt_schedlines,
DATA:   wa_created_process    LIKE LINE OF itab_created_process,
         itab_saved_objects    TYPE STANDARD TABLE OF bapibus20001_object_id,
         wa_saved_objects      LIKE LINE OF itab_saved_objects,
         gc_x TYPE c.
         gc_x = 'x'.
* CREATION OF HEADER GUID
CALL FUNCTION 'GUID_CREATE'
    IMPORTING
      ev_guid_16 = lv_header_guid16
      ev_guid_32 = lv_header_guid.
CLEAR : wa_header.
data: temp type CRMT_OBJECT_GUID_TAB.
*temp = (CRMT_OBJECT_GUID_TAB)lv_header_guid16.
* Passing the respective values from the Header table to internal table.
wa_header-guid          = lv_header_guid.
* zprocess_type           = 'ZSC'.
wa_header-process_type = zprocess_type.
* wa_header-description = 'MY S2D ORDER'.
APPEND wa_header TO itab_header.
*Appending the values to the ITAB_HEADER.
*      ls_inputfields-ref_guid = LV_HEADER_GUID.
*      ls_inputfields-REF_KIND = 'A'.
*      ls_inputfields-objectname = 'ORDERADM_H'.
**     ls_inputfields-logical_key = ' '.
*      ls_inputfields-fieldname = 'PROCESS_TYPE'.
*      APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
*      CLEAR ls_inputfields.
* HEADER PARTNER DETAILS
wa_partner-ref_guid = lv_header_guid.
wa_partner-ref_kind = 'A'.
wa_partner-ref_partner_handle = '0001'.
wa_partner-partner_fct = '00000001'.
wa_partner-partner_no = '1000007'.
wa_partner-no_type = 'BP'.
wa_partner-display_type = 'BP'.
APPEND wa_partner TO itab_partner.
* APPENDING THE ITAB_PARTNER TO INPUT_FIELDS
ls_inputfields-ref_guid = lv_header_guid.
ls_inputfields-ref_kind = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'REF_PARTNER_HANDLE'.
APPEND ls_inputfields TO itab_input_fields.
CLEAR ls_inputfields.
****PARTNER_FCT*********************************
ls_inputfields-ref_guid = lv_header_guid.
ls_inputfields-ref_kind = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'PARTNER_FCT'.
APPEND ls_inputfields TO itab_input_fields.
CLEAR ls_inputfields.
****PARTNER_NO**********************************
ls_inputfields-ref_guid = lv_header_guid.
ls_inputfields-ref_kind = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'PARTNER_NO'.
APPEND ls_inputfields TO itab_input_fields.
CLEAR ls_inputfields.
****NO_TYPE*************************************
ls_inputfields-ref_guid = lv_header_guid.
ls_inputfields-ref_kind = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'NO_TYPE'.
APPEND ls_inputfields TO itab_input_fields.
CLEAR ls_inputfields.
****DISPLAY_TYPE********************************
ls_inputfields-ref_guid = lv_header_guid.
ls_inputfields-ref_kind = 'A'.
ls_inputfields-objectname = 'PARTNER'.
ls_inputfields-logical_key = '0001'.
ls_inputfields-fieldname = 'DISPLAY_TYPE'.
APPEND ls_inputfields TO itab_input_fields.
CLEAR ls_inputfields.
*****KIND_OF_ENTRY*******************************
*      ls_inputfields-ref_guid = LV_HEADER_GUID.
*      ls_inputfields-REF_KIND = 'A'.
*      ls_inputfields-objectname = 'PARTNER'.
*      ls_inputfields-logical_key = '0001'.
*      ls_inputfields-fieldname = 'KIND_OF_ENTRY'.
*      APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
*      CLEAR ls_inputfields.
*Calling a standard BAPI to create SALES OREDER using the filled internal tables.
CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
    TABLES
          header          = itab_header
*          item            = itab_item
          return          = itab_return
          partner         = itab_partner
          input_fields    = itab_input_fields
          created_process = itab_created_process.
*         APPOINTMENT     = ITAB_APPOINTMENT
*         TEXT            = ITAB_TEXT
*          scheduleline    = lt_schedlin_i
*         pricing         = itab_pricing
*          sales           = itab_sales
*          shipping        = itab_shipping
*          product         = itab_product_i.
READ TABLE itab_created_process INTO wa_created_process WITH KEY guid = lv_header_guid BINARY SEARCH.
wa_objects_to_save-guid = wa_created_process-guid.
* Appending the Guid of the SALES ORDER to be saved to the internal table
APPEND wa_objects_to_save TO itab_objects_to_save.
*   Calling standard BAPI to save the process.
CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
    EXPORTING
      update_task_local = space
      save_frame_log    = gc_x
    TABLES
      objects_to_save   = itab_objects_to_save
      saved_objects     = itab_saved_objects
      return            = itab_return.
* Calling the Standard BAPI to Commit the transcation.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
wa_header_guid16 = lv_header_guid16.
append wa_header_guid16 to lt_header_guid16.
* Calling CRM_ORDER_READ to get the object id and add line item to the order
CALL FUNCTION 'CRM_ORDER_READ'
    EXPORTING
     IT_HEADER_GUID                    = lt_header_guid16
    IMPORTING
      ET_ORDERADM_H                     = lt_orderadm_h
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
data: object_id type CRMT_OBJECT_ID_DB,
      wa_orderadm_h like line of lt_orderadm_h.
read table lt_orderadm_h into wa_orderadm_h WITH KEY guid = lv_header_guid.
object_id = wa_orderadm_h-object_id.
Zobject_id = wa_orderadm_h-object_id.
WRITE: / 'Object ID: ',object_id.
ENDFUNCTION.

How can I buy more than one item at a time?

How can I buy more than one item at a time i iPhote fx a book and a calander? It would be nice to place one order and only pay for the shipping once!

You can't.
Regards
TD

J2ee Admin User locked on SDM Deployment - BI 7.0 and EP 7.0

Hi,
We had a recent issue on BI iview publishing from the BEX WAD 7.0 in our Production Portal server.
The BEX WAD had the error " Java communication error"
" An Error occured during communication with the BI Components of the J2ee engine"
We traced down to identify that the current stack NW 7.0 SP14 BI Components had issues and had to patch to the next level
However, during deployment of the patch using SDM, the components (all) failed posting the following error. The SDM deployment got struck and the J2ee Engine user j2ee_admin was locked.
Only a restart of the j2ee engine is allowing us to get the Visual Admin connected. But the SDM deployment again is failing and admin user gets locked. Is there any tested solution to solve this.
Kindly help asap.
Trace:
SDM:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxxx] with user name: [j2ee_admin]check your login information.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
J2ee Engine:
Error while connecting
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread.
     at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479)
     at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180)
     at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:313)
     at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345)
     at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239)
     at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     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:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

Hi Anup,
The restart unlocks the j2ee engine admin user and i am able to login to Visual admin and SDM and not otherwise (SDM is hanged and doesnot allow another session and hence only restart helps me to get into SDM again)
Admin Pwds reset etc from config tool secure store and all possible solutions have been tried before restart.
However, after restart, when we try to deploy again, the deploy fails saying the same msg
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxx] with user name: [j2ee_admin]check your login information.
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
Any clues ?
Regards
Venkat.

How to get a value from one item into another

How can i get value from one item into another item.
Ex: I have a report, in there i have check boxes, and when i have checked some rows, and press submitt, a prosses computates it into a item on another page, and a branche redirects to page 3. Then i'm going to use the value in the item into a PL/SQL script in an report to show the submittet items.
How can i do this?
Computation script, pages and all that is fixed. But i dont know which PL/SQL statement to use to get th value from the item.

Hi Fredr1k,
Use the V() function from pl/sql.
e.g. V('P3_MY_ITEM')
will return the value of that page item.
As long as the pl/sql is called from within the Apex environment.
Regards
Michael

I tried to delete one item from an email folder, and my computer deleted the whole file. I cant fint it anywhere.

I tried to delete one item from an email folder, my computer deleted the whole file and I cant find it anywhere. Any ideas?

lindafromgainesville wrote:
...is there a seperate trash for email?
In Mail, yes -

How to cancel an order or to remove one item, bought as a guest?

how to cancel an order or to remove one item, bought as a guest?

That does not help at all.
Please explain. Use sentences please.
How do you buy something as a guest?
You have an iphone?
You purchased an app?
You don't want the app? Simply delete it. This is covered in the manual.
If you do not explain what you are talking about, then it is very difficult to help

SDM deploy af atleast one item aborted

Similar Messages

Maybe you are looking for