SAP ABAP Data Element RKE_AL_DBSELECT (Type of database selection for periodic allocations CO-PA)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ KE (Package) Profitability Analysis
Basic Data
Data Element RKE_AL_DBSELECT
Short Description Type of database selection for periodic allocations CO-PA  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type KALC_DB_SELECT    
Data Type NUMC   Character string with only digits 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Selec. typ 
Medium 15 Selection type 
Long 21 Selection type 
Heading 0   
Documentation

Definition

In the Database selection field, you control the database access strategy when the system reads sender data or receiver tracing factors. This settings affects the runtime of a cycle run. The quality of the database access strategy depends to a large extent on the structure of the relevant cycles.

As a standard, the chosen setting is only valid for the current cycle run. If you want this setting to be valid permanently, you should add it to a variant. Alternatively, you can make your setting using the 'save' icon for all cycle runs.

You have the following choices:

  • Selection by cycle (Standard setting)

    For each relevant field (such as cost center, cost element, receiver characteristic etc.) an interval is calculated from the smallest and greatest value in the field in the whole cycle.

    On the receiver side, this interval is used for the database selection. This means that an access to the database is made, but that too many objects might be selected. The system eliminates these objects subsequently.

    On the sender side, only the CO-objects which were actually defined by the cycle are selected from the interval and used.

    Recommendation: The number of segments in a cycle, in which you apply this strategy, should not exceed 100. The hits for the individual segments should overlap as much as possible, particularly on the receiver side.

  • Selection by segment

    For each relevant field, an interval is calculated from the smallest and greatest value of the field in the corresponding segment and used for a database access per segment. With this option, the runtime of the database selection rises almost in direct proportion to the number of segments, rather than exponentially, which is the case with selection by cycles. However, it is possible for the same objects to be selected more than once, which leads to the number of hits for the database selection over the entire cycle becoming unnecessarily large.

    Recommendation: The hits for the individual segments should overlap as little as possible, particularly on the receiver side.

History
Last changed by/on SAP  19990520 
SAP Release Created in