Do you have any question about this error?
Message type: E = Error
Message class: GZ - Message class for FI-LC
Message number: 404
Message text: Company & not maintained
Company &V1& does not exist.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Enter another company or create the new company
&V1&.
<DS:TRAN.GC11>Create company</>
Error message extract from SAP system. Copyright SAP SE.
GZ404
- Company & not maintained ?The SAP error message GZ404, which states "Company & not maintained," typically occurs when there is an issue with the configuration of the company code in the SAP system. This error can arise in various contexts, such as during the posting of transactions, when trying to access certain reports, or when executing specific functions that require company code information.
Cause:
- Missing Company Code Configuration: The company code may not be properly defined or maintained in the system.
- Incorrect Company Code Assignment: The company code might not be assigned to the relevant organizational units or 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 transaction code
OBY6
(orSPRO
-> Financial Accounting -> General Ledger -> Master Data -> Edit Company Code Data).- Ensure that the company code in question is properly defined and all necessary details are filled out.
Verify Company Code Assignment:
- Check if the company code is assigned to the relevant organizational units (like controlling area, business area, etc.).
- Use transaction code
OX02
to verify the assignment of the company code.Review User Authorizations:
- Ensure that the user has the necessary authorizations to access the company code. This can be checked in transaction
SU53
after the error occurs or by reviewing the user's role assignments.Check Master Data:
- If the error occurs during a specific transaction, check the master data (like vendor, customer, or material) to ensure that the company code is correctly assigned.
Consult with SAP Basis or Functional Team:
- If the issue persists, it may be necessary to consult with your SAP Basis or functional team to investigate further, especially if there are underlying configuration issues.
Related Information:
OBY6
, OX02
, SU53
, and SPRO
for configuration and troubleshooting.By following these steps, you should be able to identify and resolve the issue related to the GZ404 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
GZ403
In year &, company & in invest. version & does not belong to subgroup &.
What causes this issue? The four entries 'subgroup', 'company', 'version' and 'fiscal year' are not compatibl...
GZ402
Subgroup & not maintained
What causes this issue? Subgroup &V1& does not exist.System Response The system issues an error message and will not allow you to continue w...
GZ406
In year &, no companies belong to subgroup & in version &.
What causes this issue? The entries for 'subgroup', 'version' and 'fiscal year' are not compatible.System Response The...
GZ407
Error in year: The lower limit (&) is greater than the upper limit (&) !
What causes this issue? The lower limit &V1& for the year is greater than the upper limit &V2&.System Response The system issues an ...
Click on this link to search all SAP messages.