BPE outbound status

Hi,
in transaction SXI_MONITOR for same BPE process the column Outbound Status has the status "Message being Sent", but the BPE process was completed and all messages were processed and delivered.
Because this status ( Message being Sent ) in BPE process?
tks.

HI
All BPM use the PE that can be the reason for the status. Moreover use SXMB_MONI_BPE to monitor BPM's
Thanks
Gaurav

Similar Messages

BPM outbound status?

Hi all,
I am building on a simple scenario using BPM (S/A bridge). At first it was working fine, but after some test cases (also wrong), I canu2019t make it work again.
I always get the initial message stuck in queue XBQO$PE_WS90000001 with error u201CPermanent error in BPE inbound processingu201D. I delete then these queues manually. In SXMB_MONI I see error "Timeout condition of pipeline reached", and a lot of messages that have a green or red flag under Outbound status.
My questions are:
What exactly means the outbound status in BMP?
How to get rid of this green/red flags? Or they can stay there with no harm for next messages, but what else can be the reason for errors?
Thanx, Janos

But I have one more question: In which cases I should go to SWWL to solve problems? I mean, is this a standard way, or
it is a u201Cdirty wayu201D to be used only in emergency? (I donu2019t have any error handling implemented.)
It is the dirty way
Having an error handling is always beneficial...just think how much time consumption will be there in actual Production environment if such a thing happens
With error handling not only the BPM will remain unstuck but also the Support folks will come to know why and where the error occured.....my personal opinion and experience
Update:
You just need to delete the Error instance of the BPM from SWWL
Regards,
Abhishek.
Edited by: abhishek salvi on Jul 31, 2009 1:55 PM

Outbound status to delete XML messages in PI

Hi,
we are using a deletion process in PI wiith the pg RSXMB_DELETE_MESSAGES but the XML messages with a outbound status = 1 cannot be deleted. It seems that the pg SXMS_REFRESH_ADAPTER_STATUS permits to change the status to 6 but does not work for me.
So, I need guidance. For information, we condigured the deletion period (10 days).
Thank you

Hi Pascal,
You should try to manually confirm the messages (in SXMB_MONI - Cancel Processing of messages with Error CTRL F8) and then run all the deletion jobs again.
Please see Note 872388 and 820149 for details. Following is the relevant portion from 872388:
"Check if there are asynchronous messages in error status.
Asynchronous messages in error status are neither deleted nor archived.
This behaviour is different to erroneous synchronous messages which get
deleted after their retention period (see step 5) has expired).
Asynchronous erronous messages, however, must be cancelled and then be
archived. You can either use transaction SXMB_MONI, search for erronous
messages and manually cancel them. Or you can use the report provided by
SAP: RSXMB_CANCEL_MESSAGES. Should you decide (for non-productive
systems only) that you would like to delete these manually cancelled
messages, please use note 820149."
Regards
joel

Outbound Status in the Monitor

In SXMB_MONI when i check for messags status there are several messages struck with Outbound status = Message Scheduled on outbound status
MY scenario is Idoc - XI/BPM - File . I'm collecting all Idocs in BPM before sending out to file.
Any idea what I have to do.
I did checked in SMQ2 and all queues are empty now.
Thankx

