Do you have any question about this error?
Message type: E = Error
Message class: KQ - Error Messages for Customizing Product Costing
Message number: 287
Message text: Plan version and relevance to settlement only relevant with plan RA
You have entered a <DS:GLOS.3526B5EDAFAB52B9E10000009B38F974>plan
version</>, or you have selected the indicator <LS>Version relevant to
settlement</> in planned results analysis.
However, you have <ZH>not</> indicated that this results analysis
version is intended for actual results analysis and planned results
analysis by selecting
<DS:DE.KKA_VERW_C>Actual and plan RA</>.
Instead, you have selected <LS>Actual RA</> or <LS>Simulate actual w/
plan</>.
When you select Enter, the plan version entered or the indicator
<LS>Version relevant to settlement</> is deselected.
If applicable, select <LS>Actual and plan RA</> to indicate that the
results analysis version is suitable for planned results analysis.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
KQ287
- Plan version and relevance to settlement only relevant with plan RA ?The SAP error message KQ287 indicates that there is an issue with the plan version and its relevance to settlement in the context of a specific planning area, typically related to cost planning or profitability analysis. This error usually arises when the system is trying to process a settlement for a plan version that is not configured correctly or is not relevant for the settlement process.
Cause:
- Incorrect Plan Version: The plan version being used may not be set up for settlement. In SAP, certain plan versions are designated for specific purposes, and if the version is not marked as relevant for settlement, this error will occur.
- Configuration Issues: The configuration settings in the controlling area or the specific planning area may not align with the requirements for settlement.
- Data Inconsistencies: There may be inconsistencies in the data related to the plan version, such as missing or incorrect entries.
Solution:
Check Plan Version Settings:
- Go to the configuration settings for the plan version in SAP (Transaction code: OKKP or similar).
- Ensure that the plan version you are using is marked as relevant for settlement.
Use the Correct Plan Version:
- If the current plan version is not relevant for settlement, switch to a plan version that is designated for this purpose (usually a version marked as "RA" for relevant for settlement).
Review Configuration:
- Check the configuration of the controlling area and ensure that all settings related to planning and settlement are correctly defined.
- Ensure that the planning area is set up to allow for the necessary settlements.
Data Validation:
- Validate the data associated with the plan version to ensure there are no inconsistencies or missing entries that could be causing the error.
Consult Documentation:
- Refer to SAP documentation or help resources for specific details on the configuration of plan versions and their relevance to settlement.
Related Information:
By following these steps, you should be able to resolve the KQ287 error and ensure that your plan version is correctly set up for settlement processes in SAP.
Get instant SAP help. Start your 7-day free trial now.
KQ286
WIP at target costs only allowed for operational RA version in legal val.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
KQ285
Valuation only at totals level if profit basis is standard price
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
KQ288
Enter a plan version for planned results analysis
What causes this issue? You have selected the indicator <DS:DE.KKA_VERW_C>Actual and plan RA</>. If you do this, you must enter a plan ve...
KQ289
Version &1 in CO area &2 not intended for use as plan version
What causes this issue? In the central version maintenance, version &V1& in controlling area &V2& is not defined as a <DS:GLOS.352...
Click on this link to search all SAP messages.