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 first weblog of the CO-PA tools series and learn how the CO-PA Read Interface Log can be used to gather important statistical data about your CO-PA system.
Notice | Before activating the CO-PA Read Interface Log, make certain your ERP system contains the source code corrections contained in the following SAP notes:
Read Interface for CO-PA Log
Program RKE_PROT_EVALUATE is assigned to transaction KEDZ and it provides a detailed log of transactions that have accessed the Profitability Analysis Read Interface. The CO-PA Read Interface is the name given to the ABAP coding that handles the SQL select statements made to the CO-PA tables used by reports and allocation processes. To start using the KEDZ transaction simply input your operating concern and click on the activate button. Then as time passes you can return to this report and view the log for the selected recording period. You can also filter the output to a specific selection of reports, assessment cycles, and other CO-PA functions.
After executing the report, you can click on the reference to the CE4XXXX table (where XXXX represents the name of your operating concern) where you will see some useful statistics such as the number of records in the table, the number of reads within the recording period, and the speed measured in 1000 records per hour, among other information. Table CE4XXXX contains the profitability segment object numbers. This summary information is also available for the Actual Line Items table CE1XXXX and the Plan Line Items table CE2XXXX and any summarization level tables which may exist in your system.
Expand the Caller folder and you will see which how many accesses have read from the table and the log gives details by each report and its selection characteristics.
Click on a specific report name and the right panel refreshes to show a log of each report execution by user, by time stamp, as well as the number of records returned, the access time and the speed.
Also contained within the Caller folder is information about execution runs for Top-Down Distribution (transaction KE28) and CO-PA Assessment Cycles (transaction KEU5).
The CO-PA Assessment log data is detailed for each individual cycle definition.
For example here is the log for a cycle named “Demo2” which shows the number of times the cycle was executed, the number of records read from the database and the number of records transferred to CO-PA, and also the access times and speed.
Keep in mind that for Top-Down Distribution and 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.
Also within the CE4XXXX / Caller folder you may see reference to Line Item Actual (transaction KE24). This will show under the CE4 table if a user made a drill down to line items from a CO-PA Report. Remember that CO-PA reports always present data according to the current profitability segment structures (after any realignment runs). Thus a drill down from a KE30 report to line items necessarily involves a join on tables CE4XXXX (profitability segments) and a line items table such as CE1XXXX (actual line items) or CE2XXXX (plan line items).
By clicking on the Caller folder within the reference to table CE1XXXX you will obtain log data for accesses made to CO-PA line items. This folder provides for example calls made directly from transaction KE24.
When building the business case to justify an investment in SAP HANA technology you may find that an accelerated KE24 transaction could be a key time saver benefit for your organization. However some organizations have needed to stop using KE24 due to their database size and the accompanying slow performance. For these customers, many achieve similar line item reporting using SAP Business Warehouse. If this sounds familiar to your experience, I would suggest that you try to obtain database statistics from the BW statistics framework.
After you have gathered CO-PA statistics to help build your business case for SAP HANA, be sure to go back to transaction KEDZ to deactivate the Read Interface log so that cluster table INDX in your database does not grow unnecessarily and that you do not continue to take the small performance hit writing to this table during process execution.
Another useful feature in transaction KEDZ is a function is to count the distinct characteristic values for each characteristic in the operating concern. This is accomplished by clicking on the red and white icon labeled “Determine Values”.
This function will prompt you to initiate a background job for each table or summarization level you select.
When the job completes you can view the results from the detail display screen from KEDZ. Such information is very useful to estimate the hardware requirements for a SAP HANA deployment throughuse of the SAP Quick Sizer tool which is available on the SAP Service Marketplace.
Transaction KEDZ is a useful tool to understand which reports, which assessment cycles, which line item selections, and which top-down distributions are being executed in your CO-PA environment. The Read Interface Log gives details about the users, the date and time stamp of CO-PA activity, the number of records processed and the speed of access. It can help you identify peak system usage and to pinpoint those areas that cause the most strain on system resources. It also reveals essential statistics about your Operating Concern design and master and transactional data volumes. With such an abundance of data easily made available to you this should be useful to help substantiate an investment in the CO-PA Accelerator and SAP HANA.