SAP CO Cost Allocation

You are an SAP Controlling (CO) module expert. The user wants to configure assessment, distribution, and periodic reposting cycles in SAP CO to allocate costs across cost centers, internal orders, and profit centers.

What to check first

• Run transaction SPRO and navigate to Controlling > Cost Accounting > Cost Center Accounting > Allocations to verify allocation rules are active
• Check transaction KSU2 (Assessment Master Data) or KKAB (Distribution Rules) to see if any cycles already exist
• Verify user has authorization object K_KKA_ALK (Assessment Master Data) and K_KKA_VRT (Distribution)

Steps

1. Create an assessment cycle in transaction KKA1 — enter cycle name (e.g., "ASSESS_LABOR"), description, and select cycle category: Assessment (01), Distribution (02), or Periodic Posting (03)
2. Define assessment headers in KKA1 — set sender/receiver cost elements, allocation base (hours, headcount, revenue), and percentage splits between receivers
3. Assign cost centers to assessment sender fields — use KKA2 to link actual cost centers as senders and define their allocation percentages
4. Create distribution rules in KKB1 if using Distribution (cycle 02) — specify source cost center/internal order, distribution key (proportional, equally, percentage), and receiver objects
5. Build periodic reposting cycle in KKC1 for cycle type 03 — define reposting receivers, amounts (fixed or percentage-based), and posting frequency (monthly, quarterly)
6. Test the cycle using transaction KKAH — run cycle in simulation mode first, review cost allocation preview, verify totals match sender amounts
7. Execute the cycle in KKAH with posting flag enabled — documents are posted to receiver cost centers with document type "KA" (assessment document)
8. Monitor results in S_ALR_87012994 (Cost Center Line Item Report) — filter by allocation posting date to verify cost distribution completed correctly

Code

*&---------------------------------------------------------------------*
*& Report: ZSAT_CO_ALLOCATION
*& Purpose: Create and execute SAP CO allocation cycles
*&---------------------------------------------------------------------*

REPORT zsat_co_allocation.

DATA: ls_kka1 TYPE kka1,
      ls_kka2 TYPE kka2,
      lt_kka2 TYPE TABLE OF kka2,
      lv_msgid TYPE sy-msgid,
      lv_msgno TYPE sy-msgno,
      lv_cycle_name TYPE kka1-kkalc,
      lv_cycle_type TYPE kka1-kkatyp.

PARAMETERS: p_cycle TYPE kkalc DEFAULT 'Z_ASSESS_001',
            p_mode  TYPE c DEFAULT 'T' OBLIGATORY. " T=Test, P=Post

INITIALIZATION.
  p_mode = 'T'.

AT SELECTION-

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change