Error during Outbound Delivery - Message no. VL248?

Hi,
When I am trying to do the Outbound Delivery I am getting this error"No schedule lines due for delivery up to the selected date
Message no. VL248
Diagnosis
There are no schedule lines due for the given order item up to the date
chosen.
System response
The system does not create a delivery item for this order item.
Procedure
o Check whether the order item to be delivered contains confirmed
schedule lines.
I have checked on this site and google but unable to find out anything useful. Please tell me how to resolve this error as I am not a SD guy but I unless and untill I do Outbound Delivery I won;t be able to proceed with what I am doing...
Please suggest step by step....
Thanks in advance.....
Regards
Nitin

HI
Go to VA02 , double click on the Line item and click on the Schedule tab and see the Delivery date
Go to VL01N , select the shipping point and selection date give the Delivery date which is there sale order Schedule tab
and also check the Sale order whether delivery is done fully or not (Document Flow)
Check and Revert
Regards,
Prasanna

Similar Messages

  • 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

  • Error during Returns Delivery in a Repair Order

    Hi,
    I am getting the follg error msg during Returns Delivery for a  Serviceable Material that is Serialized.:
    "Copying is not poss.because an entry is missing in Table TVCPL: LF RAS IRRS"
    However it maintain this in Copy Control for Deliveries, system is throwing a dump:
    "Short text of error message:
    No copying of object list entries not matching object usage 'S'
    Technical information about the message:
    Diagnosis
    An object list entry, which does not belong to a serial number object list, is used as a copy model."
    How can I resolve this ?
    Thanks.
    Raj

    Maintain the configuration step of copy control for deliveries. T-code VTLA.

  • 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 Inbound Delivery creation by Idoc DELVRY05

    Hi,
    We are trying to consolidate ASNs and creating an inbound delivery for the same. Thus we have more than one PO information in the idoc.
    It processes fine and creates an inbound delivery if all the line item nos are different.
    But the issue is, when there are articles which have the same line item no. even if the articles are different and they are on different POs. It gives the following errors.
    1) "Delivery item cannot be exactly determined
    Message no. HUFUNCTIONS313"
    I tried to debug the above error and found that while packing it looks to the lips-vbeln/posnr & not the PO nr./PO item.
    I am not sure if this could be handled by some config. Please advice.
    2) "V51VP - item was not found - process cancelled
    Message no. HUGENERAL056"
    Any hints or comments on the above would be appreciated.
    Thanks & Regards,
    Akshay

    Hi Raghavendra,
    It has been a long time. But, as far as I can remember we had made coding adjustments in the customer-exit EXIT_SAPLV55K_004, include ZXTRKU12 to fetch the correct item and fill the idoc segment fields.
    This resolved the issue.
    Best Regards,
    Akshay

  • An "error during rendering/encoding" message

    Hello, can someone help me? I'm trying to burn a dvd using idvd through imovie. I start to end the rendering of my menus and the message pops up:
    Error during rendering/encoding
    There was an error during rendering/encoding of the menus/slideshows. Burning process abored.
    Can any one help with this issue? thanks
    bryan

    Bryan,
    I just went through this problem, and this is the advice I got and that worked for me...
    Joan Philgreen, "Error during rendering/encoding", 01:31am Aug 11, 2005 CDT
    I hope your situation is as easy to fix as mine was.
    -Joan

  • Creating a IDOC during outbound  Delivery posting

    The requirement is to create a IDOC J3ADES01 when an Outbound delivery is created.
    Can you kindly suggest ways of doing this?
    I planned to search for BADI or user-exit and create a IDOC within it.
    But not sure.

    By the way, what message type and basic type can be used for these FM?
    I also found a lot of opinion from here, some say DELVRY03. some say DELVRY04, some say DELVRY05.
    Is it no problem with using which basic type here as long as it fits the data that u want in the IDOC?
    Please advice.
    Thanks.
    Best Regards,
    JL

  • HT1103 i am getting a error during rendering/encoding message

    I am trying to burn a DVD from  and I am getting a error during rendering/encoding message

    There are 9 versions of iPhoto.  Which version of iPhoto and any other application involved (iDVD?) are you using and what system are you running?  Also describe exactly what you're doing.  You orignal statement is way to general for us to attempt to offer any help. 
    OT

  • Issue During Outbound Delivery for STO Purchase order

    Hi,
    Delivery Quantity is not picking automatically in VL10B, while creating outbound delivery with STO purchase order with account assignment ''Q'' Project (with WBS element). Stock also available in the supplying plant as shown the below screen shot.
    MMBE:
    Please do the needful.
    Thanks,
    Ashok

    Hi Pardhu,
    Thanks for your response.
    We don't have any open reservations and safety stock available for the material. Kindly go through below screen shot for your reference:
    Thanks,
    Ashok

  • 'Customer Not found' error during inbound delivery

    Hi Experts,
    During creation of inbound delivery(IBD) with transaction VL31N (against normal PO with doc. type NB), we are getting following error.
    Customer  not found
    Message no. 8B519
    Diagnosis
    No entry found in KNA1.
    Procedure
    Please contact your system adiministrator
    As per our understanding there should not be any connection for IBD & Customer master. Moreever we are getting this error for Only Brazil Plant. IBD works fine for India & Argentina plants.
    Requested to provide any possible clues.
    Regards
    Manoj

    Hi Manoj
    This error messag should be realted to the Brazilian localization...
    and th e problem reported should be  in the table J_1BTVAKV,  If you don't need a Nota Fiscal in the step of process, you should not assign the Nota Fiscal type  to sales doc type .
    Please correct your configuration and perform a new test.
    Regards,
    Mauro

  • Error during Inbound Delivery

    Dear Expert,
    I have problem when we want to create Inbound Delivery/VL31N. Error message is "No deliveries created (check log)". The long text of log is :
    Diagnosis
                                                                                    There is no item category available in item category
        determination in the delivery (table T184L) for the following
        entries: EL LEIS V
                                                                                    System Response
                                                                                    The system does not allow further processing of this item.
                                                                                    Procedure
                                                                                    Specify the appropriate item category for the above mentioned
        entries or inform your system administrator.                    
    I confuse with this message, because i don't know the relation of table T184L with my case. the another Inbound delivery is working fine, only 1 inbound delivery that getting this error. Any solution and advice. Thx a lot
    BR,
    Affan

    hi
    go to t code 0184 and here against the entry EL LEIS V maintain item cat as norm and same manintain in ur material master
    regards
    kunal
    award if helpful

  • ME006 error during Inbound Delivery Confirmation VL06I

    Hi, to all..
    We are trying of post multiple goods reciepts (same PO) for Inbound Deliveries with trx VL06I
    When we push the botton, we get next error:
    ME006 User && is already using PO &&
    In some cases just the first InbDel is confirmated, other times, 2 or 3 ID are confirmated buy they are NO consecutives .
    We think software in Support Package 17 has some bug, but we had not been able of find any SAP Note to correct this problem (think about ENQUEUE_EMEKKOE/DEQUEUE_EMEKKOE functions)
    We have checked also trx SM12 and NO blocking appears ther...
    I'll appreciate any help in this issue.
    Best Regards..
    TMoreno

    Hello,
    I manage to check the message ME006 in IDES  and it is standard SAP message.
    I have one question, why is user who is doing the goods reciept for the inbound deliveries associated with single purchase order opening the same purchase order in change mode at the time of goods reciept
    This message ME006 only appears if your user has opened the purcahse order in chnage mode, during the goods reciept process with VL06I.
    This is also true when user XYZ has opened the purchase order in chnage mode (ME22N) and user ABC is doing the goods reciept for the same purchase order.
    I suggest that you do not open the purchase order in change during goods reciept.
    I hope this helps
    Br,
    Tushar
    Edited by: Tushar Patankar on Jan 11, 2011 3:33 PM
    Edited by: Tushar Patankar on Jan 11, 2011 3:38 PM

  • Error during inbound delivery creation for some times not always

    Hi,
    I'm getting the following error when i'm trying to create an inbound delivery for PO.
                                                                                    Diagnosis                                                                               
    The system attempted to find the reference movement type for         
         the Warehouse Management system. A corresponding entry is            
         missing in table 156S with the argument 101/X/X/ / /X/.              
         The argument consists of:                                            
         o   IM movement type                                                 
         o   Indicator: Value update                                          
         o   Indicator: Quantity update                                       
         o   Special stock                                                    
         o   Movement indicator                                               
         o   Access indicator                                                 
         o   Indicator: Consumption         
    Can someone help me to resolve it? as it is not happening always
    Appreciates everyone time and help.
    Thanks and regards,
    Siva

    Hi,
    Thanks for the response and yes i did maintained IM/WM mvt types for 101 in both places.
    If the movement type is maintained well why SAP says it is not?
    SPRO > LE > WM > Interfaces > IM > Define Movement Types - "Assign WM Movement Type References to IM Movement Types'
    Related tabel is V_156S_WM
    If you check your configuration you will see that there are many entries with 101, and there are several other parameters...
    First you should check what you are doing in IM, what parameters that mvt has (qty, value update, special stock, etc) > after that you should check whether it is maintained well in WM customizing - see steps in my previous email.
    Regards,
    Csaba

  • GR error for outbound delivery

    Hi,
      User had mistakenly processed GR for partial line items during MIGO transaction against OBD.
    When user is taking GR for that pending materials which had processed without order reference(VL01NO transaction) then system is giving eror message of "Update control of movement type is incorrect (entry 605 _ _ _ L)"
    plz suggest

    You must do customization via OMJJ
    Movement Type: 605
    from left side Update control / WM movement types
    Such a record as below must be customized
    MvT Val.Update Qty update S Mvt
    605  X X F
    Regards

  • Error during proxy processing Message E SG 105 cannot be processed in plugi

    When I move a new custom proxy from Dev to Qa I am getting the above error when running the test from XI. However, the test runs fine in SPROXY test tool. Has anyone else run into this problem in the past? The error catagory is Dynamic_Call_Failure
    Thanks,
    Chris

    Hi,
    I'm facing the same problem.
    I wrote an very easy report. It works as intended, but when i set fillable='X' i get the error FPRUNX 001.
    FP_GET_LAST_ADS_TRACE return following:
    Begin operation:
    Render, elapsed time = 16 ms.
    #   End operation: Render, elapsed time = 89 ms.
    #   Begin operation: UsageRights, elapsed time = 89 ms.
    #   End operation: UsageRights, elapsed time = 97 ms.#
    ...and the error string of FP_GET_LAST_ADS_ERRSTR is:
    ADS: Request start time: Wed Jul 01 14:44:26 CEST 2009(200.101).
    Any idea what the problem might be?

Maybe you are looking for