How To Fix DG666 - Error while determining expected delivery via user exit

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 666

• Message text: Error while determining expected delivery via user exit

What causes this issue?

An error occurred while the expected delivery was being determined.

System Response

No check schema is processed for the expected delivery.

How to fix this error?

See the long text for the error message in the dangerous goods check
log for more information.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DG666 - Error while determining expected delivery via user exit ?

  The SAP error message DG666, which states "Error while determining expected delivery via user exit," typically occurs in the context of delivery processing in SAP, particularly when the system is trying to calculate or determine the expected delivery date using a user exit or enhancement.
  Cause:
  
  
  User Exit Issues: The error often arises from issues in the custom code implemented in a user exit. This could be due to:
  
  Syntax errors in the ABAP code.
  Logic errors that prevent the expected delivery date from being calculated correctly.
  Missing or incorrect data being passed to the user exit.
  
  
  
  Configuration Issues: There may be configuration settings in the delivery or shipping modules that are not set up correctly, leading to the inability to determine the expected delivery.
  
  
  Data Issues: Inconsistent or incomplete master data (like material master, vendor master, etc.) can also lead to this error.
  
  
  System Bugs: Occasionally, there may be bugs in the SAP system or specific patches that need to be applied.
  
  
  Solution:
  
  
  Debugging the User Exit:
  
  Use transaction SE80 or SE37 to locate the user exit that is causing the issue.
  Set breakpoints and debug the code to identify where the error occurs.
  Check for any syntax or logical errors in the code.
  
  
  
  Review Configuration:
  
  Ensure that all relevant configuration settings for delivery processing are correctly set up.
  Check the shipping point, delivery types, and any related settings in the configuration.
  
  
  
  Data Validation:
  
  Validate the master data related to the delivery process. Ensure that all necessary fields are populated and correct.
  Check for any inconsistencies in the data that might affect the delivery date calculation.
  
  
  
  SAP Notes and Patches:
  
  Check the SAP Support Portal for any relevant SAP Notes that address this specific error.
  Apply any necessary patches or updates to the system.
  
  
  
  Consult Documentation:
  
  Review the documentation for the specific user exit being used to ensure it is being implemented correctly.
  
  
  
  Engage SAP Support:
  
  If the issue persists after troubleshooting, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  User Exits: User exits are predefined points in the SAP code where you can add custom code to enhance the standard functionality without modifying the original code.
  Transaction Codes: Familiarize yourself with transaction codes like SE80 (Object Navigator), SE37 (Function Module), and SE38 (ABAP Editor) for debugging and reviewing code.
  SAP Notes: Regularly check for SAP Notes related to your version of SAP, as they can provide fixes or workarounds for known issues.
  
  By following these steps, you should be able to identify and resolve the DG666 error in your SAP system.