PI : Message Status Description ?

Hi,
Please advise where i can get detail information / description on the PI Message status below :
Integration Server :
Message Status
==============
Message Status:      000
Message Status:      001
Message Status:      002
Message Status:      003
Message Status:      004
Message Status:      005
Message Status:      006
Message Status:      007
Message Status:      008
Message Status:      009
Message Status:      010
Message Status:      011
Message Status:      012
Message Status:      013
Message Status:      014
Message Status:      015
Message Status:      016
Message Status:      017
Message Status:      018
Message Status:      019
Message Status:      020
Message Status:      021
Message Status:      022
Message Status:      023
Message Status:      024
Message Status:      025
Message Status:      026
Message Status:      027
Message Status:      028
Message Status:      029
Message Status:      030
Adapter Status
==============
Adapter Status:      000
Adapter Status:      001
Adapter Status:      002
Adapter Status:      003
Adapter Status:      004
Adapter Status:      005
Adapter Status:      006
Adapter Status:      007
Adapter Status:      008
Adapter Status:      009
Adapter Status:      010
Best Regards
Fernand

Hi Ravi,
Thank You for your helpful asnwer, how about adapter status ? is that the same like Integration Server Status ?
Best Regards
Fernand

Similar Messages

Reg : SXMSMSTAT ( XML message Status Master )

Hello Experts,
There is a maintenance view for SXMSMSTAT ,
Is it advisable to change the Status Description and the ICON For same ?
Only Description and ICON
what would be the impact on standard Monitoring of the xml messages
Edited by: Anup Deshmukh on Aug 9, 2011 7:41 AM

Still waiting for inputs,
hello guys i won't change any Tech. Attributes of the table i will only be changing the contains of the same i e Description and the icon ...!
I think it should not be any problem .
What are your Views for the same

Message status "To_Be_Delivered" in MDT !!

Hi ,
Our messages are stuck with the status "To Be Delivered" in MDT. Integration engine shows a chequred flag. However FTP adapter fails to process this message(IDOC to file scenario). Any idea how and where to troubleshoot ?
We went through the applications.log , defaultrace,trc & xi.log with no use. Followed sap notes(761921) and set the trace level to debug for the adapter engine, still no messages seems to be traced about this failure.
We followed this link http://help.sap.com/saphelp_nw04/helpdata/en/49/e3fb40ef74f823e10000000a155106/content.htm(Thanks to Michal for his weblog which talks about this) as well, but only this scenario(message status with "TO_BE_DELIVERED") we are facing is missed out in this link
Any pointers ?
Thanks
Saravana

as you can find on the help.sap.com :
<i>TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue. This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
Only if this was executed successfully the MS returns HTTP 200 to the Integration Server. In this example scenario status TO_BE_DELIVERED should not appear since we presume that the IS has called the servlet successfully.</i>
so... if the messaging system can't return anything (instead of returning http 200) the status is to_be_develivered I assume:)
1. try logging into SapGUI with two users:
XIAPPLUSER
XIAFUSER
to see if <b>they are not blocked</b>
2. You can check those:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure they got the right passwords
BTW
did this scenario work in the past?
regards,
michal
Message was edited by: Michal Krawczyk

Messages status always shows "offline"

I have only updated my mid 2009 macbook pro to Yosemite.
I have synced to my iPhone ok.
My Messages status always shows "offline" on the MBP even though I can chat on it.
Many thanks for any help.

At the bottom of the left New Message box, you can change it there.

XI message status at Adapter engine level using a table (SAP table)

Hello Experts,
XI message status at Adapter engine level using a table (SAP table).
We want to write a custom report using ABAP so Pls tell why the status u2018Holdingu2019 and u2018To be deliveredu2019 are present in message monitoring of RWB but not in the status (MSGSTATE) field of SXMSPMAST table.
My need is to write a report to get the messages based on the these status from table level.
Please let me know the table name and field name for this and the table name for the desciption of the status of XI messages at Adapter level.
Thanks
Gopesh

