Do you have any question about this error?
Message type: E = Error
Message class: FB - Batch Programs
Message number: 797
Message text: Format error with DTAUS format; see long text
While importing the DTAUS format, an "A" record was imported without
the previous "A" record being closed by an "E" record.
Therefore check your input file and request a correct DTAUS file from
your credit institution.
Error message extract from SAP system. Copyright SAP SE.
FB797
- Format error with DTAUS format; see long text ?The SAP error message FB797 indicates a format error with the DTAUS format, which is used for electronic bank transfers in Germany. This error typically arises when there is an issue with the data being processed for the DTAUS file format, which is used for creating payment files for bank transfers.
Causes of FB797 Error
Incorrect Data Format: The data being processed may not conform to the DTAUS format specifications. This could include incorrect field lengths, invalid characters, or missing mandatory fields.
Configuration Issues: The configuration settings for the DTAUS format in the SAP system may not be set up correctly. This includes settings in the payment program or the house bank configuration.
Invalid Bank Details: The bank details (such as account number, bank identifier, etc.) may be incorrect or not properly maintained in the system.
Special Characters: The presence of special characters or unsupported characters in the payment data can lead to format errors.
Data Length Exceeding Limits: If any of the fields in the payment data exceed the maximum length allowed by the DTAUS format, it can trigger this error.
Solutions to FB797 Error
Check Data Format: Review the payment data being processed to ensure it adheres to the DTAUS format specifications. Pay attention to field lengths and data types.
Review Configuration: Verify the configuration settings for the DTAUS format in the SAP system. Ensure that the payment program and house bank settings are correctly configured.
Validate Bank Details: Ensure that all bank details are correctly maintained in the system. Check for any typos or incorrect information in the vendor or customer master data.
Remove Special Characters: If there are any special characters in the payment data, remove or replace them with valid characters.
Adjust Data Lengths: Ensure that the lengths of all fields in the payment data do not exceed the limits specified for the DTAUS format.
Test with Sample Data: If possible, create a test payment run with sample data that is known to be correct to see if the error persists.
Related Information
SAP Notes: Check SAP Notes for any known issues or patches related to the DTAUS format and the FB797 error. SAP frequently updates its knowledge base with solutions to common problems.
Documentation: Refer to the SAP documentation for the payment program and DTAUS format for detailed specifications and guidelines.
Transaction Codes: Use transaction codes like FBZP (Payment Program Configuration) and OBPM1 (House Bank Configuration) to review and adjust settings related to the payment program.
Debugging: If the issue persists, consider debugging the payment program to identify the exact point of failure in the data processing.
By following these steps, you should be able to identify and resolve the FB797 format error in SAP.
Get instant SAP help. Start your 7-day free trial now.
FB796
Field & contains the invalid value &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FB795
DTAUS data record A: Invalid value in field 3: &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FB798
Format error with DTAUS format; see long text
What causes this issue? While importing the DTAUS format, an "E" record was imported although until that time no "A" record had b...
FB799
Format error with DTAUS format; see long text
What causes this issue? A data record which is neither an "A" record, nor a "C" record nor an "E" record was imported i...
Click on this link to search all SAP messages.