How To Fix EZ173 - Form routine &1 does not exist in include &2

SAP Error Message - Details

• Message type: E = Error

• Message class: EZ - Print workbench

• Message number: 173

• Message text: Form routine &1 does not exist in include &2

What causes this issue?

You have attempted to access a form routine in an ABAP program. This
form routine does not exist.

System Response

INCLUDE NA_FICA_DWB_ANFORD OBJECT DOKU ID TX

How to fix this error?

Create the appropriate form routine in the ABAP program.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EZ173 - Form routine &1 does not exist in include &2 ?

  The SAP error message EZ173 indicates that a form routine specified in a program or form does not exist in the specified include file. This typically occurs when there is a reference to a routine that has either been deleted, renamed, or is not properly defined in the include file.
  Cause:
  
  Missing Routine: The form routine that is being called does not exist in the specified include file.
  Typographical Error: There may be a typo in the name of the routine or the include file.
  Transport Issues: If the include file or the routine was transported from another system, it may not have been transported correctly.
  Development Environment Changes: Changes made in the development environment may not have been reflected in the production environment.
  
  Solution:
  
  
  Check the Include File: Verify that the include file specified in the error message actually exists and is accessible. You can do this by navigating to the include file in the ABAP editor (transaction SE38 or SE80).
  
  
  Verify Routine Name: Ensure that the routine name being called is spelled correctly and matches the name defined in the include file.
  
  
  Create or Restore the Routine: If the routine is missing, you may need to create it or restore it from a backup or transport request.
  
  
  Check Transport Requests: If the issue arose after a transport, check the transport logs to ensure that all necessary objects were included and transported correctly.
  
  
  Debugging: Use the debugger to trace where the error occurs and check the call stack to understand how the program is trying to access the routine.
  
  
  Consult Documentation: If the routine is part of a standard SAP program or enhancement, consult SAP documentation or notes to see if there are any known issues or updates.
  
  
  Related Information:
  
  Transaction Codes: Use SE38 (ABAP Editor) to view and edit programs, and SE80 (Object Navigator) to navigate through various objects including includes and routines.
  SAP Notes: Check SAP Notes for any known issues related to the specific program or include file.
  Development Guidelines: Follow best practices for naming conventions and documentation to avoid such issues in the future.
  
  If the problem persists after trying the above solutions, consider reaching out to your SAP Basis or ABAP development team for further assistance.