CJ20N — Project Builder for WBS and Network Maintenance

CJ20N, Project Builder, is the single hierarchical editor for creating and maintaining a project's full structure - project definition, WBS elements, networks, network activities, relationships and milestones - in one tree view instead of separate transactions per object type. The structural fact that explains most confusion: everything visible in that tree belongs to one lock and one save. A user opens a project, expands nodes across WBS and network branches, edits several of them, and issues a single save; if one branch fails a check - a missing cost center derivation on a WBS element, an activity referencing a deleted work center - the save can be rejected outright or committed for the valid branches only, leaving a tree that looks fully edited on screen but was not actually persisted in full. That gap is the source of most 'my changes disappeared' tickets.

Reached for whenever a project's structure needs building or changing after the initial project definition exists - adding WBS elements, attaching networks and activities, setting relationships, assigning account assignment objects, releasing or closing elements, or triggering scheduling. It sits between project initiation (project definition created via a template or the create transaction) and execution reporting or settlement. Consultants reach for CJ20N rather than the classic single-object transactions whenever a change spans both WBS and network at once, since the tree view exposes cross-object dependencies that the separate transactions hide. On an S/4HANA implementation with a Fiori-first rollout, CJ20N remains the transaction opened for anything beyond simple status changes or read-only monitoring, because the Fiori apps available cover reporting and light actions, not full structural editing of a mixed WBS-and-network tree.

Pull PRPS filtered on the project definition key to list every WBS element and its object number, then join to JEST on that object number to see the actual system and user status set for each element - this confirms or disproves a claimed release or technical completion. For network-side symptoms, take the network order number referenced from the project's WBS entries, pull AFKO and AFVC for that order, and join AFVV for activity dates and quantities; comparing those values against what the Project Builder tree currently displays confirms a partial or failed save rather than a stale screen.

CJ20N runs unchanged as a GUI transaction on S/4HANA. There is no full Fiori replacement for combined structural editing of WBS and network trees; the available Fiori apps cover monitoring, financial views and simple status actions, not the detailed build-out CJ20N handles. Underlying reads benefit from HANA-optimized processing, but the transaction's screens, logic and locking behavior match ECC. Custom enhancements or BAdIs firing during CJ20N save carry over through a conversion and need re-testing, since some underlying function modules were adjusted for simplification without changing the visible transaction.

Functional PS consultant owns configuration - project profile, network profile, status profiles, field selection keys - and handles the day-to-day 'why can't I edit this' or 'why didn't my status stick' questions. Basis owns lock cleanup in SM12 and authorization objects controlling project access. ABAP gets involved only when a custom validation, substitution or BAdI fires during save. A good handover names the exact node in the tree, includes the save-time message log, and states whether the issue reproduces on a project without custom enhancements active.

CJ01 and CJ02 are worth knowing because they are the classic single-object WBS transactions CJ20N largely replaced for day-to-day work; their simpler screens help isolate whether a CJ20N symptom is really a WBS-level issue. CN22 covers the same ground for networks alone and helps separate network-specific problems from the combined tree view. CJI3 is the natural next stop once the structure is confirmed correct, to check whether actual postings landed on the right objects. CJ88 matters once WBS elements start collecting costs that need settling, since settlement rules depend on the account assignment set up through CJ20N.