How To Fix RPUGEN013 - Additional process starts for FM &1 not possible (missing resources)

SAP Error Message - Details

• Message type: E = Error

• Message class: RPUGEN - General Error Messages in Procurement (ISR)

• Message number: 013

• Message text: Additional process starts for FM &1 not possible (missing resources)

What causes this issue?

During parallel processing, the system tried a number of times to start
a new process for the RFC call of function module &1. The system could
not start a new process because of a lack of resources.

System Response

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

How to fix this error?

INCLUDE ISR_VERWALTUNG

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 RPUGEN013 - Additional process starts for FM &1 not possible (missing resources) ?

  The SAP error message RPUGEN013 indicates that an additional process cannot be started for a specific function module (FM) because of missing resources. This typically occurs in the context of background processing or when trying to execute a function module that requires certain resources (like memory, processes, or system capacity) that are currently unavailable.
  Causes:
  
  Resource Limitations: The system may have reached its limit for background processes or dialog processes. This can happen if there are too many jobs running simultaneously.
  Configuration Issues: The system configuration may not be set up to allow for the required number of parallel processes for the function module.
  System Performance: High system load or performance issues can lead to resource contention, making it impossible to allocate the necessary resources for the function module.
  Locks: If the function module is trying to access a resource that is currently locked by another process, it may not be able to start.
  
  Solutions:
  
  Check Background Jobs: Review the currently running background jobs in transaction SM37. If there are too many jobs, consider terminating some of them to free up resources.
  Increase Process Limits: If the system is consistently running out of resources, you may need to increase the limits for background processes. This can be done in the instance profile parameters (e.g., rdisp/wp_no_btc for background work processes).
  Monitor System Performance: Use transaction ST03N or ST06 to monitor system performance and identify any bottlenecks. Look for high CPU or memory usage that may be affecting resource availability.
  Check Locks: Use transaction SM12 to check for any locks that may be preventing the function module from executing. If you find locks that are no longer needed, you can release them.
  Review Function Module: If the function module is custom or has been modified, review its code to ensure it is not consuming excessive resources or causing deadlocks.
  System Restart: In some cases, a system restart may help clear up resource issues, especially if there are lingering processes that are not releasing resources properly.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Monitor background jobs.
  SM12: Display and manage locks.
  ST03N: Analyze workload and performance.
  ST06: Monitor system performance metrics.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message or provide patches and updates.
  Documentation: Review SAP documentation for guidelines on configuring background processing and managing system resources.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.