Message has a error status on outbound side

hi all
when iam doing bpm alert , in sxmb_moni iam getting the message
"message has a error status on outbound side" error flag is coming.
Regards
Raju

HI,
Check receiver agreement and reciever determination.
Regards,
AKshay.

Similar Messages

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

BPM Scenario: Message has error status on outbound side

Hi All,
        I am doing one BPM scenario. In my scenario i am collecting 12 different type of idocs in BPM and bundling these idocs and sending these to the 12 different files.
        If i send 12 idocs from the R/3 then my scenario is working perfectly fine. If i send less than the 12 idocs that time i am getting the error message as "Message has error status on outbound side" with red flag.
           Can you please explain what minght be the problem. I have already checked in SM58,SMQ1 and SMQ2.
Thanks & Regards,
Purushotham

Hi Nutan,
        I hv configured my scenario as follows
1. Start
2. Block ( Deadline and Control step for cancell the process)
   3. Fork(Necessary branches 12)
      4. Loop(12 loops)
          Under loop
          a. Receive Step
          b. Container Operation( For count)
          c. Container Operation(For append)
5. Fork( Necessary branches 12)
    6. Transformation
    7. Send
8 Stop
This is my scenario. In the first Fork step i am checking end condition as total number of idocs is reached then i am sending all the data to the target system. If the idocs are not reaching with in 1 hour then i am cancelling the process.
        Now can you please tell me what is the problem.
Thanks & Regards,
Purushotham

Message has Error status on outbound side - in ABAP inbound proxy !!

Hi All,
One interesting question for you guys. I have got one of the scenarios like File to ABAP inbound proxy. Message are going properly, no errors in receiving system. But on PI moni I can able in "outbound status" column in red colored flag. No all the messages couple of them with u201CMessage has Error status on outbound side ". Why please?
Regards
San

Hi ,
Please check whether the correct data is coming from sender side . and check the j2ee engine runtime parameters.
Cheers,
Meera
Edited by: MeeravaliDudekula on Oct 18, 2010 2:36 PM

Error status on outbound side

Hi experts,
I am in JDBC to IDOC scenario and right now i face following error in SXI_MONITOR (black and white flag in status field BUT Red flag in outbound status):
"Message has error status on outbound side"
This is a heavy interface (up to 8MB) but, in the past, we did not receive this error. I saw that there is an entry in SM58 from the PIAFUSER that says "Lock table overflow"
Thus, I set the parameter enque/tablesize up to 8192 MB but after restarting the system it did not work either, a new entry in SM58 is shown.
If i analyse the runtime tab of the response of the message i can see
<SAP:AdapterStatus>007</SAP:AdapterStatus> --> for an erroneous interface execution (payload=7,2MB)
<SAP:AdapterStatus>006</SAP:AdapterStatus> --> for a successful execution (payload 6.5 MB)
Can anyone plz, help me on this?
I cannot explain why we did not face this in the past.
Can you please explain how the lock table works? and what does the overflow means?
Thanks a lot in advance and best regards,
David

Hi Sai,
Ive checked what you mentioned but cannot see the point there. Maybe you can help me:
Enqueue Operations 847
rejected 17
Error occured 0
Dequeue Operations 604
Error occured 0
Dequeue All Operations 661
Cleanup Operations 0
Backup Operations 1
Read Operations 21
Compress Operations 0
Verify Operations 0
Records written 58408
to the backup file 2
Maximum Number of Lock Owners 58406
Maximum Fill level 4
Current Fill Level 0
Maximum Number of Lock Arguments 58406
Maximum Fill level 14
Current Fill Level 0
Maximum Number of Lock Entries 58406
Maximum Fill level 14
Current Fill Level 0
Update; Fill Level at Maximum 1
Current Fill Level 0
Time in Lock Table /Seconds 0.073970s
Wait for Lock Table /Seconds 1.691441s
Time in Lock Server /Seconds 0.000000s
Besides, i dont think it is gonna be a matter of disk spaces as all of them have, at least, 3.0 Gb of free space.
Any other clue? I increased the enque/table_size up to 65 MB and the lock table overflow in SM58 still remains!!!
Thanks a lot and best regards,
David

