CJ02 — Change Work Breakdown Structure
CJ02 is the classic Project System transaction for changing a Work Breakdown Structure. SAP documentation names CJ02 as Work Breakdown Structure: Change. It is used to maintain permitted WBS element master data and hierarchy information. In S/4HANA, SAP identifies CJ20N Project Builder as the target project-maintenance transaction, so CJ02 is a classic compatibility/support UI.
This page covers CJ02, the transaction used to change WBS element and project-level master data outside the Project Builder screen. It focuses on the status, budget-availability, and field-visibility errors that generate the majority of support tickets, and how to trace a change back through the underlying tables.
Published 20 Sept 2026· 462 words
Esta página ainda não está disponível em português.
Purpose
Change an existing Work Breakdown Structure and permitted WBS-element master data using the classic Project System maintenance interface. WBS changes can affect account assignment, planning, settlement, dates, procurement, status, and reporting, so the existing project history must be considered before editing.
When it is used
Use CJ02 when a classic PS procedure or support task requires a focused change to an existing WBS. In S/4HANA, use it with awareness that SAP's target maintenance architecture is CJ20N Project Builder rather than treating CJ02 as the preferred long-term UI.
How to use it in practice
- Enter the project/WBS to be changed and review the existing hierarchy and status first.
- Change only the approved WBS element attributes or hierarchy relationships.
- Check status and posted commitments/actuals before structural changes.
- Save and review the changed WBS in a read-only display or CJ20N.
- Regression-test downstream planning, procurement, settlement, or reporting if the changed field is consumed there.
Key data objects
These project/WBS attributes are the key anchors for analysis.
- Project/WBS identifier and hierarchy.
- Dates and organizational assignments.
- Operative/account-assignment indicators.
- System and user status.
- Settlement, planning, budget, and project-profile context.
How to prove it in the data
Capture the project and WBS element identifiers, hierarchy, status, dates, and organizational assignments in the standard transaction, then compare them with CJ20N and the relevant project report or line-item view. For a posting or settlement issue, follow the exact WBS object into the source purchasing/FI/CO document rather than inferring the cause from the structure screen alone.
ECC vs S/4HANA
SAP's S/4HANA simplification documentation includes CJ02 among project maintenance transactions categorized as not target architecture and points to CJ20N Project Builder as the target transaction. Existing CJ02 procedures may still work, but new process design should prefer the strategic maintenance surface.
Common pitfalls and how to diagnose them
- Changing structure after procurement/actual postings without impact analysis.
- Confusing a status restriction with an authorization failure.
- Editing a WBS field to bypass an upstream configuration/master-data problem.
- Treating CJ02 as the target S/4HANA project-maintenance UI when CJ20N is SAP's stated target.
Whose problem this is
Primary ownership is Project System. Controlling/Finance joins for cost, budget, settlement, or accounting questions; MM joins for project procurement; Security for authorization; ABAP only when custom enhancements are proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cj02ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.