CJ41 — Create Original Budget for a Project

CJ41 is the transaction used to enter the original budget for a project, recording the first authorized spending amount against the project definition and its WBS elements before any commitments or actual costs are posted. It sits apart from cost planning, which is a non-binding cost forecast, and from actuals, which post automatically as goods receipts, invoices and confirmations hit the project. The structural fact that causes most confusion: the amount entered here only becomes a spending control if a budget profile with availability control is assigned to the project definition and activated. A budget can be entered and saved successfully in CJ41 while purchase orders and network activities continue posting without any check, because entering the number and enforcing the number are two separate configuration steps.

CJ41 is used once the project structure, meaning the project definition and WBS elements, exists and has been released, and before procurement or network execution begins consuming the project's budget. It is the natural next step after CJ20N or CJ01 has built the WBS hierarchy and before purchase requisitions, purchase orders, or network activities are raised against individual WBS elements. Consultants reach for this transaction for single-project, ad hoc budget entry or when troubleshooting a specific WBS element's figures; mass budget loads across a portfolio of projects are normally handled through upload programs or the change transaction working from a spreadsheet, and reporting-only users are pointed to a Fiori budget monitoring app rather than this entry screen.

Find the WBS element's object number in PRPS, then look it up in the budget tables filtered on that object number and the relevant value type to see whether an original budget record actually exists and for which fiscal year. Compare the figure against actual and commitment values pulled through CJI3 or the project's cost report for the same object number and period. If the budget table shows a value but purchase orders still post over that value with no warning, the gap is in availability control configuration, not in the CJ41 entry itself.

The data model and enforcement logic behind original budget did not change with the move to S/4HANA; CJ41 still works the same way, still writes to the same underlying budget tables, and availability control still depends on the same profile and activation steps. What is new is a layer of Fiori apps aimed at project managers for monitoring budget consumption and status, which read the same data rather than replacing the entry transaction. For most implementations the classic transaction, or its mass-upload counterpart, remains the actual entry point for original budget figures.

This is functional PS territory, usually shared with FI/CO for the budget profile and availability control tolerance configuration, since those settings live in controlling area customizing rather than in the project itself. Basis involvement is rare and limited to authorization objects for budgeting activities. A useful handover states the project or WBS element number, the amount and fiscal year entered, the exact system message if the save failed, and whether availability control is active on the project.

CJ20N and CJ01 come first in the sequence, since the WBS hierarchy has to exist and be released before any budget figure means anything. CJ40 is the natural next stop when the same budget needs changing rather than created for the first time. CJI3 is the report to run immediately after any budget investigation, to see what has actually been committed and spent against the figures just checked. CJ88 matters at the far end of the process, since settlement activity is what eventually consumes and closes out the budget picture for a completed project.