Permanant Error in Inbound Processing in BPM

Hi All,
i have done a File1->JDBC(Synch)->File2 scenario using BPM.
It works fine when i have data in input file ie File1. However when my input file empty my scenario shows green flag in "OutboundStatus" and in queue gives error "Permanant error in Inbound Processing". When i tried to see the error in details got exception in START_PROCESS....
After deleting this entry from queue and sending file with data it works fine.....
I just want to know why it happens....? My input file can be empty as i am using it for triggering the scenario.
Do i need to do any settings in BPM or scenario to handle this?
Thanks,
Atul

hi atul,
in the rec step where u set the start process check box, you give the message. it is this message that is used to start the BPM process and not ur input file... the input file is used to trigger ur scenario not ur process. therefore u have exception in 'start process'.
hope it helps.
regards,
latika.

Similar Messages

Error In inbound Processing IDoc

Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
Thanks

Hi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN     005
SPRAS     E
MAKTX     MANATA2000 TEST ALE
SPRAS_ISO     EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan

Permanent error in BPE inbound processing for BPM Mesg Split

Hi Friends,
i have done the below scenario. i had done everything what theys mentioned in the blog but i am getting the error in smq2 as "Permanent error in BPE inbound processing" sysfail please helpme on this issue.
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure

Hi Uday,
Please check this blog for your error, This is really interesting. Permanent solution for your question.
Delivery Modes in BPM.
Thanks!

Sending Inbound application log error in inbound processing through email

Hello all,
My client wants application log for failed idoc through E-mail.(The application log found in we05 for failed idocs).
Please guide me how to get/fetch the error log in inbound processing.
Thank you.
Edited by: Sanjay_lnt on Feb 9, 2010 5:32 AM

Hi,
Query EDIDS table with the relevant selection criteria like date.
Here field STATXT will give you the message text. REPLACE the place holders(&) with STAPA1, STAPA2, STAPA3 and STAPA4 to build the complete message.
Make sure that you read the message for the latest counter(Check Max counter in field COUNTER). Because same IDOC can have multiple messages.
Once you get the message, you can use normal mail sending code for sendingout the mails.
Thanks,
Vinod.
Edited by: Vinod Vemuru on Feb 9, 2010 11:21 AM

AS2 adapter error during inbound processing

Hello,
We have upgraded PI to version 7.1 and now we are testing the Seeburger AS2 adapter.
We have received a testmessage from an AS2 partner and it is shown in the message monitoring of the Seeburger adapter workbench, with status succesfull.
Only the message is not on the integration server. The message is not shown in sxmb_moni or the message monitor of the RWB.
In the RWB the communication channel (CC_AS2_Sender) gives the following error:
"Message inititiation failed: Processing error"
The message itself gives the following error:
"Inbound message processing failed! performing rollback
Can anyone help us with this?
Thanks in advance.
Regards,
Marco

Hi Marco,
the message is not forwarded to the intergration egine because there might be an error in your communication channel.
Are there any other modules in the module chain of this communication channel?
Can you check "default_trace" and "application_log" for exceptions (/j2ee/cluster/serverXX/log)?
Did you also restart the Java Stack after the Upgrade?
regards,
Daniel
Edited by: Daniel Rexter on Jun 30, 2010 2:59 PM

Error in inbound processing: EDI message - XML Gateway

Hello!
I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
In the beginning of b2b.log I see this:
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
After I copy the edi file to the incoming directory B2B starts processing the file:
2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
Protocol = File
Version = 1.0
Transport Header
filename:00003442_23.CMS
filesize:12345
file_ext:CMS
fullpath:C:\xa_endpoint\00003442_23.CMS
timestamp:2009-07-06T16:14:29.393+01:00
As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
     at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
     at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
Last message repeats once more and then:
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
     at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
     at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
     at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
     at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
     at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
Error repeats a few times.
Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
Could anyone help with this? What could be wrong?
Thanks in advance.
Kind regards,
Wanda
PS. I've checked all threads that might have anything to do with this, but found nothing useful.

Hi Anuj,
thanks for taking the time to examine the file.
Answers to your questions:
1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
Installed Patch List:
=====================
1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
3. In theory the sysadmin should have run it, but how could I double-check this?
I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
also I tried the following values:
C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
true (I had no other idea)
Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
If I remove or comment the above line from tip.properties, then no transport log files are created.
I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
Changing it back to XML Gateway (and re-deploying) causes all original problems.
Regards,
Wanda

Permanent error in BPE inbound processing

