Re: Error while making a Process order in MTO scenario

Hi All,
I am having a secnario, where I am using MTO scenario. I want that the sales order should trigger the process order.The components in the BOM for the FG material .
1. Raw material: procured from outside: Stock & value relevent.
2. This one is non valuated one :procured from outside: Stock & Non-value relevent.
Now when I create a sales order, I can see a plan order in the MD04 scree for this FG . But on drilling down this plan order I can only create the PR for the 1st component only ,for the second component I cant create anything.
The second item should be non valuated & stock relevent.
Please help me in this regards,
Vivek

I have taken help from some other threads to resolve this issue.

Similar Messages

Error while creating a process order

Dear Guru's
While creating a process order ,i am facing an error.
"Unable to create batch. Storage location BPSS is invalid for material 112100050
Message no. 40116".
How to assign specific storage loaction to that particular material.I have assigned in material master "work scheduling tab",But it was throwing an error while doing process order.Pls help me to solve this problem.
Thanks in advance,
Rgds,
cherukuri

Hi Cherukuri
Are u using special procurement key "80"? It seems that storage location is not mentioned for the header material in the production plant.
Maintain this using T Code MMSC. It will solve ur issue
Rgds

Error while releasing the Process order

while releasing the Process order i am getting the follwing error message
Message no. CO118 Release of order not possible
Cna you Please any body explain me detail of thi error ie where the error lies.
Thanks

Hi,
In Process Order Header Screen Go to ---> Log ---> On Release.Here you will find the detail error behind this problem.Go though it .Resolve it and then try to release the Process Order, and if required get back to us.
Suppose reason may be,
- Missing part
- Missing Capacity
- Batch Determination is required to perform.
- Any User Exit (Other then std. SAP)
Regards,
Dhaval

Error while saving the process order

Hi All,
I changed the quantities of the components and trying to save the process order. But I'm getting a message " "PLEASE REEXPLODE BOM, SINCE THE PROCESS ORDER COMPONENTS HAVE CHANGE". What would be the reason? It is not happening to all the users. Some users can able to save after changing the qty. Some users can't?
Regards,
Sureshbabu G.

Hi,
"PLEASE REEXPLODE BOM, SINCE THE PROCESS ORDER COMPONENTS HAVE CHANGE"
I think it is your Develpment and not from SAP Standard One.So it is difficult to trace out the cause, better will be contact your devlopment team to trace out the reason.
Regards,
Dhaval

Errors while making a purchase order in Adventure Builder 1.0.4

