Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: PMMO_PEGGING - Messages for Pegging in PMMO
Message number: 015
Message text: List display incomplete; only &2 from &1 are displayed
If you display the hierarchical or list view of the pegging results,
then not all processed records will be displayed. &V1& were processed
during pegging but only &V2& records will be displayed in the list.
Due to the high number of records processed<(>,<)> the amount of data
displayed is limited to &V2& records.
The system displays an incomplete list.
Run the pegging program with more specific selection criteria to limit
the amount of data that is being processed.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
PMMO_PEGGING015
- List display incomplete; only &2 from &1 are displayed ?The SAP error message PMMO_PEGGING015, which states "List display incomplete; only &2 from &1 are displayed," typically occurs in the context of the Production Planning and Control (PP) module, particularly when dealing with pegging information in the Material Requirements Planning (MRP) process.
Cause:
This error message indicates that the system is unable to display all the pegging information for a particular material or production order. The message specifies that only a subset of the total available pegging records is being displayed. The reasons for this could include:
- Data Volume: The number of pegging records exceeds the display limit set in the system.
- Performance Optimization: To enhance performance, SAP may limit the number of records displayed in certain transactions.
- User Authorization: The user may not have the necessary authorizations to view all the pegging records.
- System Configuration: The configuration settings in the SAP system may limit the number of records displayed.
Solution:
To resolve this issue, you can consider the following steps:
Check Display Settings: Review the display settings in the transaction you are using. Some transactions allow you to adjust the number of records displayed.
Pagination: If the transaction supports pagination, navigate through the pages to see if additional records are available.
Authorization Check: Ensure that the user has the necessary authorizations to view all pegging records. You may need to consult with your SAP security team.
System Configuration: If you have access to system configuration, check if there are any settings that limit the number of records displayed. This may involve consulting with your SAP Basis or configuration team.
Performance Considerations: If the volume of data is large, consider filtering the data to reduce the number of records displayed. This can be done by applying selection criteria or filters.
SAP Notes: Check for any relevant SAP Notes or updates that may address this issue. Sometimes, SAP releases patches or notes that provide solutions for specific error messages.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
PMMO_PEGGING014
Goods issue: order quantity is missing for replenishment &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PMMO_PEGGING013
Goods issue: sending replenishment elem is missing: group &1 material &2
What causes this issue? The sending replenishment element in goods issue is missing: grouping WBS element &v1&, material &v2&.System ...
PMMO_PEGGING016
Next higher level not found for replenishment element &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PMMO_PEGGING017
Personalization data for user &1 was successfully deleted
What causes this issue? The user &V1& has been deleted from the database. The related personalization data for the pegging log tree control w...
Click on this link to search all SAP messages.