How To Fix GC174 - 'Document per transaction type' indicator not consistent

SAP Error Message - Details

• Message type: E = Error

• Message class: GC - Error Messages for Consolidation/Extended General Ledger

• Message number: 174

• Message text: 'Document per transaction type' indicator not consistent

What causes this issue?

More than one regulation for intercompany eliminations
have been assigned to one
document type. The 'Document per Transaction Type' indicator has
inconsistent settings among these rules.

System Response

The system will use the setting from the first rule.

How to fix this error?

Make the indicator settings consistent in all of the rules
assigned to the document type.
or
Use more document types if the different settings are required.
Assign the document type only to rules with the same indicator
settings.
Run the program once for each document type.

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

<DS:TRAN.OC27>Proceed</>
ENDIF

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GC174 - 'Document per transaction type' indicator not consistent ?

  The SAP error message GC174, which states "Document per transaction type indicator not consistent," typically arises in the context of financial document processing within SAP. This error indicates that there is an inconsistency in the configuration of the document types and their associated transaction types.
  Cause:
  The inconsistency usually occurs due to one of the following reasons:
  
  
  Configuration Issues: The document type settings in the configuration may not align with the transaction types being used. For example, a document type may be set to allow multiple documents per transaction type, while the transaction type is configured to allow only one.
  
  
  Custom Development: If there are custom developments or enhancements in the system that manipulate document types or transaction types, they may lead to inconsistencies.
  
  
  Changes in Configuration: Recent changes in the configuration settings without proper adjustments to related settings can also lead to this error.
  
  
  Solution:
  To resolve the GC174 error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the SAP Customizing Implementation Guide (SPRO).
  Navigate to Financial Accounting (New) > Financial Accounting Global Settings > Document > Document Types.
  Verify the settings for the document types and transaction types. Ensure that the "Document per transaction type" indicator is consistent across the relevant configurations.
  
  
  
  Adjust Document Type Settings:
  
  If you find discrepancies, adjust the settings to ensure that they are consistent. For example, if a document type is set to allow multiple documents, ensure that the corresponding transaction type is also configured to allow multiple documents.
  
  
  
  Review Custom Code:
  
  If there are any custom programs or enhancements that interact with document types or transaction types, review the code to ensure it does not introduce inconsistencies.
  
  
  
  Test Changes:
  
  After making the necessary adjustments, perform tests to ensure that the error no longer occurs and that document processing works as expected.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to this error for any specific guidance or updates that may be relevant to your version of SAP.
  
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to error GC174 for additional insights or patches that may address known issues.
  Transaction Codes: Familiarize yourself with transaction codes like OBA7 (for document types) and OBA8 (for transaction types) to quickly access and modify settings.
  Support: If the issue persists after following the above steps, consider reaching out to SAP support for further assistance.
  
  By ensuring that the document type and transaction type configurations are consistent, you should be able to resolve the GC174 error effectively.