SAP Program RKEVERT1 - Rollup of Summarization Operating Concerns

General
This program lets you create summarization data for the CO-PAinformation system. The summarization data is stored in so-called"summarization operating concerns", which can be used in the normalinformation system. It is possible to create, actualize and deletesummarization operating concerns.

Procedure
1. In addition to the operating concern in which you normally post,create other operating concerns as summarization operating concerns.When doing so, note the following:

  • The summarization operating concerns must have the same currency, the
  • same fiscal year variant, the same period block and the same indicatorfor the alternative period type as the primary operating concern.
    • In Customizing for the summarization operating concerns, you only need
    • to maintain the number assignments and plan versions.
      • The summarization operating concerns do not need to be assigned to a
      • controlling area.
        • The system summarizes data over characteristics which do not exist in
        • the summarization operating concern, or which are deactivated using thefunction "Segment level characteristics".
          2. To control how summarization levels are created, you need to maintaintable TKEVVR1 (transaction SM30).
          • You can create plan data and actual data separately.

          • The system can create the data according to different algorithms.
          • Depending on certain conditions (such as the number of summarizations,degree of summarization, size of the tables) either method 1 (Fromsegment level, read by segment number) or 2 (From segment level, readaccording to sorting characteristics) may give you better performance.Only use method 3 (From line items) under special circumstances. Youshould use method 4 (From segment level with parallel processing) whenit is necessary to create the summarization levels several times andyou have the correct hardware.
            • When you use method 2, note the following: both sorting characteristics
            • should both either be as far down as possible in the hierarchy ordirectly above the summarized characteristics. For example, if you aresummarizing over the characteristics "Customer" and "Product", you coulduse the characteristics "Customer group" and "Product group" as sortingcharacteristics, but not "Division" or "Sales organization", which arehigher up in the hierarchy. In a single run, you can only createsummarization operating concerns which have the same sortingcharacteristics.
              • For methods 1, 2 and 3, you can improve performance by creating an
              • index for the segment tables (CE4xxxx) for the summarization operatingconcerns. This index should consist of the fields MANDT, AKTBO anda few characteristics which lie further down in the hierarchy.
                3. You create, actualize and delete summarization levels usingprogram RKEVERT1.
                • You can limit which summarizations you want to process, or whether you
                • want to process actual or plan data only.
                  • When you actualize, the system rolls up the line items which have been
                  • created since the last run (see time and date in tableTKEVVR1).
                    • When you create (mode 2), the system does not delete any existing data
                    • beforehand. You therefore need to do this using mode 4.
                      • When you create summarization levels using method 4 (From segment level
                      • with parallel processing), first execute program RKEVERT1 in mode 3 toinitialize. Then you can run program RKEVERT1 repeatedly in mode 2.The different jobs communicate and divide the creation task.