Hi Gopesh,
the Adapter Engine Messaging System messages are on the Java schema,
i.e., see the following -
[XI/PI tables|https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/xi+tables]
Regards
Kenny

Change message status after release purchase order

Hi,
I'm a newbie in MM...
When a purchase order is created, the message status is not processed (yellow light) until the purchase order is released. Then the message is printed and the status changes to green light.
As far as I see, I can't find in the spro where is this customizing set or if there is a user-exit or badi for changing the message status depending on the release indicator.
Thanks in advance!
Jen

Hi Jen,
Complete the condition record, for example, like this:
- Transaction: MN04
- Output Type: NEU
- Choose third option: Purchasing Output Determination Document Type
- Document Type: NB
- Function: VN (Vendor)
- Medium: 1 (Print output)
- Date/Time: 4 (Send immediately (when saving the application))
Select the line and press button "Communication". Complete the output device and mark the option "Print immediately"
So, when the PO is created the system generates the message with yellow status. Then, when the PO is released, the message status will be green
Regards,
Fernando

XI: How to update the Message Status (shown by transaction SXMB_MONI )

Hi
My question might be stupid, but I need you help.
I would like to know how can I update the message status what we see while using trasaction SXMB_MONI . The Scenrio is, I have a Custom Interface program build on the Abap Proxy interface method called EXECUTE_ASYNCHRONOUS.
If I am not wrong, transaction SXMB_MONI is on the XI system and also on the SAP Application system. ( But I am not sure in what way the same transaction differ in two systems )
My issue is, when I receive the xml data into a structure in abap proxy, I am doing some validation on the received message data. If I found some error in the data , then I need to update the Message status of the SXMB_MONI to ERROR flag. How to implement this ? I have not done one before. And I am not sure, if any exception like error message is raised, will it stop the proxy from processing further and update the Message Status and this can be viewed using SXMP_MONI in the SAP application system to be ERROR flag?
Or is there a BAPI or function module to handle this ?
Appreciate your help
David

Hi
I am not sure If I had understood you reply. But Would need your help to have a bit more insight to your answer. I am not completely into XI , but I am from ABAP side.
At the R/3 side , Abap Proxy object geneted has the INTERFACE and its associated METHOD, in which I am building my own abap code to do any validation on incomming data. But If I want to Raise a Exception, I understand that this Expection has to be first defined .
But do I have to define a new Z Expection class or can I just add a exception in the Proxy -Interface-method.
I have not understood this process.
All I need to do is, if I find any incomming data error , during my validation at the R/3 side, I need to stop the METHOD processing ( by any means ) and Update the Message Status flag show in SXMB_MONI to Error .
What is the trigger that i can implement in myown code that will update the Message status to Error , from R/3 perspective of using SXMB_MONI.
Thanks
David

Message status is scheduled mode in SXMB_MONI

Hi Experts,
In My scenario i am Using FILE sender adapter, here i am sending multiple files at a time. if any file with errors that is failing SXMB_MONI.
Here my question is in my scenario if first message failed in SXMB_MONI remaining all messages status is in scheduled only. How over come this.
What is the solution for this can i do any changes in Communication channel, what is that changes please let me know.
thanks
Srinivas

Eg: I am getting error for one messge inthis time remaing interfaces messages scheduled in queue until deletion of the
error message from queue. after deletion of this error message from queue then remaining messages are processing.
This is a normal behaviour...since the Queue used by the messages is the same....one error message will block the queue and the rest wil go into the Scheduled status.....check if this blog helps you in running a background job which cancels/ resends the error message..
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Abhishek.

XI messages status "Message scheduled on outbound side" with Green flag

