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>

Similar Messages

Problem in TRFC queue (SM58) - IDOC2FILE scenario

Hi,
I am executing IDOC2file scenario. In the transaction we19, i have successfully posted the IDOC to external system (XI).
But the iDOC is still in TRFC queue. (SM58 or BD87).
Recipient details
Port : RFC in We21.
Partner No. : XI logical name.
Partner Type: Logical system.
Sender details
Port : SAPBIW
(This is the confusing part, I was told that first three letters should be SAP and next three should be SID of the SAP system).
Is this mandatory. But my TRFC (we21 in BW) didn't have any such port, so i created one.
Partner No. : BIW logical name.
Partner Type: Logical system.
I am getting this error in SM58
Transaction IDX1: Port SAPBIW, client 001, RFC dest contains error.
Now i want to know what is the problem because of which IDOC is not being to pushed to XI

Hi,
go to sm58 and release or delete that queue, next time idoc will not stuck in the queue.
<<<Port : SAPBIW
(This is the confusing part, I was told that first three letters should be SAP and next three should be SID of the SAP system)Is this mandatory
It is not mandatory, you can leave this option blank.
Thanks

BD87 hide "idoc entries in tRFC queue" by assigning to status or other meth

Hi,
I am working on the inbound side of an idoc interface for message type MATMAS. My problem is that when I enter in BD87 there are more than 400 hundred entries in "idoc entries in tRFC queue". Now, whatever filter I put on the first screen this line appears. Even, if I enter with a specific idoc number. These entries are obviously outbound errors and are completely irrelevant to the interface I am working on but will make the reprocessing screen unnecessarily complicated for the users. So, basically I want to allow the end user to filter out these messages.
I noticed that the errors "idoc entries in tRFC queue" aren't associated to a status and I was wondering if it is possible to give them a status value and so make them sensitive to a status filter. But if this isn't possible any solution to hide these error messages from the end user would be equally valid.
I know someone will probably suggest that the best solution would be to remove all old entries from tRFC queue in SM58 and that there shouldn't be so many idoc in entries in the tRFC queue. The problem is that it is not my role to monitor tRFC in production and if it has not been regularly monitored up to now then it probably won't be in the future.
Many thanks in advance,
Jamie.

Hi Jamie,
To the best of my knowledge the shown outbound RFC entries in BD87 are a feature that cannot be suppressed. I.e. in the coding of BD87 one can see logic where it automatically checks for outbound RFC errors and adds those to the output.
In general IDoc status 03 should be associated with the outbound RFC errors. Yet, when one sees those in BD87, the IDoc status field is empty. Along your train of thought I had also previously tried to suppress those displayed IDocs by adding a filter for suppressing status 03 or blank status, but nothing helps. And as you correctly point out, even when using BD87 on a single IDoc (e.g. specified via IDoc number), the transaction will still display the outbound RFC errors.
So unless somebody else has some good idea or insight, I'm afraid you're stuck with that behavior.
Cheers, harald

Idocs stuck in tRFC queue - why?

We had an issue where 2 Idocs looked like they where sent from our
logistics box to our HR box, but in reality, they were stuck in the tRFC
queue in our logistics box.
The idocs were created 2 days ago and were never processed. When I found
them in SM58, I executed them and they were sent and processed
successfully.
Why would those idocs get stuck in the tRFC queue? Shouldn't the queue
auto-process those idocs?
thanks,
robert.

Hi..
Normally this will happen when you Set the "Collect IDOCs" Option in the Partner profile Outbound Message type.
In that case these IDOCs will be dispatched only when the RSEOUT00 program runs in Batch or Explicitly.
If you set "Transfer Immediately" option in Partner profiles then they will be dispatched Immediately.
reward if Helpful.

JCO Server and SAP trfc queue

Hi,
we are sending IDocs from our sap system to a JCO server. Let's assume we are sending 1000 IDocs to it. After sending there are no IDocs in the trfc-queue and the status of all IDocs is "green". Can we assume the JCO server received all 1000 IDocs? Is an empty trfc-queue always an indicator for a successfull sending process even there are some problems with a weak network(network interruptions). I know IDocs are tansaction based. For my understanding a transaction is okay or not. So an empty trfc queue should indicate everything went fine and all IDocs were received?
I appreciate any comments on that issue ...
-Steffen

If the status of all idocs is green which indicates the communication layer is ok. As you said, the idocs are transaction based. You need to make use of transaction id to confirm everything is fine from the viewpoint of your business logic.
Dennis

IDOCs in TRFC Queue

Hi,
We have a ALE scenario where we send IDOCs to other SAP system.
The IDOCs we send are sitting in TRFC queues, they are not sent to the target system. I checked all the ALE settings, they are fine. The processing mode is "Immediate".
When I go to SM58 I will find the entry for the transaction with status "Transaction Recorded". If I select the entry and press F6 (Execute LUW) the IDOC is sent to the target system and the queue becomes empty.
What I am missing? I dont want to go to SM58 everytime I post an IDOC. I am sure there will be some setting to process the IDOCs from the TRFC queue automatically. Can you please let me know that?
Regards,
Ravikanth

