Objective

This solution proposal is based on “Interval” extraction in ECC. As we know, if we can get “interval” correctly for the resource capacity, we can achieve:

1). to know why the ETA is calculated to that date/time

2). To cut the “interval”, then we can quickly and correctly know how much time is REAL, and simultaneously know how much time the Machine time is about.

3). To avoid to touch and analyze so complex logic in process order scheduling, i.e. operation standard value key, schedule parameter, schedule formula, efficiency rate key, etc. As if we chose this way, it definitely costs much time and the result is for sure not correct enough.

Solution brief summary

Basically we would make use of table – CRHD, KAKO, KAZY, KAPA to get the interval and shift data for given resource;

If in the KAPA there is pre-defined shift-definition, we can refer to table TC37A and TC37P to get the shift and break detail.

And if the KAPA is standard capacity, we should refer to factory calendar to get the interval (holiday).

For multiple operation and multiple resource, the investigation is still ongoing…

Investigation

First question:

For one process order, which resource and which capacity (Labor? Machine?) Should be used?

We use below approach to answer above question:

Here we get know:

1. Resource for schedule: ZED_TES2

2. Capacity for schedule: 001 – Machine

   Second question:

   
   

   How to parse the Interval correctly?

   
   

   Well this is actually the CORE requirement of our desired.

   
   

   By abovementioned, we reach the capacity of Machine:

   
   

   

   
   

   Get the header data:

   
   

   

   
   

   
   

   
   

   Now, start our core investigation:

   
   

   Table - CRHD:  Resource Header

   
   

   Using above Resource name, plant

   
   

   

   
   

   

   
   

   Table – KAKO: Capacity header

   
   

   Using above CRHD-KAPID

   
   

   

   
   

   We can get the detail info for header data of Capacity (screen shot above).

   
   

   
   

   
   

   See only “Interval”: when there is no shift:

   
   

   

   
   

   Table – KAZY: Only Interval

   
   

   

   
   

   
   

   
   

   Now, if we see “Interval + shift”:  when there is “Shift” really set for the “interval”:

   
   

   

   
   

   
   

   
   

   Table – KAPA: Interval and shift detail

   
   

   

   
   

   We can see, actually, this table is storing the real interval + shift data:

   
   

   

   
   

   
   

   
   

   So, we can see, if there is no any predefined shift, KAZY (Interval) and KAPA (interval shift) is enough to know the interval and shift.

   
   

   
   

   
   

   However, Here we should have another tables to consider:

   
   

   If we use shift-definition:

   
   

   

   
   

   

   
   

   Now the KAPA table becomes:

   
   

   

   
   

   Table – TC37A: shift definition

   
   

   

   
   

   Table – TC37P: shift break

   
   

   

   
   

   
   

   
   

   So, we can imagine and conclude:

   
   

   We can make use of table – CRHD, KAKO, KAZY, KAPA for the interval and shift data; if in the KAPA there is shift-definition, we can refer to TC37A and TC37P to get the shift and break detail.

   
   

   And if the KAPA is standard capacity, we should refer to factory calendar to get the interval (holiday).