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 the first blog in the CO-PA tools series to find out how to use the CO-PA Read Interface Log to acquire crucial statistical information about your CO-PA system.

Make sure your ERP system has the source code corrections detailed in the following SAP notes before activating the CO-PA Read Interface Log:

SAP Note 1412463 RKE PROT WRITE: Deadlock while accessing the INDX SAP Note 1504083 KEDZ: Error converting outdated INDX entries

Read CO-PA Log Interface

Transaction KEDZ is assigned to the programme RKE PROT EVALUATE, which offers a thorough log of all transactions that have accessed the Profitability Analysis Read Interface. The SQL select statements made to the CO-PA tables used by reporting and allocation processes are handled by ABAP code known as the CO-PA Read Interface. Enter your operating concern and click the activate button to begin using the KEDZ transaction. The log for the chosen recording period can then be viewed by returning to this report later. Additionally, you can restrict the output to show only a particular set of reports, assessment cycles, and other CO-PA operations.

Following the report’s execution, you can click on the reference to the CE4XXXX table (where XXXX stands for the name of your operating concern) to view some useful statistics, including the number of records in the table, the number of reads during the recording period, and the speed measured in 1000 records per hour, among other details. The profitability section object numbers are listed in table CE4XXXX. The Actual Line Items table CE1XXXX, the Plan Line Items table CE2XXXX, and any other summarization level tables that could be present in your system are also accessible for this summary data.

By expanding the Caller folder, you can see how many times the table has been accessed and the log provides information about each report’s selection criteria.

A log of each report execution by user, by time stamp, together with the amount of records returned, the access time, and the speed is displayed in the right panel when a specific report name is clicked.

The Caller folder also includes details regarding Top-Down Distribution (transaction KE28) and CO-PA Assessment Cycles execution runs (transaction KEU5).

Each individual cycle definition’s CO-PA Assessment log data contains extensive information.

This log, for instance, indicates the number of times the cycle was executed, the number of records read from the database and the number of records sent to CO-PA, as well as the access times and speed. The cycle is named “Demo2.”

Remember that while the SAP CO-PA Accelerator can speed up database reads for Top-Down Distribution and Assessment Cycle execution, it has no effect on how quickly new database records are created (written) into CO-PA.

The CE4XXXX / Caller folder may also make mention to Line Item Actual (transaction KE24). If a user conducted a drill down to line items from a CO-PA Report, this would appear under the CE4 table. Always keep in mind that CO-PA reports offer statistics in accordance with the existing profitability segment structures (after any realignment runs). As a result, in order to drill down from a KE30 report to line items, it is necessary to combine tables CE4XXXX (profitability segments) and CE1XXXX (real line items) or CE2XXXX (plan line items).

You can get log information for accesses made to CO-PA line items by clicking on the Caller folder within the reference to table CE1XXXX. Examples of calls made directly from transaction KE24 are provided in this folder.

An accelerated KE24 transaction can prove to be a significant time-saving benefit for your company when developing the business case to support an investment in SAP HANA technology. However, because of the size of their databases and the ensuing sluggish performance, some firms were forced to quit utilising KE24. Many of these customers use SAP Business Warehouse to accomplish similar line item reporting. If you have experience with this, I would advise you to try obtaining database statistics through the BW statistics framework.

Remember to return to transaction KEDZ and deactivate the Read Interface log after collecting CO-PA statistics to support your business case for SAP HANA so that cluster table INDX in your database does not expand unnecessarily and that you do not continue to experience a slight performance hit when writing to this table during process execution.

The function to count the various characteristic values for each characteristic in the operating concern is another useful feature of transaction KEDZ. To do this, click the “Determine Values” icon, which is a red and white square.

When using this function, you will be prompted to start a background job for each table or level of summary you choose.

You can see the outcomes after the job is finished thanks to KEDZ’s detail display panel. By using the SAP Quick Sizer tool, which is offered on the SAP Service Marketplace, this information is particularly helpful in estimating the hardware needs for a SAP HANA deployment.

Understanding which reports, assessments cycles, line item selections, and top-down distributions are being used in your CO-PA environment may be done with the help of Transaction KEDZ. Information about the users, the date and time stamp of CO-PA activity, the quantity of records processed, and the access speed are all provided in the Read Interface Log. It can assist you in locating the locations that place the greatest demand on the system’s resources and in determining its peak system utilisation. Additionally, it provides crucial data regarding the design of your Operating Concern as well as the amounts of master and transactional data. With so much data readily available to you, it should be possible to justify investing in SAP HANA and the CO-PA Accelerator.