Hi,
I instaled J2EE 1.4 SDK (linux) : j2eesdk-1_4_03-linux.bin thar includes Sun
Java System Application Server PE 8.2 and Java Adventure Builder 1.0.4.
After the "build" and "deploy" of the Adventure, following the steps
presented in Install.html, i did one adventure purchase via browser. To
the client (browser) all goes ok, it gets the order ID, it is able to see
the adventure details and the order has the correct status (SUBMITTED TO
SUPPLIER and, afterwards, COMPLETED). But when i check the server logs
(SUNWappserver/domains/domain1/logs/server.log) i get the following errors:
[#|2006-04-11T16:48:08.051+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=33;|EJB5071:
Some remote or transactional roll back exception occurred
com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76406:
Concurrent access exception: object to update has been updated or deleted by
another transaction.
FailedObjectArray:
[com.sun.j2ee.blueprints.processmanager.manager.ejb.ManagerBean_1935673060_JDOState@15d65d]
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOConcurrentAccessException(SQLStoreManager.java:626)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeUpdate(SQLStoreManager.java:185)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.execute(SQLStoreManager.java:106)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStateManager.updatePersistent(SQLStateManager.java:893)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.flushToDataStore(PersistenceManagerImpl.java:1477)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.flushTxCache(PersistenceManagerImpl.java:1404)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:1338)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.notifyBeforeCompletion(TransactionImpl.java:1130)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.commitBefore(TransactionImpl.java:759)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.beforeCompletion(TransactionImpl.java:650)
at
com.sun.ejb.containers.ContainerSynchronization.beforeCompletion(ContainerSynchronization.java:137)
at
com.sun.jts.jta.SynchronizationImpl.before_completion(SynchronizationImpl.java:56)
at
com.sun.jts.CosTransactions.RegisteredSyncs.distributeBefore(RegisteredSyncs.java:120)
at
com.sun.jts.CosTransactions.TopCoordinator.beforeCompletion(TopCoordinator.java:2491)
at
com.sun.jts.CosTransactions.CoordinatorTerm.commit(CoordinatorTerm.java:240)
at
com.sun.jts.CosTransactions.TerminatorImpl.commit(TerminatorImpl.java:211)
at com.sun.jts.CosTransactions.CurrentImpl.commit(CurrentImpl.java:585)
at
com.sun.jts.jta.TransactionManagerImpl.commit(TransactionManagerImpl.java:273)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.commit(J2EETransactionManagerImpl.java:947)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:362)
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2732)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2521)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1042)
at
com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:46)
at
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:105)
at $Proxy92.afterDelivery(Unknown Source)
at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:242)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:45)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
|#]
[#|2006-04-11T16:48:08.067+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=33;|MDB00037:
[OPC:WorkFlowManagerBean]: Message-driven bean invocation exception:
[javax.ejb.EJBException: Transaction aborted; nested exception is:
javax.transaction.RollbackException]|#]
[#|2006-04-11T16:48:08.067+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=33;|javax.ejb.EJBException
javax.ejb.EJBException: Transaction aborted; nested exception is:
javax.transaction.RollbackException
javax.transaction.RollbackException
at
com.sun.jts.jta.TransactionManagerImpl.commit(TransactionManagerImpl.java:275)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.commit(J2EETransactionManagerImpl.java:947)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:362)
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2732)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2521)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1042)
at
com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:46)
at
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:105)
at $Proxy92.afterDelivery(Unknown Source)
at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:242)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:45)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
javax.ejb.EJBException: Transaction aborted; nested exception is:
javax.transaction.RollbackException
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2737)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2521)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1042)
at
com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:46)
at
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:105)
at $Proxy92.afterDelivery(Unknown Source)
at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:242)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:45)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
|#]
[#|2006-04-11T16:48:08.091+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=33;|EJB5071:
Some remote or transactional roll back exception occurred
com.sun.jdo.api.persistence.support.JDODataStoreException: JDO76406:
Concurrent access exception: object to update has been updated or deleted by
another transaction.
FailedObjectArray:
[com.sun.j2ee.blueprints.processmanager.manager.ejb.ManagerBean_1935673060_JDOState@19a7420]
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.throwJDOConcurrentAccessException(SQLStoreManager.java:626)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.executeUpdate(SQLStoreManager.java:185)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.execute(SQLStoreManager.java:106)
at
com.sun.jdo.spi.persistence.support.sqlstore.SQLStateManager.updatePersistent(SQLStateManager.java:893)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.flushToDataStore(PersistenceManagerImpl.java:1477)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.flushTxCache(PersistenceManagerImpl.java:1404)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.beforeCompletion(PersistenceManagerImpl.java:1338)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.notifyBeforeCompletion(TransactionImpl.java:1130)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.commitBefore(TransactionImpl.java:759)
at
com.sun.jdo.spi.persistence.support.sqlstore.impl.TransactionImpl.beforeCompletion(TransactionImpl.java:650)
at
com.sun.ejb.containers.ContainerSynchronization.beforeCompletion(ContainerSynchronization.java:137)
at
com.sun.jts.jta.SynchronizationImpl.before_completion(SynchronizationImpl.java:56)
at
com.sun.jts.CosTransactions.RegisteredSyncs.distributeBefore(RegisteredSyncs.java:120)
at
com.sun.jts.CosTransactions.TopCoordinator.beforeCompletion(TopCoordinator.java:2491)
at
com.sun.jts.CosTransactions.CoordinatorTerm.commit(CoordinatorTerm.java:240)
at
com.sun.jts.CosTransactions.TerminatorImpl.commit(TerminatorImpl.java:211)
at com.sun.jts.CosTransactions.CurrentImpl.commit(CurrentImpl.java:585)
at
com.sun.jts.jta.TransactionManagerImpl.commit(TransactionManagerImpl.java:273)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.commit(J2EETransactionManagerImpl.java:947)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:362)
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2732)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2521)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1042)
at
com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:46)
at
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:105)
at $Proxy92.afterDelivery(Unknown Source)
at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:242)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:45)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
|#]
[#|2006-04-11T16:48:08.096+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=33;|MDB00037:
[OPC:WorkFlowManagerBean]: Message-driven bean invocation exception:
[javax.ejb.EJBException: Transaction aborted; nested exception is:
javax.transaction.RollbackException]|#]
[#|2006-04-11T16:48:08.096+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=33;|javax.ejb.EJBException
javax.ejb.EJBException: Transaction aborted; nested exception is:
javax.transaction.RollbackException
javax.transaction.RollbackException
at
com.sun.jts.jta.TransactionManagerImpl.commit(TransactionManagerImpl.java:275)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.commit(J2EETransactionManagerImpl.java:947)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:362)
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2732)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2521)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1042)
at
com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:46)
at
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:105)
at $Proxy92.afterDelivery(Unknown Source)
at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:242)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:45)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
javax.ejb.EJBException: Transaction aborted; nested exception is:
javax.transaction.RollbackException
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2737)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2521)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1042)
at
com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:46)
at
com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:105)
at $Proxy92.afterDelivery(Unknown Source)
at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:242)
at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:45)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
|#]
[#|2006-04-11T16:48:12.449+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=23;|Initializaing
OtMessageHandler|#]
[#|2006-04-11T16:48:12.452+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=23;|
Initializaing OtMessageHandler|#]
[#|2006-04-11T16:48:12.452+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=23;|
OtMessageHandler:[ns0:getOrderDetails: null]|#]
[#|2006-04-11T16:48:12.580+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=23;|
OtMessageHandler: handleResponse|#]
[#|2006-04-11T16:50:08.045+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=33;|JTS5031:
Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed:
Maybe] on Resource [commit] operation.|#]
[#|2006-04-11T16:50:08.046+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=33;|MDB00037:
[OPC:WorkFlowManagerBean]: Message-driven bean invocation exception:
[javax.ejb.EJBException: Unable to complete container-managed transaction.;
nested exception is: javax.transaction.SystemException:
org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid:
0x0 minor code: 0 completed: Maybe] on Resource [commit] operation. vmcid:
0x0 minor code: 0 completed: No]|#]
[#|2006-04-11T16:50:08.046+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=33;|javax.ejb.EJBException
javax.ejb.EJBException: Unable to complete container-managed transaction.;
nested exception is: javax.transaction.SystemException:
org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid:
0x0 minor code: 0 completed: Maybe] on Resource [commit] operation. vmcid:
0x0 minor code: 0 completed: No
javax.transaction.SystemException: org.omg.CORBA.INTERNAL: JTS5031:
Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed:
Maybe] on Resource [commit] operation. vmcid: 0x0 minor code: 0 completed:
No
at
com.sun.jts.jta.TransactionManagerImpl.commit(TransactionManagerImpl.java:285)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.commit(J2EETransactionManagerImpl.java:947)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:362)
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2732)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2535)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.callEJBTimeout(MessageBeanContainer.java:431)
at
com.sun.ejb.containers.EJBTimerService.deliverTimeout(EJBTimerService.java:1349)
at
com.sun.ejb.containers.EJBTimerService.access$100(EJBTimerService.java:66)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.run(EJBTimerService.java:1897)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.service(EJBTimerService.java:1893)
at com.sun.ejb.containers.util.WorkAdapter.doWork(WorkAdapter.java:44)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
javax.ejb.EJBException: Unable to complete container-managed transaction.;
nested exception is: javax.transaction.SystemException:
org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid:
0x0 minor code: 0 completed: Maybe] on Resource [commit] operation. vmcid:
0x0 minor code: 0 completed: No
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2742)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2535)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.callEJBTimeout(MessageBeanContainer.java:431)
at
com.sun.ejb.containers.EJBTimerService.deliverTimeout(EJBTimerService.java:1349)
at
com.sun.ejb.containers.EJBTimerService.access$100(EJBTimerService.java:66)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.run(EJBTimerService.java:1897)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.service(EJBTimerService.java:1893)
at com.sun.ejb.containers.util.WorkAdapter.doWork(WorkAdapter.java:44)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
|#]
[#|2006-04-11T16:50:13.059+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=34;|JTS5031:
Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed:
Maybe] on Resource [commit] operation.|#]
[#|2006-04-11T16:50:13.061+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=34;|MDB00037:
[OPC:WorkFlowManagerBean]: Message-driven bean invocation exception:
[javax.ejb.EJBException: Unable to complete container-managed transaction.;
nested exception is: javax.transaction.SystemException:
org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid:
0x0 minor code: 0 completed: Maybe] on Resource [commit] operation. vmcid:
0x0 minor code: 0 completed: No]|#]
[#|2006-04-11T16:50:13.061+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb.mdb|_ThreadID=34;|javax.ejb.EJBException
javax.ejb.EJBException: Unable to complete container-managed transaction.;
nested exception is: javax.transaction.SystemException:
org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid:
0x0 minor code: 0 completed: Maybe] on Resource [commit] operation. vmcid:
0x0 minor code: 0 completed: No
javax.transaction.SystemException: org.omg.CORBA.INTERNAL: JTS5031:
Exception [org.omg.CORBA.INTERNAL: vmcid: 0x0 minor code: 0 completed:
Maybe] on Resource [commit] operation. vmcid: 0x0 minor code: 0 completed:
No
at
com.sun.jts.jta.TransactionManagerImpl.commit(TransactionManagerImpl.java:285)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.commit(J2EETransactionManagerImpl.java:947)
at
com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:362)
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2732)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2535)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.callEJBTimeout(MessageBeanContainer.java:431)
at
com.sun.ejb.containers.EJBTimerService.deliverTimeout(EJBTimerService.java:1349)
at
com.sun.ejb.containers.EJBTimerService.access$100(EJBTimerService.java:66)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.run(EJBTimerService.java:1897)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.service(EJBTimerService.java:1893)
at com.sun.ejb.containers.util.WorkAdapter.doWork(WorkAdapter.java:44)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
javax.ejb.EJBException: Unable to complete container-managed transaction.;
nested exception is: javax.transaction.SystemException:
org.omg.CORBA.INTERNAL: JTS5031: Exception [org.omg.CORBA.INTERNAL: vmcid:
0x0 minor code: 0 completed: Maybe] on Resource [commit] operation. vmcid:
0x0 minor code: 0 completed: No
at
com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:2742)
at
com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:2535)
at
com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1071)
at
com.sun.ejb.containers.MessageBeanContainer.callEJBTimeout(MessageBeanContainer.java:431)
at
com.sun.ejb.containers.EJBTimerService.deliverTimeout(EJBTimerService.java:1349)
at
com.sun.ejb.containers.EJBTimerService.access$100(EJBTimerService.java:66)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.run(EJBTimerService.java:1897)
at
com.sun.ejb.containers.EJBTimerService$TaskExpiredWork.service(EJBTimerService.java:1893)
at com.sun.ejb.containers.util.WorkAdapter.doWork(WorkAdapter.java:44)
at
com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(Unknown
Source)
|#]
[#|2006-04-11T16:50:13.062+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=34;|EJB5119:Expunging
timer ['4@@1144682418760@@server@@domain1' 'TimedObject =
WorkFlowManagerBean' 'Application = OPC' 'BEING_DELIVERED' 'PERIODIC'
'Container ID = 75023570086854669' 'Tue Apr 11 16:49:08 WEST 2006' '60000' ]
after [2] failed deliveries|#]
So, when i make hundreds of requests i have an obvious problem - a gigantic
log! I did a little benchmark using 10 clients making burst requests and
after a minute or so the Application Server simply stops replying to
requests due to the gigantic number of errors.
Do you have any suggestion of what the problem may be? I already tried the
Windows version and the same thing happens.
thank you in advance,
Jo�o Bento

Could you please run your application again, enabling the logging of the SQL statements. To enable, add the following to domain.xml:
<log-service alarms="false" file="${com.sun.aas.instanceRoot}/logs/server.log" log-rotation-limit-in-bytes="2000000" log-rotation-timelimit-in-minutes="0" log-to-console="false" retain-error-statistics-for-hours="5" use-system-logging="false">
<module-log-levels admin="INFO" classloader="INFO" cmp="INFO" cmp-container="INFO" configuration="INFO" connector="INFO" corba="INFO" deployment="INFO" ejb-container="INFO" group-management-service="INFO" javamail="INFO" jaxr="INFO" jaxrpc="INFO" jdo="INFO" jms="INFO" jta="INFO" jts="INFO" management-event="INFO" mdb-container="INFO" naming="INFO" node-agent="INFO" resource-adapter="INFO" root="INFO" saaj="INFO" security="INFO" self-management="INFO" server="INFO" synchronization="INFO" util="INFO" verifier="INFO" web-container="INFO">
<property name="javax.enterprise.resource.jdo.sqlstore.sql" value="FINEST"/>
</module-log-levels>
</log-service>

Error in creation of Process order

Dear Expert
while creating a process order i am getting 2 errors no valid task list for key date and lot size
No task list with in validity period of production version , how to resolve these error
Regards

Dear Usmfarhan,
Check your validity in your routing and BOM , and also check the lot sizes are matched or not in these two master data, in C223 check the production version you will get the error if it does not matches, check and revert back.
Regards,
Karad D D

Syntax error while creating a standard order

Hi All,
I created a projet in CMOD and than added the enhancement V45A0002.The components shown as EXIT_SAPMV45A_002(Predefined sold to party when making the standard order),i double click on the exit and entered into the function module.After that i double clicked on the include ZXVVZU04 and entered in and wrote E_KUNNR=100171
While activating i got error msg 'The last statement is not complete (period missing)." & i have saved inspite the error .After that i tried to create a order and program terminated error came after entering sold to party no. in sales order
so now i have deactivated the project which i created in CMOD & deleted it aswell,than also i am getting the syntax error while making the order thru VA01.I want to come out of this please.
I would be great ful if somebody helps me *** out of this syntax error.
Thanks
Rishi

Hi Rishi
As you are getting message that "The last statement is not complete (period missing)", check in your assigned project in CMOD the last statement , what is the last statement maintained in that project
Secondly also check the closing period and the current period. as it is giving in the message that "The last statement is not complete (period missing)".So check the current period and check the period maintained in the CMOD
It would be better if you take ABAP'ers help . So post in ABAP forum
Regards
Srinath

Fiscal Year Not allowed while creating the Process order (COR1)

Hi Friends,
My Indian client is following the Fiscal year of 2011 for the period of April 2010 to March 2011). We have gone live one month before. But now the problem we are facing is while creating the process order (T.Code COR1) system gives the error message "Fiscal year 2010 is not allowed".
The Diagnosis shows as below
Fiscal year 2010 is not allowed
Message no. F5568
Diagnosis
The fiscal year entered (2010) is different from the fiscal year derived from the posting date and fiscal year variant (2011).
System Response
Error.
Procedure
Correct the fiscal year entered.
I have Checked the Controlling area version. Fiscal Year 2011 starts from 01.04.2010. This issue is only at the time of Process oder creation and not in other module like FI, MM, SD, PS, QM and PM. I have checked with V3 Variant also and there is no problem with that.
Can any one help me where the setting is missing or what whould be the probable reason for this issue.
Regards,
Deva

