Do you have any question about this error?
Message type: E = Error
Message class: GP - FI-SL and CO planning
Message number: 589
Message text: Company code & is no longer supported
Company code &V1& is assigned in the master record of a CO object.
However, no entry exists for this company code in the appropriate
master table.
The system cancels processing.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
GP589
- Company code & is no longer supported ?The SAP error message GP589 indicates that a specific company code is no longer supported in the system. This typically occurs when the company code has been flagged for deletion or is not active in the current configuration of the SAP system. Here’s a breakdown of the cause, potential solutions, and related information:
Cause:
- Company Code Deactivation: The company code may have been deactivated or flagged for deletion in the system.
- Configuration Changes: Changes in the configuration settings or updates to the system may have led to the company code being unsupported.
- Data Migration: If data migration or system upgrades have occurred, certain company codes may not have been migrated properly or may have been excluded.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the company code, leading to the perception that it is unsupported.
Solution:
Check Company Code Status:
- Go to the transaction code
OBY6
(orSPRO
-> Financial Accounting -> General Ledger Accounting -> Master Data -> Edit Company Code Data) to check the status of the company code.- Ensure that the company code is active and not flagged for deletion.
Re-activate Company Code:
- If the company code is inactive, you may need to reactivate it. This typically requires appropriate authorizations and may involve consulting with your SAP administrator or finance team.
Review Configuration:
- Check if there have been any recent changes in the configuration that might have affected the company code. This may involve reviewing transport requests or system updates.
User Authorizations:
- Ensure that the user has the necessary authorizations to access the company code. This can be checked in the user roles and profiles.
Consult Documentation:
- Review SAP documentation or notes related to the specific version of SAP you are using, as there may be specific guidelines or patches available.
Contact SAP Support:
- If the issue persists, consider reaching out to SAP support for assistance. They can provide insights based on the specific version and configuration of your SAP system.
Related Information:
OBY6
, SPRO
, and SE16
for data checks.SU01
to ensure proper access rights.By following these steps, you should be able to identify the cause of the GP589 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
GP588
Entry for & not found in internal table &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GP587
Credit records are missing for cost center/activitiy type &/&
What causes this issue? In activity type planning for cost center/activity type &V1&/&V2&, the activity prices or the activity price ...
GP590
The master record for allocation cost element & has not been found
What causes this issue? You would like to plan an activity input from the sending object with the object number &V2&. For this object, the a...
GP591
The master record for allocation cost element & was not found
What causes this issue? The allocation cost element &V1& has been entered in the activity type &V2&. However, a valid master record f...
Click on this link to search all SAP messages.