Did you check all the steps in BPM during runtime ? Is all the steps are showing green in the Graphical View of workflow instance.. I think some of the steps are having problem..
Also which collectPattern you used in the design ? Is the end condition is satisfied ?
Go to Transaction SWEQADM ( to check if the event queue background job is running.
If everything looks ok, test the syntax for the BPM in the Repsotiory, re-import into the directory and re-run the scenario..
If it goes into qRFC monitor when you click on PE in SXMB_MONI, then I think BPM is not triggered ..
Check did you configure correct Receiver Determinations ?
i.e Idoc ->BPM
BPM->Target
Also test with one idoc first..Also make sure that Idoc data is coming to XI correctly. Check the Sender Interface, Sender Service, Reciever Interface and Service in SXMB_MONI so that you can understand which is message has come to integration server etc..
Regards,
Moorthy

Outbound status locked?

Today we sent thousands of idocs from sap systems to non sap systems, and from non sap to sap.
A strange thing happens: a lot of idocs that go from sap no non sap system, has the status "message being sent" on the outbound status (in the sxi_monitor TC), and the other idocs doesnt have this problem. They seems to be stacked in BPM, and they are passing very very slow (half an hour per 10 idocs).
How can I change this or what should I do? Because its all stacked here un Prod.
And when I refresh the cache, it appears some errors on idocs and I cant resend them because they dont appear in the TC SWPR and in the Runtime Workbench gives me the next error:
"Unable to schedule 1 of 1 messages for processing; update the status"
So I cant resend them, or maybe they were sent but I cant see that in here.
Well, if someone can help me I'll be very very happy
Thanks!!!

Hi Claudio,
>
> A strange thing happens: a lot of idocs that go from sap no non sap system, has the status "message being sent"
>
Message being sent means the messages are processing through queue and you can check these messages in queues SMQ1 and SMQ2 also execute the queue in error if any and monitor the queue if it is processing very slow you require tuning.
>
So I cant resend them, or maybe they were sent but I cant see that in here.
>
For this you can check in SXMB_MONITOR --> Advance Selection Criteria --> Out Bound Status with various options.
May be you can find some messages there.
Also Check in SWEQBROWSER , Check the box other events and radio button all events.
If you dont find any messages there then in moni tcode click on PE and check the BPM steps.
Thanks!

SXMB_MONI: Outbound Status Red (Need Err Message Alerts)

What is the best way to setup meaasge alerts in XI for a red flag in SXMB_MONI in the "Outbound Status" field? We currently have error messageing setup in ALERTCATDEF that will send an error message when the "Status" field is a red flag but I don't know if there is a way to point it to the "Outbound Status" also. We use the following short text in ALERTCATDEF for notification:
System: &SXMS_ERRSRC_SYSNAME&
POS XI Message ID:    &SXMS_MSG_GUID&
POS XI Error Category:    &SXMS_ERROR_CAT&
POS XI Error Code:    &SXMS_ERROR_CODE&
I am thinking tha ALERTCATDEF will only send an alert when the "Status" field is red flag, and may not be possible to point to the "Outbound Status" field".
     Any suggestions?    Thank-You.

Bill,
2 questions here,
1. Are alerts also triggered for outbound errors?
Am not very sure but if i remember correct ,in one of our scenarios when there was an error in SM58 while posting the Idoc ( error on outbound side in MONI ) no alert was triggered. I dont have any access to a server where alerts are working and so would just like to confirm if alerts are triggered also for Outbound side errors or are they triggered only for inbound errors?
2. If they are triggered for both, then wouldnt selectin NO RESTRICTION in where did the error occur suffice?
Regards
Bhavesh
Message was edited by:
        Bhavesh Kantilal

Idoc Outbound Status Error

Hello everybody,
I have an interface that sends and Idoc to an R/3 system and I have it on Status "Processed" but in Outbound Status "System Error" with red flag in SXMB_MONI in PI, but I can't see no dumps neither in PI or R/3, so message in queues I turned on the trace in ST01 and I can't the RFC call that PI should do to R/3 to send the Idoc, I think is about roles and security oft he communication user that exists in R/3, but I'm not sure what roles it should have to allow the Idoc to go thru, any suggestions?, thanks in advance.
Regards,
Oscar

You dont' have enough permission. SAPALL try with..
check this one SAP Note Number: 460089
Edited by: Anand on Dec 4, 2008 7:03 PM

CcBPM: Message outbound status, Message being sent

Hi
I have a message with status flag message being sent at the outbound status PE since 30 days. Because of this message many messages got blocked with scheduled on outbound side status.
I tried to delete work items related to the message in SWWL, but i am not able delete.
Please suggest solution
Regards
Subba Rao

Hi velidi subba rao,
Please go to SMQ2 and right click on the entry and Select Save to LUW. It saves it to SMQ3. You will be able to reprocess it from there.
Give it a try and let me know if it worked. Also just release the queues once you have saved the message that is stuck.
Regards,
Jannus Botha

OutBound Status in Message Processing

Hi,
I am trying to call a BAPI and pass the data to BAPI and getting the response from the BAPi. I am capturing the response from BAPI. Once I capture the message I am trying to transform the message . This transformation step is always showing as " In Process" continuously. After some time this status is getting changed to "Message has error status on outbound". And also overall status message is showing as 'CLOCK ICON'(WAIT).
Please help me, if you have any idea.
Thanks & Regards
Katta Mohan Reddy

Hi Katta,
The mapping will work fine individually. But due to the data which cannot be parsed, it will throw exception at runtime and that happens in transformation step. You can check the t-code SXMB_MONI_BPE and see the details in graphical view showing transformation step with a red mark in the full flow. If you choose for list with details you can see the error in mapping.
Thanks & regards,
Jayakrishnan

XI- CRM through IDOC adapter - error in outbound status of XI

I have set of messages created today, each of which have 10,000 records as well as same no. of idocs as outbound in XI.
only few messages have status 'messages processed' adn lot of messages are in staus 'Message Recorded (Commit follows)' and 'System Error (Restart Possible)'.
So only the expected idocs are not coming in CRM. But i see the idocs XI. i clicked on IDOC in outbound column of SXMB_MONI.
how can i restart the same message and get the idocs into CRM.
THanks for your help in advance.
Regards,
Jilan Bhasha

hi Agasthuri Doss,
Do you mean to Restart the message?
i tried restarting the message, then prompted with the below message.
Do you want to retain the trace level for the
selected messages (with errors) for the restart
or increase it (maximum level)?
i click on Retain, then the below error appears.
'You cannot restart XML message
E79C4320576611DBBAB10003BAD9E360 with this
status/type'.
Thanks & Regards,
Jilan Bhasha

Idoc Monitoring (Inbound & Outbound Status codes)

Hi ,
In a scenario...whr IDOC has to be send to XI to file.....
and idoc is sent to XI ...if an error occurs ...wht is the process to troubleshoot...wht r the various reasons codes ? in a reverse way ..an IDOC needs to send to R/3 and an error occurs..wht is the process to trouble shoot....pls give a brief note on various idoc status ???
Best Regards,
Kir@n ; )

