SAP Finite Capacity Scheduling

The finite capacity scheduling is not available in SAP,  the unique functionality is the capacity leveling that could help to smooth overloads.

In this post, some attempts to obtain finite
capacity scheduling inside SAP are shown: they are based on changes of standard SAP program and custom programs.

What I thought many years ago is that I could put in relation the scheduling and the capacity reports: they are both available in SAP, but they are not linked, that’s why the scheduling is based on infinite capacity.

What I will show below is the list of programs and tables to modify or create.

The model of course is basic and can be improved, it allow a finite capacity check during the creation of each planner order (if needed also in production order, in the planned order created directly in the sales order, etc.).

First of all there is a table in which you put the work centers to be considered in finite capacity check (for instance only bottlenecks, some WC, all, etc.), material of course must be activated and there is also a the inter-setup table (setup depending on material and the couple previous/subsequent work centers).

 

Also a video is available to show a video demo. 

 

pdf explanation of working finite-capacity-check.pdf (109 downloads)

List of programs.zip (87 downloads)
  • The function group  /PRCF/GFWI (must be renamed in Z…GFWI) contains all the custom functions
  • the FM fase_shift contains all the criteria to individuate new dates taking in account the load of the work center. It is used in the elementary SAP standard forms in which are calculated times (starting/ending) in the scheduling
  • the FM bom_check_sch takes in account (if needed) also the scheduling depending on the availability of components. It is activated by the table CHKBOM. I suggest to start without this kind of check.
  • the report /PRCF/SCHED (to be renamed starting with “Z” or “Y”)  is the one shown in the video demo.

If you think this post is useful please share it on your social forum (below the links), to share this information.
Thanks!!!!

 

4 Replies to “SAP Finite Capacity Scheduling”

  1. Hi Michele, wonderful doc, the same can be achieved while running mrp also right? I Mean like when we run MRP, simultaneously capacity leveling also to take place, by linking the above two..

    1. Hi Jeffrey, at the moment it does not work with mrp, but it can be modified to work with mrp, because the elementary form of the scheduling I suppose is the same. I did not change the mrp because the problem is the priority of the sequence, it cannot be changed (it could be complex) and you cannot give the right priority… with the cockpit you have much more flexibility.

      1. Hi Michele, its been a while and thanks again for your coding and blog about Capacity leveling on which our technical team is working to achieve the same here. So i noticed an issue recently, which i already raised in SCN but none replied. Hope you can help me on it.Here we follow MTO scenario and after MRP run if i check the date and time of planned orders for SFG and FG it is wrong, because the date and time of FG is earlier after which proceeded with SFG. Obviously we cant manufacture FG without doing SFG. But in my case it does FG first and later SFG. So how to correct the dates and time like, FG only after SFG. Am not sure whether i missed anything with Configuration.

  2. Hello Michele,
    By the way i went through your pdf document explaining scenarios about finite capacity check. So there you’ve mentioned, “Anyway the finite capacity check can also be used during “make to stock” process, because it is possible to use a custom function, based on finite capacity check, and provide the “real” delivery
    date during availability check.” So what is that custom function to achieve the same? because here since we follow MTO scenario, providing real delivery date to customer after analyzing real time capacities would be a good idea and client would appreciate it. 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *