How To Fix PMMO_PEGGING042 - No extended memory available for pegging process

SAP Error Message - Details

• Message type: E = Error

• Message class: PMMO_PEGGING - Messages for Pegging in PMMO

• Message number: 042

• Message text: No extended memory available for pegging process

What causes this issue?

The main pegging process is (or the pegging parallel sessions are)
requesting extended memory for their processing.

System Response

The request for a possible memory extension was not granted.

How to fix this error?

If the pegging run fails because of an out-of-memory runtime error in
the main process or a parallel session, we recommend using the following
profile parameters to allow the allocation of additional memory:
<DS:PP.EM/SESSIONMEM_EXT>em/sessionmem_ext</>
<DS:PP.EM/SESSIONMEM_EXT_NONDIA>em/sessionmem_ext_nondia</>

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

Procedure for System Administrators

INCLUDE PMMO_MMI_CUSTOMIZABLE_MSG OBJECT DOKU ID TX LANGUAGE EN

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PMMO_PEGGING042 - No extended memory available for pegging process ?

  The SAP error message PMMO_PEGGING042, which states "No extended memory available for pegging process," typically occurs in the context of the Production Planning and Control (PP) module when the system runs out of memory while trying to perform pegging operations. Pegging is the process of tracing the requirements of a product back to its sources, such as production orders or purchase orders.
  Causes:
  
  Insufficient Memory Allocation: The SAP system may not have enough memory allocated for the pegging process, especially if there are large datasets or complex operations involved.
  High Load on the System: If the system is under heavy load or if there are many concurrent users, it may lead to memory exhaustion.
  Configuration Issues: Incorrect configuration settings in the SAP system related to memory management can also lead to this error.
  Large Data Volume: Processing a large volume of data or complex queries can consume significant memory resources.
  
  Solutions:
  
  
  Increase Memory Allocation:
  
  Check and increase the memory settings in the SAP system. This can be done by adjusting the parameters in the instance profile (e.g., abap/heap_area_total, abap/heap_area_dia, abap/heap_area_nondia).
  Consult with your Basis team to ensure that the memory settings are optimized for your workload.
  
  
  
  Optimize Queries:
  
  Review the queries or processes that are causing the memory issue. Try to optimize them to reduce the memory footprint.
  Limit the amount of data being processed at one time, if possible.
  
  
  
  System Performance Monitoring:
  
  Monitor system performance and memory usage using transaction codes like ST02 (Tune Summary) and ST03 (Workload Analysis) to identify bottlenecks.
  Analyze the workload and identify any long-running processes that may be consuming excessive memory.
  
  
  
  Batch Processing:
  
  If applicable, consider breaking down large processes into smaller batches to reduce memory consumption during pegging.
  
  
  
  Upgrade Hardware:
  
  If the system frequently runs out of memory, it may be necessary to consider upgrading the hardware resources (RAM) of the server hosting the SAP system.
  
  
  
  SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error or provide patches and updates that could resolve memory-related issues.
  
  
  
  Related Information:
  
  SAP Basis Team: Collaborate with your SAP Basis team for any changes to system parameters or hardware upgrades.
  SAP Documentation: Refer to SAP Help documentation for guidelines on memory management and performance tuning.
  Transaction Codes: Familiarize yourself with transaction codes like ST02, ST03, and SM37 (for monitoring jobs) to help diagnose and troubleshoot memory issues.
  
  If the problem persists after trying these solutions, it may be beneficial to contact SAP support for further assistance.