Message status in Canceled-Since Already Processed

Hi All,
I could see a message is in CANCELED-SINCE ALREADY PROCESSED. What does it mean and why is that its showing in this state, which I have nver seen/come across.
Regards
KarthiSP

Hi Karthi,
The below discussion might be useful
DUPLICATE_DETECTED
regards,
Harish

Similar Messages

Reason needed for the status Canceled - Since already processed.

We have an IDOC to PROXY scenario and we encountered an error.
First time the message failed in PI with the error message as
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Timeout</SAP:P2>
As this is temporary connection problem, we tried resend the message. Then the message went to the status as Canceled u2013 Since already processed.
The Error message is:
<SAP:Code area="MESSAGE">DUPLICATE_DETECTED</SAP:Code>
<SAP:P1>4CA1DDA984FC013EE1008000C02522A4</SAP:P1>
<SAP:P2>RECEIVER</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Message ID 4CA1DDA984FC013EE1008000C02522A4 already exists in called system (pipeline RECEIVER)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
Please tell me what is the exact problem for this issue.

May be handshake was failed while updating the status of of message in XI after handed over it to target syste, please check the same message in Target system with what time it had got (whether the first time only or after resending it).
regards,
Satya.

Icloud extra storage space can not be canceled, since the processing is not available. Icloud message reads 'service cancel not available. try later'. this message shows up for days already. How to get rid of this extra storage space I cloud?

what can i do to cancel my extra storage space Icloud?

Go to "Settings > iCloud > Storage > Buy more Storage" on your iOS device and change the plan.

Job also cancelled due to process termination. See the system log

Hi Friends,
I am working Interface Programs in HCM Module.
My problem is when i am Executing my program in BACKGROUND .After some time my job is canceling. In log i am getting message
"Job also cancelled due to process termination. See the system log"
when i see that system log also i am unable to find any thing.
but in fore ground is working fine .
Please help me .
Thanks in Advance..
Regards,
Kumar...

Hi,
You need to check that program in debugging for the Backgournd process.
For doing the debugging of the background process do the following steps.
1)go sm37 and select your job.
2)in the command line just type JDBG (not the /nJDBG OR /oJDBG) and hit enter. it goes to the debuggin mode.
Thanks

Already processing the document

Hi ,
Our users are facing with the following problem, can anybody help.We deleted the lock entries in SM12 but
users are facing this problem again and again.
He chose Cart 1 for approval. Went through the details and then went to Cart 2 without taking any action on Cart 1.
Approved Cart 2,3,4.
But he could not open Cart 1 even after 15 minutes.
Every time he tried, the message says, that he is already processing the document.
Regards,
Priti

Hi
Check if the notes 670703 helps...
Rgds
Reddy

Delete messages stuck in status 12, Recorded for Outbound Processing

I am on a PI 7.10 SP8 system. I have 59,000 XML messages showing in status 12 ( Recorded for Outbound Processing) that I would like to just delete or cancel. These have accumulated over several days of testing interfaces. If I have to allow them to be processed, that would also work but is not needed. I have read about 6 different forum threads and tried several things but nothing has worked yet. 
The messages can not be cancelled from SXMB_MONI. 
The queues are no longer showing in SMQ2. 
I have tried restarting and re-registering the queues. 
I've tried RSXMB_RESTART_MESSAGES and RSXMB_CANCEL_MESSAGES. 
SWPR & SWPC show nothing to restart. 
Any ideas on something else to try? 

Hi,
You can try to delete or archive mesages. use following links.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a236f50
Delete Messages SXMB_MONI
http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm
Too many questions on Archive/Delete messages.
Inder

How to delete the messages from SXMB_MONI which are already cancelled .

Hi All,
The messages were earlier in System error(Red flag) state so i cancelled it manually.
I want to know how to delete the messages from sxmb_moni which are already cancelled manually using ctrl+f8.
if not possible , then i want to see them in earlier state i.e.., in System error(Red flag).
can any tell me the procedure of doing it.
thanks
Sai.

Hi AmitSri,
Thanks for u r reply,
What is retention period, where can i find this option.
And i don't have authorizations to sxmb_adm --> configure delete procedure
--> Define interfaces for archiving and retention period.
and to RSXMB_DELETE_MESSAGES in se38 , i don't have authorizations to run
Is there any way to delete the messages or make them to System error( Red flag) which are manually cancelled.
Thanks
Sai.
Edited by: sai_SHA on Aug 17, 2011 12:29 AM

I can't log in to ichat. Everytime I try I get a message "The server encountered an error processing registration. Please try again later" . Is there anything I can do. this has been going on since yesterday.

I can't log into ichat. Everytime i try, I get this message: "The server encountered an error processing registration. Please try again later." This has been going on since last night. Is there something I can do?

I can't log into ichat. Everytime i try, I get this message: "The server encountered an error processing registration. Please try again later." This has been going on since last night. Is there something I can do?

PO message status should change to PROCESSED

hi
we are taking PO print from ME22N(before releasing it ), here first we set message then Goto-->Print Priview--
>Print
but problem is that status of Message is not getting changed to processed as it happens in ME9F.
how i can get it , we want it for unreleased PO .
regards
sachin

Prior to hanging up with current call you can place yourself in a not ready or work state. Once you disconnect from the call you can place yourself in ready to take another call.

Cannot update my iPad2 to 5.1 An unknown error message cancels the download process. Could you please inform me how to fix this issue? Thanks!

Cannot update my jail broken iPad2 & iPhone 4S to 5.1
An unknown error message cancels the download process. Could you please inform me how to fix this issue? What is also odd is the fact that the update through iTunes is substantially bigger than downloading it directly OTA, although both methods have been unsuccessful so far...
Thanks!

About the only thing you can try is using the Online Internet Recovery system to reinstall Lion on your Mac over the top of the current install. that will reset all system files and should not touch your personal files or the apps you have installed.
Or iof you have a recent Time Machine backup use that to restore your Mac to that point in time.

Since updating to iOS 6 my phone has not been receiving text messages from some people. Already contacted my service provider and apparently nothing's wrong on their end. Any suggestions?

Since updating to iOS 6 my phone has not been receiving text messages from some people. Already contacted my service provider and apparently nothing's wrong on their end. Any suggestions?

Who's your service provider?

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.

Message status in SXMB_MONI

Could you plz tell me when this particular condition will occur ?? If i am not wrong Messae ID will be created randomly for each message that passes through the XI.
So how can message with same ID will be created in XI ??
Message already processed
A message with this message ID already exists in the receiver system. Processing is therefore completed for the sender system.
Thanks
kumar

Hey
coz XI maintains an entry in a table with the Message ID and the status of message after each processing steps..new message ID's are only generated if u have logical routing or ur sending an all together new data from the sender system.
since XI maintains the message ID along with the status,it knows that the message waz processed successfully.
Thanx
Aamir
Message was edited by:
Aamir Suhail

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 :
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.
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 they are not blocked
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

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 in Canceled-Since Already Processed

Similar Messages

Maybe you are looking for