Do you have any question about this error?
Message type: E = Error
Message class: KN - Reporting for Costing
Message number: 347
Message text: Company code must come before the plant
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
The SAP error message KN347 ("Company code must come before the plant") typically occurs when there is an issue with the sequence of data entry in the SAP system, particularly in the context of master data creation or maintenance for materials, vendors, or customers. This error indicates that the system expects the company code to be specified before the plant in the relevant transaction.
Cause:
- Incorrect Sequence of Data Entry: The error usually arises when the user tries to enter or save data related to a plant without first specifying the associated company code.
- Configuration Issues: There may be configuration settings in the SAP system that enforce a specific order of data entry.
- Missing Master Data: If the company code or plant is not properly defined in the system, it can lead to this error.
Solution:
To resolve the KN347 error, follow these steps:
Check Data Entry Sequence:
- Ensure that you are entering the company code before the plant in the relevant transaction. For example, if you are creating or changing a material master, make sure to select the company code first.
Verify Master Data:
- Check if the company code and plant are correctly defined in the system. You can do this by navigating to the relevant master data transaction (e.g., MM01 for material master, XK01 for vendor master, etc.) and verifying the entries.
Review Configuration:
- If you have access to configuration settings, review the settings related to the company code and plant in the relevant modules (e.g., MM, SD). Ensure that the settings are correctly configured to allow for the proper sequence of data entry.
Consult Documentation:
- Refer to SAP documentation or help resources for specific guidance on the transaction you are working with. This can provide insights into the expected data entry sequence.
Seek Help from SAP Support:
- If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP Notes for any known issues or patches related to this error.
Related Information:
By following these steps, you should be able to resolve the KN347 error and successfully complete your data entry in SAP.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
KN346 There are no cost component groups in this currency
What causes this issue? The system cannot find any data for the cost component ...
KN345 The node could not be expanded further because of an error
What causes this issue? An error occurred while reading the next hierachy level...
KN348 Setting for user was saved
Self-Explanatory Message Since SAP believes that this specific error message is ...
KN349 No suitable data from split available
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.