Message has error status on outbound side

Hi All.
I'm doing file to file scenario.configured everything, showing success message in SXMB_MONI but with error flag at outbound status
My R/3 system is : SAP ERP Central Component 5.0
But I'm unable to find the related product for this system from the following systems
SAP R/3 4.5, 4.6 and 4.7version
I have selected : SAP R/3 ENTERPRISE, 47X110 IDS on idesecc
my question is whether i created technical system wrong or any other mistake i have done for this problem?
pls suggest a suitable solution for my problem.
thanks,
Manoj

Hi,
My message contains following information.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000036231</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>CREMAS03</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>CREMAS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPTX1</SAP:SNDPOR>
<SAP:SNDPRN>LS_SAP</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPRD1</SAP:RCVPOR>
<SAP:RCVPRN>LS_SAP800</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS />
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>0000-00-00</SAP:CREDAT>
<SAP:CRETIM>00:00:00</SAP:CRETIM>
<SAP:ARCKEY>B07DF8A0A03811DBADD00003BAF07785</SAP:ARCKEY>
</SAP:IDocOutbound>
I'm unable to find where is this SAPTX1 .
Actually i created SAPRD1 port in XI pointing to R/3 and SAPXD1 port in SAP pointing to XI
SAP logical system as LS_SAP800 but idon't from where LS_SAP is coming
Thanks
manoj.

** BPM Error - Msg has error status on oubound side

Hi Friends,
I am doing BPM scenario. (Receive Step --> Transformation Step --> In Block (For each) Synchronous Send Step ). That's all BPM design.
We have created Server prox (inbound Proxy) in ABAP, it receives PO details and return Sales order no. Coding has been written inside Proxy. If we test Proxy in ABAP, it is working fine.
The required PO data we pass from JDBC. Receive step receives the whole message (It may contain 1 or more PO). In Transformation step, we split message using multiline checkbox( One message per 1 PO).
Message is processed successfully upto this step. In the Synchronous send step, it throws an error.
In SXMB_MONI, 3 messages are generated. In the first message itself, in the outbound status column 'Red Flag' is coming, (but processed successfully). The error is 'Message has error Status on outbound side'. Inside the message 'PE' adapter is in grey color.
So, what could be the problem ..?
Kindly reply, friends.
Kind Regards,
Jegatheeswaran P.

Hi Jegatheeswaran,
Take the Message after transformation and try to test your synchronous service with this message,
if u r using any web service you can use Altova (XML SPY) to test your service with the data after
transformation.
If it does not show any problem then try to see you have build your BPM Properly (Press F7 to test For any syntactical error).
You can also go to SXI_CACHE to see if your Workflow does have status 0 .
To get Exact error Message . Click on PE ->goto->ThechnicalSetting->select synchronous call->click on content tab->and go on navigating you will find detailed exception.
Reward Points IF Helpful
Thanks
Sunil Singh

Message has error status on outbd. side (error in Moni)

Hello All,
Iam doing soap to idoc scenario, the scenario was working fine since long time....but yesterday we had an issue...we can see the message was sucessfully processed in XI monitor and RWB, but idoc not got created in sap ecc system.
when i checked in moni one column called Outbound status is in error status and the error is message has error status on outbd. side.....i checked the idx1, idx2,sm59......all settings are fine.
How to reslove the issue, please help me.
Thanks and regards,
Chinna

Hi
Please check the below i think your problem will solve
Hi,
Check whether IDoc was created:
1. Execute Transaction WE05; enter correct date/time parameters etc. If IDoc found in failed status, open status records folder and double click on the failed status records to get error message.
Check Whether IDoc is received by the Receiver:
2. Execute Transaction WE05; enter correct date/time parameters etc and verify if the IDoc was created or not and if IDoc is in a successful status or not. If the Idoc is in Status-30(Yellow), you can push it again through Transaction BD87.
3. If the IDoc is located and status is successful but receiver has not received the IDoc, Execute transaction SM58 to determine if IDoc is stuck in the ALE/RFC layer. If entries exist in SM58, look for Message Type
4. If message type exist and Run the Program "RSARFCEX". If after the RSARFCEX program has ran and IDocs are not in SM58, issue should be solved. Validate in receiving system via WE05 that the IDoc was received or not.
5. If IDoc is still stuck in SM58, check RFC connection. Go to SE37, enter function module RFC_PING. We need to have access to SM59 to test the RFC Connection.
6. After an issue has been resolved and/or you need to process an IDoc, besides processing IDocs via programs, you can also process IDocs via Transaction BD87.
Thanks ,
Meeravali Dudekula

