Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix VVSCCHECK118 - &1: Cannot determine G/L account for external tax line


SAP Error Message - Details

  • Message type: E = Error

  • Message class: VVSCCHECK - Payment Plan: Checks

  • Message number: 118

  • Message text: &1: Cannot determine G/L account for external tax line

  • Show details Hide details
  • What causes this issue?

    You want to create externally calculated tax lines for a payment plan
    item.
    You are <ZH>not</> able to determine the general ledger account for the
    tax data with position type &V4&.
    Determine the general ledger account using posting area 0010, which is
    used for sales taxes.
    The following data is included in the posting area:
    Chart of Accounts: &V2&
    Company Code / Other Tax Code &V3&
    Procedure: &V4&

    System Response

    *********************************************************************

    How to fix this error?

    Check your entries for the company code, tax code, and transaction.
    Check Customizing for posting area 0010. In <LS>Contract Accounts
    Receivable and Payable </>, choose <ZK>Basic Functions > Postings and
    Documents -> Document -> Define Account Assignments for Automatic
    Postings -> Automatic G/L Account Determination ->
    <DS:SIMG._FICABFDP_FQZ8>Define Accounts for Sales/Purchase Tax</></>.

    Procedure for System Administrators

    *********************************************************************
    *********************************************************************

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message VVSCCHECK118 - &1: Cannot determine G/L account for external tax line ?

    The SAP error message VVSCCHECK118 indicates that the system is unable to determine a General Ledger (G/L) account for an external tax line during the processing of a transaction. This typically occurs in the context of tax calculations and postings, particularly when dealing with external tax providers or tax codes that require specific G/L account assignments.

    Causes:

    1. Missing G/L Account Assignment: The tax code used in the transaction may not have a corresponding G/L account assigned in the configuration.
    2. Incorrect Tax Code: The tax code may be incorrectly configured or not set up for the specific transaction type.
    3. Tax Configuration Issues: There may be issues in the tax configuration settings in the SAP system, such as missing or incorrect settings in the tax procedure.
    4. External Tax Provider Issues: If you are using an external tax calculation service, there may be issues with the integration or configuration of that service.
    5. Document Type Restrictions: Certain document types may not be allowed to use specific tax codes or G/L accounts.

    Solutions:

    1. Check Tax Code Configuration:

      • Go to the transaction code OB40 (for tax codes) and verify that the tax code used in the transaction has a valid G/L account assigned.
      • Ensure that the tax code is correctly configured for the relevant country and transaction type.
    2. Review Tax Procedure:

      • Check the tax procedure assigned to the company code in transaction code OBYZ. Ensure that the tax procedure is correctly set up and includes the necessary tax codes.
    3. Assign G/L Accounts:

      • If the G/L account is missing, you can assign it in the configuration settings for the tax code. This can typically be done in the transaction code OB40 or through the relevant configuration path in SPRO.
    4. Check External Tax Provider Settings:

      • If you are using an external tax provider, ensure that the integration is correctly set up and that the provider is configured to return the correct G/L accounts for the tax lines.
    5. Test with Different Document Types:

      • If applicable, try processing the transaction with a different document type to see if the issue persists. This can help identify if the problem is related to specific document types.
    6. Consult SAP Notes:

      • Check for any relevant SAP Notes that may address this specific error message. SAP frequently updates its knowledge base with solutions for known issues.
    7. Debugging:

      • If the issue persists, consider debugging the transaction to identify where the failure occurs in the code. This may require assistance from a technical consultant.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as OB40 (Tax Codes), OBYZ (Tax Procedures), and SPRO (SAP Reference IMG) for configuration.
    • Documentation: Review SAP documentation related to tax configuration and G/L account assignments for a deeper understanding of the setup.
    • Support: If you are unable to resolve the issue, consider reaching out to SAP support or your internal SAP team for further assistance.

    By following these steps, you should be able to identify and resolve the cause of the VVSCCHECK118 error in your SAP system.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant