Job is not getting triggred in source system

[Former Member]

Hi All,

At times, while executing my infopackages I could not able to find the job in source system.. It is not getting triggred in source system, when i repeat the load twice or thrice.. then it is getting triggered and done.. some times jobs are triggering fine ..what could be the reason for this . how to rectify it? ..

Thanks in advance

Br,

Harish

[KamalMehta]

Hi ,

From my point check the RFC connection between BI and source system . While you are running this IP do check the RFC connection and make sure it is working fine .

Also can you let us know whether you are triggering the Infopackage through process chain or manually .If it is working fine when you are running it manually but have issues when you are doing it through PC then it can be because of not having proper authorization for the user ALEREMOTE .

Also do check if you have some jobs running up in the source system at time when you are executing this IP .I mean do you have enough background jobs available in source system .

Please check and update accordingly later .

Thanks

Kamal

[Former Member]

Hi,

Thanks for your valuable inputs.

We are running this infopackage through PC only. and at that time BGD work processes also avalable in source systm.

If it is authorisation problem of ALEREMOTE, why it is running fine when we repeat it?

Now i checked RFC connection it is fine, I am going to check at that time of facing this problem again as u said.

Please share me if there is any other analysis.

thanks,

Harish

[Former Member]

Hi,

We found that our gateway between source system BW being broken very often,

Our basis team fixed this.

Regards,

Harish

[Former Member]

Hi Harish,

1. Are you load the data immediately or in background-immediately?

2. Are you trying to load text data from application server/ur workstation?

3. Is there any error message appear in after u execute the info package?

4. Are you check in SM37 whether the job is appear in schedule/released/cancelled status?

5. Are you check with the data target whether the request is up after u execute the info package?

[Former Member]

Hi Handoko Lim

1a) start data load immediately

2a) Data is coming from r/3 system

3a) no error message . when I click environment-> job overview in source system -> I could able to see the job name. when search the job name I could not able to see in sm37 and qm status of infopackage is yellow for long long time

4a) no job found with that name

[Former Member]

Hi ,

Sometime due to sequential read on table RSSELDONE at BW side, It takes longer than usual to send data request from BW to ECC.

When job is not getting triggered in ECC , just look into tcode SM50 in BW system if you are seeing sequential read on some table in some process. In that case you need to wait until this read gets complete.

Hope that helps.

Regards

Mr Kapadia

*Assigning points is the way to say thanks.**

[Former Member]

I didnt see any such seqential read in SM50...

I waitesd for 4 to 5 hrs still job is not getting triggered..

Br,

Harish

[ravi_chandra3]

Hi harish,

It depends on the availability of BG work process u can check that in SM50 tcode. Actually by default there are 4 work process(not sure) if all the work process are busy then u have to wait for some time till that work process becomes idle. IF the work process is idle then the process chain will execute. U can further increase the BG work process with the help of BASIS team .

Hope u got it,

Thanx & Regards,

RaviChandra

[Former Member]

Hi,

Its not about the BGD work processes.. because i checked it at the time of infopackage runing, there are so many BGD wrok processes are available...

Please suggest me what could be done for this.. what can be the reson for this.

Thanks,

Harish