How To Fix EDEREG_INV735 - Event module for sending payment advice note does not return IDocs

SAP Error Message - Details

• Message type: E = Error

• Message class: EDEREG_INV - Error Messages for Payment Management in a Deregulated Env.

• Message number: 735

• Message text: Event module for sending payment advice note does not return IDocs

What causes this issue?

No IDoc was generated.
This error can occur if a data exchange definition is incorrect. For
example, if it contains a data exchange format with a function module
that is not suitable for processing complaint notifications.

System Response

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

How to fix this error?

Check the data exchange definition for service provider &V1&.

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 EDEREG_INV735 - Event module for sending payment advice note does not return IDocs ?

  The SAP error message EDEREG_INV735 indicates that the event module responsible for sending payment advice notes is not returning IDocs (Intermediate Documents). This can occur due to various reasons, and understanding the cause is essential for troubleshooting and resolving the issue.
  Possible Causes:
  
  
  Configuration Issues: The IDoc configuration for the payment advice note may not be set up correctly in the system. This includes settings in the partner profiles, message types, and IDoc types.
  
  
  Missing or Incorrect Data: The data required to generate the IDoc may be missing or incorrect. This could include missing payment advice details or incorrect document types.
  
  
  Authorization Issues: The user or process attempting to trigger the event may not have the necessary authorizations to create or send IDocs.
  
  
  Event Triggering Issues: The event that is supposed to trigger the IDoc generation may not be firing correctly due to issues in the event handling logic.
  
  
  Technical Errors: There may be underlying technical issues, such as problems with the application server, network issues, or database errors.
  
  
  IDoc Processing Errors: If there are issues with the IDoc processing logic or if the IDoc is being generated but not processed correctly, it may not be sent.
  
  
  Solutions:
  
  
  Check Configuration:
  
  Verify the configuration settings for IDocs in transaction WE20 (Partner Profiles) and WE21 (Port Definition).
  Ensure that the message type and IDoc type for payment advice notes are correctly defined.
  
  
  
  Validate Data:
  
  Check the data being used to generate the payment advice note. Ensure that all required fields are populated correctly.
  Use transaction FBPM (Payment Advice) to review the payment advice details.
  
  
  
  Review Authorizations:
  
  Ensure that the user or process has the necessary authorizations to create and send IDocs. Check roles and authorizations in transaction PFCG.
  
  
  
  Debug Event Logic:
  
  If you have access to the ABAP code, debug the event module to see if it is being triggered correctly and if it is attempting to generate the IDoc.
  
  
  
  Check System Logs:
  
  Review system logs (transaction SLG1) for any error messages or warnings that may provide additional context about the issue.
  
  
  
  Monitor IDoc Processing:
  
  Use transaction WE02 or WE05 to monitor IDoc processing and check if any IDocs are being generated but not processed correctly.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes that may address known issues related to the EDEREG_INV735 error message.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  IDoc Basics: Understanding how IDocs work in SAP can help in troubleshooting. IDocs are used for data interchange between SAP systems and external systems.
  Event Management: Familiarity with how events are triggered in SAP can provide insights into why the IDoc is not being generated.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as WE20 (Partner Profiles), WE21 (Port Definition), WE02/WE05 (IDoc Monitoring), and SLG1 (Application Log).
  
  By systematically checking these areas, you should be able to identify the cause of the EDEREG_INV735 error and implement an appropriate solution.