During utilization showing message

Hi,
While creating the excise invoice for export, and clicking on the utilization button I am getting a msg that 'Excise tax indicator not maintained for 1 J_1IEXESTA - please maintain'. But this is not preventing me to do the further processing.The msg is coming with a green tick.Why its coming?Does it affect in any other way. In fact I am getting the required out put.Please help me out. Good points will be awarded to the deserving answers. If needed I can provide more details.
Thanks/regards
Makarand

Hi Laxmipathi,
Thanks for your quick response.In fact i have checked all the J1ID settings. they are ok. Our client uses the TAXINN tax procedure. Initially in the master record of the  foreign customers the excise indicator was maintained 3(nil duty).They have huge accumulation of CENVAT Cr. Now they want to utilize this for export. All the information regarding the excise is being fetched from the condition record.So its not preventing me to carry out the process.The only thing is that it prompts me a msg in green that the exe tax ind not maintained for 1  J1_IEXESTA . I have tried with all the combination of indicators.If I maintain the indicator in the table as 1 and also in the custmer master, the msg is coming that the excise rate for the material not found. If needed more detail can be supplied
Regards,
Makarand

Similar Messages

  • Lower limit can only be changed during initial entry, Message no. NR651

    Hi Experts,
    As per the number ranges limit values defined in the system for the planned orders, there is a need to increase the number ranges.
    System is not allowing us to change the limit values of the Planned orders in MD91 and showing the Message no. NR651.
    We have also searched for the available threads in SCN and other sites, but didn't find the root cuase link for this error.
    System message:
    Lower limit can only be changed during initial entry
    Message no. NR651
    Diagnosis
    You have tried to change the lower limit of an interval which has a non-initial number status.
    System Response
    The change was not executed.
    Please guide us how can we increase the number ranges for planned orders.
    Thanks in advance.

    Hi,
    You can create a new number range or change in transaction OMi2 or in MD91.
    Assign the 02  by clicking number range in OMi2
    or in transaction OPPQ  click on number range & select the 02.
    Do the changes as described and analyse the results. Ensure that while testing no body is creating the planned orders.
    Regards,
    Narresh

  • Mac with latest updates: installation window appears, shows message "Retrieving install" for 3 seconds then installation window goes blank. Why?

    Mac with latest updates: installation window appears, shows message "Retrieving install" for 3 seconds then installation window goes blank. Why?

    Hold down the option key during start up - you will be given the choice of which partition to use (Macintosh HD or Windows). I am having the same problem - Windows 7 seems to have installed but it goes to a blank black screen and there is nothing to do but force a reboot. I too have an i3 iMac... Windows 7 32-bit from original disc.

  • Sender Mail Adapter Error: exception caught during processing mail message;

    HI , I am configuring mail to file scenario. Need to read mail content (no need to capture From,TO or Subject details) and create a file with the content in the mail.
    Need to read mails from microsoft outlook. Exchange server has been configured for POP3 protocol.
    Following are the details provoding in sender mail adapter:
    URL: provided url in the format: pop://<server name>
    Authentication method: plain
    provided user credinetions to access mails.
    poll interval - 1min
    content encoding none.
    processing parameters : quality of service-exactly once
    Since there is no need to capture From,TO or Subject details, didn't select the option - use mail package.
    Verified for unread mails in the mail box and made sure that there are few unread mails.
    Also, created data types and other components in IR and completed mapping.
    But after starting sender mail communication channel, getting error "exception caught during processing mail message; java.lang.NullPointerException" in RWB-adapter-communication channel monitoring.
    please let me know what needs to be done to resolve this error.
    Thanks.

    HI Stefan, i tried, but still it is giving same error. Yes, i am able to access outlook mail with the user credentials given in the communication channel to access exchange server.
    I am using message protocol: xipayload . Also since i dont have to capture TO,from,subject details., created data type just with one element of type string, not in the standard format .Does this makes any difference.

  • I am not able to send messages to multiple person from my iphone 5s after updating to ios 8.1.2. It shows message not delievered

    I am not able to send messages to multiple person from my iphone 5s after updating to ios 8.1.2. It shows message not delievered

    Hi waqaskhan91,
    Thank you for visiting Apple Support Communities.
    If you're not able to send text or iMessages to certain contacts after updating your iPhone, start with the troubleshooting tips in this article:
    iOS: Troubleshooting Messages - Apple Support
    If you only see this behavior with a few contacts, you may want to try these steps first:
    If the issue occurs with a specific contact or contacts, back up or forward important messages and delete your current messaging threads with the contact. Create a new message to the contact and try again.
    If the issue occurs with a specific contact or contacts, delete and recreate the contact from the Contacts app. Send a new message to the contact.
    Best Regards,
    Jeremy

  • How to show messages in a little popup ?

    Hello,
    Im faced with an issue when I want to show messages in my little popup.
    The calling component is BT111H_OPPT.
    Whenever I want to show the message in my popup that the mandatory fields are not filled with information the systems only shows them on the view of BT111H_OPPT when I closed my popup.
    Ive implemented an own check method for that issue. See the following Code:
    IF me->check_mandatory_fields( 'CREATE' ) = abap_true.
        lr_window ?= me->view_manager->get_window_controller( ).
        lr_window->call_outbound_plug( 'CREATE' ).              "#EC NOTEXT
      ELSE.
        DATA: lr_service TYPE REF TO cl_bsp_wd_message_service.
        lr_service = me->view_manager->get_message_service( ).
    +   TESTED THAT CODE FIRST TIME, BUT NOTHING APPEARS ANYWHERE!!!!+*
    *    CALL METHOD me->messages->add_message
    *      EXPORTING
    *        condition = co_mandatory_field_empty
    *        message   = 'Test'
    **        otr_alias =
    *        severity  = cl_bsp_messages=>co_severity_error
    **        dummy     = me->component_id
    **        p1        =
    **        p2        =
    **        p3        =
    **        p4        =
    + SO I TRIED THAT ONE. NOW, THE MESSAGE APPEARS IN THE CALLING COMPONENT!+* 
    TRY.
            lr_service->add_message(
            iv_msg_type = 'W'
            iv_msg_id = 'ZICRM'
            iv_msg_number = '050'
            iv_msg_v1 = 'lv_text'
          CATCH cx_bsp_wd_dupl_mess_subscr.
        ENDTRY.
      ENDIF.
    THANK you for an answer...
    Regards,
    marcus

    Hi Marcus,
    try to use the following method as you create the popup in the calling view controller:
    <your popup ref>->set_display_mode( iv_mode = if_bsp_wd_popup=>c_display_mode_surrounded ).
    Best Regards,
    Michael
    Edited by: Michael Neumann on Feb 23, 2011 5:50 PM

  • Error during deployment of Message Driven Bean

    Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              I am getting some error (or perhaps warning) during deployment of Message
              Driven Bean. Any one seen this before?
              This error only comes on a machine with Dual Network card.
              Thanks.
              ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu> <main>
              <system> <> <160007> <You are running WebLogic Server with J2EE 1.3 features
              enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP 1.2,
              Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server 6.1
              is of a non-final version of the appropriate specification. It is subject to
              change in future releases once the specification becomes finalized. This may
              cause application code developed for BEA WebLogic Server 6.1 that uses the
              new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              supported in future releases of BEA WebLogic Server.>
              ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              container will automatically attempt to re-establish the connection with the
              JMS server. This warning may occur during WebLogic Cluster start-up if the
              JMS destination is located on another server. When the JMS server connection
              is re-established, the Message-Driven EJB will again receive JMS messages.
              The Error was:
              Unable to create a JNDI InitialContext to lookup the JMS destination. The
              error was:
              javax.naming.CommunicationException. Root exception is
              java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              nested exception is:
              java.net.ConnectException: Connection refused: connect; No available router
              to destination
              at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:307)
              at
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              textFactoryDelegate.java:211)
              at
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              ory.java:149)
              at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              at javax.naming.InitialContext.init(InitialContext.java:217)
              at javax.naming.InitialContext.<init>(InitialContext.java:193)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              rivenBeanInfoImpl.java:641)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              nPoller.java:474)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              .java:418)
              at
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              nectionPoller.java:286)
              at
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              foImpl.java:511)
              at weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              at weblogic.j2ee.Application.addComponent(Application.java:170)
              at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              arget.java:360)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              Target.java:285)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              eploymentTarget.java:239)
              at
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              entTarget.java:199)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:636)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy34.updateDeployments(Unknown Source)
              at
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              ServerMBean_CachingStub.java:2977)
              at
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              icationManager.java:372)
              at
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              r.java:160)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              .java:636)
              at
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              21)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              nImpl.java:360)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              at $Proxy49.start(Unknown Source)
              at
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              ApplicationManagerMBean_CachingStub.java:480)
              at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              at weblogic.management.Admin.finish(Admin.java:644)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              at weblogic.Server.main(Server.java:35)
              >
              ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              <system> <> <010009> <EJB Deployed EJB with JNDI name
              ASYNCMessageDrivenBean.>
              

    Hi Tom
              Yes we do have an URL provided in the descriptor. It's
              t3://jms.server.net:7001.
              and the jms.server.net is resolved via a hosts file in Win2K
              eg,
              192.168.100.200 jms.server.net
              You are right in saying that the loopback in a dual-net card is a problem.
              But our solution
              above solves the issue as long as your host file does not use 127.0.0.1 as
              the IP.
              We need the URL b/c depending on our client's deployment , the JMS Server
              may be remote or may be local.
              "Tom Barnes" <[email protected]> wrote in message
              news:[email protected]...
              > Hi x,
              >
              > Something to do with the loopback and dual-network cards is
              > messin' with WLS' mind. I do not know what the problem is,
              > but I can guess:
              >
              > You have specified an URL in the MDB descriptor when there
              > is no need for one. If t3://127.0.0.1:7001 is in the same
              > cluster the MDB is running in (I suspect this URL is
              > actually the same WL server), then don't specify the URL.
              > This URL is only useful for connecting an MDB to a JMS
              > server that is outside local server and outside the cluster.
              > The URL may be working on single-network card systems
              > as perhaps then WL has enough info to guess that you
              > actually mean the local WL server, and simply converts
              > the context to a local context.
              >
              > Note that the URL option in the MDB descriptor is actually
              > a WebLogic extension of J2EE.
              >
              > Tom
              >
              >
              >
              > x wrote:
              > > Environment: WLS 6.1SP3 on Win2K SP2, non-clustered.
              > >
              > > I am getting some error (or perhaps warning) during deployment of
              Message
              > > Driven Bean. Any one seen this before?
              > > This error only comes on a machine with Dual Network card.
              > >
              > > Thanks.
              > >
              > >
              > >
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010008> <EJB Deploying file: AppRuntime.jar>
              > > ####<Dec 11, 2002 1:23:04 AM GMT> <Warning> <J2EE> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <160007> <You are running WebLogic Server with J2EE 1.3
              features
              > > enabled. The implementation of specific J2EE 1.3 features (EJB 2.0, JSP
              1.2,
              > > Servlet 2.3, and J2EE Connector Architecture 1.0) in BEA WebLogic Server
              6.1
              > > is of a non-final version of the appropriate specification. It is
              subject to
              > > change in future releases once the specification becomes finalized. This
              may
              > > cause application code developed for BEA WebLogic Server 6.1 that uses
              the
              > > new features of J2EE 1.3 to be incompatible with the J2EE 1.3 platform
              > > supported in future releases of BEA WebLogic Server.>
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Warning> <EJB> <QAAPP01> <Makalu>
              <main>
              > > <system> <> <010061> <The Message-Driven EJB: ASYNCMessageDrivenBean is
              > > unable to connect to the JMS destination: CQM_MessageQueue. The EJB
              > > container will automatically attempt to re-establish the connection with
              the
              > > JMS server. This warning may occur during WebLogic Cluster start-up if
              the
              > > JMS destination is located on another server. When the JMS server
              connection
              > > is re-established, the Message-Driven EJB will again receive JMS
              messages.
              > > The Error was:
              > > Unable to create a JNDI InitialContext to lookup the JMS destination.
              The
              > > error was:
              > > javax.naming.CommunicationException. Root exception is
              > > java.net.ConnectException: t3://127.0.0.1:7001: Destination unreachable;
              > > nested exception is:
              > > java.net.ConnectException: Connection refused: connect; No available
              router
              > > to destination
              > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:307)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:211)
              > > at
              > >
              weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              > > ory.java:149)
              > > at
              javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
              > > at
              javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
              > > at javax.naming.InitialContext.init(InitialContext.java:217)
              > > at javax.naming.InitialContext.<init>(InitialContext.java:193)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageD
              > > rivenBeanInfoImpl.java:641)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectio
              > > nPoller.java:474)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller
              > > .java:418)
              > > at
              > >
              weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectionPolling(JMSCon
              > > nectionPoller.java:286)
              > > at
              > >
              weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanIn
              > > foImpl.java:511)
              > > at
              weblogic.ejb20.deployer.Deployer.deployDescriptor(Deployer.java:1294)
              > > at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:996)
              > > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:31)
              > > at weblogic.j2ee.Application.addComponent(Application.java:170)
              > > at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
              > > arget.java:360)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
              > > Target.java:285)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
              > > eploymentTarget.java:239)
              > > at
              > >
              weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
              > > entTarget.java:199)
              > > at java.lang.reflect.Method.invoke(Native Method)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > > .java:636)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy34.updateDeployments(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
              > > ServerMBean_CachingStub.java:2977)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
              > > icationManager.java:372)
              > > at
              > >
              weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
              > > r.java:160)
              > > at java.lang.reflect.Method.invoke(Native Method)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
              > > .java:636)
              > > at
              > >
              weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
              > > 21)
              > > at
              > >
              weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
              > > nImpl.java:360)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
              > > at
              com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
              > > at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
              > > at $Proxy49.start(Unknown Source)
              > > at
              > >
              weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
              > > ApplicationManagerMBean_CachingStub.java:480)
              > > at weblogic.management.Admin.startApplicationManager(Admin.java:1234)
              > > at weblogic.management.Admin.finish(Admin.java:644)
              > > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:524)
              > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:207)
              > > at weblogic.Server.main(Server.java:35)
              > >
              > > ####<Dec 11, 2002 1:23:07 AM GMT> <Info> <EJB> <QAAPP01> <Makalu> <main>
              > > <system> <> <010009> <EJB Deployed EJB with JNDI name
              > > ASYNCMessageDrivenBean.>
              > >
              > >
              >
              

  • Error during activation a message mapping

    Hi,
    I get this error during activation a message mapping:
    source code has an syntax error:
    D:/usr/sap/XI3/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapf1f9db20a78a11dac004000f1ff80130/source/com/sap/xi/tf/_Source2Target_.java:2: package com.sap.aii.mappingtool.tfapi does not exist import com.sap.aii.mapping.api.; import com.sap.aii.mappingtool.tfapi.; ^ 1 error
    Can anybody help me please??
    Thanks.
    Regards
    Stefan

    Hi Michal,
    I do not have deleted some libraries in the XI-Installation.
    I have some customer functions in other mappings but no message mapping without or with customer function can I activate, now.
    The mappings are in serveral software components but it is no chance to activate a message mapping.
    Regards,
    Stefan

  • In MD05 system show message "The MRP element no longer exist".

    Hi Guru,
    Need some help .
    In MD04 transaction contain Purchase order, when I double click purchase order,It will get open .  But when I open same purchase order in MD05 system show message u201CThe MRP element no longer exist".
    Please help me , if any know the solution or any input. Open purchase order in system.
    Regards
    PNU

    PNU,
    I don't believe this is the same Purchase order.
    Review closely order number/item number/schedule number.  I believe you will see that the old entry (MD05) no longer exists, and has been replaced with a similar item.
    Best Regards,
    DB49

  • Junk Mail folder refusing to show messages from a particular account

    So, I have a weird problem with Leopard Mail (3.2) - when I click on the junk mail folder, 99% of the time it won't show messages from my Yahoo POP account. The only way I can get messages from this account to show is by expanding the junk mail folder, clicking on a different sub-account, then clicking on my Yahoo account. This will show the messages in its junk folder, and if I click on the combined junk folder they will show up inside it. This will work until I click away from junk - say, to my inbox - at which point the procedure will need to be repeated if I wish to see my Yahoo junk mail.
    I've only noticed it very recently, but I'm not sure how long it's been going on. Unbelievably annoying. I deleted the junk folder, no luck. I toggled the account off/on - this seemed to work for a day, but the behaviour's back and I can't make this work again. I rebuilt the mailbox... Even deleted and added the account again, but it still did the same thing.
    Has anyone else experienced this? Is it just a bug in Leopard Mail? Something specifically with POP accounts, perhaps? (My 5 IMAP accounts seem fine). If anyone has any further suggestions I'd be really, really grateful.

    Ok, so, something in way of an update: Normal behaviour appears to be restored after Mail detects a piece of junk mail and puts it in the junk folder for this account (manual marking of junk doesn't do the trick). Then it works ok until I quit Mail.

  • Exception caught during processing mail message

    I am getting the following error in CC monitoring for my sender mail adpater:
    exception caught during processing mail message; java.io.IOException: invalid IMAP status response; not finding * STATUS, but 001I NO The requested item could not be found.
    Please tell me how to resolve ?

    NOw when i changed the protocol from IMap to POP3 the error is
    exception caught during processing mail message[18]; com.sap.aii.af.mp.processor.ModuleProcessorException: Error during processing local bean: localejbs/AF_modules/MessageTransformBean caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at AF_modules, the whole lookup name is localejbs/AF_modules/MessageTransformBean.

  • Itunes will not launch, it shows  message of "itunes library .itl" can not be read because it was created by a newer version of itunes. I tried opene it in save mode but I had the same problem.

    Itunes will not launch, it shows  message of "itunes library .itl" can not be read because it was created by a newer version of itunes. I tried opene it in save mode but I had the same problem.

    If you still have an issue you may have to see about using the iTunes version (application) included with Snow Leopard 10.6 from the installer or an another one if available online, and see if that will install.
    Sometimes you may have uninstall the bits left in your system by the earlier (or later) iTunes installers; as they all leave a trace and these can stop a different version of iTunes from being installed.
    Not sure if the following site/link will tell the method...
    •Apple - Support - iTunes - install & update:
    http://www.apple.com/support/itunes/install/
    •Troubleshooting iTunes installation on Mac OS X:
    http://support.apple.com/kb/HT2311
    Good luck & happy computing!
    ps: i see you resolved this issue. it's magic!

  • My iPad shows message that it needs to be backed up, but when connected to iTunes for backup it states all backed up. Cannot remove message by clicking ok.  Therefore iPad is locked up.  What can I do?

    My iPad shows message needs to be backed up.  When connected to iTunes it shows all backed up.  Cannot get rid of message by clicking ok.  IPad  therefore is frozen.  What to do?

    Welcome to the Apple Community.
    You might try a forced shutdown to begin with, hold down the top and home buttons together until the device shuts down, then restart it.

  • BPM Error during delivery of message

    Hi All,
    I am working on BPM Scenario, to collect the files based on Correlation Id.
    Its working file in PROD, Last 2 days back we processed 20 message, 4 was not processed. Data looks good, and i am trying to process those 4 records.
    I am getting the below error in SMQ2.
    SysFAIL - >Permanent error in BPE inbound processing -> Display Trace: 193     385     20091008225338.6300000     DATA     SWF_INB     EXCEPTIONS          WF-BATCH     X     Error during delivery of message BDAAD94EA8454FA005F1A2C9416843DC to receive processes     WS90100038     XBQO$PE_WS90100038     BDAAD94EA8454FA005F1A2C9416843DC
    I cleared the SMQ2 and SWWL, and reprocessed the file, still i am getting same error...
    SXMB_MONI_BPE - > Continoue Process flow after error nothing is displayed...
    Any cause, i am getting the error???
    Thanks,
    SR

    Hi Siva,
      Normally this error occurs when your data not sufficient,check your data its correct or not,i think its not satisying your condition / corealtion what you defined in BPM.
    Regards,
    Raj

  • I want to install Windows but Mac showed message that related partition should be in NTFS format. In which way I could format windows partition.

    I want to installWindows but Mac showed message that related partition should be in NTFS format.In which way I could format windows partition.

    Go back and re-read the guide which is also part of and in the Apple Boot Camp Assistant.
    Boot Camp Installation Guide
    Boot Camp FAQ
    Windows 7 FAQ
    Apple - Support - Boot Camp

Maybe you are looking for