How To Fix FBZI352 - Bank reports error during OFX transaction "Account statement"

SAP Error Message - Details

• Message type: E = Error

• Message class: FBZI - Payments via Internet

• Message number: 352

• Message text: Bank reports error during OFX transaction "Account statement"

What causes this issue?

The bank reported an error during triggered OFX transaction "account
statement".

System Response

Reported status code: ,,&v1&
Reported level:,,,,&v2&
Message:,,,,,,&v3&

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 FBZI352 - Bank reports error during OFX transaction "Account statement" ?

  The SAP error message FBZI352 indicates that there is an issue with the bank report during an OFX (Open Financial Exchange) transaction, specifically when trying to process an "Account statement." This error can arise from various causes, and here are some common reasons along with potential solutions:
  Causes:
  
  Incorrect Configuration: The OFX settings in SAP may not be configured correctly, leading to issues when processing bank statements.
  Data Format Issues: The data being sent or received may not conform to the expected OFX format, causing parsing errors.
  Bank Connectivity Issues: There may be connectivity problems with the bank's OFX server, preventing successful transactions.
  Authorization Issues: The user or system may not have the necessary permissions to access the bank account or perform the transaction.
  Bank Statement Format: The bank statement file may be in an unsupported format or contain unexpected data.
  
  Solutions:
  
  
  Check Configuration:
  
  Verify the OFX configuration settings in SAP. Ensure that the bank details, connection settings, and file formats are correctly set up.
  Review the settings in transaction code FBZP (for payment processing) and FBZ1 (for bank statement processing).
  
  
  
  Validate Data Format:
  
  Ensure that the OFX file being processed adheres to the required format. You can use an OFX validator tool to check the file for errors.
  If you are generating the OFX file from another system, ensure that it is correctly formatted according to the OFX specifications.
  
  
  
  Test Bank Connectivity:
  
  Check the network connection to the bank's OFX server. You can perform a test connection to ensure that the server is reachable.
  If there are known issues with the bank's server, contact the bank for support.
  
  
  
  Review User Permissions:
  
  Ensure that the user account being used to perform the transaction has the necessary authorizations. Check roles and permissions in SAP to confirm access rights.
  
  
  
  Examine Bank Statement:
  
  If you are importing a bank statement, review the contents of the statement for any anomalies or unsupported data types.
  If possible, obtain a new copy of the bank statement from the bank and try processing it again.
  
  
  
  Check SAP Notes:
  
  Look for any relevant SAP Notes or updates that may address this specific error. SAP frequently releases patches and updates that can resolve known issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FBZ1 (for bank statement processing) and FBZP (for payment processing).
  SAP Support: If the issue persists, consider reaching out to SAP support for further assistance. Provide them with detailed error logs and any relevant configuration settings.
  Documentation: Review SAP documentation related to OFX transactions and bank statement processing for additional guidance.
  
  By following these steps, you should be able to identify the cause of the FBZI352 error and implement a suitable solution.