Optimal summarization levels for CO-PA

Hi,
is there any guide or SAP Note how to optimal set the summarization levels for CO-PA?
E.g., how many characteristics should a summarization level contain or how many keydata records is maximum for a summarization level?
Thanks in advance
Regards
Peter
Edited by: Peter Jankech on Feb 1, 2010 11:58 PM

Thanks for reply Pradeep,
unfortunatelly I have not found the information I need.
Does anybody know some other source?
The question is: what is the maximum size of an summarization level (in MB)?
Because if we add more and more characteristics to a summarization level, the amount of keytable records rises and the the summatization level losses its purpose.
Within the OSS 83204 (file h83204en.doc) there is a smatement, that a summarization level is considered as big, if its size is more than 20MB...this is nonsense, our summarization levels are bigger than 1GB. Is there any newer version of the manual to the summ.levels?
Thanks
Regards
Peter
Edited by: Peter Jankech on Feb 2, 2010 3:03 PM
Edited by: Peter Jankech on Feb 2, 2010 3:15 PM

Similar Messages

Building summarization levels for reporting

Hi All,
Our system is very slow to execute COPA reports. I am willing to create summarization levels.
1. I let the system create a proposal
2. I created hiearchy levels
3. I uploaded the levels with data
4. I checked whether reports are reading hierarchy level
I am a little bit confused how this summarization level is intedted to work. I tested the summarization. It works by 1-2 reports, but not for the rest.
So my question is, when a summarization level is applicable for a report?
For examle, if I summarize for customer... and in the report I have characteristics customer... does the system takes this summarization level or not? If in general I need customer in all of our reports as characteristics, I won´t be able to use summarization level for customer?

I am looking somehow for similar answer.
When the system does proposal for sum. levels why the created levels are not used.
For your information. If you have just created new reports and hope to get them speed up it might not work properly.
When you use the proposal of levels the system analysis the ones last used. If some reports are used not often they might not be considered.
So you need to watch and fine tune it.
I noticed that the index which is important to access the level, does not really match our criteria. The sum. level might have the right data but not very good index.
Further you could check the usage of fixed characteristics. For example you copy a simple sum. level with certain data and you add fixed characteristics. Example, company code 01.
But the magical question when it is utilized is also open. Don't forget to activate the usage of sum. levels in the report attributes itself.
BR

'*' in Summarization Levels for CO-PA

Hi All,
What is the role of table "TKETRLF" in Account based CO-PA. When I try to check the CO-PA Datasource it is giving me an error. I tried to debug it and see where exactly is the problem. I found that the standard program is trying to read the data from the above said table and becoz of not finding the required data it is not picking up the summarisation level and throwing the error.
The table has got all the fields from the summarization levels and a flag(0,1,2...) which says if it is a summarization characteristic/user defined characteristic etc. The fields with out a '*' in KEDV has '0' as the flag. If the program finds the flag as '0' for any of the field in one summarization level then it is ignoring that level.
Since I have atleast one field with out a '*' in each of my summarization levels, it is not picking up the summarization level and throwing an error saying "No Source could be found".
This is very urgent...Please someone help me...
Thanks,
RPk.

Hi,
I have the same problem, and I find SAP Note Note 1069507 - BI Extraction : 'Errors occurred during the extraction'. This is for version 5.0, probably it help you, but in my case I am working in ECC 6.0.
Regards,
Gabriel Barroso.-

Summarization levels for CO-PC-IS

Hello
So far my production variance report (S_ALR_87013148) has functioned perfectly, but after inserting a new coloum I only get data for only plant.
I posted an OSS message, on which they responed - check note 422543. This note suggests to delete all entries in KKDV... Unfortunately I don't know much about summarization levels - will the needed levels be created automatically when the data collection will be executed again?
Thanks in advance
Best regards
Søren Kirch
LOGSTOR A/S

It is ok to delete the entries.

No summarization level exists for cycle 261001_KEU5

Dear experts!
Now, I'm getting some issue about performing t.code KEU5.
The first, I create cycle with t.code KEU1 with receive tracing factor rule is Variable portions.
Second, I run the cycle with t.code KEU5 then the system display warring message:
No summarization level exists for cycle 261001
Message no. GA790
Diagnosis
The tracing factors for cycle 261001 cannot be read from a summarization level.
This message is displayed when executing a periodic allocation of overhead costs (assessment, indirect activity allocation) if portions are used as tracing factors in at least one segment. It is designed to make you aware of potential improvement in performance which is not being used.
If variable portions are used as tracing factors, the distribution factors are determined from the object level (table CE3xxxx/CE4xxxx, xxxx=operating concern). If there is a large amount of data at object level, selection can take a long time. The summarization levels can be used to pre-summarize the transaction data, resulting in a drastic reduction in runtimes for periodic allocations.
System Response
The tracing factor is determined from the object level. This does not alter the result of periodic allocation, but the runtime can be lengthy.
Procedure
For large data volumes, define a summarization level in the object level in order to improve performance.
For more information, see the program documentation and the customizing functions, which include a form for defining an appropriate summarization level for periodic allocation.
Help me, please!
Best regards, Huy

