Transaction is not active

          Hi,
          We have a stateless bean defined with 'Bean' transaction type. We open a transaction
          in this bean and then call a stateful bean located on a different application
          server (container). This stateful bean is defined with 'Container' transaction
          type with trans attribute 'not supported'.
          We also tried to define the stateful bean with a transaction type 'Bean' and trans
          attribute 'not supported' and still received the same error as written below:
          We receive an error in the stateless bean 'transaction is not active' from the
          stateful bean. This error only happends after the 3rd call to the stateful bean.
          The stateful bean does not open any transaction.
          

There is some further discussion about using 'Not Supported' in the
          newsgroup
          that you might find helpful (bascially, it is implementor defined).
          WLS does not start any transaction in the case of 'Not Supported'.
          If a transaction already exists, it is suspended.
          If you call another EJB that requires a transaction, you will
          get an error that indicates that a transaction is not active.
          "Tamar" <[email protected]> wrote in message
          news:3ec7a215$[email protected]..
          >
          > Hi,
          >
          > We have a stateless bean defined with 'Bean' transaction type. We open a
          transaction
          > in this bean and then call a stateful bean located on a different
          application
          > server (container). This stateful bean is defined with 'Container'
          transaction
          > type with trans attribute 'not supported'.
          > We also tried to define the stateful bean with a transaction type 'Bean'
          and trans
          > attribute 'not supported' and still received the same error as written
          below:
          > We receive an error in the stateless bean 'transaction is not active' from
          the
          > stateful bean. This error only happends after the 3rd call to the stateful
          bean.
          > The stateful bean does not open any transaction.
          

