Reprocessing of tRFC Errors

Can anyone tell me whether we reprocess tRFC errors for all kind of RFC errors or reprocessing is restricted only for specific errors ..for eg:No authorization to send IDOC..

Kondal rao,
It is necessary to process all tRFC units. There can be many reasons why a tRFC failed. One example is target system not available. Another example from my testing scenario recently is ECC system generates idocs to PI. Lets say there were some duplicates in the buffer of PI adapters. Then the idocs will fail in ECC. This means the idocs are not transferred to PI.
Normally in this case, when the buffer is cleared the entries in SM58 should get picked up by the batch job and get pushed to PI. There can be some cases where you might want to process manually.
Tables:
When SAP issues commit work, the first ones to be processed are updates tasks (V1 - updates). Once done, SAP looks at the table ARFCSSTATE for t/qRFC. If any entries are found, those are processed.
In case of qRFC the entries are processed in the order in which they are received.
If an entry fails, the status of the same is set to SYSFAIL.
The best way to understand this process is to open SM58 and then click on the 'I' icon next to execute. It has all the good information you are looking for.
Thanks,
Vikram.M

Similar Messages

Automatic Reprocess of Trfc messages in PI production server using RSARFCEX

Hello All,
i am getting frequent errors of SYSFAIL in TRFC queue in PI. I am trying to schedule RSARFCEX report as the Background job, please advice me "is this correct solution" and also please tell whether this will effect any other messages other than reprocessing the failed TRFC messages.

Hi
RSARFCEX is the report for restarting messages with trfc errors. But if the messages are failed because of wrong entries in ALE configurations in case of IDoc scenarios then you need to resolve them manually.

Idoc or trfc error

Hi sap bw'iets
can any one describe step-by-step process to sloving IDOC or TRFC ERROR in production support.
thank you.
regards,
kiran

hi kiran,
sometimes idocs stucks in the source system, so it shows yellow in the monitor even if every thing else is showin green. so to correct this, go to environment -> Transact RFC -> In the Source System. If the status is showing "Executing" then leave it, otherwise u can drag it to BW by selecting execute LUW (F6), by selecting the tRFC.
hope this helps.
Regards,
Purvang
Assigning Point is to say Thanks in SDN *

Transfer(IDocs and TRFC) error when use infopackage to load data from R/3

I create an infopackage to load data from R/3, when start immediately ,there is no data transfered. The return error is :
transfer(IDocs and TRFC): Errors occurred
request IDoc: Application document not posted
Does anybody know how can correct this error?
Thanks great.

Hi Yimeng,
Check in SM58 transaction code in R/3 and see if any LUWs are stuck there. If so you can execute them manually and complete the data load.
regards,
Sumit

QRFC & tRFC Errors at the time of Production

Hi all,
If i got the qRFc 0r tRFC Errors in PRD system, then do we generally release those queues manually by going SMQ1 & smq2 and for tRFC Errors SM58 or do we schedule the STD programs to clear those strucked queues???
Dont provide any Blogs plzzzz
Regards
Suman

Hi
1) clear the queues in SMQ2,first try to activate them,if that doesn't work them delete them
2)You may need to re-register your queues.
Follow SXMB_ADM -> Manage Queues -> Deregister Queues
Afterwards, re-register the queues and activate from the same screen
3)Only use SMQ1 (outbound queues) and SMQ2 (inbound queues) if re-registering doesn't fix it. You will need to give the queues sometime to get activated so be patient.
4)From SXMB_MONI go to Queue ID of the message, a click here shall take you to qRFC monitor.
if the messages are stuck, you should see an entry indicating number of messages stuck in the queue.
a double click on the entry shall take you to detailed list.
if the messages are stuck because of any error (other than queue not registered etc for e.g. a message failure) then the first message shall show you that.
if indeed you find a message stuck in the queue then the way is to delete the stuck message (DONT DO THIS IN PRODUCTION SERVER without being sure of what does this mean for that particular process !!) and unlock the queue from previous screen.
5)Go to smq2 and execute F8. Then it should come as Nothing was Selected.
If any queues are present then open a queue.if the status is SYS ERROR check the entries,right click on the status text and give save LUW.This brings queue to READY. .
GoTo-> Qin Scheduler: check for the scheduler status to be inactive->Edit-> Activate Scheduler: status frm inactive to starting to wait.Now the queue will be RUNNING.U can see the entries in the queue moving.
Now go to SMQ3, right click on the queue and give Restore LUW.
6)this basically means tht message is waiting in the queue.
in sxmb_moni go to queue Id column and double click on the entry .It will take u to SMQ2.Check the status of the queue
If its SYSFAIL or STOP then double click on it and try to correct the error.After correcting the error send the message again.Also check whether the Queeu is Registred in transaction SMQR.
7)Select your queue form the sxmb_moni, you will reacht he QRFC monitor.
Here you will see some lock figures on the , Select on the 'Unlock Queues'. Activate your queues once again.
This is if your data is correct and queue is stuck. You should only delete the queue if it has errored out due to incorrect data and you need to urgenetly process the rest of the data in the queue.
If you drill down one step more than selct the error message and on the menu select edit-->Save LUW.

