How To Fix UCF6159 - Location of values: doc. type &1 is included, but doc. type &2 is not

UCF6159 - Overview

• Message type: E = Error

• Message class: UCF6 - Messages for Consolidation of Investments

• Message number: 159

• Message text: Location of values: doc. type &1 is included, but doc. type &2 is not

What causes this issue?

In Customizing for the document type assignment for the balance
carryforward, you assigned document type &V1& to document type &V2&. In
the location of values for consolidation of investments, you included
document type &V1&, but not document type &V2&, in the calculation base.
For each document type pair that you define in the document type
assignment for the balance carryforward, you must either include both
the source document type and target document type in the calculation
base or include neither of them.

System Response

The Customizing settings for the location of values for consolidation of
investments is inconsistent with respect to the document type assignment
for the balance carryforward. This leads to incorrect results when you
perform the consolidation of investments in the subsequent year.

How to fix this error?

Correct the Customizing settings for the calculation base for
consolidation of investments by selecting the <LS>Inclusion</> indicator
either for neither or both of the document types &V1& and &V2&.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UCF6159 - Location of values: doc. type &1 is included, but doc. type &2 is not ?

  The SAP error message UCF6159 indicates that there is a mismatch in the document types being processed in a financial transaction or document. Specifically, it suggests that a certain document type (denoted as &1) is included in the processing, but another document type (denoted as &2) is not included, which leads to inconsistencies or errors in the processing logic.
  
  Cause:
  The error typically arises in scenarios involving document processing where certain configurations or settings are not aligned. Common causes include:
  
  
  
  Configuration Issues: The document types may not be properly configured in the system. This could be due to missing entries in the configuration tables or incorrect settings in the financial document types.
  
  
  Inconsistent Document Types: The system may be trying to process a transaction that involves multiple document types, but one of the required document types is not included in the processing logic.
  
  
  Custom Logic or Enhancements: If there are custom developments or enhancements in