Hi all,
We have recently migrated are XI scenarios to a new server.
In one of the file to rfc scenario whenver a file is processed i get the error in smq2: Permanent error in BPE inbound processing.
The chances of BPM and mapping error are less as the BPM is working live in another server.
What could be the other problems.
REgards
Edited by: Vinithra Iyangar on Feb 26, 2009 10:36 AM

Dear Vinithra,
Its highly improbable for this error to occur because of transports going wrong. There is one more case which i am sure is the cause why you are getting this error.
"This behavior is when we place the files in the respective folders both the files are picked up by the file adapter. Process instance is generated for BPM. First receive step is encountered and the file is received by it. But due to the wait step the second receive step is not open and hence the second file cannot be delivered to it. Unlike the first case, in this case as the buffering is deactivated the file is not buffered and hence the inbound processing of BPM fails for the second receive step."
Please check if something like this is happening.
Refer : /people/milan.thaker/blog/2008/07/04/delivery-modes-in-bpm
Rgds
joel

BPM Error Permanent Error in BPE inbound processing

Hi
I require some urgent help on this BPM issue.
We are trying to integrate SRM PO being directly sent to Vendors using HTTP. We are getting an error saying Permanent Error in BPE inbound processing. The scenario works like this.
SRM system would sent PO using the SRM Standard interface PurchaseOrderRequest_Out. We need to transform the message into cXML format and send it to the vendors using HTTP adapter. Using the HTTP response we need to trigger an email to the business process team.
The SRM interface is under the software component SAP SRM Server 5.5 and our mapping is being done in a common software component and for the vendor interface we have another software component. We have created a relationship in the SLD by making the common SWC as dependent software component to SAP SRM Server and Vendor Software Component. So in the integration repository we are able to get the interfaces for the SAP SRM Server and Vendor Software Component under the common software component. The receive step for this BPM is a copy of the standard SRM interface PurchaseOrderRequest_Out(as the standard interface is an asynchronous interface) and we would require an abstract interface for the BPM. We have checked the semantics for the BPM and its fine. The related ID development is in place. When the message is being triggered, it gives us this above mentioned error. When we go to the QRFC monitor we are able to check the details.
Regards,
Indranil

Hi Indranil,
     You don't see you BPM....
First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
and check if any error is listed there.
In order to check what is going on in your BPM you can trace it:
                  SXMB_MONI_BPE->Diagnosis Processes with Errors
                  SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
         Hope this helps you....
         Regards,
            Encinas.

BPM workflow "In Process"-Queue "Permanent error in BPE inbound processing"

Hi All,
I am trying to collect messages from 2 different interfaces into BPM( Integration Process).
when I checked in sxmb_moni , i found the error on outbound status & BPM workflow has stuck with status "In Process".
it is not showing any error in Workflow, how to solve the issue.
due to the above error, other messages are stuck in Queue stating "Permanent error in BPE inbound processing".
Please help.
-Jyoti

Hi Jyoti,
Goto T.Code swwl, in that clear all fields and choose from date as 1 month ago and try to execute. Then, delete all entries there. And re-execute your scenario.
In this case, please see SAP Note 1126656.
Please see the below blog, it might be helpful to you.
/people/henrike.kaiser/blog/2009/02/03/how-to-analyze-stopped-queues-in-xi-ccbpm
Regards,
Rajesh

BPM: Permanent error in BPE inbound processing

Hi guys...
i am having a problem in my scenario which is involving BPM.
The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing error.
yes..i searched on SDN and found resources like Note number 1126656
i checked al the steps which were earlier mentioned posts like:
SWWL: there are no entries existing
SMQ2: cleared the queues ,regenerated but still no luck.
My undertsanding is no work is being generated at all .
I checked BPM with F7 : its correct no errors
BPM has return code of 0 in sxi_cache
In ID BPM is latest and refreshed.
Is there any way i can overcome this problem.
Your inputs will be of real help.
Thanks in advance.
Regards,
Kiran.

My undertsanding is no work is being generated at all .
If you are getting the error for Source ---> BPM flow then there is a possibility that the ID objects (RD, Interface determination) are to be blamed.
1) Recreate these particular ID objects/ make some dummy changes
2) Activate and ensure that Cache is refreshed
3) Delete the entry in the queue (or delete the queue)....do this only if the XI system is not of Quality, production
4) some times the BPM cannot be triggered from sending a test message from RWB .... so make a testing from the source application .... this particular case has heppened to me and hence suggesting to you.
Regards,
Abhishek.

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

Permenant error in bpm inbound processing error in inbound queue of pi7.1