BPM - Message has error on the outbound side

I get this error 'Message has error on the outbound side" . I am using IDOC - BPM - JDBC. I checked SXI_CACHE and I see ret code 99 for this Integration Process. I tried to activate it. I see an error saying that ZCUST_NUMBER is not a component object of PAYLOAD. I have this context object defined on the Abstract Message Interface built to store the IDOC.
Any ideas are helpful

Michael,
The program outputs a returncode = 99 during the cache refresh of an integration process (ccBPM), with an error message that says that 'xxxx' is not a component of the 'PAYLOAD' data object.
If you are getting the above error, check OSS NOte 890760

BPM Error: Message has error status on outbd. side

Hi,
BPM overview:
Receive Step -> Transformation Step (1) -> Send Step ASYNC (1) -> Send Step SYNC (1) -> Transformation Step (2) -> Container Operarion Step (1) -> ...
Error Message in SXMB_MONI: Message has error status on outbd. side
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MI_BPM_TRAN_EMP_DETAILS_FILE_OUT_ASYNC*</Trace>
<Trace level="1" type="T">select interface namespace urn:tranbpm</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface AI_BPM_TRAN_EMP_DETAILS_FILE_ASYNC*</Trace>
<Trace level="1" type="T">select interface namespace urn:tranbpm</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</Trace>
I am don't any Interface name MI_BPM_TRAN_EMP_DETAILS_FILE_OUT_ASYNC* in my scenario, the actual interface name is MI_BPM_TRAN_EMP_DETAILS_FILE_OUT_ASYNC does BPM adds a '*' at the end of the interface name.
In the workflow log it shows that "Transformation Step (2)" has error. I am using multimapping in the transformation step.
Any help would be greatly appreciated as I ran out ideas to fix this issue.
Thanks in advance.
Sarvesh

The issue was with the step "Transformation Step (2)" and I fixed it in the mapping.
When using two send steps "Send step (1)" & "Send step(2)", BPM is executing the second send "Send step(2)" before it completes the first send step "Send step(1)". The first "Send step(1)" inserts the data into the database table and the second "Send step(2)" retrieves the data inserted in the first send step.
If I insert a "Wait step" between the 2 send steps it working. Can anyone explain how the send step in BPM works.
I did post the same question in "Exchange" forum also so that it can be view by more people.
Thanks,
Sarvesh

Message has error status on outbd side

Hi,
I am doing File to IDoc scenario, in SXMB_MONI i am getting the following error "Message has error status on outbd side". I am not using BPM and this interface was working fine earlier .
Any clues!!!!!!!!!!
Regards
Swatantra

Hi Vijay,
Cross check whether you have done these:-
SLD-
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps.
Regards.
Praveen

Errors on the Outbound side?

Hi All,
Iam working on SOAP to IDOC scenario....when i tired to test the interface from RWB> component Monitoring-> Integration engine---> test messages.
i can see in the Moni, the error in Outbound status.....data is not passing to ERP system.
i follwed the blog and done the same as mentioned in the blog.....now problem is when i go to SWWL transaction i cant see any entries in that. Please help in this.
Blog i followed : http://www.riyaz.net/blog/xipi-dealing-with-errors-on-the-outbound-side/technology/sap/9/
Regards,
Chinna

when i go to SWWL transaction i cant see any entries in that
are you using a ccBPM? SWWL is used when a BPM entry in error needs to be deleted....the blog does not open for me.
when i tired to test the interface from RWB--> component Monitoring---> Integration engine---> test messages.
Did you try testing the scenario from SOAP Test Tool?

