Short pick automatic WT creation issue using Wave process

Hi Experts,
If we make direct pick for short pick quantity for product with multiple bins, system is creating two WTs successfully.
i.e. one for actual quantity and second WT for remaining quantity.
But, when we make above process using wave process, system is not creating automatic WT for remaining quantity.
Could you please help me on this issue? Little urgent to me.
Thank you in advance.

Hi Experts, Any thoughts on this below issue?
If we make direct pick with short pick quantity for multiple line items in ODO, system is creating two WTs successfully. i.e. one for actual quantity and second WT for remaining quantity.
But, when we make above process using wave process, system is not creating automatic WT for remaining quantity?
Anything issue with Exception code? Can you please help me on this?
Thank you ...
Sridhar

Similar Messages

Need links for creation varaibles using different processing types....

Hi All,
can you provide me links for creation of variables using diiferent processing types...
it would be grateful if you peovide any links which covers all most all the topics in bi reporting....
Thanks All.

Hi,
Pl refer to following link as well
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0b25093-b548-2e10-0cba-fcac7890585f?QuickLink=index&overridelayout=true
Customer exit for text variables
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d343131313235%7d
http://help.sap.com/saphelp_nw04/helpdata/en/61/579b3c494d8e15e10000000a114084/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d313535373530%7d
Thanks and regards
Kiran

Database Adapter - Datasource creation Issue - Using WLST

Hi ,
Im tring to create a weblogic multi data source in an osb cluistered env using the wlst script and getting an issue while updating the plan.xml via script.
im getting the plan path via this command in WLST planPath = get('/AppDeployments/DbAdapter/PlanPath')
but the issue is i dont get the complete path insted i get something like this 'osb_cluster/plans/DBAdapter/DbAdapterPlan.xml'
when i run the same script in single node environment , the script executes fine and update the plan path . Also i get the complete plan path url like this '/u9000/app/oracle/product/fmw/osb_11.1.1.5.0/Oracle_OSB/soa/connectors/DBAdapter/DBAdapterplan.xml'
is there any issue with my clustered environment . Any help is appreciated !
Thanks ,
karthik

Just one more question , even though config.xml has invalid plan path when i see the plan path from AdminConsole ->Deployments->DbAdapter , it is showing the right url there. Just wanted to understand how this plan path is referenced.I believe it can be referenced as a relative path form by weblogic... Not sure, but may be relative to domain root...

MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin

Hi,
I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
This is the setup I used:
JDBC Version "2.0 (with XA support)
JDBC 2.0 Compliant:
object factory: com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
datasource type: XADataSource
xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
On the additional tab:
databaseName=fldev_jj
portNumber=1433
serverName=dbsrv61
user=fldev_jj
password=******
Even added the url, but that made no difference. Chose Vendor SQL,
and have initial connections set to 1. This url worked when used
with a version 1.x datasource.
What can I try to do to resolve this?
Full exception:
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     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:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     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:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
     ... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
     at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
     ... 43 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     ... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     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:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
     ... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
     at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
     ... 43 more
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     ... 33 more
     at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
     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:324)
     at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
     at javax.management.MBeanException.writeObject(MBeanException.java:126)
     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:324)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
     at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
     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:324)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
     at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
     at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
     at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
     at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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)

Leaving the object factory empty is absolutely part of the solution.
I can now start the data source and it can get a connection.
The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
The problem with that is that I'm no longer sure it uses XA transactions...
Will do more testing...
Very helpful reply Yuri!
Thanks

Strange Automatic Folder Creation Issue IMAP

Hello all,
I have been using mail for over a year and besides some minor issues (delay to download attachments, messages cant be read if I click on them before they are fully loaded) it worked OK. However, since the last update I encountered the following Issue:
A new "Inbox" folder which contains other Inbox folder that contains another Inbox folder and so on is created every time I restart the application, inside my IMAP account inbox. This creates no other problems that I am aware of, but it is annoying to have to delete this folder every time.
I have no idea what could be the cause of this, or how to go about giving this a permanent solution.
Any feedback and possible solutions to this will be greatly appreciated!
HKondor

I have this same problem. Again, it does not seem to cause any problems that I know of, but it strange and just makes me think something is not correct with the setup. Any further info would be appreciated. Thanks.

ERS flag not picked automatically

hi gurus ,
we are using srm 5.0 , extended classic scenario
while creating a po in srm with ers vendor with account assignment wbs , the ers flag is not getting picked automatically.
while if i use the same vendor and use account assignment cost center , the ers flag is getting picked in the po.
so for wbs po , we are manually going to the follow -on tab in item data and ticking the ers indicator.
what could be the reason for this ? why is the ers flag not getting picked from the vendor master.

please reply !

Create TO automatic by using wave pick for outbound delivery NLC (STPO)

