How To Fix GJ919 - Recovery Indicators Are Inconsistent Between & and & , P.O. & &

GJ919 - Overview

• Message type: E = Error

• Message class: GJ - Joint Venture Accounting

• Message number: 919

• Message text: Recovery Indicators Are Inconsistent Between & and & , P.O. & &

What causes this issue?

The recovery indicator for the receipt of a component should be the
same as the recovery indicator for the receipt of the goods from the
vendor. It is possible that the goods receipt from the vendor is
billable while the receipt of the component is non-billable. This
would result in the venture receiving the component not reimbursing the
venture issuing the component.
Currently, the recovery indicators are different for the goods from the
vendor, &V1&, and the component, &V2&, on purchase order &V3&, item
&V4&.

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?

Please check that you have made a correct entry.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GJ919 - Recovery Indicators Are Inconsistent Between & and & , P.O. & & ?

  The SAP error message GJ919 indicates that there is an inconsistency in the recovery indicators between two objects, typically related to a Purchase Order (P.O.) in the context of SAP's Project System (PS) or Controlling (CO) modules. This error often arises when there are discrepancies in the data related to project costs, budget, or other financial indicators.
  
  Cause:
  
  Inconsistent Recovery Indicators: The recovery indicators for the specified objects (e.g., WBS elements, internal orders, or cost centers) do not match. This can happen if one object is set to recover costs in a certain way (e.g., through billing) while the other is not.
  Data Entry Errors: Manual data entry errors or incorrect configuration settings can lead to inconsistencies.
  Changes in Configuration: If there have been recent changes in the project structure or configuration settings, it may lead to inconsistencies.
  Incomplete Data: Missing or incomplete data in the relevant master records can also trigger this error.
  
  
  Solution:
  
  Check Recovery