Do you have any question about this error?
Message type: E = Error
Message class: KN - Reporting for Costing
Message number: 421
Message text: The orders do not belong to the same company code
You are attempting to access a report for a production campaign to
which manufacturing orders are assigned. However, these orders do not
all belong to the company code to which the campaign is assigned. It is
therefore not possible to execute the report.
Check the orders assigned to the production campaign. If you want to
use the cost reports of the information system of Product Cost
Controlling, all manufacturing orders assigned to the campaign must be
in the company code to which the campaign itself is assigned.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message KN421 indicates that the orders you are trying to process do not belong to the same company code. This typically occurs in scenarios where you are attempting to perform a transaction that involves multiple orders, such as creating a billing document or processing a delivery, and the orders are associated with different company codes.
Cause:
- Different Company Codes: The primary cause of this error is that the sales orders or delivery documents you are trying to process are linked to different company codes. In SAP, each company code represents a separate legal entity, and transactions involving multiple company codes are not allowed in certain processes.
- Incorrect Order Selection: You may have inadvertently selected orders from different company codes when trying to execute a transaction.
- Configuration Issues: There may be configuration settings in your SAP system that restrict transactions across different company codes.
Solution:
- Check Company Codes: Verify the company codes associated with the sales orders or delivery documents you are trying to process. You can do this by checking the order details in the sales order or delivery document.
- Select Orders from the Same Company Code: Ensure that you are only selecting orders that belong to the same company code for the transaction you are attempting to execute.
- Review Transaction Logic: If you are using a custom program or transaction, review the logic to ensure it is correctly handling orders from the same company code.
- Consult with SAP Support: If you believe the error is occurring incorrectly or if you need to process transactions across different company codes, consult with your SAP support team or refer to SAP documentation for potential configuration changes.
Related Information:
By following these steps, you should be able to resolve the KN421 error and successfully process your transactions.
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 | ![]() |
![]() |
KN420 Master data cannot be accessed from current cursor position
Self-Explanatory Message Since SAP believes that this specific error message is ...
KN419 Entry for table field & already exists
What causes this issue? You are attempting to select a data field that you want...
KN422 Material & is not a co-product
Self-Explanatory Message Since SAP believes that this specific error message is ...
KN423 New fields added to the summarization levels
What causes this issue? New fields are available for the drilldown reports, for...
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.