Dear all,
In Cross company code process, we have to create TO automatic by using wave pick for outbound delivery NLC (delivery type NLCC). Time data in outbound delivery NLC have been fulfilled, but there is no TO created, what is wrong in this? pls help.
Thanks

Hi Kishor,
Is there any requirement of TO when ECC system is Interfaced to EWM.
As per my understanding we have terminology WT & WO in EWM.
Regards,
Rock

Can I automate the creation of a cluster in LabView using the data structure created in an autogenerated .CSV, C header, or XML file?

Can I automate the creation of a cluster in LabView using the data structure created in an auto generated .CSV, C header, or XML file? I'm trying to take the data structure defined in one or more of those files listed and have LabView automatically create a cluster with identical structure and data types. (Ideally, I would like to do this with a C header file only.) Basically, I'm trying to avoid having to create the cluster by hand, as the number of cluster elements could be very large. I've looked into EasyXML and contacted the rep for the add-on. Unfortunately, this capability has not been created yet. Has anyone done something like this before? Thanks in advance for the help.
Message Edited by PhilipJoeP on 04-29-2009 04:54 PM
Solved!
Go to Solution.

smercurio_fc wrote:
Is this something you're trying to do at runtime? Clusters are fixed data structures so you can't change them programmatically. Or, are you just trying to create some typedef cluster controls so that you can use them for coding? What would your clusters basically look like? Perhaps another way of holding the information like an array of variants?
You can try LabVIEW scripting, though be aware that this is not supported by NI.
Wow! Thanks for the quick response! We would use this cluster as a fixed data structure. No need to change the structure during runtime. The cluster would be a cluster of clusters with multiple levels. There would be not pattern as to how deep these levels would go, or how many elements would be in each. Here is the application. I would like to be able to autocode a Simulink model file into a DLL. The model DLL would accept a Simulink bus object of a certain data structure (bus of buses), pick out which elements of the bus is needed for the model calculation, and then pass the bus object. I then will take the DLL file and use the DLL VI block to pass a cluster into the DLL block (with identical structure as the bus in Simulink). To save time, I would like to auto generate the C header file using Simulink to define the bus structure and then have LabView read that header file and create the cluster automatically. Right now I can do everything but the auto creation of the cluster. I can manually build the cluster to match the Simulink model bus structure and it runs fine. But this is only for an example model with a small structure. Need to make the cluster creation automated so it can handle large structures with minimal brute force. Thanks!

Issue in automatic delivery creation

Hello,
This is to reframe the issue again and give you some more details on
this issue –
As per SAP standard we have configured our salers order for
immediate delivery creation with a default delivery block – XX. Hence
as
per config whenever we create a sales order, it gets created with a
default delivery block – XX which later on users removes manually and
system subsequently as per design creates the delivery document
automatically.
We are facing two issues in case of sales order design –
1. Some time even after removing the delivery block –XX manually,
system do not create the delivery document automatically against those
sales order.
2. Some time if sales order is created with a credit block in
addition to Delivery Block – XX, system doesn’t create automatic
delivery document against those sales orders even after releasing /
removing the credit block as well as Delivery block.
But if you just open those sales orders in VA02 and make any change for
example – Carry out new pricing Or carry out Availability check for any
one item and save the sales order without making any change into it,
system is creating delivery document against that sales order
automatically.
This issue is happening sporadically. There is no specific pattern
where
this issue is happening. This is an inconsistent issue. We could not
replicate this issue in any of our Non-production SAP system.
Whenever we tried to investigate it in debug mode for the sales orders
where this issue has happened, it worked well and created delivery
document automatically.
Requesting you to kindly look into this issue again and help us to fix
it as early as possible.
Thanks and Best Regards,
Pankaj Jain

Hi,
plz confirm if the automatic delivery creation is activated to few sales order types
as it is most frequently used for Cash sales and Rush Orders
more ever Credit check not Applicable for cash and rush sales

I am looking for a way to automate index creation using Adobe Reader Pro without having to use the screen user interface, as the indexing has to be run by a batch process.

I am looking for a way to automate index creation using Adobe Reader Pro without having to use the screen user interface, as the indexing has to be run by a batch process.

[discussion moved to Creating, Editing & Exporting PDFs forum.]

Goods picking and Post goods issue in VL02N

