Quick Answer
The most used SAP PS transaction codes are CJ20N (Project Builder) for building projects, CJ40 and CJR2 for cost planning, CJ30 and CJ32 for budgets, CN25 for confirmations, CJ88 and CJ8G for settlement, and CN41N and CJI3 for reporting. This cheat sheet groups the standard SAP Project System transactions by project phase, so you can find the right one for the job in front of you. It also lists the system statuses that decide what each transaction allows. SaiSatwik consultants use the same grouping when training key users.
How should you use this SAP PS transaction codes cheat sheet?
SAP PS transaction codes make more sense grouped by the stage of a project than in alphabetical order. Each table below covers one phase. All codes listed are standard SAP Project System transactions that run in ECC and SAP S/4HANA.
If you are new to the module, read the SAP PS beginner guide first. It explains the objects these transactions work on. Your system may also have custom Z transactions; check with your SAP team before relying on them.
Which SAP PS transaction codes build the project structure?
Structure transactions create and change project definitions, WBS elements, networks and templates. CJ20N covers almost all of it in one screen, as the CJ20N walkthrough shows.
| Transaction | Purpose |
|---|---|
| CJ20N | Project Builder: create and change the whole project |
| CJ06 / CJ07 / CJ08 | Create, change, display project definition |
| CJ01 / CJ02 / CJ03 | Create, change, display work breakdown structure |
| CJ11 / CJ12 / CJ13 | Create, change, display WBS element |
| CN21 / CN22 / CN23 | Create, change, display network |
| CJ2B / CJ2C | Change, display project planning board |
| CJ91 / CJ92 / CJ93 | Create, change, display standard WBS (template) |
| CN01 / CN02 / CN03 | Create, change, display standard network (template) |
Which SAP PS transaction codes handle planning and budgeting?
Planning transactions record expected cost. Budget transactions record approved money. The SAP PS cost planning guide and the guide to budgeting and availability control explain when to use each.
| Transaction | Purpose |
|---|---|
| CJ40 / CJ41 | Change, display overall (structure) cost plan |
| CJR2 / CJR3 | Change, display cost element and activity input plan |
| CJ30 / CJ31 | Change, display original budget |
| CJ32 / CJ33 | Change, display budget release |
| CJ34 | Budget transfer between WBS elements or projects |
| CJBV | Activate availability control |
| CJBN | Reconstruct availability control |
Which SAP PS transaction codes are used during execution?
Execution transactions record what actually happens on the project: work done, materials needed and deliveries made.
| Transaction | Purpose |
|---|---|
| CN25 | Confirm a network activity |
| CN27 | Collective confirmation |
| MD51 | Project-driven MRP for one project |
| CNS0 | Create delivery from project |
Which SAP PS transaction codes run the period-end close?
Period-end transactions run in a fixed order: overhead, then results analysis, then settlement. The SAP PS settlement guide and the results analysis guide cover the detail.
| Transaction | Purpose |
|---|---|
| CJ44 / CJ45 | Overhead calculation, individual and collective |
| KKA2 / KKAJ | Results analysis, individual and collective |
| CNE1 / CNE2 | Progress analysis, individual and collective |
| CJB2 / CJB1 | Generate settlement rules, individual and collective |
| CJ88 / CJ8G | Settlement, individual and collective |
| CJIC | Maintain line item settlement for assets under construction |
Which SAP PS transaction codes are best for reporting?
Reporting transactions are where most users spend their time once a project is live. CN41N alone answers most structure and status questions.
| Transaction | Purpose |
|---|---|
| CN41N | Structure overview: whole project with dates and statuses |
| CN42N / CN43N | Project definitions and WBS elements overview |
| CN47N | Network activities overview |
| CJI3 | Actual cost line items |
| CJI5 | Commitment line items |
| S_ALR_87013532 | Plan, actual, commitment, remaining plan and assigned values |
| CJE0 | Run a project hierarchy report |
| CNE5 | Progress analysis (earned value) report |
CNE5 is the earned value view. The earned value management guide explains how to read it.
Which configuration transaction codes should SAP PS consultants know?
Configuration transactions belong to the SAP team, not end users. These five open the profiles that shape how every project behaves. The SAP PS configuration guide walks through them in order.
| Transaction | Purpose |
|---|---|
| OPSA | Project profile |
| OPSJ | Project coding mask |
| OPUU | Network profile |
| OPS9 | Budget profile |
| OKO7 | Settlement profile |
Which system statuses decide what SAP PS transactions allow?
Many SAP PS errors are status problems, not transaction problems. A posting fails because the WBS element is still created, not released. These system statuses matter most.
- CRTD (created). Planning allowed, actual postings blocked.
- REL (released). Actual postings allowed.
- BUDG (budgeted). A budget has been entered.
- SETC (settlement rule created). The object has a settlement rule.
- TECO (technically completed). Work finished; most new commitments blocked, costs can still post.
- CLSD (closed). No further postings.
How does SaiSatwik train teams on SAP PS transactions?
SaiSatwik trains SAP PS users by role, not by transaction list. A project administrator learns the structure and reporting codes. A controller learns planning, budgeting and period-end. Training runs on the client’s own project templates, so the first live project looks familiar.
Role-based training is part of every engagement from the SaiSatwik SAP practice. Official reference documentation sits on the SAP Help Portal, and formal courses are on SAP Learning. All the codes here also run in SAP S/4HANA, alongside newer SAP Fiori apps.
FAQs about SAP PS transaction codes
What is the most important SAP PS transaction code?
CJ20N, the Project Builder. It creates and changes project definitions, WBS elements, networks, activities and milestones in one screen. Most project administrators spend more time in CJ20N than in every other SAP PS transaction combined.
Which transaction shows actual costs on a project?
CJI3 lists actual cost line items by project or WBS element. For a summary of plan against actual and commitments, use S_ALR_87013532. CJI5 lists commitment line items such as open purchase orders.
Do SAP PS transaction codes work in SAP S/4HANA?
Yes. The standard SAP PS transactions in this cheat sheet run in SAP S/4HANA. SAP also adds Fiori apps for project monitoring, and some detailed planning moves toward SAP Analytics Cloud.
Why does SAP PS say my WBS element has the wrong status?
The element’s system status forbids the action. New elements sit in CRTD, which blocks actual postings. Release the element in CJ20N, or check whether it is already technically completed or closed.
0 Comments