CJ01 — Create Project Definition and WBS Elements

CJ01 creates a project in Project Systems: a project definition (the outer container with start/finish dates, currency, project profile and person responsible) and, underneath it, one or more WBS elements arranged in a hierarchy. The structural fact that causes most confusion is that the project definition itself carries almost no operative capability. It cannot receive costs, be budgeted directly, or be an account assignment object. Only WBS elements marked with the relevant operative indicators - account assignment element, billing element, planning element - can actually be posted to, planned against, or billed from. A project saved with only a definition and no properly flagged WBS elements looks complete on screen but is functionally inert for everything downstream: budgeting, settlement, network cost collection.

CJ01 is used at project initiation, before any network activities, cost planning or budget is entered. A consultant reaches for it when setting up a brand-new project structure from scratch or copying one from a template project rather than transferring an existing one. Once the WBS skeleton exists, work moves to CJ02 for changes, CN22 for assigning networks and activities, and CJ40/CJ41 for original budget. On systems where the Project Builder (CJ20N) is the standing entry point, CJ01 is reached for less often in daily work but remains the transaction behind mass-creation programs, LSMW loads and BAPI-based project creation, so it is still the object worth understanding even where the front end has moved on.

Start in SE16 on PROJ, filter on PSPID for the external project ID, and note the returned PSPNR (internal number). Then query PRPS filtering PSPHI equal to that PSPNR to list every WBS element created under the project, checking POSID, STUFE and the responsible cost center field. An empty result on PRPS with a valid PROJ entry confirms a project definition exists with no WBS elements underneath it, which is the most common half-finished CJ01 outcome.

CJ01 still exists and functions the same way on S/4HANA; the underlying PROJ and PRPS tables and the operative indicator logic are unchanged. SAP's preferred day-to-day entry point on S/4 is the Project Builder (CJ20N), which combines create, change and display in one screen and is where most functional consultants now do initial structuring. CJ01 remains relevant behind mass-creation loads, migration objects and BAPI-driven project setup.

Functional PS territory almost entirely. Basis involvement is limited to number range configuration and authorization objects on project and WBS creation. ABAP gets pulled in only for mass creation via BAPI or LSMW. A clean handover states the project definition ID, whether it was copied from a template, and confirmation that WBS elements exist with the correct operative indicators and released status.

CJ20N is the natural next stop, since it is the day-to-day equivalent covering create, change and display of the same structure in one screen. CJ02 is where the same project gets amended after CJ01 has run. CN22 is reached once the WBS elements exist and networks need to be assigned to them. CJ40 follows for original budget entry, which only works once the account assignment and billing flags set in CJ01 are in place.