How To Fix EDOCUMENT_GR012 - Invoice type not found for &1/&2/&3

SAP Error Message - Details

• Message type: E = Error

• Message class: EDOCUMENT_GR - Messages for eDocument Greece

• Message number: 012

• Message text: Invoice type not found for &1/&2/&3

What causes this issue?

Invoice type could not be determined for Document Type, Print Task Code
and Country Type.
Country type possible values<(>,<)>
-,,,,,,Domestic
X,,,,,,EU
' ',,,,,,Non-EU

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?

Check Invoice type determination in the customizing view.

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 EDOCUMENT_GR012 - Invoice type not found for &1/&2/&3 ?

  The SAP error message EDOCUMENT_GR012 with the description "Invoice type not found for &1/&2/&3" typically occurs in the context of electronic invoicing or document processing within the SAP system. This error indicates that the system is unable to find a specific invoice type based on the parameters provided (which are represented by &1, &2, and &3).
  Causes:
  
  Missing Configuration: The invoice type may not be configured in the system. This can happen if the necessary settings for electronic invoicing or document types have not been completed.
  Incorrect Parameters: The parameters being passed to the system (like company code, document type, or other identifiers) may be incorrect or not matching any existing configuration.
  Custom Development Issues: If there are custom developments or enhancements in the invoicing process, they may not be correctly handling the invoice types.
  Transport Issues: If the configuration was recently transported from another system, it may not have been transported correctly, leading to missing invoice types.
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the relevant configuration settings in SAP (usually in SPRO) and verify that the invoice types are correctly defined for the relevant company code and document type.
  Ensure that the necessary settings for electronic invoicing are in place.
  
  
  
  Verify Parameters:
  
  Check the parameters being passed to the system when the error occurs. Ensure that they correspond to valid and existing invoice types in the system.
  You can use transaction codes like FB60 (Enter Incoming Invoice) or MIRO (Enter Incoming Invoice) to test with different parameters.
  
  
  
  Review Custom Code:
  
  If there are any custom developments related to the invoicing process, review the code to ensure it correctly handles the invoice types and does not introduce any errors.
  
  
  
  Transport Check:
  
  If the issue arose after a transport, check the transport logs to ensure that all necessary objects were transported correctly. You may need to re-transport or manually configure the missing settings.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to electronic invoicing and the specific error message for any additional guidance or known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, especially if this is a production issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO for configuration, SE80 for development, and SE11 for data dictionary checks.
  SAP Notes: Search for SAP Notes related to electronic invoicing and the specific error message for any patches or updates that may resolve the issue.
  Community Forums: Check SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.