3727212 - Account Number Field Is Mandatory In Manage Budget Documents – Projects (F5342) Application

• In the Manage Budget Documents – Projects (F5342) application, the Budget Item field “Account Number” appears as mandatory during budget creation.

SAP S/4HANA Cloud Public Edition

1. Create an Enterprise Project using the Project Control – Enterprise Projects (F3215) application.

2. Create a budget document for the project using the Manage Budget Documents – Projects (F5342) application.

3. In the Budget Item section, maintain a G/L account in the Account Number field and save the budget document.

4. Release the project using the Project Planning (F3822) application.

5. Create a Purchase Order with Account Assignment Category “P” (Project) referencing the WBS element.

Scenario 1 – Same G/L Account Used

1. Maintain the same G/L account in the Purchase Order that was used in the budget document.

Result (Standard System Behavior):

• The commitment cost is recorded for the WBS element.

• After Goods Receipt, the actual cost is recorded.

• The Project Budget Report – Overview (F3377) shows the budget consumption and available budget.

Scenario 2 – Different G/L Account Used

1. Maintain a different G/L account in the Purchase Order than the one used in the budget document.

Result (Standard System Behavior):

• The system does not assign commitment costs to the budget item.

• The system does not assign actual costs to the budget item.

• The Project Budget Report – Overview (F3377) shows only the total budget without consumption.

• The observed behavior occurs because project budgeting in SAP S/4HANA Cloud Public Edition is controlled based on the combination of WBS Element and Account Number.
• When procurement postings use a different G/L account than the budget account, the system cannot match the commitment or actual cost to the corresponding budget item.
• The Account Number field is mandatory in Manage Budget Documents – Projects (F5342) because it is required for account-based budget control.

The system is working as designed. In project budgeting, the budget is controlled based on the combination of WBS element and Account Number (G/L account). Therefore, when a Purchase Order uses a different G/L account than the one defined in the budget document, the system cannot match the commitment or actual cost to the corresponding budget line.

As a result, the commitment and actual values are not reflected in the Project Budget Report – Overview (F3377) when the account numbers differ.

Regarding the request to make the Account Number field optional, this field is mandatory by standard application logic in SAP S/4HANA Cloud Public Edition, and currently there is no available configuration, SSCUI, or released BAdI to change this behavior.

For the second request related to adding additional selection fields (such as WBS element, Project, or Period) in the Manage Budget Documents – Projects app, the available filters are defined by the standard application design and cannot be extended via key user extensibility.

SAP Help Portal - Key User Extensibility

If these capabilities are required, we recommend submitting an enhancement request through the SAP Customer Influence Portal so that SAP Product Management can evaluate it for future releases.

Refer to: Key User Extensibility

account number, mandatory field, manage budget documents, projects, f5342, project budgeting, wbs element, account-based budget control, purchase order, gl account, budget consumption, project budget report, f3377, sscui, badi, key user extensibility , KBA , PPM-SCL-STR , Project Structure (Public Cloud) , Problem