Error while save framework purchase order.
dear all
i am working SAP R/3 4.7 ides while creating framework po, i input all the data field correctly , but when i am going to save the purchase order, it given the error Massages " Indicator for invoice receipt used not allowed
Message no. MEPO026"
then i tell me how i save the po. i request to all the experts
Dear,
What account assignment you are using?
Use account assignment category as K and item category as B Also do not enter material ID.
Now try.
Regards
Utsav
Similar Messages
-
Error while creating a Purchase Order
Hi Friends,
I am new to SAP MM. I am getting a problem while creating a purchase order. I created Purchase Info Record, Source List, but while creating Purchase Order, price is not picking from the purchase order. I am getting an error i.e. Net Value must be greater than 0. I checked all the settings, but getting same error.
Could you please solve thisHi,
Give some price at the item level for the item in the PO.
And check the Pricing procedure in PO
Hope it helps you.
Thanks. -
WebDynpro Error while creating a Purchase Order in SRM 7.0
Hello Friends,
I need help.
We are on SRM 7.0 with support pack 8.0 and we are getting the below error wile clicking on Shopping cart or Purchase Order link in Portal.
Any idea on how to resolve this error.
Thanks
Jyothi.
http://sapsrm.erpcx.com:8000/sap/bc/webdynpro/sapsrm/wda_l_fpm_oif/
ASSERTION_FAILED
The ASSERT condition was violated.
Method: ADD_EVENT_TO_QUEUE of program CL_FPM========================CP
Method: IF_FPM~RAISE_EVENT of program CL_FPM========================CP
Method: SET_CREATE_BUTTON_ACTIVE of program /1BCWDY/0FJM4718F184UKVHA34J==CP
Method: IF_COMPONENTCONTROLLER~SET_CREATE_BUTTON_ACTIVE of program /1BCWDY/0FJM4718F184UKVHA34J==CP
Method: RESET_SCREEN of program /1BCWDY/0FJM4718F184UKVHA34J==CP
Method: IF_V_PRSEL~RESET_SCREEN of program /1BCWDY/0FJM4718F184UKVHA34J==CP
Method: WDDOMODIFYVIEW of program /1BCWDY/0FJM4718F184UKVHA34J==CP
Method: IF_WDR_VIEW_DELEGATE~WD_DO_MODIFY_VIEW of program /1BCWDY/0FJM4718F184UKVHA34J==CP
Method: DO_MODIFY_VIEW of program CL_WDR_DELEGATING_VIEW========CP
Method: MODIFY_VIEW of program CL_WDR_VIEW===================CPHere is what I see:
Error analysis |
The following checkpoint group was used: "No checkpoint group specified"
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"ASSERTION_FAILED" " "
"CL_FPM========================CP" or "CL_FPM========================CM004"
"ADD_EVENT_TO_QUEUE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
| -
Error, While updating a purchase order
Hi All,
I am getting following error massage while updating a existing PO:
" Cannot Insert the value null into column docentry, Table db name.dbo. POR4; column does not allow nulls. Insert Fail."
We have upto 886 items in the PO and the summary type is " No summary". Even when i treid to change the summary type to "By items", the system is till throwing the same error message. Please let me knwo the cause of this error and how to rectify this??
Thanks in advance,
JosephDear Joseph,
Please try the followings in a testing database and check the results:
1. if you give full authorisation to this specific user, will the error persist when adding the rows?
2. if adding new rows at the end of the purchase order will it be successful?
3. if you duplicate the sales order then add the new rows, will the error occur?
4. will the error persist if you upgrade the client to the latest patch?
5. please check the note 1139134 and 1249795.
Regards,
Varun
SAP Business One Forum Team -
Error while uploading Complex Purchase Order through POXPOPDOI open interfa
Dear Gurus,
I am trying to upload Complex Purchase Orders in Oracle EBS R 12.1.2
The PO_INTERFACE_ERRORS table is populated with the following message:
STYLE_ID Error: Style (STYLE_ID = 103) with progress payments is not supported.
We have checked each and every setup. It is OK.
We tried to enter the complex POs from Front end screen, there is no issue. But I dont know why this error comes everytime we try to upload the POs throught the interface
We ran the Diagnostic Test. It is also OK.
Cannot figure out what is the issue. Please help.
RegardsHi
I think some basis related configuartions to be done
Try like this and inform me
A cyclic job runs, which processes the messages seen in the SOST queue.
Are you sure it's not the frequency of the cyclic job, rather than the
number of messages in the queue, that you are observing? In messages
that are queued and before the cyclic job runs, "wait for comm. service"
is the normal status.
If you mean that there are always 4 items queued in SOST regardless of
the cyclic send job, then I have no ideas. I would have thought there
was no way to do that.
when the send job runs it just never
picks them up & sends them, while it picks up many others. The send job
is somehow blind to these; no error message occurs. In this case, I
'delete' them from the queue (in SOST) and then 'undelete' (drop down
menu -> /Go to /Deleted Items) them and then re-queue them. THEN they
actually get picked up & sent when the next cyclic send job executes.
Regards
Pavan -
Budget exceeded error while deleting CAPEX Purchase order
Hello All,
We've created purchase order with WBS element for some materials & account assgn P. This however needs to now be deleted as there has been mistake in th PO.
But while trying to delete the PO the system gives an error message " WBS element XXXX.XXX.. budget exceeded"
I've tried deleting the PR first and then the PO which works fine, BUT we are not able to create another PO as the error of Budget exceeded is seen here as well.
Please advice on how to delete the PO.
Regards,
ManojRHi,
Please read note 178837 which gives information on how to check the real assigned value.
I would like you to run report ZKAOIDE0 from Note 100409 to remove
the data which is not linked to a valid purchase order or requisition.
After running the report then run transaction CJEN to reconstruct the
project. Then run report RKANBU01 after completing the reconstruction.
The problem is probably that a purchase order has the deletion indicator set but it still appears in table COOI.
I hope this helps!.
Best Regards,
Arminda Jack -
Error while creation of PUrchase order by using BAPI.
Hi All,
We are creating a purchase order thru BAPI ("BAPI_POEC_CREATE") and we are passing the following parameters ( I_PO_HEADER , I_PO_ITEMS , I_PO_ACCASS , I_PO_PARTNER and I_PO_ORGDATA) to the bapi and after processing we are getting the following error and Abend messages.
Messages:
1) Enter at least one item or one limit ( we have added line items in I_PO_ITEMS structure).
2) Incorrect interface data for set 78 in method C.
3) Interface data contains errors.
Can anyone help me in fixing these errors inorder to proceed further.
Regards
DharmarajuHi there,
Did you manage to sort this problem ?
If not let me know
I am using the same and know how to overcome
Thanks
Turlock
T -
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 BentoCould 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> -
Get "Error in Net Price Calculation" error while creating a Purchase Order
I am getting a error when i try to create a PO. Says "Error in Net Price Calculation item 00010(Please correct)"
I have defined conditon records with the price for the material and have also created info record.However the price in the info record (including currency i.e USDN is different than the one defined in the conditon records currency is USD).
However the price is different from the one defined in info record and in material master.
Where is it picking the price from also is there any way to edit the price in material master or info record ?
Also when i view the condition records by using Tcode MEK1 i get the following error
"Access Pricing Purchasing Z00q 20 contains no fields"
I know Z001 is the access sequence
Can any one tell me wht is this error message about ?
Edited by: Dspsac on Jan 29, 2008 4:31 AMhow can u maintain the condition record as well as info record for a vendor -material in the same time frame
it is not possibe
as info record is also 1 of the condition table
if u have maintained the info record then system is going to fetch the data from there but point top notice is it depends on the validity of record
system fetch the price from info record
and the currency used is fom vendor master -
While creating the purchase order
Hi all,
While creating the purchase order I am getting error like No account assignment to customer order (Not Active in co area 1100, Year 2007)
please help me out from this problem
Thanks and regards,
Sreekanth LokarayHi Nazim,
I got the solution by doing the maintain controlling area I activate the sales order.
and In t.code vkoa I have given the condition type for sales organization.
Thanks and regards,
Sreekanth.L -
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
PavanHi,
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 -
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 BoraDear 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 saving the Production Order
Dear Experts
Pls let me know why am getting the below error while saving the production order after release..
PSFC_STD_LAYOUT does not exist
Message no. SSFCOMPOSER004Dear,
Please check have you assigned the scheduling profile in work scheduling view of materail master?
Then go to OPKP check the same scheduling profile where you have activited the On realese execute printing remove this tick mark and then try with new order.
Or you can do the configuration in Tocde :OPK8 here assign the PSFC_STD_LAYOUT in forum.
Regards,
R.Brahmankar
Maybe you are looking for
-
Hi, I have an Imac (27", mid-2011) and I just bought a 4Gb Ram memory to install in one of the free slots, I installed and turn on my computer, the computer recognized the new memory but when I'm going to open a program (and even when I leave the com
-
Importing LCA applications issues
Hello everybody. In the last few days I've been working with the LCES2 Linux virtual appliance made available by Adobe and I tried to import a fairly complex application developed with LCES 8.2.1. I stumbled across a few issues I'd like to share with
-
Can I backup internal HD to external keeping a large file stored in ext.?
I have a file of over 100GB stored in the external and I need to backup my iMac's internal for safety but I'm new to this so don't want to end up deleting it... Also App suggested to do it? 500GB internal 1.5 TB external Thanks!
-
Why is it that the sort order on my Music Library Playlists are not replicated on the Apple TV? (They are in different order) I want them in "Date Added" order. Is there a way to get the play list on the Apple TV to sort to this?
-
http://lh6.ggpht.com/_rhCtHYLiamQ/S5EUBvp6DfI/AAAAAAABXtY/SnEtDnGNKSc/s800/01_example.png Sorry, but the ! doesn't seem to be working correctly, so you'll have to click through. The first column is from a dimension, the following 2 are measures from