CJ03 — Display Work Breakdown Structure
CJ03 is the classic Project System transaction for displaying a Work Breakdown Structure in read-only mode. SAP documentation lists CJ03 as Work Breakdown Structure: Display. It is useful for safe WBS master-data and hierarchy checks. In S/4HANA, SAP identifies CJ20N Project Builder as the target project-maintenance transaction, while CJ03 remains a classic display path.
CJ03 is the read-only counterpart to CJ02 for viewing a project's WBS hierarchy and master data. This page covers when consultants reach for it over the Project Builder, what actually gets checked, and the diagnostic categories behind the most common confusion it causes - authorization errors mistaken for bugs, status-locked fields mistaken for authorization problems, and missing WBS elements caused by deletion flags or hierarchy scope.
Published 20 Sept 2026· 455 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
Display the WBS hierarchy and WBS-element master data without changing it. CJ03 is useful for confirming project structure, dates, organizational assignments, operative indicators, and status before troubleshooting planning, procurement, settlement, or actual-cost issues.
When it is used
Use CJ03 when a read-only classic view is sufficient for support, audit, or handover. For broader project/navigation context, CJ20N can show project structures in the target maintenance environment.
How to use it in practice
- Enter the project or WBS identifier.
- Review the hierarchy and WBS element attributes on the relevant key/date context.
- Check system/user status and operative indicators for the affected element.
- Record the exact WBS IDs and organizational assignments before analyzing follow-on postings.
- Use CJ20N or specialized reports to continue into networks, planning, costs, or settlement as needed.
Key data objects
These project/WBS attributes are the key anchors for analysis.
- Project definition and WBS hierarchy.
- WBS element identifier, description, and hierarchy position.
- Dates and organizational assignments.
- Operative/account-assignment indicators.
- System/user status and related 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 categorizes CJ03 and related classic project-structure maintenance transactions as not target architecture, with CJ20N Project Builder as the target transaction. CJ03 remains useful as a classic read-only support/search term.
Common pitfalls and how to diagnose them
- Calling CJ03 a generic 'Display Project' transaction rather than specifically WBS display.
- Looking at the wrong WBS hierarchy or project version/context.
- Using current master data to explain historical posting behavior without change/status history.
- Assuming availability means CJ03 is SAP's strategic S/4HANA project UI.
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/cj03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.