IDOC to IDOC queue blockek status shows green flag

Hi i' m doin an iDOcto idoc scenario.. in sxmb_moni the status flag is green...queue is blocked.. i tried activating the queue
it still shows sysfail...
this is the trace message... any problem with my design or the message passed.. or is it a queue problem if so how to handle
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="IDX_INBOUND_XMB" />
- 
<Trace level="1" type="T">User: PI_RM_USER</Trace>
<Trace level="1" type="T">Language: E</Trace>
<Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
<Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
<Trace level="1" type="T">Syntax-Check-Flag</Trace>
<Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
<Trace level="1" type="T">Queueid</Trace>
- <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
<Trace level="1" type="T">Get the Metadata for port SAPDEC</Trace>
<Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
</Trace>
<Trace level="1" type="T">Set Receiver Routing-object</Trace>
<Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = DIN</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PI_RM_USER</Trace>
<Trace level="1" type="Timestamp">2009-08-07T09:08:38Z CST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 80144FDD6C661DEEA0E63CA33DA20911</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">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name =</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>
<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 COELEM.COELEM01</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
</SAP:Trace>
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:22 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:23 AM
Edited by: Indudhar P.G on Aug 7, 2009 11:24 AM

HI,
Correctly said by Abhishek, click on Queue Id and then further selct the Queue and Click on details to see all the messages in that Queue. Select the First Message in SYS FAIL and try to restat that. If that again Fails. Don't delete the whole Queue but delete the selected message from Queue in Error. Then go Back and Unlock the Queue and refresh. All messages behind this message will re-process automatically.
SMQ1 and SMQ2 are tcodes foe Queues.
REgards,
Anurag

Similar Messages

WCS Alarm Status shows green but LAP is unplugged ?! Oper Staus shows Down

Hello,
we are operating a Cisco WLAN environment with 1242 and 1131 LAP. Some of them have been converted from AP to LAP.
Now we took some LAP off the wall.
They are now packed in a box in our storage room.
But the WCS is showing a green Alarm Status for these LAP and as Oper Status Down.
How can that be ?
Is there a way to fix this problem, because we want to see the Alarm Status in Red.
Thx for all your input.
Best Regards
Christian

This is very interesting. If I try to put myself in the WCS developer's shoes, I think:
- if you get an alarm for missing AP, then acknowledge the alarm, WCS has no reason to re-display the same alarm. This is precisely what Acknowledge is for, to say "don't bother me with this issue anymore".
- Even if you manually remove the AP from WCS, it clearly keeps some memory of it, at least for a while. This is something you can clearly see if you run a report of any kind, WCS has to keep track of objects even if you remove them.
My suggestion would be:
- Unacknowledge the alarm, then delete it... acknowledging an alarm is probably not the best way to deal with removing an AP. You would use Aknowledge for alarms such as "your neighbour AP keep being detected as rogue, you can't remove your neighbour AP but don't want to hear about this warning anymore." You acknowledge the alarm, WCS keeps it in its database and remembers NOT to bother you with it anymore (exactly what happens in your case).
For an AP you remove, I would not acknowledge the alarm, but simply delete it after having removed the AP. This removes the alarm from the WCS database.
If you ever re-plug this AP to the network, WCS may remember it, but any new alarm about it will display.
Hope it helps
Jerome

When RFC-Adapter is down, only the adapter-status shows error flag

Hi all,
How can I reprocess a message that did not reach the endpoint because the rfc-adapter was down, if the overall status of the message is "Message Processed"?
Thaks,
Nuno

Hi,
The question is about receiver RFC adapter and not about the sender RFC adapter. So single / mass re-start from SM58 won't help (Report RSQIWKEX for q-RFC and report RSARFCEX for t-RFC).
If RFC adapter is down, message won't reach to the destination system via adapter engine. IE monitoring will say that message is successfully processed (so report RSXMB_RESTART_MESSAGES will not help) . In this case, if you go to adapter engine monitoring from RWB, you will be able to see the status Waiting or System error.
I'm not sure how to re-start this message, but probably you can do this through MDT.
May be SAP note - 813993 will help you.
Good Luck & Bapu, Jalasa Kar........

