Skip to Content

Is your Controlling – Profitability Analysis (CO-PA) system performance not meeting your business user’s expectations?  Have you heard about the SAP CO-PA Accelerator for SAP HANA?  Are you accountable to build the business case for adopting SAP HANA to take advantage of this exciting new in-memory technology?   If you have answered yes to these questions, then read this third weblog of the CO-PA tools series and learn how the CO-PA Assessment Cycle Overview can be used to gather important statistical data about your CO-PA system.

Display Cycle Overview

Program SAPLKAL1 is assigned to transaction KEUD and it provides an overview of the assessment cycles which are available from Profitability Analysis.  KEUD can also be called by report RKE_KEUD.  CO-PA Assessments are notoriously a performance bottleneck in some CO-PA systems.  In an earlier weblog post I discussed how to use the Might HANA Help?  Use Transaction KEDZ to View the CO-PA Read Interface Log to view the processing speed of each CO-PA Assessment Cycle.    Since CO-PA Assessment cycles are a function that can be greatly accelerated by use of SAP HANA, let us look at the information that the Cycle Overview transaction provides.


In the left side panel is a listing of the assessment cycles sorted by Operating Concern and Controlling Area and grouped by Actual Cycles and Plan Cycles.  When you expand the Actual Cycles folder and select a Cycle, the right side panel updates with general information about the cycle, as well as details about each selected Segment.


What is very helpful to see from this Overview screen is the “Receiver Rule” field in the lower right corner.  It is important to know that CO-PA Acceleration using SAP HANA will impact only those cycles that read reference data from CO-PA to determine allocation proportions.  In other words, assessment cycle segments that use Fixed Amounts, Fixed Percentages or Fixed Portions will not be accelerated by SAP HANA.  To be more specific, CO-PA acceleration is only possible for those cycle segments which have a Receiver Rule defined using “Variable Portions” as its tracing factor.  Since some CO-PA systems may have tens or even hundreds of allocation cycles and each cycle can have one or many segments it might be difficult to know which ones use variable portions and consequently what opportunity SAP HANA will offer for improving allocation run time during your period end close schedule.  The CO-PA Cycle Overview transaction (or the SE16 direct method explained below) will help you to identify where the CO-PA Accelerator can provide performance gains.

Note: if you are authorized to browse SAP table contents using transaction SE16 you might find this method an even quicker approach to identify those segments and cycles that use Variable Portions.  From Table T811S select records that exist in Table CE7XXXX (where XXXX is the name of your operating concern) and have a Rule Receiver (RRULE) equal to 1.


Keep in mind that with assessment cycle execution the SAP CO-PA Accelerator can improve the read time from the database, but it will not impact the time it takes to create (write) new database records into CO-PA. I’ll explain in another blog how to isolate these two key pieces of information about the total run time of assessment cycles using the analysis tools which are available during execution from Might HANA Help?  Use Transaction KEU5 CO-PA Assessment Cycle Analysis Tools.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. arturo senosain


    I have a question about this statement:

    Keep in mind that with assessment cycle execution the SAP CO-PA Accelerator can improve the read time from the database, but it will not impact the time it takes to create (write) new database records into CO-PA ‘

    If i have Hana as primary database, the performance gain is both in read and write ?

    1. Big Choi


      Now, I’m carrying out the project using HANA database.

      I felt that it didn’t not impact the time it takes to create (write) new data into HABA database.

      My ABAPer created database views to improve the read time from the database using “HAHA studio”.

      1. arturo senosain

        Thanks BC for your input.

        Im ending unit testing in my project so We don’t have to much data to test, but in the short term i plan to do a performance test. I see strong performance problems with assessments in other customer

        Jeffrey is talking about the accelerator (i understand this as Hana is not the primary persistant database).


Leave a Reply