Dear,
          On My XI system , i have too old messages and i want to clear those.
          In moni messages status is "Message scheduled on outbound side" with Green flag .
         When i am trying to cancel these messages i am getting a popup saying
          "Cannot cancel message because of it's status"
          And there is no queue entries for these messsage on smq1 or smq2 (perhaps deleted by someone)
          I just want to cancel these messages, please tell me if there is any way .
Thanks in Advance,
Sandeep

Dear Sunil,
                Thanks, these meesages are neither active nor used anywhere,
                Problem is somebody has manually deleted entries for these messages from SMQ1 and SMQ2.
Regards,
Sandeep

Moni message status

Hi,
Iam getting message status in moni (Transport acknowledgement ) it tells acknowledgment not possible. So the reason is messages got stucked up. Is that only reason or are there are any reasons? what to do now? Because of that i cannot able to run another interfaces also and they also getting stopped.Do we have to delete the queues or are there anyways to do that? can anybody explain me???

Hi,
if possible correct that error ...so that queues will get released automatically....else you can delete the message blocking queue...so that other entries will be processed....
better try to rectify the error and reprocess the messages..which will release the queue...
HTH
Rajesh

Troubleshoot-Adapter engine:Error Setting the message status to DLNG failed

Dear Experts,
We use SAP RFC- PI-JDBC(MSSQL). here the Data(message) successfully transfered to mssql table but the status is been set to DLNG failed, And it finally shown as SYSTEM ERROR.
QoS required: ExactlyOnce , here The Message has got inserted in that particular table and in PI adapter the status turned to DLNG faild and the service again tries to send the same message which is not possible becoz the data is set for primary value.
2010-09-15 09:59:48 Success Message successfully received by messaging system. Profile: XI URL: http://XXXXX:50000/MessagingSystem/receive/AFW/XI Credential (User): YYYY
2010-09-15 09:59:48 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2010-09-15 09:59:48 Success Message successfully put into the queue.
2010-09-15 09:59:48 Success The message was successfully retrieved from the receive queue.
2010-09-15 09:59:48 Error Setting the message status to TBDL failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
2010-09-15 09:59:48 Success Delivering to channel: CCR_JDBC_ZZZZZ
2010-09-15 09:59:48 Success MP: Entering module processor
2010-09-15 09:59:48 Success MP: Processing local module localejbs/CallSapAdapter
2010-09-15 09:59:48 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2010-09-15 09:59:48 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party , service BS_BCP_IMPLOG_ZZZZZ
2010-09-15 09:59:49 Success Database request processed successfully
2010-09-15 09:59:49 Success MP: Leaving module processor
2010-09-15 09:59:49 Success The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.
2010-09-15 09:59:49 Error Setting the message status to DLNG failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
2010-09-15 10:37:01 Success The message was successfully retrieved from the receive queue.
2010-09-15 10:37:01 Success The message status set to DLNG.
2010-09-15 10:37:01 Success Delivering to channel: CCR_JDBC_ZZZZZ
2010-09-15 10:37:01 Success MP: Entering module processor
2010-09-15 10:37:01 Success MP: Processing local module localejbs/CallSapAdapter
2010-09-15 10:37:01 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2010-09-15 10:37:01 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party , service BS_BCP_IMPLOG_ZZZZZ
2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
Thanks in advance for your valuable answer.

Hi Vinaygam,
2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
See above error, It cannot the Duplicate Key in your log table. Duplicate means repeated as a same data.So kindly check once your data.
IF,I assume your scenario is Synchronous, If you are using any sender JDBC adapter just check with your Quality of Service and set it to "Exactly once".
so kindly do it.
Thank you,
Sateesh
Edited by: sateesh kumar .N on Sep 17, 2010 8:17 AM

Sent messages missing 'Message Status' link

