cancel
Showing results for 
Search instead for 
Did you mean: 

Delay in IDOC posting from R3 system

former_member226000
Participant
0 Kudos

Hello Experts ,

We are missing our SLAs daily due to late posting on IDOC from R3 to BI system . Generally there are 4 IDOCs that are posted on daily basis . First 3 IDOCs arrive at BI side immediately within 5 minutes. However the last i.e. 4th IDOC takes almost 2 hours to arrive at BI side . Can you please throw some light on what may be the reason for late posting of IDOC ? Your help here is much appriciated .

Best Regards,

Mandar

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi mandar,

If idocs are getting stuck , you can schedule the program RBDAPP01 to run for say every 2 minutes in BI side, please remember to change the partner profile setting in WE20 for RSINFO to " trigger by background program" ..... this program will manually puch idocs which are stuck ....

Also you can use BD87 to manually clear idocs which are in yellow status ...

former_member226000
Participant
0 Kudos

Hello Sreejith ,

BD87 , I have to use in source system OR BI system ?

-Mandar.

RamanKorrapati
Active Contributor
0 Kudos

hi mandar,

check at bw side t code BD87

Regards

TammyPowlas
Active Contributor
0 Kudos

This thread belongs in the BW space

In the future please post these questions there

This thread will be moved

Tammy (Moderator)

Former Member
0 Kudos

Hi Mandar,


Can you check or ask Basis team to monitor the CPU Utilization and network utilization at the time when iDocs are coming to BI system.

May be they can put some light on your issue.

Regards,

Ganesh

oliver_uy2
Active Participant
0 Kudos

Check the status of the IDoc in SM58. if the idoc pushing do BI is  on "transaction recorded" state, try to execute the LUW to transfer data to BI.

Try to check this link:

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=145719978

former_member226000
Participant
0 Kudos

Thanks a lot Ganesh for prompt response . We have already checked with our basis team for CPU utilisation and jobs sharing CPU with BI processes . We didn't observe any process consuming much CPU at the time of Infopackage run . Is it possible that from BI side we need to any tunning ( I don't think so as Infopackage is purely R3 thing )

Best Regards,

Mandar

former_member226000
Participant
0 Kudos

Thanks Oliver for your reply . My concern is IDOC postings are getting delayed  . IDOCs are not stuck in R3 system and we haven't interferred with there posting .

Best Regards,

Mandar.

oliver_uy2
Active Participant
0 Kudos

Hi Mandar

I'm not sure why but sometimes idocs get stuck but will then proceed to transfer to BI after certain number of hours. if you can replicate the problem again try to check if the idoc gets "transaction recorded", then you can manually execute to continue to transfer to BI by selecting on the idoc and pressing F6 or "Execute LUW". if that still does not proceed to transfer to BI then the link i provided is not correct.

former_member226000
Participant
0 Kudos

Hello Oliver ,

As we are facing this problem on daily basis , I will check whether IDOCs are in status " Transaction Recorded " today night . Will keep you posted about the progress . Also my concern was , though I manually "Execute LUW" for today , it is not a permanant solution for that . Maybe I have to chase BASIS team to know why IDOCs feel comfortable in residing in R3

-Mandar

former_member226000
Participant
0 Kudos

Also can you help me out with the job name which delivers IDOC from R3 to BI IF ANY ? Because I discussed with BASIS team and they are asking us job name which posts IDOCs from R3 to BI which we don't know.

Awaiting your reply !

-Mandar

oliver_uy2
Active Participant
0 Kudos

Hi Mandar

The procedure is for immediate fix and identify the problem.

There are corresponding sap notes to permanently fix the problem.

Notes: 1548446 and 1333417 might help with you on this. you can also try Note 1163359 to help regarding data transfer from R3 to BW.

Hope this can help.

oliver_uy2
Active Participant
0 Kudos

Hi Mandar:

job name in R/3 is the request number in BW

EX.

in BW  request number  : REQU_EJTADFGAN3KDMFME

in SOURCE Job is BIREQU_EJTADFGAN3KDMFME in sm37

but for idocs you can check on sm58 and input the backgound user as filter. for this its normally "ALEREMOTE" unless you change the backgound user. you can also filter using * since this will only display current idoc processes.

Former Member
0 Kudos

Hi Mandar,


Also check iDoc in BW in both inbound and outbound queue. you can directly go from monitor screen for all the steps of your extraction and check where it is taking time.

Regards,

Ganesh