How To Fix GJ892 - Cutback Can not Post to Intercomp. Acct. & (Wrong Tax Code Req.).

SAP Error Message - Details

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 892

• Message text: Cutback Can not Post to Intercomp. Acct. & (Wrong Tax Code Req.).

What causes this issue?

Cutback tries to do a intercompany posting in company code &V2& to
account &V1& which requires a tax code that is not a input tax code.
This is not possible.
Accounts used by cutback must either use no tax code or an input tax
code.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If you want to run cutback with the selected account,
<DS:TRAN.FS02>change</> the allowed tax codes in the account master
data.
Otherwise, <DS:TRAN.GJ26>change</> the intercompany cutback account
for company code &V2&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GJ892 - Cutback Can not Post to Intercomp. Acct. & (Wrong Tax Code Req.). ?

  The SAP error message GJ892, which states "Cutback Cannot Post to Intercompany Account & (Wrong Tax Code Req.)," typically occurs in the context of intercompany transactions in SAP, particularly in the area of financial accounting and controlling. This error can arise due to several reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  
  Intercompany Account Configuration: The intercompany account may not be properly configured in the system. This includes settings related to account determination for intercompany transactions.
  
  
  Tax Code Issues: The tax code used in the transaction may not be valid for intercompany postings. This can happen if the tax code is not set up correctly for the specific transaction type or if it is not allowed for intercompany transactions.
  
  
  Cutback Configuration: If the transaction involves cutback accounting, there may be issues with how cutback is configured in the system. This could include missing or incorrect settings in the cutback configuration.
  
  
  Posting Period: The posting period may be closed, preventing any postings to the intercompany account.
  
  
  Document Type: The document type used for the transaction may not be allowed for intercompany postings.
  
  
  Solutions:
  
  
  Check Intercompany Account Configuration:
  
  Verify that the intercompany accounts are correctly set up in the system. This includes checking the account determination settings in the configuration.
  
  
  
  Review Tax Code:
  
  Ensure that the tax code used in the transaction is valid for intercompany postings. You may need to create or modify the tax code to allow it for intercompany transactions.
  
  
  
  Examine Cutback Configuration:
  
  Review the cutback configuration settings to ensure they are correctly set up. This may involve checking the cutback rules and ensuring they align with the intercompany transaction requirements.
  
  
  
  Check Posting Period:
  
  Confirm that the posting period is open for the transaction date. If the period is closed, you may need to open it or post the transaction in an open period.
  
  
  
  Document Type Validation:
  
  Ensure that the document type used for the transaction is configured to allow intercompany postings. You may need to adjust the settings for the document type.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes or documentation that may address this specific error message. SAP frequently updates its knowledge base with solutions for common issues.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBY6 (for intercompany settings) or OBC4 (for tax code configuration) to access the relevant configuration areas.
  SAP Support: If the issue persists after checking the above areas, consider reaching out to SAP support for further assistance. They can provide more specific guidance based on your system configuration and version.
  Testing: After making any changes, conduct thorough testing to ensure that the issue is resolved and that intercompany transactions can be processed without errors.
  
  By following these steps, you should be able to identify the root cause of the GJ892 error and implement the necessary changes to resolve it.