Does the performance of your Controlling – Profitability Analysis (CO-PA) system fall short of what your business users expect? The SAP CO-PA Accelerator for SAP HANA has you interested, right? Are you responsible for developing the business case for using SAP HANA in order to benefit from this innovative new in-memory technology? If you said yes to either of these questions, read this third blog post in the CO-PA tools series to find out how the CO-PA Assessment Cycle Overview may be used to collect crucial statistical information about your CO-PA system.
Overview of the Display Cycle
Program SAPLKAL1 is associated with transaction KEUD and offers a summary of the evaluation cycles that can be found in Profitability Analysis. Report RKE KEUD can also be used to invoke KEUD. In some CO-PA systems, CO-PA Assessments are infamously a performance bottleneck. I already covered how to utilise the Might HANA Help? To see how quickly each CO-PA Assessment Cycle was processed, use Transaction KEDZ to View the CO-PA Read Interface Log. Let’s look at the data that the Cycle Overview transaction gives as CO-PA Assessment cycles are a process that can be substantially accelerated by the usage of SAP HANA.
A list of the evaluation cycles is presented in the left side panel, organised by Actual Cycles and Plan Cycles and categorised by Operating Concern and Controlling Area. The right side panel updates with details about each selected Segment as well as general information about the cycle when you expand the Actual Cycles folder and select a Cycle.
The “Receiver Rule” field in the lower right corner of this Overview screen is quite useful to see. It is crucial to understand that only cycles that read reference data from CO-PA to calculate allocation proportions will be impacted by SAP HANA’s CO-PA Acceleration. In other words, SAP HANA won’t speed up evaluation cycle parts that use fixed amounts, fixed percentages, or fixed portions. To be more precise, only cycle segments with Receiver Rules defined using “Variable Portions” as its tracing factor are capable of CO-PA acceleration. It might be challenging to identify which CO-PA systems use variable portions and, consequently, what opportunity SAP HANA will present for enhancing allocation run time throughout your period end close schedule because some CO-PA systems may have tens or even hundreds of allocation cycles, each cycle having one or many segments. You can determine where the CO-PA Accelerator can improve performance by using the CO-PA Cycle Overview transaction (or the SE16 direct technique described below).
It should be noted that this method may be considerably quicker to discover the segments and cycles that use variable portions if you have permission to view SAP table contents using transaction SE16. 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.
Remember that while the SAP CO-PA Accelerator can speed up database reads during assessment cycle execution, it has no effect on how quickly new database records are created (written) into CO-PA. I’ll go into more detail in future blog post about how to use the analysis capabilities offered by Might HANA during execution to separate out these two critical pieces of data regarding the overall run time of assessment cycles. Help? Utilize the tools for Transaction KEU5 CO-PA Assessment Cycle Analysis.