Skip to Content
avatar image
Former Member

Capacity Leveling question - heuristic

we use capacity leveling with backward scheduling only and one of the behaviors is causing problem and not liked - I understand there is nothing wrong in the system but any body faced a similar problem and have any ideas please share ..

pls let me know should you need any further information - I can think of using Badi to influence this behviour

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 02, 2015 at 06:42 AM

    Hello,

    I think you can achieve it by using capacity leveling with optimizer. If I recall correctly, optimizer will not move the order (order size bigger than the available capacity in the bucket) to the first bucket, right after the production horizon. It would leave it there at over-utilized.

    Thanks,

    Satyajit

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      One question,  why do you (I mean your client) need this? This is more of a master data issue. You can always restrict the max. order size by maintaining a max lot size! So that you don't face this type of issue (I guess planning run with monthly bucket doesn't make much sense here with the actual planning schedule).

      Thanks Satyajit - Its not only a matter of how much big the order is - which is placed / accumulated in the first buckets - no accumulation should happen- for ex if i specify the lot size as 50000 , the orders can accumulate util 50000 and it is not accpetable for business - if we decrease it much then we will interfere with the actual functionality where genuinely there is capacity available for 50000 units but cant place because of the master data we maintained

      there is not much change interms of limitaions in the latest cap leveling optimizer - I checked the help on latest version

      Runtime with optimizer might be a problem, when we plan with discreat optimizer with lot of constraints (like min. lot size, integral lot, transport lot, storage space, capacity ...) applicable and number of bucket is very high (say planning in daily bucket for 6 months).

      But I guess with capacity leveling optimizer, run-time should not be a big deal.

      whatever i mentioned in my earlier reply only applies to cap leveling optimizer - we dont have snp optimizer and not intent on using it - currently only heuristics- so there are no constraints / costs maintained at all - cap leveling optimizer calculates costs automatically

      the capacity leveling optimizer itself is taking lot of time -and still gives sub optimal results meaning leveling is not fully completed - still buckets left with overloads and under 100% utilization in prior buckets with available capacity

      thanks for the good analysis -

  • Dec 31, 2014 at 08:55 AM

    Hello Siva,

    Is there any BAdi is activated in your system for capacity leveling?

    Which scheduling type are using forward scheduling: backward scheduling?

    Are you using any Planning Buckets Profile during leveling?

    Have you used"Level fixed orders" option ?

    Are you using any period factor?

    Best Regards,

    R.Brahmankar

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks Rupesh for the initial analysis

      Is there any BAdi is activated in your system for capacity leveling?

      No

      Which scheduling type are using forward scheduling: backward scheduling?

      Only Backward

      Are you using any Planning Buckets Profile during leveling?

      no

      Have you used"Level fixed orders" option ?

      yes

      Are you using any period factor?

      yes-it just places the order on first day of the week

  • avatar image
    Former Member
    Jan 06, 2015 at 09:44 PM

    Hi Siva,

    But why you are not working with the combined backward & forward scheduling direction?

    Thanks, Marius

    Add comment
    10|10000 characters needed characters exceeded