Time Bucket Issue

[former_member182537]

Hi Gurus,

While loading data in BW from APO system manytimes we are getting below error -

"time bucket does not exist.

Error for COM routine using application program (return code 40.010 )

error in source system"

It comes randomly either for MALA ,MALO ,MALORE,RE data source & here we are loading full data everyday from APO in BW.

when we repeat problesm is resolved.

ww discused with APO team and they said that it might be due to some new master data created in APO & then there is a consistency check job that runs in APO everyday and in case there is some new master data and if process chain in BW runs before that then on that day chain will fail & on repeating it completes succesfully

can u advise any solution in order to prevent this scenario .As our APO system is 24/7 so many times it is possible that live cache is accessed by some one.

any suggestions welcome

thanks

pathak

[rico_frenzel]

Hi,

Com error 40010 means: TimGrid not exists. The reason why you got this

that another process was running at the same time and deleted the

timegrid used by the job.

This may have been either //TS_LCM_REORG OR transaction //OM17.

Some technical background of the correlation from batchjob and OM17:

When running a batchjob, the system creates a so-called timegrid for

reading the data on the aggregated level. In fact, these timegrids are

always created when data is read on a time-based aggregated level.

This timegrid is deleted at the end of each activity - so also at the

end of the Batchrun.

But also in OM17 and /SAPAPO/TS_LCM_REORG the system checks for these

temporary timegrids. As there is no check whether a temporary timegrid

is still used, repairing the the data with OM17 or /SAPAPO/TS_LCM_REORG

will delete all temporary timegrids that exist at that point of time. So

, OM17 or /SAPAPO/TS_LCM_REORG deleted the timegrid that still was in

use by the Batchjob..

For this reason, OM17 and /SAPAPO/TS_LCM_REORG should be only used at a

time where no processes are running on the system.

I'm pretty sure that one of the 2 checks have been running at that time and deleted the timegrid.

Best regards

Rico Frenzel

[former_member182537]

Thanks Rico i will check this and let you know

[rico_frenzel]

I'm sure this is the issue

[former_member187488]

Hello,

You'll need to avoid running APO consistencty check report during extraction, especially extraction with aggregates.

When extracting data, the system creates a so-called timegrid for reading the data. In fact, these timegrids are always created when data is read on a time-based aggregated level. This timegrid is deleted at the end of each activity - so also at the end of the extraction.

But also in some consistency checkes at APO side, like OM17, or /SAPAPO/TS_LCM_REORG, the system checks for these temporary timegrids. As there is no check whether a temporary timegrid is still used, repairing the data willl delete all temporary timegrids that exist at that point of time. So, these reports may delete the timegrid that is still in use by the extractor.

Generally, consistency check reports should be only run at a time where no processes are running on the system.

Best Regards,

Ada

[former_member182537]

Hi Ada,

Thanks for reply

but i would like to inform that we are not getting this time bucket issue on daily basis .Generally it comes 1-2 times a week.

And the consistency check job in APO runs daily at the same time when the process chain in BW is in progress.

If time grids are deleted by consistency checjk job in apo then process chain should fail daily.

so can u pls update more

thanks in advance

pathak

[former_member182537]

hi gurus,

any update on this ??