Hi Prakash,
Thank you for your reply. I have checked the MMPV and MMRV set up and that is fine with fiscal year 2011. We are also processed lot many Material receipts for the fiscal year 2011. I have checked with OB52 for finace it is opened for the entire year of 2011 from 2009 for all periods.
We are facing only when we try to create the process order. When we enter the starte date as 24.11.2010 the derived period shows as fiscal year 2011. But entered fiscal year shows as 2010. We are not entering any other dates in the process order.
Is there any other probablity the date is picking from any Production related set ups??
The costing version fiscal year 2011 starts from 01.04.2010. So no problem with Controlling area. I have Checked the Factory calendar. The calendar starts from 01.01.2010 to 31.12.2010 for the year 2010.
Is there any other possibility of the missing settings or problem in date control???
Regards,
Deva

Error while invoking a process

Hi Team,
I get the following error while invoking a process.
ALC-DSC-125-000: com.adobe.idp.dsc.registry.EndpointNotEnabledException: SOAP endpoint is not enabled for: ExtractingXML/ReadResource
at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.validateEndpoint(AbstractMes sageReceiver.java:258)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invokeCall(SoapSdkEndpoint. java:136)
at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invoke(SoapSdkEndpoint.java :81)
at sun.reflect.GeneratedMethodAccessor755.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper. java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.adobe.idp.dsc.provider.impl.soap.axis.InvocationFilter.doFilter(InvocationFilter.java :43)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at com.adobe.idp.um.auth.filter.CSRFFilter.doFilter(CSRFFilter.java:41)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC ontext.java:3496)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2 180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Can anyone please help me with this error.

