SAP ABAP IMG Activity CRM_COOMOPA_CL_KSR (Strategy sequences for automatic generation of settlement rules)
Hierarchy
SAP_APPL (Software Component) Logistics and Accounting
   CO (Application Component) Controlling
     IAOM_CRMSERVICE (Package) Cost and Revenue Controlling for CRM Service
IMG Activity
ID CRM_COOMOPA_CL_KSR Strategy sequences for automatic generation of settlement rules  
Transaction Code S_AX8_68000382   IMG Activity: CRM_COOMOPA_CL_KSR 
Created on 20030307    
Customizing Attributes CRM_COOMOPA_CL_KSR   Strategy sequences for automatic generation of settlement rules 
Customizing Activity COOMOPACL_KSR_OB   Strategy Sequences for Automatic Generation of Settlement Rules 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name CRM_COOMOPA_CL_KSR    

You only need to process this IMG activity if you are using single-object controlling. In that case, you define a strategy sequence for automatic generation of the settlement rule for the internal orders here. You can change the settlement rule later in the internal order.

Strategies can be prioritized in strategy sequences. A strategy sequence specifies the order in which strategies are processed. If a strategy is successful, strategies with a lower priority are not executed.

Requirements

Standard settings

You can use the supplied strategy sequence SAPCRM for all controlling scenarios because it ensures appropriate settlement in all cases:

  • If you enter an account assignment in CRM, a settlement rule with a distribution rule with settlement type GES is created based on strategy 31. This settlement rule results in settlement to the transferred account assignment object. If you do not enter an account assignment, a distribution rule with settlement type GES to a profitability segment is created.
  • If you use accounting indicators, then based on strategy 35 a distribution rule with settlement type PER is also created for each source assignment that you assigned to a settlement receiver in the controlling scenario.

If you use this strategy sequence, you must settle periodically. If you do not want to do this, copy the strategy sequence and change the copy as follows:

  1. Enter the same settlement profile that you also select in the controlling scenario(s) to which you want to assign this strategy sequence. You must carry out this step to be able to select a source assignment in step 3.
  2. In strategy 35, replace the settlement type PER with GES. When this strategy is used in settlement, the costs of all periods are included and not only the costs that were posted during the last period.
  3. Choose Expert Mode On. For strategy 31, select the source assignment that includes all combinations of cost elements and accounting indicators that are not settled by strategy 35. To do this, you must have selected a settlement profile in the controlling scenario to which a source structure is assigned that meets the above condition.

Recommendation

SAP recommends using the strategy sequence SAPCRM unchanged and settling periodically. If you neither want to do this nor do you want to copy and change the strategy sequence SAPCRM as described above, you can use the following strategies:

  • 02: A distribution rule to a profitability segment is created, based on the relevant characteristics.
  • 30: A distribution rule that contains the transferred account assignment object as the settlement receiver. If no account assignment object is transferred from CRM, an error message is generated that is displayed in the Cockpit in ECC. For this reason you should only use this strategy if you always want to enter an account assignment in CRM.
  • 31: A distribution rule is created that contains the transferred account assignment object as the settlement receiver. If no account assignment object is transferred from CRM, a distribution rule to a profitability segment is created that is based on the relevant characteristics.
  • 35: This strategy includes the accounting indicator. A distribution rule is created for each source assignment to which you have assigned a settlement receiver in the controlling scenario. Select this strategy in addition to one of the three other strategies.

If you want to execute more than one strategy, you must assign priority 1 to each strategy.

Activities

  1. Choose New Entries.
  2. Enter a name (column StS) and a meaningful description for the strategy sequence.

    If you need to assign a source assignment (see step 5), select the same settlement profile (column SProf) that you select in the controlling scenario. A source structure must be assigned to this settlement profile.

  3. Choose Enter, select the line, and double-click on Strategies.
  4. Enter a priority and use the input help to select a strategy.
  5. Choose Enter. The columns Text, Percentage (Proz), and Settlement (AbA) are automatically filled with default values from the selected strategy.

    If you want to execute more than one strategy with settlement type GES (same priority) whose percentages add up to more than 100%, you must assign a source assignment to at least one of these strategies. To do this, choose Expert Mode On. You cannot assign a source assignment to strategy 35 because the settlement receivers for this strategy are always determined from the settings entered in the step Assignment of Settlement Receiver in the controlling scenario.

  6. Save your entries.

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG CRM_COOMOPA_CL_KSR 0 HLA0001410 Order Settlement 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
KSR2_ORC T - Individual transaction object KSR2_ORC  
History
Last changed by/on SAP  20030307 
SAP Release Created in 2002_1_46C