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

Similar Messages

LUW data for smq2--Error During Delivery: Ibound processing locked

Hi all,
There are lot of messages(more than 7000) stucked in d Inbound queues, as viewed by SMQ2, and are in the retry mode for long.
In the LUW data the status of the queue is showing error during delivery and the error text is <b>Inbound Processing Locked for example Deadline Processing </b>
can anyone please suggest what this problem is about and suggstions for removing this problem will be really appreciated.
This is urgent as the problem is in production.
Regards,
Rookie.

Hi Prateek,
The BPM involved is a dicesion making BPM which is creting large Idocs.
We have checked in SM12 and the messages are locked there. Can you please advice how can we unlock the messages from SM12.

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

I keep getting "Problem during delivery processing" messages

This morning I started getting "Problem during delivery processing" messages like this one...

Same problem here. And i can't fine apple support contact for submit this problem. Bad bad bad bad support page appe .

Budget exceeded error during delivery creation

Dear All,
We are facing a problem during delivery creation. Our business scenario is engineered to order and every customer order is created as a Project in PS module. the sales order is linked to the WBS element. While creating an outbound delivery for the sales order the system gives error message that "Budget exceeded for the WBS." This is for first time such error has occurred during the delivery creation. Logically delivery creation and PGI indicates negative incurrence on the WBS elements so even if the budget is not there or exhausted still then system should allow to create the delivery.
Please let me know if anybody has face this problem and solved it.
regards'
Preetam

Preetam,
What you are saying is correct. Delivery creation and PGI indicates negative incurrence on the WBS elements, the system should not check budget of the WBS.
Just for checking manually, read the details of the error and note the amount. Check budget availability of wbse and compare this amount with available budget.
Regards,
Amol Sarode

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.>
          > >
          > >
          >

BPM: error at exactly 2500 messages after message split: no coincidence?

Hi everybody,
we poll a message, split it in BPm and than call a WebService.
We got an error exactly after 2500 messages were processed successful.
Is there a special parameter which influences the BPM?
Thanks a lot
Regards Mario

