How To Fix BFIBL02310 - Prefix and trans. record separator entered although prefix is not active

SAP Error Message - Details

• Message type: E = Error

• Message class: BFIBL02 - Payment Medium: Messages

• Message number: 310

• Message text: Prefix and trans. record separator entered although prefix is not active

What causes this issue?

You entered a character for the separation of the prefix from the
following transaction record despite the fact that output of the prefix
is inactive.

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?

Switch output of the prefix to active (field <DS:DE.PAYMHEAD_FPM>SWIFT
MTxxx create prefix</>) if you want to keep the separator.

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 BFIBL02310 - Prefix and trans. record separator entered although prefix is not active ?

  The SAP error message BFIBL02310 indicates that there is an issue with the configuration of the bank file format, specifically related to the prefix and transaction record separator settings. This error typically arises when the system expects a prefix to be active, but it is not configured as such.
  Cause:
  
  Inactive Prefix: The error occurs when a prefix is defined in the bank file format settings, but it is not activated. The system is trying to process a file that includes a prefix, but since the prefix is not active, it leads to this error.
  Configuration Mismatch: There may be a mismatch in the configuration settings for the bank file format, where the prefix and transaction record separator are not aligned with the expected settings.
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Check Bank File Format Configuration:
  
  Go to the transaction code OBPM1 (or the relevant transaction for your version) to access the bank file format configuration.
  Look for the specific bank file format that is being used and check the settings related to the prefix and transaction record separator.
  
  
  
  Activate the Prefix:
  
  If a prefix is defined but not active, you need to activate it. Ensure that the prefix is correctly configured and marked as active in the settings.
  
  
  
  Adjust Settings:
  
  If the prefix is not needed, you can remove or deactivate the prefix from the configuration to align with the file being processed.
  Ensure that the transaction record separator settings are consistent with the prefix settings.
  
  
  
  Test the Configuration:
  
  After making the necessary changes, test the configuration by processing a sample bank file to ensure that the error does not occur again.
  
  
  
  Consult Documentation:
  
  If you are unsure about the settings, refer to the SAP documentation or help resources for guidance on configuring bank file formats.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBPM1 (for bank file formats) and OBPM2 (for bank master data).
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  Support: If the problem persists after following the above steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  By following these steps, you should be able to resolve the BFIBL02310 error and ensure that your bank file processing works correctly.