How To Fix FKK_EBS320 - No IDocs were created

SAP Error Message - Details

• Message type: E = Error

• Message class: FKK_EBS - Interface between FI-CA and External Billing System

• Message number: 320

• Message text: No IDocs were created

What causes this issue?

The function module MASTER_IDOC_DISTRIBUTE has been called up but no
outgoing IDocs have been created.
This may be due to an error that occurred in filling the input
variables.
The cause of this error might be an incorrectly maintained distribution
model.

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 whether the above reasons apply.

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 FKK_EBS320 - No IDocs were created ?

  The SAP error message FKK_EBS320: No IDocs were created typically occurs in the context of Electronic Bank Statement (EBS) processing. This error indicates that the system did not generate any IDocs (Intermediate Documents) for the bank statement processing, which can hinder the automatic processing of bank transactions.
  Causes:
  
  Configuration Issues: The EBS configuration may not be set up correctly, leading to no IDocs being generated.
  Missing Data: Required data for processing the bank statement may be missing or incomplete.
  Selection Criteria: The selection criteria used for processing the bank statement may not match any records, resulting in no IDocs being created.
  Technical Errors: There may be technical issues or bugs in the system that prevent IDoc creation.
  Authorization Issues: The user may not have the necessary authorizations to create IDocs.
  
  Solutions:
  
  
  Check Configuration:
  
  Verify the configuration settings for Electronic Bank Statement processing in transaction OBBA or FBZP. Ensure that the settings for the bank account and the IDoc processing are correctly defined.
  
  
  
  Review Bank Statement Data:
  
  Ensure that the bank statement data being processed is complete and correctly formatted. Check for any missing or incorrect entries in the bank statement.
  
  
  
  Adjust Selection Criteria:
  
  Review the selection criteria used in the EBS processing. Make sure that the criteria are set to include the relevant records.
  
  
  
  Check for Errors in Logs:
  
  Use transaction SLG1 to check the application logs for any errors or warnings that may provide more context on why IDocs were not created.
  
  
  
  Test IDoc Generation:
  
  Manually trigger the IDoc generation process to see if it works outside of the automated process. This can help identify if the issue is with the data or the process itself.
  
  
  
  Review Authorizations:
  
  Ensure that the user executing the EBS process has the necessary authorizations to create IDocs. Check the user roles and permissions.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address known issues related to this error message.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the program responsible for IDoc generation to identify any potential coding issues.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  FBZ0: Electronic Bank Statement processing.
  OBBA: Configuration for Electronic Bank Statement.
  SLG1: Application log for error analysis.
  
  
  
  IDoc Types: Familiarize yourself with the IDoc types used for bank statements, such as DEBMAS or FINSTA, depending on your specific implementation.
  
  
  SAP Community: Engage with the SAP Community forums for additional insights and shared experiences from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to diagnose and resolve the issue related to the FKK_EBS320 error message in SAP.