Hi,
In SXMB_ADM you can set the time out higher for the sync processing.
Go to Integration Processing in SXMB_ADM and add parameter SA_COMM CHECK_FOR_ASYNC_RESPONSE_TIMEOUT to 120 (seconds). You can also increase the number of parallel processes if you have more waiting now. SA_COMM CHECK_FOR_MAX_SYNC_CALLS from 20 to XX. All depends on your hardware but this helped me from the standard 60 seconds to go to may be 70 in some cases.
Make sure that your calling system does not have a timeout below that you set in XI otherwise yours will go on and finish and your partner may end up sending it twice
when you go for BPM the whole workflow
has to come into action so for example
when your mapping last < 1 sec without bpm
if you do it in a BPM the transformation step
can last 2 seconds + one second mapping...
(that's just an example)
so the workflow gives you many design possibilities
(brigde, error handling) but it can
slow down the process and if you have
thousands of messages the preformance
can be much worse than having the same without BPM
see below links
http://help.sap.com/bp_bpmv130/Documentation/Operation/TuningGuide.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/43/d92e428819da2ce10000000a1550b0/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/sap%20exchange%20infrastructure%20tuning%20guide%20xi%203.0.pdf
BPM Performance tuning
BPM Performance issue
BPM performance question
BPM performance- data aggregation persistance
Regards
Chilla..

Error during delivery

hi all
Getting error before delivery
"Create delivery" not allowed (Sys. status Cost, object VB7071110001000010)
Message no. BS051
Diagnosis
The status check for the status object VB7071110001000010 indicated that the procedure "Create delivery" cannot be performed because Sys. status Cost forbids it.
System Response
Procedure "Create delivery" is not performed.
Procedure
If procedure "Create delivery" is to be performed, the Sys. status Cost of object VB7071110001000010 must be reset.
Other statuses than Sys. status Cost can also prevent the procedure. This message does not tell you all statuses which currently prevent procedure "Create delivery".
Thanks
sandeep patil

Dear Sandeep,
is this for export third party orders??? if you go to header export data in the order you will see more
details on this error in te log.. to make a long story short sys status is received when the export license has not been created or it has expired in master data...
If this is not the case, then I think someone had activated the export control check for Document types and item categories in VI57 and VI58. Also, check 24455 SAP Note. It could prove useful.
regds
Jude

ERROR DURING DELIVERY PROCESSING --PL. HELP

Dear All,
Pl help me that user is making a delivery & he is getting an error as --> " Error during copy of partener : Partener role SP, Pl help what to do for thsi how to solve ? User is processing the delv by t.code = CNSO ,
Points will be immed. rewrded for helpful solution
sap11
Edited by: sap11 on May 9, 2008 7:01 AM
Edited by: sap11 on May 9, 2008 7:02 AM

Hi Friend,
Iam not aware regarding CNSO and says transaction does not exist. Check for the exact transaction code used by the user.
In customising Check for the partner determination for delivery. Check for your delivery type what is the partner determination procedure is assigned and for that procedure check for the partner functions. Here sold to party (SP) should be assigned to the procedure with not modifable check box ticked.
Regards

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

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

Error during delivery creation

Hi Friends,
I have created a PO, now when i am trying to create its delivery through VL10D, system is showing error message " delivery from plant XX for material YY not possible" and "shipping from shipping point X and plant Y is not possible".
Although, shipping point is assigned to plant code.
Plz suggest if any other config needs to be checked.
Regds

Hi,
Check the Customizing properly:
If stock balance is available in supplying plant, then goods issue (outbound delivery) should get created.
Please check whether that material blocked in issuing plant.
If this doesnot work then
1. You must assign a delivery type to the purchase order document type/supplying plant combination.
You can do this in the IMG for purchasing under "Purchase Order > Set Up Stock Transport Order> Assign Delivery Type and Checking Rule". NL (Replenishment delivery) is provided for intra-company-code stock transfers and
NLCC (Replenishment delivery cross company) for cross-company-code stock transfers.
2. You must assign sales and distribution (SD) organizational units to the supplying plant. They are a sales organization and a
distribution channel. Purchasing > Purchase order > Set up Stock Transport Order > Plant.
3. You must assign a customer master record to the receiving plant. IMG Purchasing > Purchase Order > Set Up Stock
Transport Order > Plant. You require a customer master record for the receiving plant. This customer master record must be
created for the organizational units of the supplying plant.
(point 2) (Logistics > Sales and Distribution > Master Data > Business Partners > Customers > Create -> sales and
distribution VD01 or total XD01).
For the intra-company-code stock transport, it is sufficent to create the customer master record as a goods recipient (VD01).
For the cross-company-code stock transport with shipping and billing documents, a complete cutomer master reccord is required
(XD01).
4. For the material to be transferred, you must create the sales organization data for the sales organization/distribution channel
of the supplying plant (point 2), and you must maintain the sales view (general plant data) for the supplying plant.
5. If there is a cross-company-code stock transport, you must create a vendor master record for the purchasing organization of the receiving plant. You must assign the supplying plant to the vendor master record. The assignment is executed in the vendor master record from the purchasing organization screen using "Extras > Additional Purchasing Data".
6. You must enter a shipping point for the combination of shipping condition (from the customer master record of the
ordering plant, see point 3) - loading group (from the material master) - supplying plant, IMG: Logistics Execution > Shipping
> Basic Shipping Functions > Shipping Point and Goods Receiving Point Determination > Assign shipping points.
Regards,
Prashant

Unauthorized Error during Processing Outbound Message in XI

I have configured a scenario that whenever there is a file of certain filename it will trigger one of the out bound message.
But the following error occured during processing of the out bound message:
Error Msg: Failed to transmit message due to Unauthorized
May I know how/where to set the acess right?
StackTrace is as follow:
find . -type f -exec grep "61abff41-dd01-11dc-c53d-001a4b053868" /dev/null {} \;
./defaultTrace.3.trc:#1.5#001A4B053868006E0000001600004E4900044651CF729F25#1203217093532#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage, boolean)#J2EE_GUEST#0####2d915860dd0411dccdbb001a4b053868#SAPEngine_Application_Thread[impl:3]_116##0#0#Error##Java###Failed to transmit message due to .#2#61abff41-dd01-11dc-c53d-001a4b053868(OUTBOUND)#com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 401 : Unauthorized#

Hi,
>>I have configured a scenario that whenever there is a file of certain filename it will trigger one of the out bound message.
What does it mean
Procedure to trigger any of the interface.
1) Develop IR Objects according to the scenario
2) Develop ID objects according to the scenario.
3) In the Sender Communication channel Specify the name of the file and the Source directory that the outbound interface shld pick to process it in XI
4)In the Rec Channel Similarly specify the name of the file and the Target directory to place the file.
If u specify the file name in the sender channel means according to that file name corresponding interface will be run.
Regards
Seshagiri

Error During Delivery creation with reference to Sales order

Hi all,
I am confused while creating delivery order with reference to sales order as this error *" Number of copying routine for table VBKD is missing in Table TVCPL"* is coming again and again.
I have perhaps made all possible things in VTLA ( Copy sales doc to delivery doc) but still i m finding it difficult to remove it
Please guide me in it.

Hi,
You will need to make assignment from So item to Delivery item please check if copy control is maintained at item level. Also make sure that Copy controls are maintianed for the billing document from the SO & Delivery both as this would be the next step.

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?

BPM Error during delivery of message

Similar Messages

Maybe you are looking for