Do you have any question about this error?
Message type: E = Error
Message class: GJ - Joint Venture Accounting
Message number: 888
Message text: Account & for Intercompany & Does not Exist.
Cutback tries to do a intercompany posting in company code &V2& to the
account &V1& that does not exist.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
<DS:TRAN.FS01>Create</> the account in company code &V2& or
<DS:TRAN.GJ26>change</> the intercompany account mapping for cutback.
Error message extract from SAP system. Copyright SAP SE.
GJ888
- Account & for Intercompany & Does not Exist. ?The SAP error message GJ888 typically indicates that there is an issue related to intercompany transactions, specifically that an account does not exist in the context of the transaction being processed. This error can arise in various scenarios, particularly in financial accounting and controlling modules when dealing with intercompany postings.
Cause:
- Missing Account: The account specified in the transaction does not exist in the chart of accounts for the company code involved in the intercompany transaction.
- Incorrect Configuration: The intercompany settings may not be properly configured, leading to the system not recognizing the account.
- Data Entry Error: There may be a typo or incorrect account number entered in the transaction.
- Inactive Account: The account might exist but is inactive or not available for the specific transaction type.
- Missing Master Data: The necessary master data for the intercompany transaction may not be set up correctly.
Solution:
- Verify Account Existence: Check if the account number mentioned in the error message exists in the relevant chart of accounts for the company code. You can do this by navigating to the account master data in SAP.
- Check Configuration: Ensure that the intercompany settings are correctly configured in the system. This includes checking the configuration for intercompany accounts in the Financial Accounting (FI) module.
- Correct Data Entry: Review the transaction entry for any typos or incorrect account numbers. Make sure that the correct account is being used for the intercompany transaction.
- Activate Account: If the account exists but is inactive, you may need to activate it or ensure it is available for the type of transaction you are processing.
- Review Master Data: Ensure that all necessary master data for the intercompany transaction is set up correctly, including vendor/customer master records and any relevant intercompany agreements.
Related Information:
FS00
to view or edit the account master data, and OBY6
to check the company code settings.If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in financial accounting and intercompany processes.
Get instant SAP help. Start your 7-day free trial now.
GJ887
Currency conversion & to & with type of rate & does not exist.
What causes this issue? Cutback tries to post a document for an intercompany partner (company &V4&) with local currency &V2& for the ...
GJ886
Field 'Recovery Indicator' not Open for Input for Account &
What causes this issue? Cutback tries to post to account &V1& which does not allow the manual input of the field 'Recovery indicator...
GJ889
Cutback Cannot Post to Intercomp. Acct. & (Reconciliation Acct.).
What causes this issue? Cutback tries to do a intercompany posting in company code &V2& to account &V1& which is a reconciliation acc...
GJ890
Cutback Can not Post to Intercomp. Acct. & (for Autom. Post. only).
What causes this issue? Cutback tries to do a intercompany posting in company code &V2& to account &V1& which is only allowed for aut...
Click on this link to search all SAP messages.