I checked my server (which has all the default Adobe services) and the only service I have that comes close is:
the Repository service's "Read Resource Content" operation. In the list that comes up as RepositoryService.
The Barcode's Extract to XML service. In the list that comes up as BarcodedFormsService
Neither of these is an exact match to the error. Is your process calling a sub process you built? Does that service actually exist on the server? If you do a record/playback (in workbench) on which step does the process fail?
If you look through the entire list of SOAP services (in Adminui) are any of them disabled?

Error while saving the Sales Order

Hi experts,
i am getting a runtime error while saving a sales order stating: SAPSQL_EMPTY_TABNAME. It says the field T681-KOTAB could be empty. I would give in more inputs. Someone plz help.
Thanks.

I would expect that KOTN521 would be a Database table defined in the ABAP Dictionary that relates to the condition implemented in 521 for the usage specified in that record.
You should be able to go into the info system, SE84, and search under ABAP Dictionary / Database Tables to see what KOTN521 is.
Also, since the only Keys to T681 are KVEWE and KOTABNR, and there are two KOTABNR entries with a value of 521, then there must be two different usages (KVEWE) associated with that table.
If you see what they are, you can check to see what the usages represent. Based on a lookup, it appears that a usage of N is for Free Goods, A is for Pricing etc. In our system, we only have A entries.
What are the usages for the 521 entries? Do they relate to Free Goods/Pricing???
Does the table KOTN521 exist in the ABAP Dictionary?
Answering these questions may get you closer to the answer.
Can you compare the values in these entries to what you have in different SIDs?
Is this problem happening in Production, or is it still in a development or Quality Assurance client?
If it is still in development or Q, then it may be that a recent customization change was made.
Compare the entries across your systems, if possible.
Good luck
Brian

