Do you have any question about this error?
Message type: E = Error
Message class: KE -
Message number: 474
Message text: Plan/actual indicator in external file does not match
The value &V1& in the field 'PLIKZ' is not allowed in the internal
structure. If you import the file as actual data, the field must either
be blank or contain the value "0". If you import the file as plan data,
the field must either be blank or contain the value "1".
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If the field 'PLIKZ' is not filled from the external structure (that is,
if it remains blank), you can import the file as either plan data or
actual data. However, if the field is filled ('0' for actual or '1' for
plan), you can only import the file for that type of data.
Field 'PLIKZ' was assigned to a field in the external structure.
There are two ways to correct the error:
You can delete the assignment for this field. Then you can import
either plan or actual data from the external file.
Or you can make sure that all the data records in the external file
have the correct plan/actual indicator.
To see how much data was imported before the error occurred, see the
management table for external data transfers (transaction SM30,
view V_T258E)
Error message extract from SAP system. Copyright SAP SE.
KE474
- Plan/actual indicator in external file does not match ?The SAP error message KE474, which states "Plan/actual indicator in external file does not match," typically occurs during the process of uploading or processing external data files related to cost center accounting or profitability analysis. This error indicates that there is a mismatch between the plan/actual indicators defined in the external file and those expected by the SAP system.
Cause:
- Mismatch in Indicators: The plan/actual indicators in the external file do not correspond to the indicators defined in the SAP system. For example, if the external file has a different code or value for the plan/actual indicator than what is configured in SAP, this error will occur.
- Incorrect File Format: The external file may not be formatted correctly, leading to misinterpretation of the data by SAP.
- Data Entry Errors: There may be typographical errors or incorrect values in the external file that do not match the expected values in SAP.
- Configuration Issues: The configuration settings in SAP for plan/actual indicators may not be aligned with the data being uploaded.
Solution:
- Check External File: Review the external file to ensure that the plan/actual indicators are correctly defined and match the expected values in SAP. Make sure that the codes used in the file are valid and recognized by the SAP system.
- Validate File Format: Ensure that the external file adheres to the required format and structure as specified by SAP. This includes checking delimiters, data types, and overall layout.
- Correct Data: If there are any discrepancies or errors in the external file, correct them and attempt the upload again.
- Review SAP Configuration: Check the configuration settings in SAP for plan/actual indicators. Ensure that they are set up correctly and that they match the values being used in the external file.
- Consult Documentation: Refer to SAP documentation or help resources for specific details on the expected values for plan/actual indicators and how to configure them properly.
Related Information:
KE4S
(for planning) or KE5S
(for actuals) to review or adjust settings related to cost center accounting.By following these steps, you should be able to identify and resolve the KE474 error in SAP.
Get instant SAP help. Start your 7-day free trial now.
KE473
Currency type is not allowed for actual data update
What causes this issue? While updating actual data in Profitability Analysis, the system tried to read the currency information from the FI/CO docume...
KE472
Inconsistency in currency translation in Profitability Analysis
What causes this issue? While processing the reference document &v1& from the FI/CO document, line &v2&, in Profitability Analysis, t...
KE475
Inconsistency occurred during processing of FI/CO document
What causes this issue? An inconsistency was found in Profitability Analysis (CO-PA) while processing an FI/CO document. The document has the record ...
KE476
Error creating the document in Profitability Analysis
What causes this issue? An error was found while the system was processing the FI/CO document in Profitability Analysis.System Response The document...
Click on this link to search all SAP messages.