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 *

Similar Messages

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

Transfer (Idocs and TRFC): Errors ocurred

This error occured when we are loading flatfile (trans) into transactional infocube:
Info Idoc 1: IDoc with errors addeed (in red)
Info Idoc 2: IDoc with errors addeed (in red)
Info Idoc 3: IDoc with errors addeed (in red)
Data Package 1: arrieved in BW; Processing: Selected number does not agree with transferred
Info Idoc 3: IDoc with errors addeed (in red)

What other data package errors are you getting? TRy going to a PSA first if you can...I have never tried loading a flat file to a transactional ODS directly.
/smw

Transfer (Idocs and TRFC): Errors occured

Dear All,
data extraction from R/3 into BI is working for small number of records. for huge number of records it ends with error,
i have adjusted info package setting DataS. Default Data Transfer but did't work. on the R/3 side i can see "transaction recorded" on tcode SM58 and the job successfully completed
please share me your experience on this issue,
With Regards,

Okay then I would think that there is some cofiguration issue related to communication between two system. Can you check below:
1. SM59 - RFC connections are wroking fine?
2. Any stuck Idoc or failed idocs in WE05/WE02- just trigger the infopackage and have look at WE05 and monitor the idocs. It may happen that you are able to recieve the Idocs but not able to send it back.
3. Configuration in WE20 for partner profiles in ECC system for your BW system. mainly outbound parameters message type RSSEND. Check if is as transfer immedeately.
4. Try executing your datasource in RSA3 with same exact selections as you pass from BW.
5. Check if you have any short dumps in ST22.
6. Check logs in SM21.
7. Try running infopackage for the same selection from past when you know it worked fine.
Please let me know findings.
Thanks
Amit

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.

Error in Transfer (IDOC and TRFC )

Hi experts
I am getting the error in Transfer (IDOC and TRFC ) Info IDoc 1 : Sent not arrived : Error posting data to port" when I am trying to Upload data by executing an infopackage.
Pl. advice.
Thankls in advance
Dinesh Sharma

Hi Dinesh,
This latest error code E0 266 & is really a Basis one (BC-MID-ALE); not BW.
If the error occurs all the time then please do the following.
Firstly, please ensure that the relavant RFC destination is set up as per SAP Note 613389. The use of a logon language is a must.
Secondly, please also add the value of SCP2 as well as SCP5 to the role of the RFC user as per Note 784381 (SCP2 isn't mentioned in the note but please add it anyway) - This should resolve your issue.
If you only see this error sometimes, then set the flag in tcode OYEA as per Note 784381.
Hope this helps,
Colum

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

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

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

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.

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

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

IDOCs Packaging ... What if one IDOC is in error in the packet ?

Hi all,
What will happend to the rest of the IDOC in the packet ?
Lets say, i packaged my IDOC in a bunch of 5. The first 3 IDOCs, their payload are ok. However the 4th has a bad payload and it crash in the mapping section ...
Does the first 3 IDOC (and the 5th one) will be sent and the one in error (4th one) will remain (in XI for mapping error) ?
Thank.
michel osborne

Hi chandrakanth.k,
Thank for your response. I have seen these blogs. I am not using the BPM.
I am using the IDXPW + Messages filter (sxmsfilter) to packaged the IDOCs.
I have made some tests ... wird enough ...
test #1:
idoc (1) - error
idoc (2) - valid
idoc (3) - valid
.... etc ...
test #2:
idoc (1) - valid
idoc (2) - error
idoc (3) - valid
test #3:
idoc (1) valid
idoc (2) valid
idoc (3) - valid
idoc (4) - error
In the "test #1", idoc (2) & idoc (3) are processed correctly (idoc sent to the SAP ECC backend system). Idoc (1) is stuck in XI with errror (mapping) which is OK.
In the "test #2", work the same as in test #1, idoc(1) & idoc(3) hs been delivered to the SAP ECC backend system.
However, in the "test #3"all idoc (1, 2, 3,4) are stuck in XI ... idoc(4) in error (which is ok), idoc(1) up to - idoc(3) in sxmb_moni has the racing flag .... but not delivered to the SAP ECC backend system ... they have the status: Message Schedule for outbound side ....
It seem that each time the package end with and idoc in error, the entire batch get stuck in XI .
How can i get sent them (test case #3) !!?!?
Thank in advance !

IDOC Tables with Errors Post System Refresh

Hi Everyone,
Is there any Report or other way through which one can get List of IDOC Tables with Errors Post System Refresh.
Thanks,
Regards,
- Ishan

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

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.

Idoc or trfc error

Similar Messages

Maybe you are looking for