Cutoff period in OKG9

[Former Member]

Hello experts,

We implemented SAP in 2000 but we have not changed the cut off period(4,2000) in OKG9 as of now.

Our wip job takes so much time in background so we decided to try changing the cutoff period to optimize the job.

Kindly provide some insight into whether we shall change the cutoff period?

If yes what should be the cutoff period and what should be the impact?

Shall we change the cut off period every month?

Our company's average life cycle for a project is 3-4 years but  certain projects may extend beyond 5 years.

I have attached screen shot of OKG9 kindly provide suggestion change to any settings to reduce the wip job timing.

Thanks in advance.

Regards,

GSR

[Former Member]

Hi Sethuraman,

Cutoff period

http://help.sap.com/saphelp_470/helpdata/en/90/ba6609446711d189420000e829fbbd/content.htm

That a cutoff period is defined to protect the data of the previous period from being overwritten.

The cutoff period divides the life cycle of the production order into open and closed periods.

The work in process calculated up to the cutoff period is not changed the next time WIP is calculated.

The work in process calculated for later periods is overwritten by the current WIP calculation.

To prevent data that has already been posted from being changed, you usually define the cutoff period as the period preceding the results analysis period.

For a product cost collector, work in process is calculated in May, June, and July. The valuation for July should not change the work in process for May and June.

I would suggest these steps to reduce timing.

Set CLOSED status to completed orders and Archive orders

other option is SAPKKA07 as background job with parallel processing option. but check with BASIS team parallel processing is active or not.

Hope this helps you.

Thanks,

Rau

[ankur_kabir]

Cut off period should be changed every month (n) to last month (n-1) using T-code: KKA0.  This will prevent you overwriting result analysis on figures which is older than cut off period.  System will consider values only after cut off period and it might help you with performance.  But I am not sure if this alone will entirely improve your performance.  You should also consider closing objects like sales order, internal order, service order, service contract (whichever all applicable to your business needs) and putting deletion flag indicator (for production order) to improve job performance.  You will find standard SAP documentation on cut off period in SAP library.

Also refer to SAP note 190816 - CO cutoff period for some reference.

SAP Library:

Changing the Cutoff Period - Cost Object Controlling (CO-PC-OBJ) - SAP Library