I have a problem and am curious if other Apple Mail users are seeing this issue.
I have just migrated from Entourage about a week ago and am confused by how message linking works. While I miss the 'Message History' available in Entourage, I assumed that the links that only appear in the 'Message Status' column in list view of a mailbox would achieve a similar effect in allowing me to connect incoming and outgoing replies in a conversation, no matter what folder they are contained in (Inbox, Sent, or a local folder for sorting).
I see links in messages in my Inbox as well as local folders I have sorted messages into, but for some reason there are no links in my Sent Mail folder. That column is blank, making a chain of conversation break as I try to traverse an email conversation.
Is this normal, or is my database somehow corrupted? If there is corruption can it be repaired?
Thanks.

It doesn't mean the mapping is correct. If it's sent through the server and you have it set to store sent messages on the server, then the server is coping it to the folder. If it isn't showing in Mail, then it's probably not mapped correctly.
Check the exchange folder in the sidebar. If it isn't expanded, put the cursor over it until show appears. Then click show to expand the folder. If the Sent Items is listed under it, highlight it and choose Use This Mailbox For: Sent under Mailboxes in the menu.

Message Status as scheduled..

Hello All,
I configured scenario which use SOAP as sender and XI Adpter as receiver.
It is syncrnous call. I can see different message status...
intiatially it came as black triangle --> scheduled for outbound processing.
Now, It is showing Green flag which is just sceduled......
What is wrong and how to troubleshoot further....
Thanks,
Srini

