How To Fix JO036 - Objects were filtered

SAP Error Message - Details

• Message type: E = Error

• Message class: JO - Project Information System: All Overviews

• Message number: 036

• Message text: Objects were filtered

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 JO036 - Objects were filtered ?

  The SAP error message JO036, which states "Objects were filtered," typically occurs in the context of job scheduling or background processing in SAP. This message indicates that certain objects (like jobs, tasks, or requests) have been filtered out from the display or processing due to specific criteria set in the system.
  Cause:
  
  Filter Settings: The most common cause of this error is that the user has applied filters in the job scheduling or monitoring transaction (like SM37 for job monitoring) that exclude certain jobs or objects from being displayed.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view certain jobs or objects, leading to them being filtered out.
  Job Status: The jobs may be in a status that is not included in the current filter settings (e.g., completed, canceled, or not started).
  Selection Criteria: The selection criteria used in the job monitoring transaction may be too restrictive, causing some jobs to be excluded from the results.
  
  Solution:
  
  Check Filter Settings: Review and adjust the filter settings in the transaction where the error occurs. Ensure that the criteria are set to include all relevant jobs or objects.
  Review Authorizations: Ensure that the user has the necessary authorizations to view all jobs. This may involve checking roles and permissions assigned to the user.
  Modify Selection Criteria: If using a transaction like SM37, modify the selection criteria to broaden the search (e.g., change the status of jobs to include all statuses).
  Clear Filters: If applicable, clear all filters to see if the objects appear without any restrictions.
  Check Job Logs: If the issue persists, check the job logs for any additional information that might indicate why certain jobs are being filtered.
  
  Related Information:
  
  Transaction Codes: Common transactions related to job monitoring include:
  
  SM37: Job Monitoring
  SM36: Define Background Job
  SM21: System Log
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to job scheduling and monitoring.
  Documentation: Refer to SAP Help documentation for detailed information on job scheduling and monitoring, including how to set filters and manage jobs.
  
  If the problem continues after trying the above solutions, it may be beneficial to consult with your SAP Basis team or SAP support for further assistance.