Why am I receiving the "Unfortunately, Messaging has stopped" error message and how do I fix it?

Why am I receiving the "Unfortunately, Messaging has stopped" error message and how do I fix it?

I am so upset. Please read my messages from my postings. This has nothing to do with SIM Card, Hard Reset, Apps, Google Gmail Account, nothing. I have gone thru all of this and NOTHING has fixed this. I went to the store today and spoke to the manager on duty. He said he had to try and duplicate the problem before he could help me. I showed him "screen captures" I did, told him it's out here on the board, etc. etc. Needless to say I ended up coming home with the same phone, "he" erased the phone and started over again. Well guess what, it's not a error with "MY" Gmail account being corrupted because if that is the case Mrs. Hayden14 has a bad Gmail account too. If you guessed it, the phone just crashed again! I was able this time to capture a report with ALL the history in it and saved screen captures to PROVE to him this is not a joke. Even the report says "Crash". This time it was something else I don't even or ever have used. I have also wasted over a day , yes a full work day on this without question.
I have had to get the run around for the last day. This is totally ridiculous, including them putting me on hold for 55 min. Oh, that's another funny story. Anyways, tomorrow morning I am going to the Verizon store one last and final time and I hope they decided to do the right thing and give me a phone that does not crash and works. It would be handy at work for me, especially where I work at. I hope hope hope someone listens to and helps me. I would love for them to see me walk in, take my phone and say to me were going to get you another phone, hand it to me, see if it works and prove it's the device. I don't hear anyone having this issue on other phone types so sounds like its the phone type.
I have had 3 phones now in the matter of 2 weeks. I am sure the FedEx charges will add up to a cost of a new phone at some point and start to outbalance your requirement to give me the same phone when it has the same problem.
Can't wait to see what happens tomorrow.

"Unfortunately, Messaging has stopped" error keeps popping up and text messages are not being received on Droid Maxx I got less than 2 weeks ago.

I upgraded to a Droid Maxx about 2 weeks ago and all seemed well. Last Friday, I started receiving an "Unfortunately, Messaging has stopped" error message randomly--sometimes when I was writing a text, sometimes when I would open other apps, there was no rhyme or reason to when it would occur. Now it also appears that I am not receiving some of my texts. I called Verizon Support who told me that they are experiencing this problem on several devices and that she was going to forward me to someone for help. 20 minutes later, no one had picked up and I had to leave. So I thought I would try here to see if Verizon has come up with a fix for this, if I should get another phone, or if they are working on a software update or something. Help, I really liked this phone until now!

Hello,
I am using the messaging app that was preloaded with the phone, the green face icon. I do not have an "Android Keyboard" app, but I have cleared the cache on the "Messaging" app, several times. I have also gone to the Verizon store where an associate did a soft reboot, telling me that would work. A very short time later, the error message started appearing again--so this did not work either.
The error message comes very sporadically. Sometimes several in a few minutes, other times not for hours.

'unfortunately messaging has stopped' error

Hi all, I have bought an Xperia Z3 compact phone few days ago. And since yesterday, I get the message 'unfortunately, messaging has stopped' as soon as I try to open the messaging app. It is really annoying, as this is a basic function of a phone. I have tried restarting, force closing the app, updating with sony udpates, and clearing all data. Any ideas how to repair this?

well, It seems my problem has been solved miraculously! Here is what I did: Following some suggestion on another forum to use another app for messaging, I installed the 'GO SMS PRO' to use instead of the default messaging. The new app asked me if I wanted to have it as default instead of the 'messaging' app, and I said yes. Then by mistake I clicked again on the messaging app icon on my phone, the messaging also asked me if I wanted to use messaging app instead of the GO SMS PRO to read my messages and I said yes. AND BINGO all of a sudden the 'Messaging' app is working again! I guess moving to the new default app has changed some thing that was giving the error. Anyways, I thought to share it with you, in case someone else has the same problem

Message has a error status on outbound side

Similar Messages

Maybe you are looking for