TRFC Errors in BI

Hello Gurus,
Why I have tRFC Errors in the Development System BI..
THANKS...
barish

Hi,
we see at the error message we find that the failure is due to Non-arrival of IDOCs from Source System to BW.
Idocs posted successfully with status '03' sometimes don't get through to the receiver port. i.e. It will be still waiting in the trfc queue(SM58) these also refer to as 'trfc errors.
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
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"
Check Note 561880 - Requests hang because IDocs are not processed.
Tarak

Trfc error elimination

Hi,
I am working in SAP BW 3.1c version. I would like to know is there any way in making disappearance of Trfc error from the system.
Thanks
Arul antony.

Hi,
first confirm Trfc error from the system means is it in transaction SM58 only?
if yes and u r finding errors in system u have the option to delete one by one jst to select an entry and delete
(or)
if u want to do in a group u have the option *reorganize*-- in menu options.
the path is sm58>after getting the entries on different selections->log file(1st option in menu)-->reorganize.
here u have the option of deleting different TRFC(s) depending on different error selections...
rgds,

Trfc error in the source system

Hi,
I got an error as trfc error in the souirce system,How to proceed regarding this.How to check RFC connections.What are the transaction codes for trfc and to check rfc connections.. please let me know.
Many Thanks

Hi,
We are having some problems.
While loading the data in BI 7.0 from R/3 ECC 6.0, sometimes (not always) IDOCs are getting stuck before coming to BW System.
The job always finishes successfully from R/3 side but before coming to BI, IDOCs are getting stuck and we manually have to push them into BI System.
How to avoid the situation of IDOCs getting stuck and what could be the possible reasons.
Please guide.
Thanking You,
Tarun Brijwani.

TRFC error "time limit exceeded"

Hi Prashant,
No reply to my below thread...
Hi Prashant,
We are facing this issue quite often as i stated in my previous threads.
As you mentioned some steps i have already followed all the steps so that i can furnish the jog log and tRFC details for reference long back.
This issue i have posted one month back with full details and what we temporarily follow to execute this element successfully.
Number of times i have stated that i need to know the root cause and permanent solution to resolve this issue as the log clearly states that it is due to struck LUWs(Source system).
Even after executing the LUWs manually the status is same (Request still running and the status is in yellow color).
I have no idea why this is happening to this element particularly as we have sufficient background jobs.
we need change some settings like increasing or decreasing data package size or something else to resolve the issue permanently?
For u i am giving the details once again
Data flow:Standard DS-->PSA--->Data Target(DSO)
In process monitor screen the request is in yellow color. NO clear error message s defined here.under update 0 record updated and missing message with yellow color except this the status against each log is green.
Job log:Job is finished TRFCSSTATE=SYSFAIL message
Trfcs:time limit exceeded
What i follow to resolve the issue:Make the request green and manually update from PSA to Data target and the job gets completed successfully.
Can you please tell me how to follow in this scenario to resolve the issue as i waiting for the same for long time now.
And till now i didn't get any clue and what ever i have investigated i am getting replies till that point and no further update beyond this
with regards,
musai

