CJ02 — Change Project WBS Elements and Status

CJ02 changes an existing project definition and its WBS elements: basic dates, responsible cost center, project profile-driven fields, user status, and settlement rule at WBS level. The one structural fact that explains most confusion is that CJ02 is not the Project Builder (CJ20N) — it opens a flat or hierarchical overview screen with 'Level' pushbuttons controlling which fields display, and what is editable depends entirely on the project profile's field selection and the current system/user status of the element being touched, not on any authorization the user thinks they have. Two consultants looking at the same WBS element can see different editable fields simply because they navigated in at different hierarchy levels.

CJ02 is used during project execution when a specific WBS element needs a targeted change: extending a finish date, reassigning a responsible cost center, releasing or closing an element, setting a user status, or amending a settlement rule. Consultants reach for it instead of CJ20N when the WBS number or project number is already known from a ticket and there is no need to navigate the full structure tree, or when doing bulk field checks across levels is faster in the overview grid. In S/4HANA, Fiori project apps cover high-level status and date changes for project managers, but detailed field-level edits and status transitions not exposed in Fiori still land back on CJ02.

Pull PRPS filtered by the project's internal number (PSPHI) or the WBS element's own key, and compare AEDAT and AENAM against the ticket's reported change time. To confirm a status transition, query JEST for the object key and join to JCDS to see the status history with timestamp and user ID — this settles disputes about who closed or released an element and when. For settlement rule questions, check COBRA against the same WBS key. If a change appears lost, check for an open enqueue lock on the project or WBS object before assuming the save failed silently.

CJ02 remains available in S/4HANA and writes to the same underlying tables as in ECC. SAP steers users toward Fiori project management apps for status overviews and toward CJ20N's Project Builder for structural navigation, but detailed field-level edits and status changes not exposed in the Fiori apps still go through CJ02. No functional deprecation of the transaction is documented; treat it as a durable classical-GUI tool alongside the newer front ends rather than a legacy screen scheduled for removal.

This is a functional PS consultant's transaction for day-to-day field and status changes. ABAP gets involved only when a custom validation, substitution, or user exit on save is suspected. Basis is needed only for a stuck enqueue lock. A good handover includes the project number, the specific WBS element, the exact field being changed, the error message text, and the element's current status from JEST.

CJ03 is the display-only counterpart and should be the first stop to confirm current values before attempting a change in CJ02. CJ01 is the creation transaction that establishes the project profile and structure that CJ02 later constrains. CJ20N is the tree-based Project Builder covering the same data with a different navigation model, useful when structural changes span multiple WBS elements at once. CJI3 is the reporting transaction to verify that a CJ02 change actually reached actuals and commitments as expected. CJ88 handles settlement, which depends directly on the settlement rule maintained through CJ02.