CJ41 — Display Overall Costs in WBS
CJ41 is the Project System display transaction for overall WBS cost planning. SAP documentation lists CJ40 as Change Overall Costs in the WBS and CJ41 as Display Overall Costs in the WBS. CJ41 is therefore a read-only planning analysis transaction, not a transaction for creating or releasing original project budget.
This page covers what CJ41 actually writes when a project's original budget is entered, and why a saved figure sometimes fails to stop over-spending. It focuses on the diagnostic sequence for the failures consultants actually see: enforcement gaps, distribution mismatches, wrong-level budgeting, status blocks, and confusion between budget and cost planning data.
Published 20 Sept 2026· 458 words
Esta página ainda não está disponível em português.
Purpose
CJ41 displays overall planned cost values for the project/WBS hierarchy without changing them. It is the display counterpart to CJ40. The transaction helps project controllers review aggregate planned costs and compare them with detailed planning, actual cost, commitments, or revenue plans.
When it is used
Use CJ41 when a controller, auditor, or support consultant needs a read-only view of overall project cost planning. It is useful for verifying whether CJ40 changes were saved, reviewing planning before forecast/close activities, or reconciling plan values with reports without risking accidental changes.
How to use it in practice
- Enter the project or WBS selection and relevant planning context.
- Display the hierarchy and review overall/annual planned cost values.
- Confirm version, currency, and fiscal-year context before comparing with another report.
- Drill or navigate to the relevant WBS elements where a variance appears.
- Use actual/commitment reporting separately to compare execution with the displayed plan.
Key data objects
CJ41 is a planning display, so context determines whether two figures are comparable.
- Project definition/WBS element.
- Plan version and fiscal-year/period context where applicable.
- Currency/value view.
- Overall versus annual planned cost.
- WBS hierarchy level and aggregation.
How to prove it in the data
Compare CJ41 with CJ40 for the same project/WBS and planning context to verify stored plan values, then reconcile to project planning reports. Use CJI3 or other actual/commitment reports only after aligning project, WBS, currency, and period. If the question is about spending authority or availability control, move to the separate budget process rather than interpreting CJ41 plan as budget.
ECC vs S/4HANA
SAP's documented Project System role still identifies CJ41 as Display Overall Costs in the WBS. S/4HANA may offer additional Fiori planning/reporting surfaces, but the transaction's role as a cost-plan display—not budget creation—remains the key semantic point.
Common pitfalls and how to diagnose them
- Calling CJ41 a budget creation or release transaction.
- Comparing plan figures from different versions or currencies.
- Expecting CJ41 to show actual or commitment values as part of the plan.
- Using a planned-cost variance to diagnose availability-control behavior without checking the actual project budget.
Whose problem this is
Project System/Controlling owns overall cost planning and interpretation. Project-budget owners handle spending-control questions, while Finance supports accounting/actual-cost reconciliation.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cj41ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.