Hi @lisbeth_z
Thank you for your question! Let me clarify the behavior of KORS and provide guidance on your scenario.
KORS is not a pricing condition type that you configure in the pricing procedure. Instead, it is an Account Determination Type used for General Ledger (G/L) account determination in SAP. Similar to KOFI, which is generally used for postings to Finance in SAP SD, SAP CCM has its own Account Determination Types such as KORS, KORP, KORR, and KORC, each serving different purposes in rebate and settlement processes.
Configuring Different Accounts for KORS
While you can assign different account keys for various condition types in the pricing procedure, I recommend carefully reviewing your configuration. This is because setting up different accounts for each condition type would require duplicating several critical condition types, such as RES2, REA2, RED2, REA5.
These condition types play a vital role in the calculation and reversal of rebates and accruals. Any misconfiguration can lead to incorrect postings, so ensure that you align your account keys and G/L assignments with the relevant reversal and settlement logic.
Recommendation
It is best practice to use Condition Tables 015 and 016 for maintaining account keys and G/L determination for SAP CCM. These tables simplify account assignment and ensure consistency across different Account Determination Types.
Please also review the configuration guide provided by SAP:
2535889 - CCM - Description of delivered configuration
Best regards,
Gauthier
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.