How To Fix KG825 - Plan version &1 cannot be planned for fiscal year &2

KG825 - Overview

• Message type: E = Error

• Message class: KG - CO-PA Planning

• Message number: 825

• Message text: Plan version &1 cannot be planned for fiscal year &2

What causes this issue?

The plan version &V1& that you selected is not currently allowed for
fiscal year &V2&.

System Response

The related plan values cannot be entered.

How to fix this error?

If you would still like to plan the plan values, you must unlock plan
version &V1& in the current operating concern.
You always have two options:
The entire version is locked
1) Start the transaction for version definition:
<DS:TRAN.OKEQ>Version Definition</>

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

2) Select plan version &V1&, and choose <ZH>Settings for the
Operating Concern</>. Deselect the indicator for the <ZH>Version
Locked</> field.
The version is only locked for the particular fiscal year
1) Start the transaction for view maintenance:
<DS:TRAN.SM30>Table/View
Maintenance</>
2) Enter the table name: TKEVSGJ
3) Deselect the <ZK>Version Locked</> indicator for the corresponding
fiscal year

Error message extract from SAP system. Copyright SAP SE.

KG825 - Details

• The SAP error message KG825, which states "Plan version &1 cannot be planned for fiscal year &2," typically occurs in the context of planning in SAP Controlling (CO) or SAP Financials (FI). This error indicates that the specified plan version is not available for the fiscal year you are trying to use it with.
  Causes:
  
  Plan Version Not Defined: The plan version you are trying to use may not be defined for the specified fiscal year in the planning settings.
  Fiscal Year Variant Issues: The fiscal year variant assigned to the company code or controlling area may not align with the fiscal year you are trying to plan for.
  Version Status: The plan version may be set to a status that does not allow planning (e.g., it may be locked or not activated).
  Incorrect Configuration: There may be configuration issues in the planning settings that prevent the version from being used for the specified fiscal