Hi Experts,
In E filling scenario in SAPPI7.1, iam facing a problem. i.e In sxmb_moni message monitoring, the message was schedule at outbound side.when i extend that, the message was stuck in smq2 with "permenant error in bpm inbound processing".can any one please tell me how to relove this issue.
Thanks & Regards,
Giri.

Hello
Check the note #1126656 BPE-TS: Permanent errors in the BPE inbound processing. This describes some possible causes and solutions for this error.
Regards
Mark

Permanent error in BPE inbound processing error

Hi guys...
i am having a problem in my scenario which is involving BPM.
The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing error.
yes..i searched on SDN and found resources like Note number 1126656
i checked al the steps which were earlier mentioned posts like:
SWWL: there are no entries existing
SMQ2: cleared the queues ,regenerated but still no luck.
My undertsanding is no work is being generated at all .
I checked BPM with F7 : its correct no errors
BPM has return code of 0 in sxi_cache
In ID BPM is latest and refreshed.
Is there any way i can overcome this problem.
Your inputs will be of real help.
Thanks in advance.
Regards,
Seshagiri.

Hi Praveen,
If the BPM goes in error due to "The incoming payload structure is incorrect (not matching message type structure of abstract interface)" , is there any work around?
Currently in my scenario BPM goes into error due to incorrect structure , error show up in SMQ2 . And the subsequent message also get stuck. What I have to do is to delete the queue in error and reactivate the queue manually.
Is there any way we can avoid this situation.
Thanks,
Pankaj

BPM getting failed with unknown error in inbound queue

Hi ,
I am using BPM for simple IDOC collection( time based collection) .Its working fine also .However once it fail we can see the BPE failed in inbound processing error in smq2 and status is system faliure.
on debugging we can see a unknown error in transformation step that error in conversion [NN]. to proxy Z_interface name ( the proxy which automatically get created for transformation step. ) data related issue.
When we check the same input data in IR its working fine in message mapping . we are unable to find any other error either in BPM or in the input data.
The most surprising thing is that when we deleted the message from queue and re-triggered the IDOC once again from SAP system then its worked fine .
Can any body kindly suggest what can be the probable reason of this .As we are afraid that if the same thing will happen in production what we will do without any expalination we can't delete queue and retrigger IDOCs there.
Regards,
saurabh

One option would be to raise an exception for such steps....in the Exception handler you can repeat the same step....in your case it will be the mapping (n:1) .....are you sure that the process failed in Transformation step and that the data was correct....i mean all the 5 IDOCs were sent as an input to the mapping?
Can you ensure that during this time there was no connection issue between the BPM and the mapping runtime (IE)....may be you can check with your BASIS.
Regards,
Abhishek.

"Permanent Error in BPE inboubd Processing" if payload is incomplete

hi all,
I have an BPM scenario and when payload is wrong or some field in the payload is missing i am getting "Permanent Error in BPE inboubd Processing" error. I have searched on SDN for same and found two blogs which might be helpful
/people/henrike.kaiser/blog/2009/02/03/how-to-analyze-stopped-queues-in-xi-ccbpm
/people/shabarish.vijayakumar/blog/2005/12/07/transformation-error-and-still-stuck
As per blog : /people/henrike.kaiser/blog/2009/02/03/how-to-analyze-stopped-queues-in-xi-ccbpm,
when i execute the function u2018Display Traceu2019
Data is coming as: 16 31 21.04.2010 - 12:06:37.0810000 DATA SWF_INB EXCEPTIONS WF-BATCH X Error during start of process of type WS90100001 by message 0050569F4A4E1DDF93A20375C360F54F WS90100001 XBQO$PE_WS90100001 0050569F4A4E1DDF93A20375C360F54F
when i execute the function u2018Simulate Message Delivery' it is coming as: Result of simulation: Message starts a new process
What is the meaning of this?
I have a transformation step in BPM only. Is there any validation of data performed before message is passed to BPM?
Thanks,
Mayank

Hi Maynak,
Whenever you will put incorrect data or missed any mandatory field to be created on target side then this error will occur .
Take the input and chek in the mapping test of IR and correct your source message.
In this situation we can do these two things if we are not in Production server.
1. Delete the errored queue and re trigger the message after correcting the source XML
2. Even if correcting the mapping error also again its not working then go to SWWL and delete all the process instaces and again re trigger the message .
It will work. As per my knowledge in PI7.0 the XML validation option is not available .
Regards,
Saurabh

Permanant Error in Inbound Processing in BPM

Similar Messages

Maybe you are looking for