How To Fix FIKZ_DDX027 - Step '&1' finished, step '&2' in progress.

SAP Error Message - Details

• Message type: E = Error

• Message class: FIKZ_DDX - Message class for digital documents exchange

• Message number: 027

• Message text: Step '&1' finished, step '&2' in progress.

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 FIKZ_DDX027 - Step '&1' finished, step '&2' in progress. ?

  The SAP error message FIKZ_DDX027 typically indicates an issue related to the processing of a document in the context of the Document Compliance (DDX) framework. This message suggests that a particular step in the document processing workflow has been completed, while another step is still in progress. 
  Cause:
  
  Asynchronous Processing: The error often arises in scenarios where document processing is asynchronous. This means that one step of the process has completed, but the subsequent step has not yet started or is still running.
  Long Processing Times: If the system is processing a large volume of documents or if there are performance issues, it may take longer for the next step to begin.
  Configuration Issues: There may be configuration issues in the Document Compliance settings that are causing delays or failures in processing.
  System Performance: High system load or resource constraints can lead to delays in processing steps.
  
  Solution:
  
  Monitor the Process: Check the status of the document processing in the relevant transaction (e.g., SLG1 for application logs) to see if the next step is still in progress or if it has failed.
  Increase Timeout Settings: If the processing is taking too long, consider increasing the timeout settings for the document processing jobs.
  Check System Performance: Ensure that the SAP system has adequate resources (CPU, memory, etc.) to handle the processing load. You may need to optimize performance or schedule processing during off-peak hours.
  Review Configuration: Verify the configuration settings for Document Compliance to ensure they are set up correctly. This includes checking any relevant customizing settings in SPRO.
  Error Logs: Look for any related error messages in the application logs (transaction SLG1) that might provide more context on why the next step is not progressing.
  Reprocess the Document: If the document is stuck, you may need to reprocess it or manually trigger the next step in the workflow.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SLG1 (Application Log), SOST (Send Requests), and others that may help in monitoring and troubleshooting document processing.
  SAP Notes: Check for any SAP Notes related to the FIKZ_DDX027 error message or Document Compliance processing. SAP Notes often provide patches or additional guidance for known issues.
  Documentation: Review SAP documentation on Document Compliance and the specific steps involved in the processing workflow to understand the expected behavior and troubleshooting steps.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or technical team for further investigation or to reach out to SAP support for assistance.