Optimizer: A valid time buckets profile has not been chosen

[former_member200568]

Dear Experts,

We are in the process of Taking SNP Discrete as well as Linear Optimiser run & PPDS activity at every block beginning.

From last Optimizer run, we observed that SNP Run is failed due to error message "Optimizer: A valid time buckets profile has not been chosen"

We have Extended periodicity of planing area via /sapapo/MSDP_ADMIN:

also extended time series for the used planning area for SNP Optimiser.

Also checked data view validity. All looks OK to me.

I know this error is occurred to many user in the past. I am still not sure what & where i am missing in checking the Bucket Profile.

Need your view point to resolve the issue.

Regards,

Deep Dave

[former_member200568 · Accepted solution]

Dear All,

Found the solution i guess.

It was issue regarding resources which were used during the optimiser run.

Factory Calendar was not extended which were assigned to resources & hence while taking demand of 2016, It was showing error of no valid time bucket profile was selected.

Closing the thread. Hope it will be the reason for many like me where demands of next year horizon will be planned.

Regards,

Deep Dave

[SatishWaghmare · Accepted solution]

Hi Deep

I am glad you found the solution to your issue.  Appreciated you sharing the solution details for benefit of others.

Thank you

Satish Waghmare

[SatishWaghmare]

Hi Deep,

Please refer this thread for potential clue.

A valid time buckets profile has not been chosen | SCN

Thank you

Satish Waghmare

[former_member200568]

Dear sir,

Thanks for your input.

Still i would like to know how to set correct time bucket profile. as when i run SNP otimiser it keep on giving error as valid time buckets profile has not been chosen.

I have extended storage bucket profile 0 which was previously 01.01.2009 to 31.12.2015 to now 01.01.2009 to 31.12.2018 via tr32

And time bucket profile dp/snp which is 18 weeks basic as well as display periodicity.

it was working fine till it was planning under 31.12.2015.

Must be some small parameter i am missing to check or doing wrongly.

Is there any thing to do with resources ? as few jobs are completed successfully.

Regards,

Deep Dave