How To Fix OPS_SE_APPL_SHP036 - Returning number of hits only as requested by BADI implementation

SAP Error Message - Details

• Message type: E = Error

• Message class: OPS_SE_APPL_SHP - Proxy Messages for Delivery Services

• Message number: 036

• Message text: Returning number of hits only as requested by BADI implementation

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 OPS_SE_APPL_SHP036 - Returning number of hits only as requested by BADI implementation ?

  The SAP error message OPS_SE_APPL_SHP036, which states "Returning number of hits only as requested by BADI implementation," typically occurs in the context of SAP's Advanced Planning and Optimization (APO) or Supply Chain Management (SCM) modules. This message indicates that the system is configured to return only a count of hits (i.e., the number of records that match a certain query) rather than the detailed data itself. This behavior is often controlled by a Business Add-In (BADI) implementation.
  Cause:
  
  BADI Implementation: The error is usually caused by a specific BADI implementation that has been designed to limit the output to just the number of hits. This is often done for performance reasons, especially when dealing with large datasets.
  Configuration Settings: The settings in the BADI or the related configuration may have been set to return only the count of records instead of the detailed data.
  Custom Logic: If there is custom logic implemented in the BADI, it may be intentionally designed to restrict the output to just the number of hits.
  
  Solution:
  
  Review BADI Implementation: Check the BADI implementation associated with the error. You can do this by navigating to the relevant BADI in the SAP system (using transaction SE18 or SE19) and reviewing the code to see if it is set to return only the count.
  Modify Logic: If you need detailed data instead of just the count, you may need to modify the BADI implementation to return the full dataset. This may involve changing the logic to fetch and return the detailed records.
  Consult Documentation: Review any documentation related to the BADI and its intended use. There may be specific guidelines on how to handle the output.
  Performance Considerations: If you decide to change the implementation to return detailed data, consider the performance implications, especially if the dataset is large. You may want to implement pagination or filtering to manage the volume of data returned.
  Testing: After making changes, thoroughly test the implementation to ensure that it behaves as expected and does not introduce performance issues.
  
  Related Information:
  
  BADI Documentation: Look for SAP notes or documentation related to the specific BADI you are working with. This can provide insights into its intended use and any known issues.
  SAP Community: Engage with the SAP Community forums or other user groups to see if others have encountered similar issues and what solutions they have implemented.
  SAP Support: If you are unable to resolve the issue, consider reaching out to SAP Support for assistance, especially if this is impacting critical business processes.
  
  By following these steps, you should be able to address the OPS_SE_APPL_SHP036 error and adjust the BADI implementation to meet your requirements.