Main Tools
XI Runtime Workbench
Transactions:
●     IDX1
●     IDX5
●     SXMB_MONI
●     SM58
●     SM21
Analysis
For an overview of analysis steps see a very good link to troubleshoot
[http://help.sap.com/saphelp_nw04/helpdata/en/05/d5fc3f8fc2c542e10000000a1550b0/frameset.htm]

Outbound Status of PE is green in SXMB_MONI

Hi,
working on 1:N mapping with BPM...
getting the following error...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
<Trace level="2" type="T">Host = XXXXXXXX</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
<Trace level="2" type="T">Remote address = 10.130.20.175</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="2" type="T">system-ID = PID</Trace>
<Trace level="2" type="T">client = 200</Trace>
<Trace level="2" type="T">language = E</Trace>
<Trace level="2" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-06-23T09:45:22Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 0D92EE4F5E0C45793027E4BDFD98B66B</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0005</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0005</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MI_CognosEplanningData_OB*</Trace>
<Trace level="1" type="T">select interface namespace http://sws.com/BAS/FI/RTR/Controlling</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 *</Trace>
<Trace level="1" type="T">select interface namespace</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>
</SAP:Trace>
Thanks,
kumar

Hi,
Error log clearly saying no interface found i.e
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 *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
Please check once again your BPM corresponding abstract intetrfaces.
Mean-while monitor this from sxmb_moni_BPE.
warm reagrds
mahesh.

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

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

BPE outbound status

Similar Messages

Maybe you are looking for