How To Fix FDM_COLL_01054 - Obsolete basis type &1 maintained for message type &2

FDM_COLL_01054 - Overview

• Message type: E = Error

• Message class: FDM_COLL_01 - Messages in Collections Management

• Message number: 054

• Message text: Obsolete basis type &1 maintained for message type &2

What causes this issue?

When data is sent to collections management (logical system &V3&), the
obsolete basis type is maintained in your ALE distribution system for
message type &V2& in the partner profile &V1&.
You are currently using the new <DS:DE.FDM_COLL_XBRANCH> All Items for
Branch</> functions or have used them in at least one company code.
This function presupposes you are using the most current basis type.

System Response

The system terminates processing.

How to fix this error?

Maintain the current basis type in transaction <DS:TRAN.WE20>Partner
Profiles</>.

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 FDM_COLL_01054 - Obsolete basis type &1 maintained for message type &2 ?

  The SAP error message FDM_COLL_01054 indicates that an obsolete basis type is maintained for a specific message type. This error typically arises in the context of Financial Data Management (FDM) or related financial processes within SAP.
  
  Cause:
  The error occurs when the system detects that a message type is associated with a basis type that is no longer valid or has been deprecated. This can happen due to:
  
  Configuration Changes: Changes in the configuration of message types or basis types in the system.
  Upgrades or Patches: After an upgrade or patch, certain basis types may become obsolete, and the system may still reference them.
  Data Migration Issues: During data migration, obsolete types may inadvertently be retained in the configuration.
  
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Identify the Obsolete Basis Type: Check the error message for the specific basis type (&1) and message type (&2) that are causing the issue.
  
  
  Review Configuration:
  
  Go to the relevant configuration