Hi
Its just a warning message saying that cycle execution time can be more in the absnce of Summ level
You can create summ levels from ORKE > Tools > Summ Levels
br, Ajay M

CO-PA Summarization Level

Hi,
I am very unclear about summarization levels in CO-PA. Please can any one explain me what is the real significance of summarization level, why do we need it and steps to configure it, and on what logic is data extracted from it.
Thank you,
Sam

1. What is use of summarizattion in COPA?
summarization level in Profitability Analysis (CO-PA):
A summarization level is a tool for improving performance.
Summarization levels store an original dataset in summarized form. This gives quick access to presummarized data for functions that do not need detailed information, and means that the data does not need to be summarized separately each time.
you can check this in this link
http://help.sap.com/saphelp_nw04/helpdata/en/ae/bd116e940f11d2b63c0000e82debc6/frameset.htm
2. If we dont give summarization in COPA Account based will records be available in RSA3 - yes
2. How to create summarization level for a datasource?
You can do this in Transaction - KCDU/KCDV or SPRO
Hope it helps.
Regards

Summarization Levels in CO

Hi,
Im extracting from a particular CO table in ECC. The CO team is setting up summarization levels for that table. When they create a summarization level the system automatically creates a new table. Since im extracting from the source table how does BI identify the table that the system created automatically? What do i need to do on BI side?
Thanks

Hi,
take a look at this blog:
/people/swapna.gollakota/blog/2008/01/14/one-stage-stop-to-know-all-about-bw-extractors-part2
First link was regarding what you have to do if none of the SAP- predefined extractors meeting the business demand, then the choice is to go for generic extraction.
Additional info:
COPA EXTRACTION
Regarding CO-PA......
http://help.sap.com/saphelp_47x200/helpdata/en/74/e3a226e64e11d1a5300060087a7a87/frameset.htm
Regards
Andreas

Summarization Levels in COPA. Tr Code KEDV

Dear All,
I request you to give me some Clarifications on Summarization Levels namely;
1) Are the summarization levels build form Line Items tables(CE1XXXX and CE2XXXX).
2) If so how does it get the field "PLIKZ"(Plan/Actual Indicator) for Plan line items as this field so not part of CE2XXXX, so How is it Updated?
3) Assuming that there are Performance problems even after using Summarization Levels, can you please explain as to how exactly do the Indexs work.?
4) In Indexes, there are 5 Columns with the title "Field", each of the column containing multiple rows, can you please explain what is the use of each of the columns.?
5) i have gone through the OSS Note "83204", in it there is a path(given below) given to download the information on Summarization Levels. However, i was not sure as to how to download it Could you please let me know how to download it.If Possible can you upload the document under "Wiki" or " Articles".
Below is the data and the file path from the note:
===============================================
The document can be downloaded via ftp from the sapserv3 server (binary
transfer mode). The German or English version is stored in directory:
(~ftp/)general/R3server/abap/note.0083204
under the name h83204dt.doc or n83204en.doc.

Hi,
Please follow instructions in note 480180 to download the file. Also for creating index you can refer to note 35288. Together with summarization levels and a proper secondary index you should not face major performace issue. If the performance continues to be bad then you must think about archiving the CE1 or CE4 tables in CO-PA.
Regards,
Abhisek

CO-PA Summarization Levels

Hi,
for a report with many characteristics I created 4 summarization levels in such a way that
Summarization Level 2 includes all characteristics of the Summarization Level 1 + some more
Summarization Level 3 includes all characteristics of the Summarization Level 2 + some more
Summarization Level 4 includes all characteristics of the Summarization Level 3 + some more
In the report options, in Presummarized data section, I selected "Read upon each navigation step".
Now when I execute the report, data is first read from the Summarization Level 1. During drill down data is read from further summarization levels depending on which characteristic is used for the drill down.
There is one thing that I don't understand:
None of these summarization levels is used by the system if it does not contain the characteristic "Product".
As Product is not used for the initial selection of the report I initially put it on Summarization Level 3. But the system did not want to use Summarization Levels 1 and 2 then. When I added the Product to the Levels 1 and 2, everything is working fine. However this is not what I need because Product is not displayed on the first screen of the report.
Do you know why the characteristic "Product" is required in each summarization level?
I will appreciate your help very much!
With best regards,
Marcin

Hi Surya,
My report is calling all summarization levels.
At the start the summariyation level 1 is called. It is most aggregated so it is little time needed to start the report. It contains only the most frequently used characteristics.
During drilldown other summarization levels can be called (this is achieved thru the option "Read upon each navigation step"). It depends on which characteristic is used for drilldown: if the characteristic used for drilldown is not included in the currently used summarization level, the next least aggregated summarization level which includes this characteristic is called.
The most frequently used characteristics are included in the most aggregated summarization level, the least frequently used characteristics are included in the least aggregated summarization level, which contains all characteristics used in the report.
With best regards,
Marcin

