Do you have any question about this error?
Message type: E = Error
Message class: FB - Batch Programs
Message number: 738
Message text: Program termination: DTAUS file already imported; see long text
This DTAUS file was already imported at an earlier stage.
Since only data for a single account statement can be contained in a
DTAUS file, the program is terminated.
No data was imported into the bank data clipboard by this program run.
No postings were generated.
Error message extract from SAP system. Copyright SAP SE.
FB738
- Program termination: DTAUS file already imported; see long text ?The SAP error message FB738 indicates that there is an issue with the DTAUS file import process. Specifically, it means that the DTAUS file you are trying to import has already been processed in the system. This can happen if the same file is imported multiple times, leading to a program termination.
Cause:
- Duplicate Import: The most common cause of this error is that the DTAUS file has already been imported into the system. SAP tracks the import status of DTAUS files, and if it detects that the same file has been processed, it will raise this error.
- File Identification: Each DTAUS file has a unique identifier. If the system recognizes that the identifier of the file being imported matches one that has already been processed, it will prevent the import to avoid duplication.
Solution:
- Check Import Status: Verify if the DTAUS file has already been imported. You can do this by checking the relevant transaction codes (like FBPM or FBL1N) to see if the transactions related to the DTAUS file are already present in the system.
- Use a Different File: If you need to import a new DTAUS file, ensure that it is a different file with a unique identifier. You may need to generate a new DTAUS file from your source system.
- Review Long Text: The error message suggests checking the long text for more details. You can do this by clicking on the message or using transaction SE91 to look up the message and its long text for additional context.
- Consult Documentation: Review SAP documentation or help resources for more information on handling DTAUS files and the import process.
Related Information:
If the problem persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP's support portal for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FB737
No G/L account entered for & & & in bank account management
What causes this issue? You must maintain a G/L account in company code &v1& for house bank &v2& account ID &v3& to run this ...
FB736
Bank account management has no entry with bank key & and account &
What causes this issue? Bank account management has no entry with bank key &V1& and account number &V2&.System Response The system i...
FB739
Table T049E: & &: Specify offset and length of document number
What causes this issue? Length or offset of the document number are not maintained in the ISR table (T049E).System Response The system issues an err...
FB740
Company code & does not exist in table T001
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.