CJ40 — Change Original Budget for a Project

CJ40 opens a hierarchical display of a project's WBS structure and lets the user enter or overwrite the original budget, either as one overall value per WBS element or split into annual values by fiscal year, depending on the budget profile assigned to the project. The structural fact that drives most of the confusion around this transaction is that the figure entered here is the original budget only. It is not the current available budget. Once the project goes live, changes to that baseline are meant to flow through supplement, return, and transfer transactions, each of which adjusts a separate 'current budget' figure while leaving the original untouched. Consultants who use CJ40 to 'correct' a live budget lose that audit trail and confuse anyone reconciling original versus current values later.

CJ40 is reached once the project structure exists and has been released (via CJ01/CJ02 or the project builder CJ20N) and cost planning is either done or deliberately skipped. It is the point where a controller or PS consultant loads the approved budget figure onto the structure before availability control is switched on, or at the start of a new fiscal year when annual values need to be entered for the new period. It is not used for planned costs (that is cost planning, a separate set of transactions) and not used for releasing budget for annual control (that is CJ41). On S/4HANA some organisations use a Fiori budgeting app for review and light editing, but CJ40 remains the transaction of choice whenever a full hierarchical mass entry or redistribution across many WBS elements is needed in one screen.

The safest first step is the display counterpart, CJ42, run against the same WBS element and fiscal year in dispute, because it reads the same tables through the standard logic and avoids version or currency misreads. To go behind that, pull the object number for the WBS element from PRPS, then filter BPGE and BPJA on that object number and version 0 (original budget version) for the fiscal year in question. Compare the total in BPGE against the sum of the annual rows in BPJA for the same object and version; a mismatch there, rather than in the transaction screen, points to a profile-level consistency check that was bypassed by a direct table update or an interface load.

CJ40 runs unchanged as a classic GUI transaction on S/4HANA and continues to write to the same underlying budgeting tables. SAP offers a Fiori app oriented toward reviewing and lightly editing project budget figures, which some organisations use for ad hoc changes, but it does not fully replace CJ40's hierarchical mass-entry and distribution functions, so most PS teams still use CJ40 for initial loads and large redistributions. There is no structural redesign of the budgeting data model to account for here.

This is a functional PS/CO problem, owned by the project controller or PS consultant responsible for the budget profile and the project's control settings. Basis involvement is limited to authorization objects for the transaction. ABAP is only pulled in if a customer validation, exit, or BAdI on the budget check is suspected. A good handover includes the WBS object number, fiscal year, budget profile name, and a screenshot or extract of the BPGE/BPJA figures alongside the expected value.

CJ41 is the natural next transaction to understand, since it governs release of the original budget for annual availability control and is where most 'budget entered but not usable' complaints actually get resolved. CJ20N and CJ02 are worth checking early whenever the project structure or status looks suspect before touching budget figures at all. CJ88 matters because settlement postings are what ultimately consume the budget entered here, so a discrepancy often traces back to a settlement run rather than to CJ40 itself. CJI3 gives the actual and commitment line items to compare against the budget total when a tolerance error does not match what the user expects.