How To Fix UCMI043 - Doc.type &1: Properties of "&2" and "&3" differ

UCMI043 - Overview

• Message type: E = Error

• Message class: UCMI - Messages for Breakdown Category, Item, Document Type, ...

• Message number: 043

• Message text: Doc.type &1: Properties of "&2" and "&3" differ

What causes this issue?

In document type customizing on the <ZK>Document Field Options</> tab,
you can define "fixing" options and entry options for the document
fields. Plus, you can determine whether the document field should be
hidden. Note that these properties must be identical for the two
document fields <ZK>Asset/Liability-managing Consolidation Unit (ALMU).
</>
However, in document type &V1& the field properties concerning fixing,
entry, and hiding are not the same for the two document ALMU fields '
&V2&' and '&V3&'.

System Response

Processing is terminated.

How to fix this error?

In document type &V1&, choose the same properties for fixing, entry, and
hiding for document fields '&V2&' and '&V3&'.

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 UCMI043 - Doc.type &1: Properties of "&2" and "&3" differ ?

  The SAP error message UCMI043 indicates that there is a mismatch in the properties of two document types in the context of the SAP Document Management System (DMS) or the SAP ArchiveLink. This error typically arises when you are trying to perform an operation that involves two document types that are expected to have consistent properties, but they do not.
  
  Cause:
  The error message UCMI043 is triggered when:
  
  You are trying to link or compare two documents that have different properties defined for their respective document types.
  The properties in question could include attributes such as document type, status, or other metadata that are expected to be consistent across the document types involved in the operation.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Document Types: Review the properties of the document types involved in the operation. You can do this by navigating to the document type configuration in SAP DMS or ArchiveLink.
  
  
  Standardize