Info Package running long time stuck in Yellow status

[Former Member]

Hi,

I have an Info Package which is running very long time, moreover it is extracting only 53 records, till last week it was fine and from past two days there was this issue. I have checked all the tcodes (BD87, SMQ1 etc)  at ECC side as well and everything looks fine. Even the QM status stuck in Yellow color. I tried activating the data source once again and also tried creating a new info package but still the issue prevail. There are other process chains which runs daily and the info packages are running fine in that process chains.

[RamanKorrapati]

Hi,

Assuming as info pack in process chain and taking log time.

Have you tried to run manually?

please run and check it.

Have you checked your ecc job log?

Please go to your info pack monitor, menu Environment-->job overview--> job in the source system--> enter ecc user id and pass word, you will get your ecc job, select job and click on log details icon on tool bar. See job log details and share if you see any abnormal message.

Can you try to change your info pack schedule time and see.

As my guess during your info pack loading time, all application servers(BGD) might be busy and unable to process your info pack status messages back to monitor.

Next time you keep on montir your info pack loading and see the SM50/51.

Mean while at ecc side You can check SM58, if see any failed queues there, you can process them by manual(F6).

Thanks

[Former Member]

Hi Raman,

I've tried all the inputs which you've given and still I'm facing this.

I've created a new IP and tried to run it manually but still issue prevail.

[RamanKorrapati]

Replicate your data source and activate it.

later trigger and see.

during your info pack load, have you seen SM50 at bw side.

SM50 - will shows available free/running application servers.

[Former Member]

Hi Raman,

Replicated datasource too and still issue prevails. There were good no of processes available at SM50.

[Former Member]

hi,

is it a standard data source or a customized one. Also if it is a custom data source then has the abap code if any been optimized. Please share more details regarding the data source,  this would help in the analysis for the long runtime of data loads.

regards,

Arvind.

[Former Member]

There could be few reasons for this:

a. Check the job in R3 or source system. There is a chance that job got stuck in source system itself. Based on status, you can decode what to do.

b. If the job is successful in source system, the long running ststaud could be because of TRFC or IDOCS. Check and lear all the TRFC/IDOCS. (From IP monitor screen, go to Environment -> Transact RFCs - Source system/Data ware House).

Rgds..

Shambhu

[Former Member]

Hi Shambhu,

I have checked if there is no stuck at ecc side.

Also job is successful in ECC side, and the trfc/idocs are also looks fine.

[Former Member]

Then check the job in BW side. If the extraction is done, may be IDOCs are stuck in BW side.

If nothing found, then you can change the QM status to green and proceed.

Rgds..

Shambhu