request running for long time

[#1]

hi,

the below request has been running since last 1 hour.

as shown , the transferred records r 3, but added is 0.

whaty is the reason for this and how can i resolve it?

[Former Member]

hi,

check the job overview in source system and if its lo data source see whether the LUW are struck

then try making it green and see if you are getting those records.

if it is HR time extractor then a setting needs to be done in the r/3 side

Thanks

Krishna

[Former Member]

how do i chk for the lo data source?

[Former Member]

Hi

Check if job is extraction job is active in source ( Job name will be *BI Request number ) if Job is over check the if you have stuck idocs in SM58 T code . If there no Idooc . Mark this load as red and perform the manual update . sometime if you issues in ABAP routine it will stall for long time . once you simulate it will give you exact error.

Regards

Raj

[Former Member]

the source is tsr. how do i check for extraction job here?

[RamanKorrapati]

Hi Kirti,

Copy request name form header tab, and check in source system, t code SM37, job name: BI(request name).

if Your TSR system is SAP R/3, then you can go to t code SM37, provide job which i said above line. see the status, if its in active, select ur job and click on job step. its shows where its running/data packets sizes, records all info.

Some times due to busy of application servers, system may wont respond, check it once inbound and outbound Queues in source system(with help of basis team or TSR maintaince team).

second options: cancel this request, make it red in monitor as well as cube--> manage--> Request tab--> QM Staus make it red, delete it. Try to run again.

try to load again.

Regards

[Former Member]

i cannot see the job (bi-request id) in the sm37

[Former Member]

sorry, in tsr - source sys, i am able to see the job. it has completed. ut in bi, sm37 i cannot see tht job.

[RamanKorrapati]

Hi Kirti,

PFA,

by seeing your screen, its info package. so  go to in monitor,header tab, there is request id copy it,

go to Tcode - SM37 at source side, in job name: BI+reuest id, No gap between them.(Ex  BIREQXXXXXXXXXXXXXXXx).

below select all check box and see the job log and job step which i said in above message.

Regards

[RamanKorrapati]

ok. ask basis team ant inbound outbound queues and SM38 may be busy..ask them check at source, after that try to run again.

regards

[Former Member]

ok..

[Former Member]

Check in SM37 the job is terminated or running.

Give it some more time.

Sometimes process get stuck but 3 records shouldn't take that long.