IDoc - XI (BPM) - File, Successful status but no message generated

Hi,
I am trying to do Sravya's blog for BPM correlation.
I am sending IDocs from R/3 system to XI, even though message shows successful status there is no message is created on the receiver.
One strange thing is when I go into the SXI_MONITOR -> process (radio button) -> messages -> PE is taking me to the Inbound Queue not to the workflow log.
The next button is outbound status has green flag (message scheduled on outbound side).
Could you please help me resolving this problem.
Thanks
Kiran
Message was edited by: Kiran Reddy

Thanks and that solved the problem.
Now my multi source mapping is not working any ideas ?

In SXMB_MONI with(Green Flag) "Message Scheduled Outbound Side" (using BPM)

Hi All,
I had a Scenario where I am using BPM (to collect the Idocs received from Sender SAP R/3 system) and create a File as target structure. But one of the entry i found as (Green Flag) with status "Message Schedule Outbound Side". But the remaining messages are processed successfuly through the same BPM.
I even found that the when i double click on the PE of the "Green flag entry". its leading to "qRFC Monitor(Inbound Queue) with empty entries" instead it should lead me to the workflows Log screen. Since other successfully messages are leading to workflow log when i double click on the PE.
Please let me know your comments on this.
Thanks,
Shailaja

Hi Gouri,
I am getting gray flag in the column (Status - XML Message Status) and green flag in Colum (C- Outbound Status). So this Greem flag itself is creating the problem, because of this itself my messages is not getting processed and not delivered to target system.
I have even checked SXI_CACHE, when i click on the Integration Process-- Right click on my BPM and select the "Activation Log" .. here a message which i had
I Language not set. Using system default E
The container element MULTI_INVOIC02 is written, but not read or exported
The container element MULTI_INVOIC02 is written, but not read or exported
So the "MULTI_INVOIC02 " is used in the Container Operation & Multimapping of my BPM. I suspect that error as taken place in doing Corelation. Do you have any comments on this. If i get any error in Corelation .. how can i debug my BPM.
Thanks,
Shailaja

Green flag to Red flag in SXMB_MONI

Hello experts,
During the FILE -> BPM -> RFC scenario, i use a mapping step to intentionally throw an exception to make application errors visible in the monitoring logs (SXMB_MONI).
This way a red flag on the outbound status field is shown if the condition to execute this mapping is met.
This works well for its intended purpose in a scenario, but doing the same approach for another scenario (everything is done exactly the same way), the second scenario shows a green flag on the outbound status field.
the Greed flag dictates "message is scheduled on the outbound side", once i click the "PE", i can see the queue has failed in the BPM.
I am not clear as to why it displays green flag instead of a red flag. The requirement is to display the red flag. (and so that no queue-clearing is required).
Any ideas on how to achieve this is greatly appreciated.
Thanks.

hi, thanks,
when i click to the Queue ID, it opens the SMQ2 (qRFC inbound) .. here i can only see 1 LUW displayed, with SYSFAIL status. This is because of the intentional exception thrown via a mapping step.
Instead of failing at the queue (and get a green flag in sxmb_moni), it should show error status in sxmb_moni with red flag in the "outbound status" field.
If i clear this and unlock the queue, the next execution again falls into a failure in queue status (and a green flag in the sxmb_moni).
I appreciate any other ideas.
Thank you.

IDOC TO XI WITH DEDICATED QUEUE HAS STATUS 30

