How To Fix /UI2/CDMFCC104 - LRep DB time stamp (&1) for file type &2 with name &3 does not match &4

/UI2/CDMFCC104 - Overview

• Message type: E = Error

• Message class: /UI2/CDMFCC -

• Message number: 104

• Message text: LRep DB time stamp (&1) for file type &2 with name &3 does not match &4

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /UI2/CDMFCC104 - LRep DB time stamp (&1) for file type &2 with name &3 does not match &4 ?

  The SAP error message /UI2/CDMFCC104 indicates a mismatch in the database timestamp for a specific file type and name. This error typically occurs in the context of the SAP Fiori Launchpad or when dealing with the SAP UI5 framework, particularly when there are issues with the cache or the deployment of UI5 applications.
  
  Cause:
  The error message can be caused by several factors, including:
  
  Cache Issues: The client-side cache may have outdated information that does not match the server-side data.
  Deployment Problems: If a UI5 application was recently updated or deployed, the timestamps for the files may not have been updated correctly.
  File Type Mismatch: The file type specified in the error message may not correspond to the expected file type in the system.
  Transport Issues: If the application was transported from one system to another (e.g., from development to production), there may be discrepancies in the timestamps.
  
  
  Solution:
  To resolve this error, you can try the following