Symptom
Postings are successfully made to a specific cost center even though the Lock Primary Costs Posting indicator is active in the Control Indicators section of the Manage Cost Centers app. The expected error message KI260 (Cost center &1 blocked against direct postings on &2) is not raised during the transaction.
Environment
SAP S/4HANA Cloud Public Edition
Cause
The standard cost center lock indicators are designed to control Controlling (CO) relevant postings. The system behavior is determined by the G/L account type and the application component initiating the posting:
-
Primary Cost Accounts: The lock is strictly enforced for accounts with the G/L Account Type "Primary Costs or Revenue."
-
Balance Sheet Accounts: Since balance sheet accounts do not typically generate actual primary costs in CO, the cost center assignment is often considered statistical. In these cases, the standard master data lock is bypassed to ensure logistical processes are not disrupted.
-
Application-Specific Logic: * Logistics (SD/MM): For transactions such as Sales Distributions (SD00) or Material Postings (MIGO, MIR7), the system prioritizes the completion of the logistical chain. Locks are often bypassed for balance sheet accounts to prevent process deadlocks in the supply chain.
-
Financial/Controlling (RFBU/COIN): Direct financial postings or CO-internal transactions execute a stricter validation. In these interfaces, the system checks the lock indicators even for balance sheet accounts if the cost center is a required entry.
-
Resolution
This behavior is a result of the standard architectural design of the FI/CO interface. The Lock Primary Costs Posting indicator is intended to prevent the erosion of cost center budgets through expense accounts, rather than restricting all possible statistical assignments.
Keywords
KI260, Cost Center Lock, Primary Costs Posting, Balance Sheet Account, Manage Cost Centers, Control Indicators, SD00, MIGO, MIR7, RFBU, COIN, S4_PC , KBA , CO-OM-CCA-2CL , Cost Center Accounting (Public Cloud) , Problem
SAP Knowledge Base Article - Public