Hi, i have an interface IDOC to XI to JDBC, it has implemented a dedicated Queue, it dosnt have configured the acknowledge.
it was working fine, then we implemented the dedicated queue, it works fine a cuple of thays but then the idocs start to have all status 30. (note: i have configured output mode 2)
SM59 config image:
<a href="http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG">[IMG]http://img144.imagevenue.com/loc991/th_95044_SM59_122_991lo.JPG[/IMG]</a>
or:
<a href="http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG">[img=http://img144.imagevenue.com/loc991/th_95044_SM59_122_991lo.JPG]</a>
WE20 config image:
<a href="http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG">[IMG]http://img169.imagevenue.com/loc768/th_95050_WE20_122_768lo.JPG[/IMG]</a>
or:
<a href="http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG">[img=http://img169.imagevenue.com/loc768/th_95050_WE20_122_768lo.JPG]</a>
Table IDXQUEUE in XI SE16 image:
<a href="http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG">[IMG]http://img140.imagevenue.com/loc850/th_95050_XI_SE16_IDXQUEUE_122_850lo.JPG[/IMG]</a>
or:
<a href="http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG">[img=http://img140.imagevenue.com/loc850/th_95050_XI_SE16_IDXQUEUE_122_850lo.JPG]</a>
Function module in SE80 image:
<a href="http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG">[IMG]
http://img41.imagevenue.com/loc768/th_95052_SE80_FM_122_768lo.JPG[/IMG]</a>
or:
<a href="http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG">[img=http://img41.imagevenue.com/loc768/th_95052_SE80_FM_122_768lo.JPG]</a>
First message that came out by de dedicated queue image:
<a href="http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG">[IMG]http://img179.imagevenue.com/loc193/th_95057_first_message_122_193lo.JPG[/IMG]</a>
or:
<a href="http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG">[img=http://img179.imagevenue.com/loc193/th_95057_first_message_122_193lo.JPG]</a>
Last message that came out by de dedicated queue image:
<a href="http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG">[IMG]http://img192.imagevenue.com/loc343/th_96230_last_message_ok_122_343lo.JPG[/IMG]</a>
or:
<a href="http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG">[img=http://img192.imagevenue.com/loc343/th_96230_last_message_ok_122_343lo.JPG]</a>
BD87 from the day that everything work fine to today image:
<a href="http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG">[IMG]http://img178.imagevenue.com/loc90/th_96306_bd87_122_90lo.JPG[/IMG]</a>
or:
<a href="http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG">[img=http://img178.imagevenue.com/loc90/th_96306_bd87_122_90lo.JPG]</a>
Anyone has an idea why is this? I have allready tried the report and TRX to process the idocs with status 30 and it didnt work.
Thanks.
Regards.
Mariano Billinghurst

Sorry i have posted wrong the images, here it goes again...
Hi, i have an interface IDOC to XI to JDBC, it has implemented a dedicated Queue, it dosnt have configured the acknowledge.
it was working fine, then we implemented the dedicated queue, it works fine a cuple of thays but then the idocs start to have all status 30. (note: i have configured output mode 2)
SM59 config image:
http://img144.imagevenue.com/img.php?image=95044_SM59_122_991lo.JPG
WE20 config image:
http://img169.imagevenue.com/img.php?image=95050_WE20_122_768lo.JPG
Table IDXQUEUE in XI SE16 image:
http://img140.imagevenue.com/img.php?image=95050_XI_SE16_IDXQUEUE_122_850lo.JPG
Function module in SE80 image:
http://img41.imagevenue.com/img.php?image=95052_SE80_FM_122_768lo.JPG
First message that came out by de dedicated queue image:
http://img179.imagevenue.com/img.php?image=95057_first_message_122_193lo.JPG
Last message that came out by de dedicated queue image:
http://img192.imagevenue.com/img.php?image=96230_last_message_ok_122_343lo.JPG
BD87 from the day that everything work fine to today image:
http://img178.imagevenue.com/img.php?image=96306_bd87_122_90lo.JPG
Anyone has an idea why is this? I have allready tried the report and TRX to process the idocs with status 30 and it didnt work.
Thanks.
Regards.
Mariano Billinghurst

Idocs in inbound queue

Hi,
We have a very critical issue wherein many a times in actual production system idocs are going into status 75 and hence into Inbound Queue.
So user currently has to go transaction WEINBQUEUE and restart queue details.
Just to give more technical details as only these type of idocs are going into queue's:
Basic type: WMTOID02
Message type :WMTORD
Please help asap.Issue is very critical here.
Thanks,
Vikram

Hi Ravi,
Thanks for your quick response.
As you have explained I see that from the Message Mapping I must mapping a timestamp in SERIAL field of the Control Record. This implies that the IDOC Receiver Communication Channel should not mark the checkbox "Queue Processing" (I get the feeling that this does nothing) and I have to mark the checkbox "Apply Control Record Values from Payload '.
In conclusion, I understand that the IDOC Adapter for queued processing on a target system such as SAP adds nothing as standard. That is, I've mapping identifiers as timestamp to ensure the execution sequence in SAP and this will be done through a program in background. As is done with ALE...
Furthermore, I can not avoid a "delay" in processing these messages. In my client does not allow me to schedule the job in less than 5 minutes.
Is not there another solution where PI contribute just over? Any ideas?
Thanks in advance,
Jose.

IDoc- XI- IDoc - Problem in TRFC-Queue

Hi everybody,
in Integration Builder i have created an A2A-Scenario (Idoc->XI->IDoc).
After designing and configurating i want to send an IDoc to XI.
But the IDoc stands in the TRFC-Queue with error "no service for system <xxx> client 020 in Integration Directory."
In ID i have set Business Systems for sender and receiver both with outbound/inbound interfaces of idoc-type, which i have upload from relevant sap-system.
What is my fault?
Thanks a lot.
Greetings
Joerg Knaust

hi,
most probably it's a typo
there's no sender agreement if you're sending idocs
from r3 to the xi
1. how does your service in TCODE - IDX1 look like?
sapSID ?
2. adapter specific identifiers (do it step by step):
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

Deactivate idoc generation for order when status is not completed

Hi Guru,
In CRMD_ORDER when sales order is created it will generate bdoc and for that bdoc idoc is going to create for every status , my requirement is to stop the creation of idoc if status is not completed please provide solution for that.
Regards,
Naveen.

Hi Naveen,
As u said u dont want to create idoc on the particular User status(i.e. Not Completed ), in this case u check for u r subcription setting in administration console (txn: SMOEAC) that in which statuses u r idoc get created in field crieteria value, maintain status operator (NE) Not Equal to Not Completed , u r idoc will not get created if u r user status in Not Completed
Regards,
DD's

IDoc Delays: 64 to 62 status

Hello - We have been seeing some intermittent delays on some of our ORDERS idocs. They are configured to process immeadiately, but we have been seeing some delays when they are going from status 64 (Ready to be Transferred) to status 62 (IDoc passed to application). These delays are sporatic and ranging from 2 minutes to 20 minutes.
Any thoughts?
Thanks - Kyle Winters

Hi,
Are these idocs processed using workflows or ??
Please have a look at following SAP notes.
» SAP Note Number: 160670 Idocs remain in inbound with status 62
» SAP Note Number: 836022 ALE: Link to application log in status 62
» SAP Note Number: 92552 IDocs-Status 62 cannot be processed
» SAP Note Number: 631039 IDoc: Problems with inbound processing using workflow
» SAP Note Number: 194640 IDoc: Workflow is not started in RSEINB00
» SAP Note Number: 181729 ALE: IDocs remain in status 64 / 3.X inbound
» SAP Note Number: 168276 IDocs remain in status 64
KR Jaideep,

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

IDoc missing in IDoc - XI - IDoc scenario

Hello!
The integration scenario is R/3 4.6C (IDoc) -> XI -> (IDoc) R/3 4.6C for DELFOR, ORDERS, ORDCHG, DESADV and ORDRSP.
Now we switched to a new XI development system and the flow is working for all message types besides DELFOR.
WE20 -> New XI Logical System Name -> DELFOR points to the new receiver port which referenced to the correct SM59 destination that is used by all other message types as well.
There is also no error in SM58 in the sending R/3 system and the DELFOR IDocs are in status 12 in WE02 but when I search the IDoc number in IDX5 on XI the IDocs are not there.
Does anybody have an idea where to find the DELFOR IDocs?
Regards, Tanja

Hello!
> IDOC staus if it is sent out from R/3 should be 03 or
> 12?
First it was 03 but as I was not able to find it anywhere I ran a report and the status changed to 12 afterwards.
> if IDOC is coming out of R/3 without any errors( sm58
> no errors) then it should come in the SXMB_MONI in XI
> as it usess th TRFC Port........
Yes, this is also my understanding but it is not in SXMB_MONI nor in IDX5.
> if it is not check the SMQ2 and SMQ! in both XI and
> R/3...it cannot go anywere else (-:
I have checked SMQ2 and SMQ1, the queues are empty in XI and R/3.
Regards, Tanja

SM58 Error For IDOC to IDOC Scenario

Folks,
I am getting an error in SM58 from Sender system ( IDOC-XI-IDOC Scenario ) IDoc adapter inbound channel: Error Error when reading. The Issue is XI is not receiving any IDOCS. Does anybody know what is the problem
Thanks
Manish

Hi Renjith,
I'm facing the same problem the flow is basically form BW to BO.
When they load the data at sender side the idocs are stucked with error status 2:
"Could not find code page for receiving system" in transaction BD87.
Also when I reprocess it is successful. But its is getting stucked in SM58 with errors like:
1)Error in RFC connnection
2)ERROR REQU_D38IW3WD0XGK1DA48DM96N12J PG# 8 in BW
When I execute it throes an error saying "Function Module does not existsor EXCEPTION raised".
Also are many queues stucked in SMQ1 Outbound.
Please help. Many Thanks.

Messages stuck with green flag A. Status (XI 2.0)

Hi All,
we are running an instance of XI 2.0 and for this interface in particular we are pulling a file off an FTP server via the file adapter and pushing it through to a remotely enabled function which creates a batch session on our SAP R/3 4.6C instance. The interface used to work but we have now changed the name of the function within R/3 then made the corresponding changes in XI. Since we've done this the messages appear to be getting caught up somewhere between XI and R/3. The XI monitor (SXMB_MONI) shows in the A. Status field a green flag. To me this would imply that it is processing on the remote end (R/3) however there has not been any batch session created. This flag remains green indefinately.
I thought it could have something to do with XI caching some old objects so I ran tx SXI_CACHE and did a complete cache refresh (F6). This did not change anything. I have cleared all messages out of the queue using tx SM58. Then after reading another post in this forum I ran tx smq1 and smq2 to clear messages out of there but there was nothing in those queues.
When I push another message through it will sit in SXMB_MONI with the A.Status field having a green flag. Then I look in tx SM58 and find that the status text field displays "Transaction executing" for a very long time. Eventually it changes to "timout during allocate of registered program / CP" but the message is not going through. The only thing that has changed has been the name of the function in R/3.
any thoughts?

Hi Mark,
under the 'Target System' column in transaction SM58 it says "AI_RFCADAPTER_JCOSERVER". When I test it out it seems to work fine ... no errors.
When I looked at the trace labeled "Adapter_rfc.log" within the adapter engine it lists the following error.
>>RfcAdapter> Tue Oct 11 07:46:12 CDT 2005>>
> cannot load function template for Z_XI_INTERFACE_TEST1
> exception occurred, detail:
> com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'C
> MRCV'
I'm not sure why we get this error. The function template Z_XI_INTERFACE_TEST1 does exist and we were using it before. If I run the interface again this error will no longer appear. It almost seems like it will display only once a day.
any other thoughts?

IDOC to IDOC queue blockek status shows green flag

Similar Messages

Maybe you are looking for