How To Fix CCMSBI_MESSAGES274 - Serious error: New request before old request completed, or no init

SAP Error Message - Details

• Message type: E = Error

• Message class: CCMSBI_MESSAGES - Messages for the Extraction of CCMS Data into BW

• Message number: 274

• Message text: Serious error: New request before old request completed, or no init

What causes this issue?

The extractor was called with a new request ID, before a previous
request had been fully executed,
or
the initialization call was missing for a new request.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Case 1:
It is probable that not all of the data was transferred for the previous
request. For a renewed data load, the delta pointer must first be reset.
Case 2:
With a new request make sure that the init flag is set first when the
extractor is called.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CCMSBI_MESSAGES274 - Serious error: New request before old request completed, or no init ?

  The SAP error message CCMSBI_MESSAGES274 indicates that there is a serious issue with the processing of requests in the SAP system. Specifically, it suggests that a new request is being initiated before the previous request has been completed, or that there is no initialization of the request. This can occur in various contexts, such as background jobs, data processing, or when using the SAP Business Intelligence (BI) tools.
  Causes:
  
  Concurrent Requests: Multiple requests are being sent to the system simultaneously, and the system is unable to process them in the expected order.
  Long-Running Processes: A previous request is taking longer than expected to complete, causing subsequent requests to be blocked.
  Initialization Issues: The system may not have properly initialized the necessary components or data for the new request.
  System Configuration: There may be configuration issues in the SAP system that prevent proper request handling.
  Resource Limitations: Insufficient system resources (CPU, memory, etc.) can lead to delays in processing requests.
  
  Solutions:
  
  Check Request Status: Monitor the status of the previous requests to ensure they have completed. You can use transaction codes like SM37 (Job Monitoring) to check for any long-running jobs.
  Increase Timeout Settings: If the previous requests are taking too long, consider increasing the timeout settings for the relevant processes.
  Sequential Processing: Ensure that requests are processed sequentially rather than concurrently, if possible. This may involve adjusting the scheduling of jobs or requests.
  System Resources: Check the system resources and performance. If the system is under heavy load, consider optimizing performance or scaling resources.
  Review Configuration: Review the configuration settings related to the BI or data processing components to ensure they are set up correctly.
  Restart Services: If the issue persists, consider restarting the relevant services or the entire SAP system to clear any stuck processes.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Logs and Traces: Review system logs (transaction SM21) and traces (transaction ST22 for dumps) for any additional error messages or warnings that could provide more context.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found effective.
  
  If the problem continues after trying the above solutions, it may be necessary to involve SAP support for further investigation.