RunTime Error while saving a Sales Order

Hi All,
When i am saving a Sales Order, the system is throwing a Runtime Error.
The ABAP Code in the Runtime Error screen as follows.
          select * from (t681-kotab) appending table <cond_tab>
                 up to 1 rows
                 where kappl = se_kappl
                 and   kschl = se_kschl
                 and   datbi >= se_date
                 and   datab <= se_date
                 and   (coding_tab).
Till these days, there was no such error while saving a Sales Order.
How to resolve this issue?
Regards
Pavan

Hi,
The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
select * from (t681-kotab) appending table <cond_tab>
up to 1 rows
where kappl = se_kappl
and kschl = se_kschl
and datbi >= se_date
and datab <= se_date
and (coding_tab).
The reason could be is someone has screwed up the entries in T681 table. Check that out.
Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
Let me know if you are still stuck up.
If you can send me the ST22 dump of the run time error, i might be able to help you more on this.
Hope this helps.
Thanks,
Balaji

Error while invoking BPEL Process through HTML Page

Hi ,
I have created a HTML Page to invoke BPEL synchronous process .
HTML Page contains :
<html>
<head>
<title>Untitled Document</title>
<h1>Add Macro Task Input Form </h1>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="cyan" text="#000000">
<form name="form1" method="get" action="/httpbinding/default/AddMacroSync/process">
EmployeeId :
<input type="text" name="EmployeeId" ><br>
<br>
TaskName :
<input type="text" name="MacroTaskName" >
<button
id="identifier"
class="dialog"
label="OK"
accesskey="t"/>
<br>
</form>
</body>
</html>
I am able to invoke my BPEL Process named as " AddMacroSync" .
It also creating instance for this BPEL Process .
But when I go BPEL Console and check my instance , it is always faulted .
I am providing two inputs : Employee Id and Taskname through HTML Page .
These inputs got assigned to their respective output variables .
But when I click on audit link ..it shows error while invoking the Process .
It Show error :
when invoking endpointAddress 'http://152.69.248.232:8990/AddMacroTask-AddMacroTask-context-root/AddMacroTaskWebService', [java.lang.NumberFormatException]
But this end point address is working when I put this address in URL .
Please someone help me how to solve this problem .
Thanks
Prashant Dwivedi
Message was edited by:
Prashant Dwivedi