Hi,
You have mentioned that already you have checked for LUWs, so the problem is not there now.
In source system, go to we02 and check for idoc of type RSRQST & RSINFO. If any of them are in yellow status, take them to BD87 and process them. If the idoc processed is of RSRQST type, it would now create the job in source system for carrying out dataload. If it was of RSINFO type, it would finish the dataload in SAP BI side as well.
If any in red, then check the reason.

TRFC error

I need to configure central user administration for two clients in one physical system. I've created RFC destinations and assigned logical systems to clients. But I've got this problem: tRFC fails with error message 'No business system for system SID, client 200 in SLD.' What's wrong? I use SAP R/3 4.7, WAS 6.20 without j2ee. Is it about the System Landscape Directory?

http://<XIServer>:50000/sld/ListServlet?tsview=true
With this link you can see all WAS ABAP. Click on your SAP R/3 and add the new client if doesn't exist.
http://<XIServer>:50000/sld/ListServlet?bsview=true
With this link you can see all your business system check if the business system corresponding to your client. If it doesn't exist, create it. You can use this schema "XISID"_"R3SID"CLNT200 example : DX1_DT1CLNT200
Regards,
Chris
Message was edited by: Christophe DUMONT

SC workflow - "set status to released" step tRFC error

Hi All,
We have a "Shopping Cart without approval" workflow defined in our SRM system.
The workflow is working fine in Develpoment scenario however in Production it is stuck at "set status to released" step.
Checked that step and its a backgroung step with tRFC Object type.
When we click on tRFC Object Type it opens up "Transactinal RFC" screen with msg "error during tRFC call" and tRFC destination field as WORKFLOW_LOCAL_500.
Any help is this regard will be highly appreciated.
TIA
Regards,
Richa Sinha

Hi RS,
havent worked on SRM WF's,
check with BASIS on the Automatic WF Settings in SWU3 tcode, as you maintain RFC there, may be the RFC node in SWU3 is not active or something.
Hope it helps.
Aditya

Reprocess the bdc error session

hi all
in bdc session method .i have a error log how. ican reprocess the error log

Go To Analyze Session in SM30 for your records processed with errors.
Compare with your text file to trace the records not processed.
Copy them to new text file. do the corrections and re-processed.
But be sure that you had kept the previous session, otherwise you are not able to trace the records.
Regds,
Anil

JMS error reprocessing an syntax error edifact. Loopin error

Hello all,
The problem I have found is that the adapter is trying to process an not well formed edifact. As I read in the JMS FAQ
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/604e2b64-e689-2910-64b3-ffd650f83756
In chapter 13 it is said that is the standard behavior. Does anybody know the way to fix this error?
P.S. libraries installed v7.0
This topic was discussed here JMS adapter does not recover from error
Thank you for your time,
P.S.This issue is urgent Points will be given for sure if the answers help

Hi Sergio
Is your scenario transactional? Just try to uncheck "Transactional JMS Session" and try.
It may help
Thanks
Sai

BW-SRM TRFC Error when loading PO data

Hello,
We are implementing an extended classic scenario in SRM. Invoices are created on R/3. All data is loaded into BW. When loading the PO data into BW, we receive the error message: 'For purch. order 4320000040 backend source system is empty even with extd sc'
In SRM, where the PO was created, the PO is present and in the tables EKKO and EKPO in R/3 as well. Does anyone have an idea why this error occurs?
Grtz

Hi Juno,
Do you get this for this particular document or all the postings?
THanks and Regards
Subray Hegde

TRFC error status

Dears,
I am getting the error "RfcAbort: get_idoc: file(IDOC TYPR) exist,..." at SM58 transaction and I can't find anything here about that message error.
I have checked the WE02 transaction and the Idoc was created, the RFC destination that the Idoc should be sent is working fine.
Testing the partner at IDOC transaction no problem was found.
The message error at SM58 is incomplete, is there any other transaction that I can check to clarify what would be happening?
Thanks for your attention.
Best Regards!
Anaer

Hi Thanga, thanks for your response.
I had already tested the connection and it is working fine.
When I tried to activate the debug option I get the error message "You cannot debug type T connections".
Is there any system log that I possibly could check to get more detais of SM58 errors?
Thanks in advance!
Anaer Lima

Reprocessing of tRFC Errors

Similar Messages

Maybe you are looking for