How To Fix DG663 - Check method &1 is initialization method for checks at header level

DG663 - Overview

• Message type: E = Error

• Message class: DG - DG: Messages for Dangerous Goods Management

• Message number: 663

• Message text: Check method &1 is initialization method for checks at header level

What causes this issue?

You have entered a usage profile (mode of transport category, country,
and role) for check method &V1&.
However, check method &V1& is selected as the initialization method for
header check methods (for example, mixed loading checks).
Check method &V1& has the task of collecting all dangerous goods master
records relevant for the current SD document for the header check
method.
The header check methods should therefore be assigned to the same usage
profiles as the initialization method.

System Response

Check whether a usage profile is required for the check method &V1&. If
this is the case, check whether the same usage profiles are assigned to
the header check methods.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DG663 - Check method &1 is initialization method for checks at header level ?

  The SAP error message DG663 indicates that there is an issue with the check method specified in the context of a header-level check in a business process, such as sales order processing or delivery processing. This error typically arises when the system expects a specific check method to be used for validation at the header level, but the method defined is not appropriate or is incorrectly configured.
  
  Cause:
  
  Incorrect Check Method: The check method specified in the configuration is not set as an initialization method for checks at the header level.
  
  Configuration Issues: There may be issues in the configuration of the check methods in the relevant customizing settings.
  Missing Implementation: The check method may not be implemented correctly or is missing necessary logic to handle header-level checks.
  
  
  Solution:
  
  
  Check Configuration:
  
  Go to the relevant customizing transaction (e.g., SPRO) and navigate to the area where check methods are defined.
  Verify that the check method you are using is