How To Fix WI136 - Form not found

SAP Error Message - Details

• Message type: E = Error

• Message class: WI - BPT Workflow: Messages from Info System

• Message number: 136

• Message text: Form 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 WI136 - Form not found ?

  The SAP error message WI136 "Form not found" typically occurs in the context of SAP Workflow or SAPscript/Smart Forms printing processes. It indicates that the system is unable to locate the specified form (SAPscript form or Smart Form) that is required for output processing.
  
  Cause
  
  The form name specified in the workflow or print program does not exist in the system.
  The form might have been deleted or not yet created.
  The form name is incorrectly specified (typo or wrong case).
  The form is not transported to the current system/client.
  The form is not assigned or linked properly in the workflow or print program.
  Authorization issues preventing access to the form (less common).
  
  
  Solution
  
  
  Check the Form Name:
  
  Verify the exact form name used in the workflow or print program.
  Ensure there are no typos or case sensitivity issues.
  
  
  
  Verify Form Existence:
  
  For SAPscript forms:
  
  Use transaction SE71 to check if the form exists.
  
  
  For Smart Forms:
  
  Use transaction SMARTFORMS to check if the form exists.
  
  
  
  
  
  Create or Transport the Form:
  
  If the form does not exist, create it or transport it from the development system.
  If the form was deleted accidentally, restore it from backup or transport.
  
  
  
  Check Workflow or Print Program Configuration:
  
  In the workflow, check the step or container where the form name is specified.
  In print programs, check the code or configuration where the form is called.
  
  
  
  Check Authorizations:
  
  Ensure the user or background job running the workflow/print has authorization to access the form.
  
  
  
  Check Client and System:
  
  Make sure the form exists in the correct client and system where the error occurs.
  
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  SE71 – SAPscript form maintenance
  SMARTFORMS – Smart Forms maintenance
  SWDD – Workflow Builder (to check workflow steps)
  SP01 – Output request monitoring
  
  
  
  Notes and Documentation:
  
  SAP Notes related to form issues can be searched on SAP Support Portal.
  Check OSS notes if the problem persists after verifying form existence.
  
  
  
  Common Scenarios:
  
  Printing invoices, delivery notes, or purchase orders where the form is missing.
  Workflow steps triggering print output without proper form assignment.
  
  
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Error
  WI136 Form not found
  
  
  Cause
  Form name missing, incorrect, or not transported
  
  
  Solution
  Verify form name, check existence in SE71/SMARTFORMS, create or transport form, check workflow/print program configuration
  
  
  Related Tcodes
  SE71, SMARTFORMS, SWDD, SP01
  
  
  
  
  If you provide the exact context (e.g., workflow step, print program, transaction), I can help with more specific troubleshooting steps.