HI,
the problem is caused by immediately processing.
Pipeline:
Outbound Processing -> sender IDOC -> TRFC Queue -> receiver IDOC - Inbound Processing
In case your are using IP (immediately Processing) at sending side your are using 1 LUW to send it to the TRFC Queue and saving IDOC at receving side -STOP.
In case your are using IP at both sides .. your are using 1 LUW for the complete Pipe.
That means this LUW is still open if the IDOc is processed in the receiving system.
ToDO:
Go to your Receiving System and check the Processing Settings. Try to use Background Jobs or get higher Batch Processing to avaoid TRF Queue Jam
Regards,
Gordon

Idoc in trfc queue

Hi,
I have requirement where the idocs are sent to external (non sap) system, now when system is down or for some other reason the idocs gets queued up in trfc queue(SM58) , now when the system is up and running these idoc gets passed to the external system without any particular sequence, i.e. suppose for HR data there is 2 idoc for same employee and the IDOC1 should go before IDOC2 , then this not happens when the trfc queue(SM58) is cleared.
I wanted to know how to mantain this idoc Serialization so that the idoc go in sequence, i have gone through some idoc Serialization document but i think its useful when both system is receiveing system is also SAP.

Hi Sudhakar,
Check this:
Re: tRFC & qRFC
Reddy

Idoc stuck in trfc queue

Hi,
I have requirement where the idocs are sent to external (non sap) system, now when system is down or for some other reason the idocs gets queued up in trfc queue(SM58) , now when the system is up and running these idoc gets passed to the external system without any particular sequence, i.e. suppose for HR data there is 2 idoc for same employee and the IDOC1 should go before IDOC2 , then this not happens when the trfc queue(SM58) is cleared.
I wanted to know how to mantain this idoc Serialization so that the idoc go in sequence, i have gone through some idoc Serialization document but i think its useful when both system is receiveing system is also SAP.

duplicate post, locked.
Thomas

IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

R/3 to XI manually IDOC sending and problem:

R/3 to XI manually IDOC sending and problem:
I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
I check XI (sxmb_moni) but there is nomessage there.
Problem 1: I don't want R/3 ask me UID and password for XI access
Problem 2: I want to see message in XI (sxmb_moni)
Thanks

Hi Cemil,
>>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
check the RFC destination from R3 to XI (SM59)
you will find the right one from your port (We21)
you can also check step by step procedures
for IDOC - XI in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Idoc to file problem.......... IDOC lost

i have a idoc to file problem,
the idoc is sent from R/3 to XI,
the problem is IDOC is sent from R/3,
it didnt reach to XI.....
i have checked.......we05 in R/3, it gives a status 3,
then i checked SM58 in R/3, it shows nothing,
when i check in idx5 in XI, theres no trace of that idoc....and no trace of the scenario run in SXMB_MONI
pls help, where can i trace the idoc.....
pls help

Hi sudeer,
Did You Check It In WE19.(Test Tool For Idoc Processing)
If Not Do The Following Steps:
Step1:
>> Give Your Existing Idoc Number.
Step 2:
>> Basic Type is Your Message type.
 Ex: MATMAS05 or CREMAS05.
Step 3:
>> In Your Existing MATMAS05 or CREMAS05 Structure say EDIDC,
>> You Should Fill Your Mapped Entries In Data Structure of EDIDC.
>> So that Those Fields Gets Framed as Segments.
Step 4:
>> After Doing It goto Menu Bar and Click Idoc And Goto Edit Control Record.
Step 5:
>> Now You Give Your Sender And Receiver Port Number Along With Your
 Logical System And Message Type again its Your MATMAS05 or
 CREMAS05 .
Step 6:
>> After Doing It Click Standard Outbound Processing.
Step 7:
>> It Will Say what Happened To your Idoc.
Step 8:
>> It Is For Sure That if This Processing Fails It Wont Go To XI..
Regards,
Dhayanandh .S
Dont forget To Provide Points If Found Helpful...
Message was edited by:
 DHAYANANDH SIVASANKARAN

InfoPackage Stalls in tRFC Queue

Hi All.
I have a problem I've been unable to figure out. I trigger an InfoPackage that starts an extraction from an ECC 5.0 system. When we trigger the InfoPackage, we get the "Data is Requested" message at the bottom of the screen (BW 3.5). When we check RSMO, it stays yellow until it times out. I checked out the tRFC queue (SM58) and saw an IDoc listed as "Recorded" but we didn't expect to see anything. Upon triggering another load, we saw the entry in SM58 and told the system to execute the LOW. The load itself completed as expected.
We also checked out a load from BW to BW (via the Myself connection). This load executed completely without getting stuck in the tRFC queue.
I checked the RFC connection settings (SM59) and the partner profiles (WE20) and don't see any differences between the ECC and BW system connections. Both are set to process automatically and the connections work.
Does anyone have an idea what may be the cause of this problem?
Thanks,
Adam

Hi again,
it looks like the tRFC handling is different in the latest version....
See note
Number of dialog processes for data transfer
SAP Note Number: 916706
and help
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/13/083f420e09b26be10000000a155106/frameset.htm">BI Service API tRFC Data Transfer Using QOUT Scheduler (New)</a>
the main difference is that there are no IDOCs anymore...
hope this helps...
Olivier.

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.

IDoc- XI- IDoc - Problem in TRFC-Queue

Similar Messages

Maybe you are looking for