Message has Error Status Outbound Side

Hi All,
I have one question.... we procssed one file from ftp it should creates Idocs in R/3 side we developed this scenario using BPM....it processed successfully inbound side but in Outbound side it is showing Red Flag (Error Meaase : Message has Error Status Outbound Side) and its not creating IDOCs in R/3 Side but in Process engine all steps completed Sucessfully and created Idocs in XI....i tried so many ways...like in Queues and Refreshed Cache and checked RFC connection in Both ways and checked passwords in communication channels.... i could't find any this....if any body help me on this....it would be appritiated.
This was i am testing on Test system i got this type of problem but in Development box it is working successfully we are using the same fuctionality and same code also i don't know why its happening.
Thanks,
Sudheer.

Hi,
Where are you find the Error and
> Process engine all steps completed Sucessfully and created Idocs in XI....
Can you explain in detail
Regards
Sangeetha

Similar Messages

IDoc error :'Message has error at outbound side'.

Hi Experts,
am working on JMS-->IDoc, where TIBCO sends MBGMCR01 IDoc to ECC through XI .
in SXMB_MONI : shows red flag in outbound:with the message as 'Message has error at outbound side'.
please, suggest to solve the issue.
thank you,
MK

Hi
Have a look this
Message has error on outbound side in sxmb_moni
BPM - Message has error on the outbound side
Reprocess a message with error at outbound side

Message has error on outbound side in sxmb_moni

Dear All,
I have a query related to sxmb_moni messages.
Scenario : FILE - XI - IDOC
In sxmb_moni, message is successfully processed by XI but it is showing error " message has error on outbound side".
My questions are:
1)Is it possible to restart the message . When I tried to restart the sucessful message with error on outbound side it showed me message " You cannot restart xml message".
2)I tried to analyze error for outbound side using SM58, it showed me message "No connection to database,session terminated" .
Can anyone please advice what could be the reason for this .
Thanks & Regards
Prabhat

Hi Prabhat,
the message was send to the IDoc adapter. The error occures there.
Control, if the send XML can be translated to IDocs (use a message mapping).
Control, if the SM59 destination to R/3 is working.
Conrol, if the communication channel is customized in the right way. Control, if the port is customized (transaction IDX1).
Also the metadata for that IDoc should be in IDX2, that should happen automaticly, if not, assumedly the destination is not working.
Regards,
Udo

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

SXMB_MONI - Message has error on outbd. side

Hello,
We have occurences when interfaces appear to be successful in the SXMB_MONI monitor for processed xml messages. The status flag = successfull. But there is a column just in front of "Message ID" that also has another status flag.
When this flag is red and you hover over it, it shows the following "Message has error on outbd. side". How can we locate a corresponding log and get some more detail behind this message? We cannot seem to connect the dots between this red flag and a corresponding log entry to give us details of the problem.
When it says "outbound", which system should we be examining (PI or the receiving system)?
Thank you,
John

Hi,
Select the Messge in MONI and MenugotoOutbound Channel monitor
Double Click on the Idoc Number, this will take you to SM58 Screen
Here you can be able to seee the reason why it got errored out at Outbound Side.
Now in SM58Edit-Execute LUWs
Selection screen will appear and here select all the check boxes irrespective of any Error and select the date that when these message got into Error state and all.
And Now Execute that either in Foreground or in Background
This will execute all the Errored messages at Outbound side will process and the Idocs will reach to R/3
XI : How to Re-Process failed XI Messages Automatically
Regards
Seshagiri

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

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

IDoc error on outbound side

Hi.
I'm setting up a communication with (JMS adapter -> XI -> IDoc adapter).
No w to the problem. When we send the message with the IDoc adapter we get the following error.
Message has error status on outbd. side
We can see this message when I put my cursor over the red flag in the outbound status column in SXMB_MONI.
I do not think there's anything wrong with the adapter because we are using it to send an other IDoc and that IDoc gets processed correctly to the target system.
What can cause the error on the that I get above?
BR
Kalle

Hi,
go to details of that transaction and check the error that caused idoc in outbound status failure...
an error tab can be seen in the outbound binding pipeline entry of that transaction and check the error caiused that
Rajesh

Cancel or Reprocess BPM message with error on outbound state

I have a BPM scenario, IDOC comes from R3 and triggers a BPM. The BPM has a fork step which sends the message across 4 branches. Each branch has its own steps. Now, the problem is the IDOC has come and has trigerred the BPM but has errored on outbound side. The first step in each branch is a mapping step and the BPM has failed at this due to Jco communication failure. This has been fixed now. Now I need to reprocess this message, but can not restart as it shows succes message in inbound side.
I have to re process this message, but how?
Regards,
Jaishankar

Jai,
I dont know whether it is the correct appraoch.
Have a look at the transaction SWWERRE_DEBUG
Regards,
Sudharshan N A

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

Message has Error Status Outbound Side

Similar Messages

Maybe you are looking for