CJ03 — Display Project - WBS Structure Read-Only View

CJ03 opens the classic project structure display for a project definition, showing the WBS element hierarchy, basic dates, organizational assignments, responsible cost center, and system/user status for each level. Every field is greyed out; there is no save. The structural fact that drives most confusion is that CJ03 belongs to the older, separate PS transaction family split between project transactions (CJ01/CJ02/CJ03) and network transactions (CN01/CN02/CN22 etc). It shows the WBS tree only. Networks, activities, and relationships assigned to the project are not displayed here even though they belong to the same project structure - that view lives in CN22/CN23 or in the integrated Project Builder, CJ20N. Consultants expecting a full project-with-network tree in CJ03 are looking in the wrong transaction, not hitting a data problem.

CJ03 gets used for fast, safe lookups of WBS master data where accidental change is a risk - before running settlement, during an audit walkthrough, or when checking status and dates ahead of a period-end close. It is also the fallback when a user's role only grants display authorization for project master data, since attempting CJ02 in that case throws an authorization dump rather than opening in display mode. Consultants reach for CJ20N instead when the task requires seeing WBS elements alongside networks, activities, and milestones in one navigable tree, or when mass changes across levels are needed. CJ03 remains useful precisely because it is lighter and faster to open than the Project Builder for a single, narrow question about one WBS element.

To confirm what a user sees in CJ03, pull the WBS element directly from PRPS filtered on POSID (or PSPNR for the internal number) and compare planning dates and responsible cost center against what the screen shows. To check status, take the object number from PRPS-OBJNR and read JEST for that object number, then resolve the status codes through TJ02T. A mismatch between what CJ03 displays and what JEST holds usually means a buffered screen that needs a fresh transaction call rather than a data problem.

CJ03 still exists on S/4HANA as the classic display transaction and continues to work the same way as in ECC; there is no material behavior change. A Fiori app exists for displaying project and WBS information with a more modern layout, but the classic transaction is not deprecated and remains in daily use, particularly for consultants who need a fast, low-overhead lookup rather than the fuller Project Builder or Fiori experience.

This is functional PS territory almost every time - the fields, statuses, and hierarchy logic are all project system master data concerns. Basis gets involved only when the issue is a genuine authorization role gap. A good handover states the exact WBS element or project definition, the status shown in JEST, the transaction and mode attempted (display vs change), and whether the same object behaves correctly in CJ20N.

CJ02 is the change-mode counterpart and the natural next transaction once a display check in CJ03 confirms an actual edit is needed. CJ20N, the Project Builder, is the broader replacement view that shows WBS elements together with networks and activities, and is worth learning immediately after CJ03 since most real project work happens there. CJ01 is the creation transaction and useful context for understanding how the fields seen in CJ03 first get populated. CJI3 gives the actual cost line item view for a WBS element, useful when a display check in CJ03 raises a question about postings rather than master data.