Hi Clemens ,
I changed My HTML ...Now it looks like as :
<html>
<head>
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="application/x-www-form-urlencoded; charset=iso-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<form name="form1" method="post" action="/httpbinding/default/AddMacroSync">
<input type="hidden" name="msg_part" value="payload">
<input type="hidden" name="namespace" value="http://xmlns.oracle.com/AddMacroSync">
EmployeeId:
<input type="text" name="EmployeeId">
TaskName :
<input type="text" name="TaskName">
<input type="submit" name="Submit" value="Submit">
</form>
</body>
</html>
After this when I try to incoke my BPEL Process through this HTML :
I am gettign following error :
500 Internal Server Error
java.lang.IllegalStateException: IOException: Premature end of POST data
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.EvermindHttpServletRequest.getParameter(EvermindHttpServletRequest.java:2452)
     at com.collaxa.cube.ws.http.HttpBindingServlet.checkSecurity(HttpBindingServlet.java:281)
     at com.collaxa.cube.ws.http.HttpBindingServlet.doPost(HttpBindingServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
     at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.0.2)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
     at java.lang.Thread.run(Thread.java:534)

Serial number error while creating the production order

Hello frds,
I am getting the following error while creating the production order.
"Item 000000 requires exactly 100 serial numbers for the asset".
If i give 100 serial numbers in the order, the error is solved. But i do not want to assign 100 serial numbers, i want to assign only 2 numbers.
I have tried using the new serial number profile also, but it is giving same error.
Kindly guide.
Regards,
Narendra Bora