See below SAP Note 1118297:
Liang
=====Note 1118297===========
Symptom
You are using the Exchange Infrastructure and you are processing asynchronous messages. These messages are scheduled in queues that are no longer processed. The inbound queue of the qRFC Monitor (transaction SMQ2), for example, contains entries with the status "Running". However, you recognize in the process overview (transaction SM50) that there is no active work process.
Other terms
QRFC, SXMS_ASYNC_EXEC, inbound, running, resource
Reason and Prerequisites
You are using the Exchange Infrastructure and you are processing asynchronous messages. These message are scheduled in the QRFC and are only processed slowly or not at all.
Solution
The asynchronous messages are scheduled in the queues.
Check the following points of your middleware.
Queue configuration:
If the QRFC Inbound Scheduler is configured, see Note
369007.qRFC: Configuration for the QIN Scheduler
Are the XI queues registered and active? In transaction SXMB_ADMIN->Administration->Manage Queues, you can register the queues for the XI runtime.
If the resources are configured for TRFC/QRFC, note the common usage of system resources. For further details, see Notes
74141 Resource management for tRFC and aRFC
527481 tRFC or qRFC calls are not processed
For the qRFC resources see Note
1051445 qRFC scheduler does not use all available
resources
For further information see Unit 3.1 of the "SAP Exchange Infrastructure Tuning Guide", which you can download from the marketplace.
In the XI configuration you can set locks for the processing of XI messages. Note that for many parallel queues there are also sufficient resources for lock objects. At least one enqueue entry is required for each queue, depending on the configuration. For further information see Notes
552289 FAQ: Lock management R/3
654328 Enqueue: System log message GE9
Queue status:
Transaction SMQ2 contains queue entries with the following status
"Running"
If the J2EE engine is downloaded in production mode with the mapping engine or recipient Adapter Framework, processing QRFC entries may not recognize this and remain in the "Running" status. A symptom can be, for example, that the RFC destination "AI_RUNTIME_JCOSERVER" is no longer registered. You can find this information in the Gateway Monitor (transaction SMGW).
Otherwise, the system may reach this status if the application server is downloaded in a controlled manner, and long-running processes can no longer terminate.
The system no longer processes any message. In transaction SMQR, you can activate the queues manually again. You can also schedule the report RSQIWKEX, which automatically restarts the queues. For further information see Notes
620633 Status RUNNING in SMQ2 with XI queues
864333 RSQOWKEX & RSQIWKEX start Running(Executed) queues
"Sysfail"
A queue entry with the status "Sysfail" can have two possible causes.
1. Further processing cannot be carried out on the process for technical reasons (for example, the program terminates with a dump or a system (mapping or recipient system cannot be reached).
2. Queue processing should be stopped, as the message cannot be processed, due to a configuration error. Processing is not permitted for the subsequent messages, as the queue sequence displays the message sequence. You can use the report RSXMB_RESTART_MESSAGES to restart the message processing again. See Note
813029 Automatic processing of failed XI messages
XI-QRFC and IDoc-TRFC processing:
Note that when you use the IDoc adapter this uses the RFC/TRFC resources, which are used together with the QRFC resources. This means an intensive usage of the TRFC can influence the performance of the XI queue message processing. When possible always use the package processing of the IDoc adapter (transport of several IDocs with an RFC call to the recipient system):
1. Package created from an IDoc XML payload with several IDocs
2. Packaging, package created with IDoc package filter
3. Package created with message packaging (queue message package)
(as of NW2004s)
For more information about acknowledgements, see also Note:
1111968 IDoc adapter: Parallel processing of acknowledgements
to reduce the number of acknowledgement queues.
Tuning Balancing parameter :
The BALANCING parameter activates the entries for the parameters B_EO_IN_PARALLEL_SENDER, B_EO_OUT_PARALLEL and B_EO_IN_PARALLEL.
They are used if the number of parallel queues is changed and the messages are distributed to the new queues. A balancing procedure is already used in the Standard System to distribute the messages equally to the queues. If the Balancing parameter is continually active, it has a negative impact on performance (as queue entries are constantly distributed between the queues and this means they cannot be processed). This can cause problems during queue processing.
Its use in the Tuning Guide is not described clearly.
Oracle database:
When using an Oracle database see Note
742950 Performance affected on Oracle DB with supplement 11
if you discover performance problems when processing queue entries. This improves the scheduling process only, and not the processing time of a queue entry.
See also Note
1020260 Delivering Oracle statistics
EO (exactly once) handling of XI-Messages when you restart QRFC entries:
The XI log guarantees the uniqueness of the transfer between the client and server. A restart does not trigger a double execution of messages. Note that a synchronization of the reorganization between client and server is guaranteed. The EO recognition is executed with the message ID. The retention time determines the amount of time this information is retained in the system for.
The individual messages are saved to the database in the system with a key from the message ID and version. This prevents a parallel execution of the same message. A queue entry can be executed in parallel using the report RSQIWKEX or by carrying out a manual start from the queue. We recommend to set the parameter LOCK_MESSAGE (default value is active "1") of the category "RUNTIME" in the XI configuration to the value '0'. More information is contained in Note
1058915 Outbound queue remains in status 'SYSFAIL'
=====End of Note 1118297===========

MEssage status as stoped

Hi all
I sent a message to the XI, In SXMB_MONI the message Q status showing as stopped. Why the message status shows like that? And what is the solution when the problem get.
Thanks,
Satish,

Rani,
Check this weblog for furhter info:
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Also If the status is Queue stopped, click the entry in the Queue ID column, and double-click the queue until you see the entries within the respective queue. The first one will be in an error state. Double-click the entry and you will see the message in error. Check the error, correct it, and restart the message. If the error cannot be corrected, cancel the message in transaction SXMB_MONI so that the other messages in the queue can be processed.
Hope this helps...
---Saish

Message Status as "Scheduled" and Queue Status "Queue Stopped".

Hi friends,
My scenario is from Peoplesoft -> XI -> BI
Message has reached BI, but in SXMB_MONI, its showing Message Status as "Scheduled" and Queue Status "Queue Stopped".
How to proceed further ? How can I start that queue ?
Thanks ain advance,
Neena John

Hi Neena,
Go to SXMB_ADM -> Manage Queues -> Register Queues
More on queues
XI : How to Re-Process failed XI Messages Automatically
Run the report RSXMB_REGISTER_QUEUES and register the queues
Run the report RSXMB_RESTART_MESSAGES for restarting ur messages
Refer this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
Regards,
Vinod.

PI : Message Status Description ?

Similar Messages

Maybe you are looking for