CJ01 — Create Work Breakdown Structure
CJ01 is the classic Project System transaction for creating a Work Breakdown Structure. SAP documentation lists CJ01 as Work Breakdown Structure: Create, CJ02 as Change, and CJ03 as Display. In S/4HANA, SAP has identified CJ20N Project Builder as the target maintenance transaction, so CJ01 should be treated as classic WBS maintenance rather than the strategic project-structure UI.
This page covers CJ01, the classic PS transaction for creating a project definition and its WBS element structure. It focuses on the numbering mask, operative indicator, template-copy and status traps that generate downstream failures in budgeting, settlement and network assignment.
Published 20 Sept 2026· 465 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
Create the WBS structure and WBS-element master data for a project using the classic Project System maintenance screen. A WBS decomposes project scope into controllable/account-assignable elements. Project definition maintenance is a related but distinct concept; SAP's official transaction list names CJ01 specifically for creating the Work Breakdown Structure.
When it is used
Use CJ01 in classic PS procedures, support, migration validation, or legacy documentation when a WBS structure is being created through the older maintenance UI. For new S/4HANA operating procedures, evaluate CJ20N Project Builder as SAP's target project-maintenance transaction.
How to use it in practice
- Enter or create the project/WBS context required by the classic transaction.
- Maintain WBS element identifiers, descriptions, dates, organizational assignments, operative indicators, and other required master data.
- Build the hierarchy carefully because parent/child relationships drive planning, reporting, settlement, and account assignment.
- Save and inspect statuses and assignments for representative WBS elements.
- Validate the same structure in CJ20N, especially in S/4HANA procedures.
Key data objects
These project/WBS attributes are the key anchors for analysis.
- Project definition and WBS hierarchy.
- WBS element identifier and hierarchy position.
- Dates, responsible organizational assignments, and operative indicators.
- System/user status and account-assignment relevance.
- Settlement/planning/budget-related profile context where applicable.
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 categorizes CJ01/CJ02/CJ03 and other redundant project maintenance transactions as not target architecture, with functional equivalent available in CJ20N Project Builder. They may remain available, but CJ20N is the strategic maintenance transaction.
Common pitfalls and how to diagnose them
- Calling CJ01 the transaction that creates both the project definition and WBS without distinction.
- Building the hierarchy under the wrong project/profile.
- Changing WBS IDs or hierarchy without assessing posted commitments/actuals.
- Designing a new S/4HANA procedure around CJ01 without evaluating CJ20N.
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/cj01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.