Dear Narendra
Select the serial number profile and go to serialization procedure and set the ser. usage status 02 - Optional as below.
Procd Procedure description Ser.Usage
PPRL PP order release 02
since the serail number creation is optional for order relase this will allow you to relase with out error and with serail number assigned in partial.
Regards
Soundar

Error while creating the sales order with billing reference

hi alll
i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
cheers
shalsa007........

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

Error while running the process chain

Hi, I am getting following error while running the process chain.
"Lock NOT set for: Deleting the data completely from a data target"
Please suggest.
amit

hi,
This is due to a lock on the objects which is being used by ur load.
Even if master data used by this would be in a lock by an attribute change run. wait till that attribute change run finishes and then repeat.
If this target itself is locked by someother process like rollup , compression , this error would appear. In this case also repeat the step after those locking process finish.
some general locks during loading:
Sometimes parallel processing in DTP might lead to this, its better set the DTP and infopackage in serial processing. In this case change the settings and then repeat the process.
There is a specific case in which the Serial DTP gets locked by itself, in this case repeat it untill it succeeds.
You can identify the above scenario as below. This is applicable only if the DTPs processing mode is serial.
if u see in SM 37 this load would have three DTP processes running.
it should have only two.
In this case cancel the process and repeat it untill u get it right.
hope this helps u
regard,
ranjith
Edited by: Ranjith Kumar Murugesan on Sep 12, 2008 10:44 AM
Edited by: Ranjith Kumar Murugesan on Sep 12, 2008 10:46 AM

Re: Error while making a Process order in MTO scenario

Similar Messages

Maybe you are looking for