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

Similar Messages

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

IDOCs in trfc with status text as error

Hi,
I have IDOCs in trfc queue with status text as 'The ABAP/4 Open SQL array insert results in duplicate database records'.
How to reach this error point and rectify the same.
Regards,
Sheetal

Hi Sheetal,
Please refer the link,
Successfully posted IDOC from XI but not reflected in Receiver R/3 system
Best Regards.
Reward points if it is useful.

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>

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.

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

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

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.

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

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

Run Reorg of tRFC queue like transaction SM58

Hi.
Does somebody know how I can run a reorg of the tRFC queue from an ABAP program?
Cheers,
Nils

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

Transfer (IDocs and TRFC ) Missing Messages

Hi,
I have taken INIT load and records were loaded successfully in the target system.Now when i run delta , the status goes Green but 0 records are loaded ,and also there is error as :
Requests (messages): Everything OK
Data request arranged
Confirmed with: OK
Extraction (messages): Everything OK
Data request received
Data selection scheduled
No data available, data selection ended
Transfer (IDocs and TRFC): Missing messages
Processing (data packet): No data
Subseq. processing (messages) : No errors
Process Chains : Everything OK
Other (messages): Everything OK
I have checked extractor in source system and it has records in it.
Edited by: Bhavna_m on Aug 26, 2011 12:57 PM

Hi,
Transact RFC error
tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
Thanks,
JituK

Transfer (IDocs and TRFC): Missing messages or warnings

Hi,
While loading data from ECC to BI, I'm getting the following Error. It is for all DataSources...even for Full loads with 15 records also.
Requests (messages): Everything OK
Extraction (messages): Missing messages
-->Missing message: Request received
-->Missing message: Number of sent records
-->Missing message: Selection completed
Transfer (IDocs and TRFC): Missing messages or warnings
Info IDoc 1 : sent, not arrived ; Data passed to port OK
Info IDoc 2 : sent, not arrived ; Data passed to port OK
Info IDoc 3 : sent, not arrived ; Data passed to port OK
Info IDoc 4 : sent, not arrived ; Data passed to port OK
Request IDoc : Application document posted
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
Processing (data packet): Everything OK
Data Package 1 ( 10 Records ) : Everything OK
Note: I tried with following options, so please don't repeate again.
1. No LUWS in ECC in SM58.
2. Connections are OK an dtested in SM59.
3. WE20 is also OK.
4. Job Finished successfully in ECC.
5. No Dumps in ST22 in ECC.
6. Dumps in BW in ST22.
Error Message is:
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSSM" or "LRSSMU36"
"RSSM_OLTPSOURCE_SELECTIONS"
7. Tried with BD87 in ECC and BI also.
Thanks
Ganga

Hi,
Every thing is fine. And I searched for OSS note and I found some notes but I'm unable to resolve it. My data Target is Cube and DSO's.
Note 852443 - Dump in include LRSSMU36 RSSM_OLTPSOURCE_SELECTIONS
Note 869628 - Constant WAITUPDA in SMQ1 and performance optimization
Note 901878 - Information IDoc Sent, but did not arrive
Note 913330 - tRFC LUWs are not created
Thanks
Ganga

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.

TRFC Queue

Hi,
Is there any job that can check the trfc queues for any error entries and remove it automatically so that it process the next one in the queue.
Regards
Krish

> Is there any job that can check the trfc queues for any error entries and remove it automatically so that it process the next one in the queue.
Using this program you can delete RSARFCER Delete various LUWs
[http://help.sap.com/saphelp_nw04/helpdata/en/25/bcfa40badbf46fe10000000a1550b0/content.htm]
Thanks
Siva

IDOCs in TRFC Queue

Similar Messages

Maybe you are looking for