How To Fix CNV036 - Different FORM routines found: &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV - Conversion: Messages for Conversion Services (CNCC)

• Message number: 036

• Message text: Different FORM routines found: &1 &2

What causes this issue?

During blending of the source packages at least two different
(conversion or aggregate) routines were assigned to the same field.
When two different conversion packages are blended together and both of
them indicate that they are configured to convert the same field of the
same table then conflict occurs (as long as these two packages use
different routines for conversion). This can happen for example if the
table field contain some non-transparently stored data ("many values" in
one field).

System Response

Packages cannot be blended together.

How to fix this error?

A top-level package can be created to resolve the conflicts. If the
source packages are meant to be executed together contact SAP support.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CNV036 - Different FORM routines found: &1 &2 ?

  The SAP error message CNV036, which states "Different FORM routines found: &1 &2," typically occurs during data migration or conversion processes, particularly when using the SAP Conversion Tools or during the execution of programs that involve FORM routines. This error indicates that there are two different FORM routines with the same name but located in different programs or function modules, which can lead to ambiguity in execution.
  Cause:
  
  Duplicate FORM Routines: The error arises when the same FORM routine name is defined in multiple locations (e.g., different programs or function modules) but with different implementations.
  Inconsistent Code: The routines may have been modified independently, leading to discrepancies in their logic or functionality.
  Namespace Conflicts: If custom developments or enhancements have been made, they might conflict with standard SAP routines.
  
  Solution:
  
  Identify the Routines: Check the details of the error message to identify the two FORM routines (denoted by &1 and &2). You can use transaction SE80 or SE37 to locate the routines.
  Review the Code: Compare the implementations of both FORM routines to understand the differences. This may involve checking the logic, parameters, and any dependencies.
  Rename or Refactor: If the routines serve different purposes, consider renaming one of them to avoid the conflict. If they are meant to be the same, consolidate the logic into a single routine.
  Adjust Program Logic: Ensure that the program or function module calling the FORM routine is referencing the correct one. This may involve modifying the call to explicitly specify the correct routine.
  Check for Enhancements: If the routines are part of a custom enhancement, review the enhancement implementation to ensure it does not conflict with standard SAP code.
  Testing: After making changes, thoroughly test the affected programs to ensure that the issue is resolved and that the functionality remains intact.
  
  Related Information:
  
  Transaction Codes: Use SE80 (Object Navigator) or SE37 (Function Module) to analyze the routines.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on best practices for handling FORM routines.
  Documentation: Review SAP documentation on data migration and conversion processes to understand how FORM routines are utilized in these contexts.
  
  If the issue persists after following these steps, consider reaching out to SAP support or consulting with a developer who has experience with the specific programs involved.