How To Fix FCC0355 - There are no change documents

SAP Error Message - Details

• Message type: E = Error

• Message class: FCC0 - Messages in Financial Closing Cockpit

• Message number: 355

• Message text: There are no change documents

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 FCC0355 - There are no change documents ?

  The SAP error message FCC0355, which states "There are no change documents," typically occurs in the context of the Financial Accounting (FI) or Controlling (CO) modules when a user attempts to access change documents for a particular object (like a vendor, customer, or other master data) but finds that no change documents exist for that object.
  Cause:
  
  No Changes Made: The most straightforward reason for this error is that no changes have been made to the object in question since the change document functionality was activated.
  Change Document Not Activated: Change document tracking may not be activated for the specific object type you are trying to view.
  Data Deletion: Change documents may have been deleted or archived, leading to the absence of records.
  Authorization Issues: The user may not have the necessary authorizations to view change documents, which could lead to the perception that no documents exist.
  
  Solution:
  
  
  Check Change Document Activation:
  
  Ensure that change document tracking is activated for the relevant object type. This can usually be checked in the configuration settings of the relevant module (e.g., FI or CO).
  For example, in the case of vendor or customer master data, you can check the settings in transaction code SPRO under the relevant section for master data.
  
  
  
  Verify Changes:
  
  Confirm that changes have indeed been made to the object. If no changes have been made, there will naturally be no change documents to display.
  
  
  
  Review Authorizations:
  
  Check the user’s authorization profile to ensure they have the necessary permissions to view change documents. This can be done through transaction SU53 or by consulting with your security team.
  
  
  
  Check for Archiving:
  
  If change documents were archived, you may need to check the archiving settings or retrieve the archived documents if necessary.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources for specific details related to the object type you are working with, as there may be additional considerations or settings that need to be addressed.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SPRO (Customizing), and SU53 (Authorization Check).
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  Change Document Tables: Understand the relevant tables where change documents are stored (e.g., CDPOS, CDHDR) to investigate further if needed.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP Basis or functional team for further investigation.