Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: GC - Error Messages for Consolidation/Extended General Ledger
Message number: 730
Message text: Company & not maintained
The given company is not in the company master data.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Please check your entry or create this company.
Error message extract from SAP system. Copyright SAP SE.
GC730
- Company & not maintained ?The SAP error message GC730, which states "Company & not maintained," typically occurs when there is an attempt to access or process data related to a company code that has not been properly configured or maintained in the system. This error can arise in various contexts, such as during financial transactions, reporting, or when trying to execute certain functions that require company code information.
Cause:
- Missing Company Code Configuration: The company code in question has not been created or is not properly configured in the SAP system.
- Incorrect Company Code Assignment: The company code may not be assigned to the relevant organizational units or may not be linked to the necessary master data.
- Authorization Issues: The user may not have the necessary authorizations to access the company code.
- Data Inconsistencies: There may be inconsistencies in the master data or configuration settings related to the company code.
Solution:
Check Company Code Configuration:
- Go to the SAP transaction code
OBY6
(orSPRO
-> Financial Accounting -> General Settings -> Company Code -> Define Company Code) to verify if the company code exists and is properly configured.- Ensure that all necessary settings (like currency, fiscal year variant, etc.) are maintained.
Assign Company Code:
- If the company code is missing, create it using the same transaction (
OBY6
).- Ensure that the company code is assigned to the relevant organizational units, such as controlling areas or business areas.
Review Master Data:
- Check if the master data (like vendors, customers, or GL accounts) is correctly linked to the company code.
- Use transaction codes like
FK01
(Create Vendor),FD01
(Create Customer), orFS00
(Create GL Account) to verify the assignments.Authorization Check:
- Ensure that the user has the necessary authorizations to access the company code. This can be checked in the user roles and profiles assigned to the user.
Consult with SAP Basis or Functional Team:
- If the issue persists, consult with your SAP Basis or functional team to check for any underlying issues or inconsistencies in the system.
Related Information:
OBY6
, SPRO
, FS00
, FK01
, and FD01
.By following these steps, you should be able to resolve the GC730 error and ensure that the company code is properly maintained in your SAP system.
Get instant SAP help. Sign up for our Free Essentials Plan.
GC729
According to co. master record, roll-up not allowed for & and version &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GC728
Data transfer method for company &1 not equal to periodic extract.
What causes this issue? Periodic extract from FI or step consolidation was not set as a data transfer method for the company.How to fix this error? ...
GC731
Transaction not allowed according to company (trans = &)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GC732
Company & not maintained
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.