Issue/Solution: COPA Performance Improvement using Summarization Levels

Issue:
Very long processing time or frequent TIME_OUT errors while execution of COPA reports (KE30) or assessment cycles.

Solution:

1. Activate CO-PA log (T-Code KEDZ, Program: RKE_PROT_EVALUATE)

Purpose:
Any COPA report/cycle execution or data access from COPA tables would be recorded in the log after this activation. This allows SAP to analyze the CO-PA usage pattern /access information based on which automated summarization levels could be created to improve COPA performance.

Execution Steps:
Execute t-code KEDZ

• Enter the Operating Concern (PI02) and click “Activate” (Ctrl+F1)

2. Collect CO-PA log data for a few weeks or months. (T-Code KE30, KEU2, etc)
This will be done automatically by the system when COPA reports or assessment cycles are executed.
For quick resolution in reports with poor performance, you may choose to execute all COPA reports /cycles, for which performance improvement is required to update the log data.

3. Create Summarization levels proposal (T-Code: KEDVP, Program: RKETRERU)

Purpose:
In this step, the system would read the access log information as recorded in step 2 and present a proposal to create summarization levels according to the database access patterns identified in the COPA log.

Execution steps:
Execute t-code KEDVP

• Enter Operating Concern
• Select COPA Type (Costing Based /Account Based)
• Select the type of proposal to be created
  -Enhancement: Existing summarization levels are taken into account during optimization, and only additional summarization levels are proposed
  - Replacement: With this type of proposal, all existing summarization levels are ignored. The proposed summarization levels replace the existing levels. Even replacement proposal does not delete any existing summarization levels. However existing levels can be manually deleted using T-Code KEDV
• Select the period (select maximum period for which log data is available) for which logged COPA transaction data should be considered to create the proposal.
• Click “Create Levels” button to accept the summarization level proposal displayed

Note: The analysis can take quite a long time. If the program aborts during dialog processing, due to run time being exceeded, restart the program in background processing. To display the result when the program has completed, choose Display last proposal.

4. Build Summarization levels (T-Code: KEDU)

Purpose: Large volume of data available in COPA tables is organized into various summarization levels using this transaction, which allows for quick data access at the summary levels for various reports and cycle executions instead of the high time and system consuming process of direct data retrieval from COPA tables.

Execution Steps
Execute t-code KEDU

• Enter Operating Concern
• Choose type of Profitability analysis (Costing/Account)
• Select “Build new Levels”
• Execute in background mode only using menu option Program > Execute in Background (F9)
• Click “Immediate”
• Click “Save”

5. Wait for the summarization level build process to complete (T-Code: SM37)

Status of the background job scheduled in step 4 can be using t-code SM37 with job name “RKETRER


6. Schedule a Daily Background Job to refresh summarization level data (T-Code: KEDU/SM36)

Purpose: The summarization levels created above would hold only the data available in COPA tables as on 30 minutes before the build process. To update the summary tables with the latest transaction data, summarization level refresh process needs to be executed daily.

Execution Steps:
Execute t-code KEDU

• Enter Operating Concern
• Choose type of Profitability analysis (Costing/Account)
• Select “Refresh”
• Save as a variant “COPA Summarization Refresh”

Execute t-code SM36

• Click “Job Wizard” button
• Click Continue
• Enter a descriptive job name (example: COPA summarization refresh) and priority, leave the target server blank and click “continue”
• Select “ABAP Program Step” and click “Continue”
• Enter ABAP program name as “RKETRERU” and choose variant “COPA Summarization Refresh” and click “Continue”
• Do not select add additional steps and click “Continue”
• Select option “Date/Time” and click “Continue”
• Enter a scheduled start date and time (non- business hour) , Check “Periodic” and click “Continue”
• Select “Daily” and click “Continue”
• Click “Complete”

Notes:

- Report for which performance improvement is sought must be configured to use the summarization levels in the report option field for presummarized data
- Population of initial summarization level , could be a very time consuming job and hence it may require to be executed into multiple parts with different executions for different summarization levels.
- Do not execute t-code KEDV while trying to execute a background job for summarization level population using KEDU.

Issue/Solution: Accounting document posted without Profit Center even if Profit Center is mandatory in document splitting

Issue:
An accounting document is posted without profit center, segment or business area, even though it is mandatory field in the document splitting characteristic configuration. The system may not allow to reverse or clear such corrupt line items, and users may get the following error while trying to reverse of clear the erroneous document.
Balancing field "Profit Center" in line item 001 not filled

Erroneous line items thus posted would have blank Profit Center even in the general ledger view.
All such inconsistent documents may be found from table FAGLFLEXA - General Ledger: Actual Line Items, Profit Center=Blank

Solution:
Implement the following SAP Notes to prevent further occurrences of this issue
Note 1249888 - Simulate General Ledger: Incorr. data or dump MESSAGE_TYPE_X

To reverse any inconsistent documents which have already been posted erroneously before implementation of the above note, create an OSS message under the component FI-GL-GL-X

Information: Performance Analysis for COPA reports

The following notes provide helpful information for analyzing and improving performance of CO-PA reports and interfaces (KE30)
1. Note 532252 - INFO: performance analysis for CO-PA read interface - Provides basic information on how to conduct performance analysis for COPA reports, using t-code KZDP
2. Note 363890 - Long runtimes with update and selection - List some common reasons for low performance or frequent time out errors on execution of CO-PA reports.
3. Note 35288 - Profitability Analysis: Technical Documentation

Issue/Solution: No profit center determined for withholding tax items after document splitting

Issue:
While making vendor payments using the automatic payment program (F110) or manual payment using F-53 , user receives the following error
Balancing field "Profit Center" in line item 002 not filled
Depending upon the document splitting characteristics defined in your system, the error may be for Segment, Business Area or any other field
for example
Balancing field "Segment" in line item 002 not filled
Balancing field "Business Area" in line item 002 not filled

Causes:
If Extended Withholding taxes applicable at the time of payment are being used , The standard splitting rules and transaction variant may not be able to identify the profit center/segment/business area for withholding tax line item which is automatically generated the during payment posting.

This is due to fact that the newly generated item may be considered as a base item category instead of a derived item category due to the document splitting configuration

Solution:
1. Identify the document type being used for the payment posting. For example KZ or ZP
2. Identify the transaction type and business variant being used for the document type found in step 1 from SPRO node " Classify Document Types for Document splitting" (SIMG_GLT0_T8G12). Most likely it would be Transaction Type : 1000 - Payments and Variant 0001 - Standard, unless you have defined your own transaction types and variants
3. Identify the document splitting method being used in your implementation from SPRO node "Activate Document Splitting" (SIMG_FAGL_ACTIV_SPLI) . Most likely to be 0000000012 or 0000000012
4. Go to the SPRO node "Define Document Splitting Rule" (FISL_PS_GBEB_SPLT_DC) and locate the header item with Splitting Method, Business Transaction and Transaction Variant identifies in step 1,2 and 3. For our example it would be 0000000012, 1000 - Payments, 0001 - Standard respectively
5. Add item category "05200 - Withholding Tax", into the "Item categories to be edited" list for the header selected in step 4.
6. Add "Base item categories" "02000 - Customer" and "03000 - Vendor" for item category "05200 - Withholding Tax".