GJ911 - Corporate RI & from Table T8JZ Must Be Non-Billable (Check Table T8JJ).

Start a new search

SAP Error Message - Details

  • Message type: E = Error

  • Message class: GJ - Joint Venture Accounting

  • Message number: 911

  • Message text: Corporate RI & from Table T8JZ Must Be Non-Billable (Check Table T8JJ).

  • Show details Hide details
  • What causes this issue?

    Corporate recovery indicator from table T8JZ (joint venture
    configuation
    table) must be non-billable.

    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?

    Maintain table T8JJ (recovery indicator) and set the corporate RI to
    non-billable, or change the RI in table T8JZ to a non-billable RI.

    Error message extract from SAP system. Copyright SAP SE.


AnswerBot

  • What is the cause and solution for SAP error message GJ911 - Corporate RI & from Table T8JZ Must Be Non-Billable (Check Table T8JJ). ?

    The SAP error message GJ911 indicates that there is an issue with the configuration of the Corporate Revenue Item (RI) in the context of the Joint Venture Accounting (JVA) module. Specifically, it suggests that the Corporate RI must be non-billable according to the settings in the relevant configuration tables.

    Cause:

    The error occurs when there is a mismatch in the configuration settings for the Corporate Revenue Item (RI) in the system. The system checks the entries in table T8JZ (which contains the Corporate RIs) and table T8JJ (which defines the characteristics of these RIs). If the Corporate RI is set to be billable when it should not be, the system will trigger this error.

    Solution:

    To resolve this error, you need to ensure that the Corporate RI is correctly configured as non-billable. Here are the steps to do this:

    1. Check Table T8JZ:

      • Go to transaction SE16 or SE16N in SAP.
      • Enter table name T8JZ and execute.
      • Look for the Corporate RI that is causing the error and check its settings.
    2. Check Table T8JJ:

      • Similarly, check table T8JJ to see the characteristics of the Corporate RI.
      • Ensure that the RI is marked as non-billable.
    3. Adjust Configuration:

      • If you find that the Corporate RI is incorrectly set as billable, you will need to change its configuration.
      • This can typically be done in the JVA configuration settings (transaction SPRO) under the Joint Venture Accounting section.
    4. Testing:

      • After making the necessary changes, test the transaction that was causing the error to ensure that it no longer occurs.
    5. Consult Documentation:

      • If you are unsure about the configuration settings, refer to the SAP documentation or consult with your SAP functional consultant for guidance.

    Related Information:

    • Transaction Codes: SE16, SE16N (for table checks), SPRO (for configuration).
    • Tables: T8JZ (Corporate Revenue Items), T8JJ (Characteristics of Revenue Items).
    • SAP Notes: Check for any relevant SAP Notes that might provide additional insights or updates related to this error message.

    By following these steps, you should be able to resolve the GJ911 error and ensure that your Corporate RI settings are correctly configured.

  • AnswerBot is an artificial intelligence solution provided by tomco.ai.
    Disclaimer

Related SAP Error Messages

Click the links below to see the following related messages:


SAP messages fall into 3 different categories: Error messages (message type = E), Warnings (W) or Informational (I) messages.

An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.

Click on this link to search all SAP messages.