Delta infopackage still running in proces chain

[amine_lamkaissi]

Hi guys,

A delta infopackage is still running in a process chain in BW since many hours.

Here the screenshots :

What can be the causes of this behavior? What is the best way to solve it and avoid any delta data lost?

Thanks.

Amine

[RamanKorrapati]

Hi,

Seems like some thing not responding properly from CRM system.

from PSA please download 164 records into excel sheet and keep them as backup.

make your latest psa request as red and keep it there.

Rerun your delta info pack by manual, it will asks for repeat delta - yes and continue it.

it may pulls previous 164 + new records also.

if issue still continued then better think about activation of data source or re transportation of data source or Recheck CRM-BW adapter settings.

is this is happening for this CRM data source only or all CRM data sources have same issue?

Thanks

[amine_lamkaissi]

Hi Raman,

It's happenning only with this datasource.

Can you please tell me more about how to check CRM-BW adapter settings?

Thanks.

Amine

[RamanKorrapati]

please go thru CRM- BW Adapter settings doc which is available here(Google/SCN).

it would be helpful.

[amine_lamkaissi]

Hi guys,

When i set the request to red. The system sent me an information message that told there is a risk to loose data.

Did someone has this message before? what do you think about this informative message?

Thanks.

Amine

[karthik_vasudevan]

Hi Amine

I think its just an warning message as you are stopping delta. No need to worry if your jobs successfully completes when you repeat the step in process chain.

I didn't notice your log from ECC system. Did you check the ALE management from your monitor before trying repeat option. The log shows something wrong with Idocs

Regards

Karthik

[amine_lamkaissi]

Hi Karthik,

ALE are all green (Inb and Out) in both source system and BW.

Amine

[karthik_vasudevan]

OK then. You need to go by the way others have mentioned. Repeat the job once you have changed the status to red and see how it works.

The warning message is normal. I have got it few times when we had problems in delta process. So please proceed

Regards

Karthik

[Former Member]

Hi Amine,

Go ahead with the repeat of last delta. It should not create a problem with W.R.T Data

Regards

Vivek

[karthik_vasudevan]

Hi Amine

Hope you have checked some basic things.

If not, please check the job status in source system. There might be scenarios where there are some idocs stuck in source system.

Go to Environment in the monitor screen, Job overview and Transact RFC in source system (check both individually) and see if there is any clue there.

If there are any TRFCs in recorded mode, execute them manually by pressing F6.

If the job is in active status, check if there are resource available sin source system to process the Idocs.

Please check these and let us know. we will proceed further

Regards

Karthik

[amine_lamkaissi]

Hi Karthik,

First, thank you very much for your answer.

I checked everything. No idocs blocked in BW or ECC.

The job in ECC has status finished.

Thanks.

Amine

[Former Member]

Hi Amine,

it could also be the reason if the job in BW(BI_PROCESS_LOADIGN) got stuck . check the job status. if it stuck, then you can change the total status to RED and then repeat the info package again. this will bring the last failed delta (repeat request of last delta), there wont be any data loss.

[karthik_vasudevan]

Could you please check the logs of pervious days?

Did you make any changes to the flow? Do you have any short dumps in ST22

Please click on application log in monitor screen and provide the screenshot.

Regards

Karthik

[amine_lamkaissi]

Karthik,

No modifications were done. But we made a refresh few days ago. But everything was fine until today.

I checked for dumps in both BW and ECC, i found nothing.

Which logs do you need please?

Thanks.

Amine

[karthik_vasudevan]

Thanks Amine

What do you mean by refresh. Is it quality system then?

If so, do you have problem only with this info package or any other?

In the status tab of the monitor screen, click on Application Log at the bottom and see if it gives some useful information.

Regards

Karthik

[amine_lamkaissi]

Hi Jyothi,

This job is in BW or ECC level?

Thanks.

Amine

[amine_lamkaissi]

Hi Karthik,

We made a refresh of quality with data of production, so we stopped the process chain in production and reinit the delta afterwards.

It's the only infopackage i had the problem with.

Thank u for the application log, but i couldn't found any logs related to my issue.

Amine

[Former Member]

Hi,

BI_PROCESS_LOADIGNG --> is from BW (if you are running it from process chain, then right click infopackage-->display message-->batch monitor).

REQU_** is from Source (Infopackage-> header)

[amine_lamkaissi]

Ah ok thank you,

Actually the job in source system seems to be fine.

Thanks.

Amine

[Former Member]

Hi Amine,

I could see from your above comments that the extraction job already completed and the ipak is taking long time to complete(164 records), then forcefully change it to red and then repeat the job.

Let's see whether that was a one off issue.

Regards

Vivek 

[karthik_vasudevan]

Strange but an interesting issue. Could you please what is the full text below in your technical status.

Regards

Karthik

[amine_lamkaissi]

Hi Vivek,

In fact, i was thinking about that solution.

But i will wait a little before doing it, since business is not blocked today.

But i really need to understand what can be the root cause of that kind of issues?

I tought about RFC connections problem, basis team checked and told me that everything is fine on their side.

Do you know what can be the root causes?

Thanks.

Amine

[Former Member]

yeah, I read it from your previous posts that source job finished with no errors, that is why I ask you to check the BW background job. well, if you ran info package in foreground, then there wont be any job.

as you said, this is the only one which had issue, you can change the status to RED and re-run .

if it is a recurring issue, then we can investigate further. Thanks

[amine_lamkaissi]

information has been derived from data extraction

Amine

[karthik_vasudevan]

haha. Good one. As you said, before trying to make the request red, we could try all possible ways to get the exact root cause.

Then obviously,we could try the other way.

In the details tab, extraction shows errors occurred, but the status is yellow. Do you think there is any more information in that? by right clicking the data packet and clicking display messages or help for node or anything else.

Regards

Karthik

[amine_lamkaissi]

Here you are:

Display messages

Display logs

Amine

[karthik_vasudevan]

Good. Now we have some more information to check against.

Go to SLG1 in your source system and provide the object name and subobject name as below. See if you have got some logs.

Regards

Karthik