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?

Similar Messages

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

Error getting the server-side naming service functionality

Hi all,
we are currently setting up the CTS+ activity based transport scenario. Everything seems to be working fine, however, we have to import each transport twice...
Before I go into detail in the error we get I will first describe our landscape. All the configuration we did was done in debate with SAP.
We use the SAP Solution manager (ehp1 SP 4) as the CTS+ server as recommended by SAP and have an NWDI system of which we only use the components DTR and CBS (since CMS is not used anymore in the activity based transport). We have defined three logical ports/RFCs. CTSCONFIG points to the NWDI system. CTSDEPLOY is running on the java stack of the solution manager and is only used for portal content (=epa) transports. CTSDEPLOY_DI is pointing to the NWDI system and is used for all NWDI (=dip) changes. The NWDI is running ehp1 SP3.
In STMS I defined all the non-abap systems (and configured them to use CTSDEPLOY_DI) and created the following transport route:
upload system (IMP) -> DEV -> ACC -> QAS -> PRD
I first attached the used dependencies in a transport request (SAP_BUILDT, EP_BUILDT, etc) these imported just fine. Then I did the SCA files which contain our custom code. I extracted these from the assemble step on our current NWDI system which will be removed as soon as we switch to the new CTS+ environment.
When we import the transport into the runtime systems then we see the DTR and CBS be filled sucesfully for this specific system. However, the transport request itself always fails with errorcode 12 and the error is:
Error during export service registration: Error getting the server-side naming service functionality during getInitialContext opera
tion. com.sap.engine.services.jndi.persistent.exceptions.NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
Error in execution of Web services CTSDEPLOY_DI , exception is cx_cts_file_import_failed
File import canceled
When we then reimport the same transport it will go the second time fine. This is no problem during the setup but will not be workable when we go live ofcourse. Is there anyone who had this issue before as well and have a solution for it?
Kind Regards,
Nico van der Linden...

Hello Nico,
I would need the java trace files to get more info on this issue, but you can start troubleshooting this error with these notes:
#1172252: CTS+, 'attach file': Troubleshooting Guide;
#1003674: Enhancement for non-ABAP systems in CTS;
#1155884: CTS+, configuration 'close coupling': Troubleshooting guide;
Pay special attention to parameter NON_ABAP_WBO_CLIENT, whether it's correctly set on your CTS+ system(s).
Note #1003674 is a must for any CTS+ systems to work properly, as well as having an updated version of the transport programs (tp and R3trans).
Lastly, note #1155884 goes through some JCoException exceptions that commonly take place during CTS+ transports. But again, you need to check the underlying trace files to find the root cause of your issue.
I hope this information helps.
Best regards,
Tomas Black

BPM : Message scheduled on the outbound side

Hi
I have messages in SXMB_MONI that have been received into my BPE. They have a status flag ok (chequered flag ) but the Outbound Status is green (message scheduled on outbound side).
The BPE would have finished by now ...been in Message Scheduled on Outbound side for the entire day now.
What has happened ? I have no error - nothing !
(there are no entries in SMQ2, nothing in SXMB_MONI_BPE in error etc etc or Short Dumps)
Please help.

I posted an OSS note on this - so answer from SAP.
Solution is to delete the old entries via RSWWWIDE report (which could also delete work items that do not have a final status.) I ran this for everything not COMPLETED.
When I send another message in - it worked fine. So the fact I had a stalled WF a week ago was affecting any new one coming in.
Drilling down into the message in SXMB_MONI from the PE I could see an Exception Handling in the MergeandSendBlock - no error given - but it did have a time of a week earlier.. anyway then in the ST22 Dump I could see wf-batch with runtime error MESSAGE_TYPE_X_TEXT.
I feel this is very poor design on the BPM processing ! oh well.
See also
#Note 836092 - Archiving/deleting work items in the XI
PS Thanks to Sudhir earlier on... You nailed it - but at that stage I did not know what you mean so did not consider this - as I had no idea what affect running that transaction would do.

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.

