跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

sap-co

This skill handles all SAP CO (Controlling) topics: cost center accounting, profit center accounting, internal orders, product costing, profitability analysis (CO-PA), assessment and distribution cycles, actual vs plan postings, settlement, and CO period-end closing. Use when user mentions CO, cost center, profit center, internal order, KSU5, KSV5, KO88, CK11N, CO-PA, COPA, assessment, distribution, settlement, variance, controlling area, allocation cycle, activity type, KSB1, KSB5, cost element, plan vs actual, product cost collector.

BoxLogoDev · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add BoxLogoDev/sapstack --skill sap-co

技能说明


name: sap-co description: > This skill handles all SAP CO (Controlling) topics: cost center accounting, profit center accounting, internal orders, product costing, profitability analysis (CO-PA), assessment and distribution cycles, actual vs plan postings, settlement, and CO period-end closing. Use when user mentions CO, cost center, profit center, internal order, KSU5, KSV5, KO88, CK11N, CO-PA, COPA, assessment, distribution, settlement, variance, controlling area, allocation cycle, activity type, KSB1, KSB5, cost element, plan vs actual, product cost collector. allowed-tools: Read, Grep

1. Environment Questions

Ask before answering:

  • Controlling area (KOKRS) — single or cross-company code?
  • Company code assignment to controlling area: OX19
  • Controlling area currency vs company code currency
  • Fiscal year variant (must match FI)
  • CO-PA activated? If yes: costing-based, account-based, or both?
  • Material Ledger foundation active? S/4HANA에서는 inventory valuation의 기반이며, actual costing run 활성화 여부는 별도로 확인한다.

2. Cost Center Accounting (CCA)

Period-End Sequence

  1. Repost FI → CO if needed: KB11N (manual reposting) / KB15N (activity allocation)
  2. Enter statistical key figures: KB31N (required for assessment/distribution bases)
  3. Assessment cycles (actual): KSU5 → cycle/segment → sender cost centers → receivers
  4. Distribution cycles (actual): KSV5 → distribute primary costs (preserves cost element)
  5. Indirect activity allocation: KB65 (if applicable)
  6. Variance analysis: S_ALR_87013611

Cycle Configuration

  • KSU1 / KSV1 → create/change cycle → segments → sender/receiver rules
  • Sender: cost center + cost element range
  • Receiver: cost center / order / WBS / cost objects
  • Receiver rule: fixed amounts / fixed percentages / variable percentages / statistical key figures

Common Errors

ErrorRoot CauseFix
"No valid receiver found"Receiver in cycle not active or no postingsCheck cycle segment receiver list: KSU1
"Period already closed for CO"CO period lockedOKP1 → open period for controlling area
"CO document not generated"account assignment, real/statistical object, integration setting 불일치원천 FI 문서와 CO line item을 read-only로 대조하고 release별 reconciliation 절차 확인
"Sender has no costs"Nothing posted to sender cost centerKB11N or check primary cost posting

3. Profit Center Accounting (PCA)

ECC vs S/4HANA

AspectECC (EC-PCA)S/4HANA
TableGLPCT / GLPCAACDOCA
Period-end transfer1KEI (balance sheet items)Automatic via Universal Journal
Transfer prices1KE8Integrated in Universal Journal
ReportingKE5Z / S_ALR_87013326Fiori Profit Center app / KE5Z

Profit Center Derivation

  • OKB9는 cost element별 default CO account assignment에 쓰이며 profit center의 일반 default 도구로 단정하지 않는다.
  • Material master → Costing 2 view → profit center
  • Sales order item의 profit center는 material/plant 및 configured substitution 등 실제 derivation trace로 확인한다.
  • Manual entry 허용 여부는 field status, substitution, validation과 권한에 따라 다르다.

4. Internal Orders

Order Lifecycle

Create (KO01) → governed release → Post costs → Settle (KO88) → TECO → Close status

Configuration

  • Order type: OKT2 → drives settlement profile, number range, status management
  • Settlement profile: OKO7 → allowed receivers (cost center / G/L / asset / WBS)
  • Budget: KO22 (budget entry) → OKOB (availability control tolerance)
  • Commitment management: orders can carry purchase order commitments

Settlement (KO88)

  • KO88: individual order settlement
  • Always simulate first (test run)
  • Settlement rule: inspect the sender master from the settlement context; maintain receivers and percentages only through the approved master-data process

Common Errors

ErrorFix
"Order is locked"Inspect sender system/user status; request governed release only when business prerequisites are met
"No settlement rule defined"Inspect sender settlement data; create the approved receiver rule through the master-data owner
"Receiver not valid"Check settlement profile allows this receiver type
"Budget exceeded"KO22 → increase budget or KO26 (supplement)

5. Product Costing (CO-PC)

Standard Cost Estimate Flow

CK11N (single material)  → cost estimate per material / plant / lot size
CK40N (costing run)      → mass processing across multiple materials
CK24                     → Mark (set as future std cost) → Release (activate)

Configuration Elements

  • Cost component structure: OKTZ → groups cost elements into components (material / labor / overhead)
  • Overhead: KZS2 → costing sheet → overhead rates
  • Activity rates: KP26 → plan activity prices per cost center / activity type

Common Errors

ErrorRoot CauseFix
"No valid price found"Missing purchase info record or activity rateME11 (info record) or KP26 (activity price)
"BOM not found"BOM not created or not assigned to plantCS01 / CS03 → check usage = 1 (production)
"Routing not found"No routing for material/plantCA01 → create routing
"Costing variant not assigned"Plant not assigned to costing variantOKKN → costing variant → valuation

6. CO-PA (Profitability Analysis)

Types

  • Account-based PA: uses G/L accounts directly → S/4HANA default → ACDOCA
  • Costing-based PA: uses value fields → configured SD condition/value-field transfer와 operating concern의 segment-level line items

Key Configuration

  • Characteristic derivation은 operating concern의 derivation strategy와 trace를 기준으로 검증하며, condition/value-field assignment와 혼동하지 않는다.
  • SD → costing-based CO-PA transfer는 billing condition과 value field assignment, transfer status를 함께 확인한다.
  • Planning은 시스템 release와 활성 planning framework에 따라 classic plann
阅读完整来源 ↗