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

SAP Error Message - Details

• 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 the system, they may not be handling the document types correctly, leading to this error.
  
  
  Solution:
  To resolve the UCF6159 error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for document types in the SAP system (Transaction code: SPRO).
  Ensure that both document types (&1 and &2) are correctly defined and configured in the system.
  
  
  
  Review Document Type Settings:
  
  Verify that the document types are included in the relevant processing logic. This may involve checking the settings for the specific transaction or process you are working with.
  
  
  
  Analyze Custom Code:
  
  If there are any custom developments or enhancements, review the code to ensure that it correctly handles the document types involved in the transaction.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific transaction or module you are working with. There may be known issues or additional configuration steps required.
  
  
  
  Testing:
  
  After making any changes, perform testing to ensure that the error is resolved and that the document processing works as expected.
  
  
  
  Seek Help from SAP Support:
  
  If the issue persists, consider reaching out to SAP support for further assistance. They may provide additional insights or solutions based on the specific context of your system.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (Customizing), SE80 (Object Navigator), and SE37 (Function Module) for debugging.
  SAP Notes: Search for SAP Notes related to UCF6159 or the specific document types involved for any patches or updates that may address the issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  By following these steps, you should be able to identify the root cause of the UCF6159 error and implement a suitable solution.