Do you have any question about this error?
Message type: E = Error
Message class: MG - Batch input: material master
Message number: 120
Message text: Transaction &: company code copied from 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.
MG120
- Transaction &: company code copied from plant ?The SAP error message MG120 ("Transaction &: company code copied from plant") typically occurs in the context of material management and inventory management when there is an issue related to the configuration of a plant and its associated company code. This error indicates that the system is trying to perform a transaction that requires a valid company code, but it has encountered a problem with the plant's configuration.
Cause:
- Missing or Incorrect Configuration: The plant may not be properly assigned to a company code in the system. This can happen if the plant was created without linking it to a company code or if there are inconsistencies in the configuration.
- Data Inconsistency: There may be inconsistencies in the master data related to the plant or company code, such as missing entries in the relevant tables.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the plant or company code, leading to this error.
Solution:
Check Plant Configuration:
- Go to the transaction code
OX10
(orSPRO
-> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check plant).- Ensure that the plant is correctly assigned to the appropriate company code.
Verify Master Data:
- Check the material master data for the specific plant and ensure that all necessary fields are filled out correctly.
- Use transaction code
MM03
to view the material master and confirm that the plant and company code are correctly linked.Review Company Code Settings:
- Ensure that the company code is active and properly configured. You can check this in transaction code
OBY6
(orSPRO
-> Financial Accounting -> Financial Accounting Global Settings -> Company Code -> Edit, Copy, Delete, Check Company Code).Check User Authorizations:
- Ensure that the user has the necessary authorizations to perform transactions related to the plant and company code. This can be checked with the help of your SAP security team.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that resolve known issues.
Testing:
- After making the necessary changes, perform a test transaction to ensure that the error has been resolved.
Related Information:
MM01
(Create Material), MM02
(Change Material), and MM03
(Display Material) for managing material master data.If the problem persists after following these steps, it may be necessary to involve your SAP Basis or technical team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
MG119
Transaction &: not possible to adopt forecast values
What causes this issue? You have entered forecast values although the chosen forecast model does not allow the specification of forecast values.Syste...
MG118
Transaction &: valuation type reset (new material created)
What causes this issue? You cannot assign the material to a valuation type when you create its material master record. The valuation category must fi...
MG121
Transaction &: plant & is not defined
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MG122
Transaction &: company code reset (not relevant)
What causes this issue? Since valuation is at company code level, the company code specified is not relevant.System Response The system issues an er...
Click on this link to search all SAP messages.