Error in the outbound Que CIF 'vesrsion 0 isnot maint for the fis yr 2015

Hi ,
I sending the Process order through CIF , there is out bound que for CIF while executing the transfer i am getiing the error
' Version 0 is not maintained for the fiscal yr 2015' I j=have check the production version validity ddate & version 0 in the controlling also .
Plz let me know the reason for error .
Regards
satish

Dear Bramhankar Sir ,
Thanks for the reply ,
But sir , i have check in the OKEV transaction , in that o version is maintained for the year up to 2010 , but why is is showing me the 2015 in the error. fromwhere it is picking 2015 fiscal yr ?
Sir i will reply back once i will check the SAP notes
Thanks for the valuable reply .
Reagrds
satish
Edited by: satish kapartiwar on Nov 10, 2009 7:13 AM
Solution :-
We Rerun the Que & refresh it , it works ...... I think the issue with scheduling .
Anyway thanks for the help .
regards
satish
Edited by: satish kapartiwar on Nov 11, 2009 11:00 AM

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

BPM Mapping error in SXI_MONITOR Message scheduled on outbound side.

When I try to process this message i get an error.
Message scheduled on outbound side.
I am using a BPM.
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Using EOIO in the send step Queue Name: cases
If I remove MI_TRANS2_BPM the message reaches the bpm, but with both transformation in the BPM the message gets an error in the queue where I get a green flag 'Message Scheduled on the outbound side"
This BPM was working on Friday but hasn't worked since. There have been no changes to the my development XI environment.
Some things that i have tried: Clearing the Queues (smq2), Redoing the entire scenario, clearing cpa cache.
Please help.
Thanks
Chirag

Hi,
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Any specific need to have the above design pattern....you can also try:
MI_Receive_BPM -> MI_TRANS_BPM -> MI_TARGET
You can use the message that you initially receive and apply all the necessary transformation on it and the map it to the target structure....
As you mentioned that if you remove MI_TRANS2_BPM your message is executed successfully...it means that the BPM transformation 2 is waiting for some event / Message....
If you need to go by the same design then you can follow the below steps to resolve the problem:
1) Check the return code of BPM in SXI_CACHE...it should be 0
2) Check for any errored instance of your BPM in SWWL (as mentioned in above posts)
3) Open the corresponding Queue and see for the messages stuck in the Queue....your Queue may be blocked....your BPM will be using a particular Queue and if any message is stuck in the Queue then all the messages that follow will get stuck in the Queue....
Now if it is only your BPM that is using this particular Queue then Delete the Queue (applicable to development environment....do not try in QA or Production environment)
4) In SXMB_MONI click on "PE" and open the Graphic Flow to see where actually your BPM has failed (possible only if the message has entered the BPM.
Regards,
Abhishek.

Two comm channels at the PI outbound side

Hi All,
Can we use two communication channels at the outbound side.my scenario is to send a file from database system to SAP. I know that we can use JDBC adaptor at the inbound (PI receiving side) and FILE adaptor at outbound (PI sending side). at the same time when we dump the file onto SAP application server , i need to send workflow notification to relavant department agent informing about the file location.
Could anyone tell me how we are going to configur this scenarion.
Regards
Sre.

>
sre wrote:
> Hi All,
>
> Can we use two communication channels at the outbound side.my scenario is to send a file from database system to SAP. I know that we can use JDBC adaptor at the inbound (PI receiving side) and FILE adaptor at outbound (PI sending side). at the same time when we dump the file onto SAP application server , i need to send workflow notification to relavant department agent informing about the file location.
>
> Could anyone tell me how we are going to configur this scenarion.
>
> Regards
> Sre.
so your scenario is
JDBC -> FILE & WORKFLOW Notification
The answer is yes. you can add as many receivers and its corresponding communication channels.
One question, how do you want to send the WORKFLOW Notification?

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

Errors on the Outbound side?

Similar Messages

Maybe you are looking for