How To Fix J-036 - Generation template for extended list display not found

SAP Error Message - Details

• Message type: E = Error

• Message class: J- -

• Message number: 036

• Message text: Generation template for extended list display not found

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 J-036 - Generation template for extended list display not found ?

  The SAP error message J-036, which states "Generation template for extended list display not found," typically occurs when the system is unable to find the necessary template for generating an extended list display in a specific transaction or report. This can happen for various reasons, including configuration issues or missing templates.
  Causes:
  
  Missing Template: The required generation template for the extended list display is not defined in the system.
  Incorrect Configuration: The configuration settings for the report or transaction may not be set up correctly.
  Authorization Issues: The user may not have the necessary authorizations to access the template or the report.
  Transport Issues: If the template was recently transported from another system, it may not have been transported correctly.
  
  Solutions:
  
  
  Check Template Configuration:
  
  Go to the transaction code SE80 (Object Navigator) or SE11 (Data Dictionary) and check if the generation template exists.
  If it does not exist, you may need to create it or restore it from a backup.
  
  
  
  Review Report Settings:
  
  Ensure that the report or transaction is correctly configured to use the appropriate generation template.
  Check the settings in the relevant customizing transaction (e.g., SPRO) to ensure everything is set up correctly.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access the report and the associated templates.
  You can check this using transaction SU53 after the error occurs to see if there are any authorization issues.
  
  
  
  Transport Check:
  
  If the template was recently transported, check the transport logs to ensure that the transport was successful and that all necessary objects were included.
  If there are issues, you may need to re-transport the missing objects.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific transaction or report to see if there are any known issues or additional configuration steps required.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide specific notes or patches that address the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80, SE11, SPRO, and SU53.
  SAP Notes: Search for SAP Notes related to the error message J-036 in the SAP Support Portal for any specific fixes or recommendations.
  User Forums: Check SAP community forums or other user groups for similar issues and solutions shared by other users.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.