Similar Messages

  • [Urgent] Error: The transaction is not active

    Our process encounters some errors when the execution time takes longer than normal, e.g. 5mins. Any help is much appreciated.
    Process Flow:
    The flow consists of 3 process, 1 long-lived process and 2 short-lived processes, let say process A, B and C
    Long-lived process A call short-lived process B,
    and then, short-lived process B call another short-lived process C.
    There is a loop inside process B, so that process C would be called several times.
    * Both invocation policy have been tested, including "Do not wait for response" and "Wait for response".
    Problem:
    Everything work fine when the whole process is within a short-period of time. e.g. 1-2 minutes
    However, when the process takes longer, e.g. > 5mins, we got some error message in the sever log.
    Server log:
    2011-08-18 18:43:11,625 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterLocal.doRequiresNe w(com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.Transa ctionCallback) throws com.adobe.idp.dsc.DSCException, causedBy:
    java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!
    at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commit(TransactionImp le.java:223)
    at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:501)
    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:411)
    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
    at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
    at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
    at org.jboss.ejb.Container.invoke(Container.java:960)
    at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
    at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
    at $Proxy167.doRequiresNew(Unknown Source)
    at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:143)
    at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:188)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
    at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
    at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
    at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
    at com.adobe.workflow.engine.PEUtil.invokeAction(PEUtil.java:886)
    at com.adobe.workflow.engine.SynchronousBranch.handleInvokeAction(SynchronousBranch.java:510 )
    at com.adobe.workflow.engine.SynchronousBranch.execute(SynchronousBranch.java:888)
    at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBea n.java:2792)
    at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncInvokeProcessCommand(ProcessEngineBMT Bean.java:697)
    at sun.reflect.GeneratedMethodAccessor1076.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
    at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
    at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 73)
    at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77)
    at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
    at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
    at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
    at org.jboss.ejb.Container.invoke(Container.java:960)
    at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
    at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
    at $Proxy200.asyncInvokeProcessCommand(Unknown Source)
    at com.adobe.idp.workflow.dsc.service.ProcessCommandExecutorService.invokeProcess(ProcessCom mandExecutorService.java:55)
    at sun.reflect.GeneratedMethodAccessor3010.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
    at com.adobe.idp.workflow.dsc.invoker.WorkflowDSCInvoker.invoke(WorkflowDSCInvoker.java:154)
    at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.DocumentPassivationInterceptor.intercept(DocumentPassi vationInterceptor.java:53)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:357)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doSupports(Ej bTransactionCMTAdapterBean.java:227)
    at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.jboss.invocation.Invocation.performCall(Invocation.java:359)
    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:237)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:158)
    at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:169)
    at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121)
    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:378)
    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181)
    at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205)
    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:138)
    at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648)
    at org.jboss.ejb.Container.invoke(Container.java:960)
    at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430)
    at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103)
    at $Proxy167.doSupports(Unknown Source)
    at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:104)
    at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:165)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
    at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:129)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:93)
    at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:20 9)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:66)
    at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
    at com.adobe.workflow.engine.PEInvokeProcessCommand.execute(PEInvokeProcessCommand.java:126)
    at com.adobe.workflow.workadapter.WorkflowCommandExecutionUnit.execute(WorkflowCommandExecut ionUnit.java:22)
    at com.adobe.idp.dsc.workmanager.adapter.ManagedAsynchronousWorkAdapter.run(ManagedAsynchron ousWorkAdapter.java:70)
    at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
    at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
    at java.lang.Thread.run(Unknown Source)

    Hi Paul,
    Thank you for your advice.
    It seems that it is not a bug of Adobe Livecycle, but some kind of configuration problems. Since the problem does not occurs when the process implementation time is short, such as 1-3 minutes.

  • Balance sheet valuation not active (Customizing transaction OMWE)

    Hi,
    For FIFO Valuation, I have done the following SPRO setting:
    1. Activate balance sheet valuation (Trans: OMWE) - as LIFO not relevant, FIFO active.
    2. Defined LIFO/FIFO valuation levels (Trans: OMWL) - set as Plant (valuation area).
    3. Configured FIFO Valuation areas for year 2008.
    4. Define LIFO/FIFO method (Trans: OMWP) - FIFO01 as CUR u2013 current
    5. No changes made to movements relevant to FIFO (Trans: OMW4);
    While running the MRF1, the system is throwing the following message:
    Balance sheet valuation not active (Customizing transaction OMWE)
    Message no. MY043
    Pls. help in rectifying the problem.
    Pls. note that I have already activated the LIFO/FIFO-relevant Check box while creating the Material.
    Do I need to execute MRF4 before executing MRF1?
    Regards,

    hey guys... can anyone help  me to solve this issue....

  • In SFP transaction , when i press layout buton , give me error 'Direct display for documents not activated'

    in SFP transaction;
    when i press layout buton , it give me an error.
    SOFFICEINTEGRATION020
    'Direct display for documents not activated'

    Yes i installed .
    One of our product systems , i take  this error but  another one it works correctly . 

  • JTA transaction is not present or the transaction is not in active state

    Hi,
    I am trying to execute an asynchronous bpel process. the bpel process has 5 OSB calls and is taking approximately 100 seconds for completion. The OSB calls in the BPEL are taking 90 seconds for completion. In the end of the BPEL process, after completion I get the following error:
    [2010/07/22 01:56:44] BPEL process instance "1220007" completed
    [2010/07/22 01:56:44] There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1,220,007". The reason is The execution of this instance "1220007" for process "BPELProcess1" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
    We do not want to increase the transaction-timeout properties in the server in the Transaction-manager.xml or in the orion-ejb-jar.xml since we have other projects with synchronous processes running in the same server.
    Can anybody please suggest a workaround to overcome this issue apart from increasing the transaction-timeout?

    Hi 783703,
    As Sridhar suggested for your problem you have to set transaction-time out in j2ee/home/config/transaction-manager.xml.
    If you use Idempotent as false for your partnerlinks, BPEL PM will store the status till that invoke(Proof that this invoke gets executed).
    So better to go for increasing the time instead of going for idempotent as it has some side effects.
    And coming to dehydration ....Ideally performance will be more if there are no much dehydration poitns in our process. But for some scenarios it is better to have dehydration(ex: we can know the status of the process...etc)
    Dehydration store will not get cleared after completion of the process. Here dehydration means ....it will store these dtails in tables(like Cube_instance,cube_scope...etc).
    Regards
    PavanKumar.M

  • On transaction FBL3N  report change layout and save layout icons  not activ

    Hi,
    I am working on upgrade project from 4.6C to ECC6.0. On transaction FBL3N  report change layout and save layout icons  not active; only select layout icon is active.
    Please advise how these two icons can be activated.
    saeed

    Hi,
    The object F_IT_ALV has a field, the activity ACTVT, which can
    contain four permitted values: 01, 02, 03 and 70.
    Activity 03 corresponds to the minimum authorization, which is the
    most restricted one: You can only select layouts which have
    been configured already. In particular, all of the other functions
    named above are inactive with activity 03.
    I guess that your user-id have set activity 03 for this object.
    The SAP notes 374656 and 409190 are recommended.
    So, if the values 01 and 02 are not included, then
    the user can't change and save layouts.
    For the line item display in FI the authorization
    object FI_IT_ALV has been created as an extra security check in addi-
    tion to the ALV authorization object S_ALV_LAYO.
    Please check note 374656 where you should be able to find
    relevant info about this. Also note 637554 should be helpful.
    Regards,
    Aidan

  • RFC : Transaction Program not Registered

    Hi Folks,
    We have registered the server program from the middleware onto SAP R/3 System and is successfully registered as per the logs. As a next step, we have logged into R/3 System, SM59, in the RFC destination (Type TCP/IP) after specifying the registered program, we have tested it(Connectivity test). The test is positive and connectivity is established successfully.
    The solution was working for months and suddenly connectivity is broken.
    To restore the connection, we have repeated the steps, registered the server program, tested and everything is fine.
    But when we have pushed a new message, then onwards the RFC destination shows an error. "TP is not registered", Return Code 679. That is when the first message is pushed, it is de-registering the server program and running into error. All the messages got stuck in SM58 with status 'Error when opening an RFC connection'.
    RFC trace shows
    ERVER> Caller transaction code:  (Caller Program: SAPLQOWK)
    ERVER> Called function module: ARFC_RUN_NOWAIT
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
    CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
    Transaction program not registered.
    Please let me know for any inputs.
    Thanks, Suraj

    My problem got solved. In the middleware, when TRFC connection is made, it has created a lock entry during the time, system was brought down for maintenance activity. When the system is brought up, then as the connection lock entry is available, then it deregistered the server program and not able to establish further connection.
    To resolve the issue, we have just deleted lock file and registered server program from middleware. This time the connection was established successfully and could able to restore the message flow.
    Thanks, Suraj

  • CPIC-CALL Transaction program not registered Error while creating RFC Desti

    Hi All,
    I am trying to create a new RFC Destination.
    Details I have provided are..
    1.RFC Destination Name
    2.Connection Type - TCP/IP
    3.Description
    4. Activation Type - Registered Server Program.
    5.Program Id.
    6. Gateway Host and Gateway Service.
    But When I Test the connection, I am getting the following error.
    <b>" program xyz not registered / CPIC-CALL: 'ThSAPECMINIT'# Transaction program not registered"</b>
    However I was able to create and connect RFC Destinations successfully previously.
    I am not SAP guy. Could someone help resolve this issue.
    Thanks,
    Phani

    hi Sekhar,
    I request you to please help me out in this issue. I am getting similar kind of problem. I am trying to replicate the customer from CRM to R/3 and i get a bdoc message in SMW01 that "RFC connection failed please press the save button again". When the basis team further investigated they came up with the below error..
    User: CRREMOTE (Client: 071)
    Destination: OCR (handle: 1, , )
    Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1462
    CPIC-CALL: 'ThSAPECMINIT'
    Transaction program not registered
    DEST =OCR
    HOST =%%RFCSERVER%%
    PROG =dpssrfc
    Trace file opened at 20061121 140451 EST SAP-REL 640,0,109 RFC-VER
    3 804778
    resize I/O buffer to 28000 bytes
    >>>> [2] MQ_LINK      : TCP  <ac: 3> K %%RFCSERVER%% >>> OPEN
      {45632F14-288E-0046-0000-0000A888A7AA}-
    ======> CPIC-CALL: 'ThSAPECMINIT'
    can you please tell me where can be probelm. Regarding your message, where can i get the communication channel to assign the program id.
    Awaiting your reply,
    Thanks & Regards,
    Yogesh

  • Material is not activated error in MM

    Hi,
    We'vs installed SAP IDES in our Landscape recently. Whenever I tried to create a new material using MM01 transaction code, it creates. But then when I tried to view the same in MM03 or MM02 it throws an error of the following,
    The material XXXXX does not exist or is not activated
         Message no. M3305
    I'm unable to diagonis the problem properly. Will appreciate your help.
    Thanks,
    Rajesh Manoharan

    >
    Kishore Kumar Chiluka wrote:
    > Hi
    >
    > Please get in touch with your BASIS consulatant , as the updates are not performing rightly, this seems to be asystem error.
    >
    > Thanks & Regards
    >
    > Kishore
    Thanks a lot Kishore.
    But unfortunately we don't have any Basis Guy separately. I was doubling up as Basis as well APO in my org . I'm pretty new to all these stuff. I searched in help.sap.com about this a lot, but couldn't find anything useful.
    Can you help me in identifying a solution to this problem?
    Thanks,
    Rajesh Manoharan

  • While creating SAP ISU Device category i got one error message like The material 5 does not exist or is not activated Message no. M3305

    while creating SAP ISU Device category EG01 .i got one error message like The material 5 does not exist or is not activated Message no. M3305

    I don't know EG01 transaction, but if SAP says "material 5 does not exist " then SAP is usually right.
    Can you give an evidence that material 5 exists? e.g. screenshot from  SE16 at table MARA, MARC and MAST

  • Getting "JTA transaction is not present" error while updating db table.

    Hi All,
    In one of my BPEL process, In a loop, I am updating value of database column Flag from 0 to 1. It was working fine in dev environment, but failed in Prod with below errors, Can Any one suggest on this.
    There is a system exception while performing the BPEL instance, the reason is "JTA transaction is not present or the transaction is not in active state. The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.. Please consult your administrator regarding this error. ". Please check the error log file for more infromation. Please try to use bpel fault handlers to catch the faults in your bpel process. If this is a system exception, please report this to your system administrator. Administrator could perform manual recovery of the instance from last non-idempotent activity or dehydration point.
    OPMN logs:
    <2010-05-05 01:56:49,395> <ERROR> <gemptp.collaxa.cube.engine> The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    The current JTA transaction is not present or it is not in active state when processing activity or instance "1020112-BpInv7-BpSeq14.87-2". The reason is The execution of this instance "1020112-BpInv7-BpSeq14.87-2" for process "UpdateOrderReqABCS" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
    Thanks in advance.

    I can envisage this happening only in a case where the update is taking a longer time than the value of JTA transaction timeout.
    Is this happening for all BPEL instances or some of them get thru succesfully ?
    Are you EVER updating that particular row of your table ( before/after) ?
    -Shishir

  • Bapi_Goodsmvt_Create: Material does not exist or is not activated....

    Hi all,
    I'm using .Net connector to execute BAPI from my program and I'm able to login but always get the same message when I try to execute the material transfer: <b>Material xxx does not exist or is not activated</b>.
    I'm not sure it has anything to do with the permission of my account because this is the first time our SAP admin create a "Communication" type user and we really don't know what kind of permission is good enough for BAPI_GOODSMVT_CREATE. Plus the error message does not show any thing about permission.... And same message returned if I use the dialog user.
    If I use transaction MB1B to do the transfer (with the same material) then things are ok.
    Any ideas are appreciated,
    Eric
    Message was edited by:
            Eric Nguyen

    The only thing I can think of is that when calling from .net,  you are passing the material number without its internal format.  The material number field in R/3 is an 18 character field.  If the material number is numeric, the materail number is then padded with zeros on the left.  Example, for material 12345, the internal format is 000000000000012345.  If the BAPI in question is not fomatting the material internally in the BAPI, then it must be passed this way.  CHeck how you are passing, if it is numeric and not zero filled left,  then you must write some .net code to do so.
    Regards,
    Rich Heilman

  • No externally managed transaction is currently active for this thread

    Got the following exception after updating an entity bean and call persist method. Code the given below the exception.
    Exception [TOPLINK-23010] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.TransactionException
    Exception Description: No externally managed transaction is currently active for this thread
    public Object persistEntity(Object entity) {
    em.flush();
    em.persist(entity);
    return entity;
    private void modifyUser (Iuser user, String newHandle, Hashtable userDetails) throws UnknownException, WarningException {
    if (user == null) {
    throw new WarningException (new CatalogHelper("ITOOLS_000015", "to modify a user"));
    boolean handleUpdate = false;
    if ((newHandle != null) && !newHandle.equals("^\\s*$")) {
    handleUpdate = true;
    String oldHandle = user.getUserhandle();
    if (handleUpdate && oldHandle.equalsIgnoreCase(newHandle)) {
    handleUpdate = false;
    if (!handleUpdate && (userDetails == null) || (userDetails.size() == 0)) {
    return;
    if (handleUpdate) {
    userDetails.put("userhandle", newHandle);
    IToolsUtil.validateInputData("iuser", userDetails, false);
    if (handleUpdate) {
    userDetails.remove("userhandle");
    System.out.println("handleUpdate " + handleUpdate);
    // For User admin, handle, isactive, isadmin cannot be changed.
    if (oldHandle.equals("admin")) {
    if (handleUpdate) {
    throw new WarningException (new CatalogHelper("ITOOLS_000045", "Handle"));
    String active = (String)userDetails.get("isactive");
    if ((active != null) && !active.equals("Yes")) {
    throw new WarningException (new CatalogHelper("ITOOLS_000045", "Is Active"));
    String admin = (String)userDetails.get("isadmin");
    if ((admin != null) && !admin.equals("Yes")) {
    throw new WarningException (new CatalogHelper("ITOOLS_000045", "Is Admin"));
    System.out.println("user transaction started");
    if (handleUpdate) {
    FinderMethods fm = new FinderMethods();
    try {
    fm.findByUserHandle(em, newHandle);
    throw new WarningException (new CatalogHelper("ITOOLS_000043", newHandle));
    } catch (ObjectNotFoundException onfe) {
    user.setUserhandle(newHandle);
    System.out.println("User handle modified");
    } catch (SQLException se) {
    se.printStackTrace();
    throw new UnknownException (new CatalogHelper("ITOOLS_100000", new Object[]{"modifyUser", se.getMessage()}));
    String lname = (String)userDetails.get("userlname");
    if (lname != null) {
    user.setUserlname(lname);
    String fname = (String)userDetails.get("userfname");
    if (fname != null) {
    user.setUserfname(fname);
    String email = (String)userDetails.get("useremail");
    if (email != null) {
    user.setUseremail(email);
    String passwd = (String)userDetails.get("userpasswd");
    if (passwd != null) {
    user.setUserpasswd(passwd);
    String active = (String)userDetails.get("isactive");
    if (active != null) {
    user.setIsactive(active);
    String admin = (String)userDetails.get("isadmin");
    if (admin != null) {
    user.setIsactive(admin);
    System.out.println("details are updated");
    persistEntity(user);
    System.out.println("committed");
    How to resolve this issue? I am using Jdeveloper 10.1.3.0.4 (SU4)
    regds
    -raju

    The stack trace is given below. This exception is occured at "em.flush()" method. I even tried removing em.flush() method. Even then I got the same exception.
    I tried a different way of overcome this problem. Used UserTransaction instance say "ut" before create / modify the entity bean and later comitted. In that case I am not getting any exceptions. However, commit is happening only when new instance is created, commit works, but modification of an existing instance, commit is not working. Looks like there is some serious problem with EJB 3.0 in OC4J. Basic functionality is not working.
    Stack trace when flush method is called:
    Local Exception Stack:
    Exception [TOPLINK-23010] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.TransactionException
    Exception Description: No externally managed transaction is currently active for this thread
         at oracle.toplink.exceptions.TransactionException.externalTransactionNotActive(TransactionException.java:98)
         at oracle.toplink.internal.ejb.cmp3.transaction.base.JTATransactionWrapper.checkForTransaction(JTATransactionWrapper.java:39)
         at oracle.toplink.internal.ejb.cmp3.base.EntityManagerImpl.checkForTransaction(EntityManagerImpl.java:322)
         at oracle.toplink.internal.ejb.cmp3.base.EntityManagerImpl.getActiveUnitOfWork(EntityManagerImpl.java:314)
         at oracle.toplink.internal.ejb.cmp3.base.EntityManagerImpl.flush(EntityManagerImpl.java:164)
         at com.itools.vs.model.session.AdminSessionBean.persistEntity(AdminSessionBean.java:57)
         at com.itools.vs.model.session.AdminSessionBean.createUser(AdminSessionBean.java:124)
         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:585)
         at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    Stack trace when persist method is called:
    Local Exception Stack:
    Exception [TOPLINK-23010] (Oracle TopLink - 10g Release 3 (10.1.3.0.0) (Build 060118)): oracle.toplink.exceptions.TransactionException
    Exception Description: No externally managed transaction is currently active for this thread
         at oracle.toplink.exceptions.TransactionException.externalTransactionNotActive(TransactionException.java:98)
         at oracle.toplink.internal.ejb.cmp3.transaction.base.JTATransactionWrapper.checkForTransaction(JTATransactionWrapper.java:39)
         at oracle.toplink.internal.ejb.cmp3.base.EntityManagerImpl.checkForTransaction(EntityManagerImpl.java:322)
         at oracle.toplink.internal.ejb.cmp3.base.EntityManagerImpl.getActiveUnitOfWork(EntityManagerImpl.java:314)
         at oracle.toplink.internal.ejb.cmp3.base.EntityManagerImpl.persist(EntityManagerImpl.java:74)
         at com.itools.vs.model.session.AdminSessionBean.persistEntity(AdminSessionBean.java:57)
         at com.itools.vs.model.session.AdminSessionBean.createUser(AdminSessionBean.java:123)
         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:585)
         at com.evermind.server.rmi.RmiMethodCall.run(RmiMethodCall.java:53)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)

  • Unable to do the restriction at Fund Center or FM Area when FM is not activ

    Hi,
    we have the following business requirement:
    Background of the issue:
    Field Status variant in Account Assignment category and GL:
    We are in the process of rolling out one of our company codes which is
    in a different instance(server).
    We already have some 130+ company codes running in a different
    instance. This is a kind of Instance consolidation to bring all systems
    under one instance.
    Funds Management has been activated in the company code for which we
    are carrying out the rollout. FM has not been activated for the
    existing company codes.
    Now, the issue is with regard to the field status variants, which can
    be controlled at the company code level and which cannot be controlled
    which is at the client level.
    (i)     The existing company codes have a field status variant which
    has the field status groups having the fields Commitment items and
    Funds center in Suppress mode in the existing instance.
    (ii)     The company to be rolled out has the field status variant which
    has field status groups having the fields Commitment items and Funds
    Center in Optional mode.
    (iii)     On the other hand, there is yet another field status control
    for the Account assignment objects like Cost center, WBS elements, etc.
    in the MM-FI integration area. This is at client level and at present
    the same has the status of u201CSuppressu201D for Commitment items and Funds
    Center. We have changed the same to u201COptionalu201D for the purpose of
    testing the proposed roll out in our existing instance.
    In that case, the status of GL account assignment in above is
    clashing with our client level field status as described in (iii)
    above. As a result, we are forced to change the field status in
    above to optional mode for our existing company codes which we do not
    intend to do.
    When only one company within a group of companies is activated with FM,
    I feel that:
    (i)     At the client level, there is no option for me other than to
    keep the Funds center and commitment items in optional mode
    (ii)     At the GL level, I should be able to keep my field status in
    Suppress mode (If FM is not activated) and in Optional mode (If FM is
    activated) and SAP should be able to take care of the clash in the
    field status at the transaction level in such a scenario.
    The issue is we are able to control the access if FM is activated for a particular company code, where as we are unable to control the access for other company codes where FM is not activated and FM Area is not linked.
    We tried to use the BADI ME_PROCESS_REQ_CUST, but this is applicable for POs only.
    Please look into this  issue and help us in meeting our business requirement.
    Thanks & Regards,
    Ramakrishna

    Hi Justin,
    Thanks for the extra points.
    Copy and save this bold text some where
    /Applications/iChat.app/Contents/MacOS/iChat -errorLogLevel 7
    This needs to be run in Terminal.
    iChat needs to be shut down to do so.
    Just paste it in Terminal after the Welcome to Darwin message and hit enter.
    It will launch iChat and create an on-going log in the Terminal window.
    You will see the reference to the Harware rules.plist
    Further down you will see the bandwidth found by iChat, followed by the number of Audio and Video Buddies that you can support.
    It goes on.....
    It makes a note of the router that you are connected to.
    After that it will end up lists listening checks until you connect to a Chat.
    This makes this a useful way to find out what iChat can see at it's startup.
    To Stop - Quit iChat in the Normal way.
    Save the Log in a Text editor of some sort. (Post here if required).
    Then Quit Terminal.
    It is a useful tool to highlight some things in the start up phase, (And a reminder to look in specific places) when you think you have looked at all the settings.
    8:12 PM Wednesday; November 15, 2006

  • Any Special transaction code for Activation of Work flow

    Hi all.
    Any Special transaction code for Activation and deactive of Work flow?
    which have we need to transport after WF (like task,method,rule)?
    To be reward all helpfull answers.
    Regards.
    Jay

    If I understand your question correctly, you want to know how to activate your workflow after transport ?
    Normally, the status of a workflow is included in your transport (if I'm not mistaken)
    So activate/deactivate in your dev-system and transport it..

Maybe you are looking for