Summarization levels in CO-PA extractor

HI Experts :
I am working on creating additional co-pa extractor. I got the requirement like below:
create the extractor for
CoArea 1100 is using summarization level 3
CoArea 1200 is using summarization level 8
CoArea 1660 is using summarization level 10
CoArea 1550 is using summarization level 20
always using the same info provider .
We are creating the additional extractor . So please any one help creating the extractor using these summarization levels .Please provide me some tips or some steps to create the additional extractor ..(Operating concern already exists)
Thanks in advance.
Reddy

Hi reddy,
see this links.....
http://help.sap.com/saphelp_nw04/helpdata/en/53/c1143c26b8bc00e10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fb07ab90-0201-0010-c489-d527d39cc0c6
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1910ab90-0201-0010-eea3-c4ac84080806
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ff61152b-0301-0010-849f-839fec3771f3

Summarization Levels COPA

Hello all,
I´ve created a Summarization Level using transaction KEDV.
The Summarization Level has still the status "to be created" in KEDV, even when I safe it, it does not change the status, so the tables are not built.
When I try to update/ built/ rebuilt the level by using KEDU, it says it is not possible, because of the status "to be created".
How can I change the status and built the tables for the summarization level?
Thanks for your answers,
Michael

Try using the program "RKETREGN" to build.

COPA Summarization Levels

Hi All,
I have created summarization levels in COPA and when I run the COPA KE30 report with the summarization levels being active or inactive, it produces the same numbers in the Dev system, so no issue there. But in QA system, same summarization levels do not provide the same numbers. The numbers when summarization levels are activated are less than half of the numbers when summarization levels are deactivated. Same problem in the PRD system. I have tried to resolve the issue by creating the summarization levels directly in the PRD system.But the numbers did not match in that case either. The numbers provided by the report when the summarization levels are deactived are less than even half of the numbers when the summarization levels are activated.
I have checked the report parameters in the DEV, QA and PRD systems and they are same.
Please let me know what may be causing this inconsistency.
Can it be because of some basis problem? I mean some memory problem etc which may be causing the summarization tables not to have all the data in QA and PRD systems.

You wouldnt have any message in reports yaar.
Just compare the authorisations in the development system with others.
Also, do one thing., execute transaction SU53 immediately after the report execution, to see for any missing authorisations.

How to "active" copa summarization level ????

Hello:
    I create COPA summarization level in R3 .When I save the level, the system generates these tables and sets the status to "active, without data".I need to fill the level with data, at which time the status changes to "active".But I don't know how to do it !
Thanks for your help!
   lian

Dear Consultants, Learner & Readers,
The problem with changing the status of a summarization level from "To be created" into "Active, without data" in a system that is not open for customizing can indeed be solved by execution of program RKETREGN as it's described in attached SAP Note 52636.
I quote from the note:
If you have created summarization levels, the tables generated are not also transported. To create the tables in the target system, start report RKETREGN (Summarization Levels: Generate Tables for Summarization Levels) in the target system. Enter 'KE'     for application, '01' for sub-application and 'CE1xxxx' for TABNAME (Replace xxxx with your operating concern). If the program does not run, then the program terminates with error message KE707 when building summarization levels
I hope this answers your query. Else do not hesitate to get back for more clarifications.
You may write to my personal mail id : fico_rss at yahoo.com
Best regards
Dr. Ravi Surya Subrahmanyam, PhD (Finance)
Senior SAP FICO Consultant,
Answerthink India Ltd
Hyderabad. India
Phone : +91 - 9848550024
Email : [email protected]

What is COPA- Summarization Level

hi
COPA- Summarization Level
can u give me some theory for this
and also what is filed partation in co-pa while creating datasource its aksing?
regards
suneel.

A summarization level stores an original dataset in a reduced form. This original dataset
describes the individual profitability segments in terms of the amount of characteristics each has.
Summarization means that selected characteristics are left out. Any segments in the original
dataset that are now identical through having had characteristics removed are combined into a
single pseudo-segment in the summarization level.
From the technical point of view, a summarization consists of two tables that have just been
generated, the key table and the totals table. Key table corresponds to the segment table and
contains the pseudo-segments produced from the reduced characteristics. The totals table
corresponds to the segment level and contains the associated value fields.
The summarization levels can be used in a number of different areas in Profitability Analysis:
The information system Drilldown Reporting
To find the tracing factor for cost center assessment
Manual planning
Automatic planning
Transfer to Sales and Operations Planning (SOP)
Edited by: dheeraj dinanath on Apr 2, 2008 4:15 AM

COPA Summarization level.

Dear Gurus,
Can any one explain me about COPA Summarization level and how we can do in the system.
Thanks and regards.
Ramesh.

Hi,
Please check the note 83204 which provides you a detailed information about the usage strategy for summarization levels.
Best regards,
MLM

Optimal summarization levels for CO-PA

Similar Messages

Maybe you are looking for