Dear All,
Am hving problem in Picking goods and Post goods issue.
This is for the Stock Transport Order with Delivery via Shipping
Supplying plant is 1000(SAP std,sloc 0001) and Receiving plant 1100(sloc 0001).
Sales org:1000
Distrbn Chnnl:10
Division:00
1.maintained matrial for both the plants.
2.Creted STO by using DOC type as "UB" and item cat "U".
3.And getting the Shipping data for the material in the STO.as shipping point is 1000.
saved the Po.
4.After that i done the GR w/o PO for the material using Mvt type 501.
5.Then,VL10B creating Delivery doc.n this is also created.
6.but when i do the picking and PGI in VL02N there picking field is greyed out bt i have tried to mangae that when i give the picking Qty in the picking qty field system is throwing the following error.
<b>Item to be picked by WM (picking quantity cannot be entered)
Message no. VL118
Diagnosis
For this item, picking is carried out using warehouse management transfer orders since the material is stored in a warehouse with random storage.
System Response
The system does not allow you to enter a picking quantity manually. The picking quantity is copied automatically into the delivery during the creation of the corresponding transfer order.</b>
is any data missed by me while doing this process?
pls let me know n help me in this regrds
Thank you all

Hi Vijay
By changing storage location you could do b'coz the new storage location is not maintained with warehouse, hence no need to perform warehouse transactions (TO creation and confirmation) before inventory mgmt transactions (PGI).
For trying pick up with WH, first u should have enough stocks in approppriate storage bins and u should perform pick up by creation of TO and confirmation.
warm regards
sairam akundi

Freight picking automatically in PO

Hi Team,
i am using info record in creation of PO and enter a manual z-condition type at header level for freight. but i am facing an issue when i am create a PO there is picking automatically freight in same condition value without manually enter.
it's happening when i am using info record but in info record there is no condition type define like z-condition for freight,
there is neither any condition record and nor use any routine in pricing procedure.
how could i solve this problem.

Dear ,
In customizing settings
SPRO->MM->Purchasing->Environment Data->Define Default Values for Buyers->Settings for Default Values
Select 01 (or what ever ) ->Details ->go to Price adaptation tab here copying of conditions from last purchase order
select Do not Copy
and Assign the Paramater EFB to user's in SU01..
So that you will not freight from last PO

Error during automatic PO creation by PR (ME59N)

Dear All,
Following errors has been shown after automatic po creation by ME59N:-
Message text     Message Class Message Number
PO could not be created
PO header data still faulty        MEPO               2
Enter Validity End        ME              83
Enter Latest GR Date        ME              83
Can delivery date be met?        ME              40
Requisition could not be converted
Please suggest how to solve above .
with regards,
Pradeep Bhardwaj

Hello,
to check the errors issued I suggest to try to create the PO converting the PR from transaction ME21N.
I guess that some fields, mandatory for the PO creation, were not filled in the Purchase Request and could not be determined in any different way. If you can't maintain them on the PR you should set them as optional, if possible, in the customizing for Screen lay-out of transaction ME59N, under "Materials Management --> Purchasing --> Purchase Order --> Define Screen Layout at Document Level".
Hope to be useful.
Best regards,
Andrea

Automatic PO creation from SC

Hi Experts,
I am using SRM 7.0 with extended classic scenario and I have issue in the automatic po creation. For some Shopping Carts the PO is not automatically created. The SC is having Source of Supply Assigned and all the approves have completely approved the SC. The latest status is I1111 Item in Transfer Process.
I checked in RZ20, ST22 and could not find any error or dumps.
For the SC item under BBP_PDBEI the BE_OBJECT_TYPE is BUS2201 and BE_OBJECT_ID 1, once I trigger the PO creation manually the PO object id is reflected here.
For such SC I am running the report BBP_ALERT_SB_NOTTRANSFERED manually which puts the SC in I1112 Error in Transmission Status and later I can trigger the SC creation from the alert monitor.
For POs created in this manner the PO is created in Held Status without any line items, is this normal?
I have two questions which I want to understand, how is the automatic po creation from SC setup, is there any customizing involved for the po creation from SC to happen automatically?
What else should I check to find the reason why the the SC was stuck in I1111 status and PO was not created?

You need to configure the Purchasing group and this will take care of automatic transfer of Doc to sourcing cockpit. Make sure you also maintain the customization for sourcing always carried out for Prod categories.
Regards
Saurabh

Automatic TO creation for delivery

Dear Experts ,
We are facing a problem with Automatic TO creation for delivery only in some storage types ( not all the types , some types are working fine )
The problem happened after we applied a user exit for a specific picking strategy , but even after we have cancelled that user exit still problem remained.
We have checked the following settings, and everything seems fine:
1-Warehouse management - Activities u2013 transfers u2013 define Mvt type
2-Warehouse management u2013 interfaces- Automatic TO creation
Looking for your help in this issue
Thanks ,
Malik

Hi Malik,
You mentioned that you have previously implemented the picking user-exit and removed it later. Did you enter the correct picking strategy for the effected storage types after removing the user-exit? This could be one reason.
What happens when you try to create the TO manually?
Regards,
Osman

Short pick automatic WT creation issue using Wave process

Similar Messages

Maybe you are looking for