How To Fix UCF6155 - Location of values: Document type &1 is not part of the calculation base

UCF6155 - Overview

• Message type: E = Error

• Message class: UCF6 - Messages for Consolidation of Investments

• Message number: 155

• Message text: Location of values: Document type &1 is not part of the calculation base

What causes this issue?

In Customizing for the location of values for consolidation of
investments, you have selected the <LS>Suppress Minority Interest
Posting</> indicator for document type &V1& in the calculation base.
However, you have not included document type &V1& in the calculation
base.

System Response

Customizing settings for the location of values are inconsistent and
cannot be saved.

How to fix this error?

If document type &V1& is to be included in the calculation base, you
must select the <LS>Inclusion</> indicator. You can then use the
<LS>Suppress Minority Interest Posting</> indicator to specify whether
the system is to suppress the adjustment of minority interest postings
for document type &V1&.
If you do <ZH>not</> include document type &V1&, you cannot select the
<LS>Suppress Minority Interest Posting</> indicator.

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 UCF6155 - Location of values: Document type &1 is not part of the calculation base ?

  The SAP error message UCF6155 indicates that the document type specified in the error message is not included in the calculation base for the financial transaction or process you are trying to execute. This typically occurs in the context of financial accounting or controlling processes where specific document types are expected to be part of a calculation or reporting process.
  
  Cause:
  
  Document Type Configuration: The document type you are trying to use is not configured in the system to be part of the calculation base. This could be due to incorrect settings in the configuration of the financial module.
  Missing Entries: The document type may not have been included in the relevant configuration tables or settings that define which document types are valid for the calculation.
  Business Process Changes: Changes in business processes or requirements may have led to the exclusion of certain document types from the calculation base.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the configuration