CJ40 — Change Overall Costs in WBS
CJ40 is the Project System transaction for changing overall cost planning on WBS elements. SAP documentation identifies CJ40 as Change Overall Costs in the WBS or Change Cost Planning. It is a planning transaction, not the original-budget entry transaction. Budgeting and availability control use separate Project System transactions and data from overall cost planning.
This page covers CJ40, the classic PS transaction for maintaining original budget on a project structure, including the hierarchical entry logic, the tables the save writes to, and the diagnostic order for the most common budgeting failures: profile mismatches, level restrictions, and confusion between original and current budget. It also covers what changes, and what does not, on S/4HANA.
Published 20 Sept 2026· 542 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
CJ40 maintains overall planned costs for a project's Work Breakdown Structure. Project planners use it to enter or change top-down or WBS-level cost plan values, depending on project/planning configuration. Planned cost is a forecast/baseline for controlling and results-analysis purposes; it must not be mislabeled as original project budget.
When it is used
Use CJ40 during project planning and forecasting when overall planned cost values need to be entered or revised on WBS elements. SAP documentation for Project System overall CO planning explicitly lists CJ40 as Change Overall Costs in the WBS, alongside CJ41 for display and CJ42/CJ43 for revenue planning/display.
How to use it in practice
- Enter the project or WBS selection and the planning context required by the project.
- Review the WBS hierarchy and existing overall/annual planned cost values.
- Enter or change planned cost only at WBS levels permitted by the planning design.
- Use appropriate distribution/copy functions where the process requires planned values to be spread by year or hierarchy.
- Save and compare the resulting plan with detailed planning and actual/commitment reports.
Key data objects
CJ40 works with project/WBS cost planning, not budget control.
- Project definition and WBS elements — define the hierarchy being planned.
- Plan values — overall and, depending on planning design, annual/project-period values.
- Plan version/currency context — use the same context when comparing reports.
- Detailed versus overall planning — distinguish aggregate CJ40 values from detailed cost-element/activity planning.
- Actuals/commitments — separate posted/committed cost from the plan when analyzing variances.
How to prove it in the data
Display the same project plan with CJ41 and compare the overall cost plan to project planning reports using identical version, currency, and fiscal-year context. Then compare planned cost against actual/commitment line items such as CJI3 where relevant. If a user expects a spending block, verify Project System budgeting/availability control separately—CJ40 planned cost alone is not the original budget.
ECC vs S/4HANA
SAP documentation continues to identify CJ40 as Change Cost Planning/Change Overall Costs for projects. S/4HANA project and accounting models can add Fiori planning/reporting options, but the conceptual distinction between planned cost and project budget remains critical.
Common pitfalls and how to diagnose them
- Calling CJ40 a budget transaction and expecting availability control to enforce the entered plan.
- Comparing overall planning with detailed cost-element planning without matching version/currency/year.
- Changing plan values to explain an actual-posting error.
- Assuming a project is over budget because actual cost exceeds CJ40 plan without checking the actual budget/availability-control configuration.
Whose problem this is
Primary ownership is Project System/Controlling planning. Project controllers define plan values and versions; FI/CO supports reconciliation; Budget/availability-control owners manage the separate project-budget process.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cj40ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.