Do you have any question about this error?
Message type: E = Error
Message class: AU - FI-AA utility program error messages
Message number: 171
Message text: RAALTD11 cannot be started in a Unicode system
You tried to start RAALTD11_NONUNICODE in a Unicode system. However,
the RAALTD11_NONUNICODE report is not Unicode-capable.
The program terminated.
Use the RAALTD11_UNICODE report instead. Or you can use the BAPI for
legacy data transfer, BAPI_FIXEDASSET_OVRTAKE_CREATE, or transfer
legacy data usisng Excel with transaction AS100.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
AU171
- RAALTD11 cannot be started in a Unicode system ?The SAP error message AU171, which states "RAALTD11 cannot be started in a Unicode system," typically occurs when you attempt to run a program or report that is not compatible with Unicode systems. This error is related to the use of the ABAP program RAALTD11, which is used for generating the payroll results.
Cause:
- Non-Unicode Compatibility: The program RAALTD11 is designed for non-Unicode systems and cannot be executed in a Unicode environment. This is a common issue when legacy programs or reports are still being used in a Unicode SAP system.
- System Configuration: The system may have been upgraded from a non-Unicode to a Unicode version, and certain programs have not been updated to support Unicode.
Solution:
- Use an Alternative Program: Instead of RAALTD11, you should use the Unicode-compatible version of the program or report. For payroll processing, you might want to look for a different report or transaction that is designed for Unicode systems.
- Check for Updates: Ensure that your SAP system is up to date with the latest support packages and notes. SAP may have provided a Unicode-compatible version of the program or a workaround.
- Custom Development: If no alternative exists, consider developing a custom ABAP report that replicates the functionality of RAALTD11 but is compatible with Unicode.
- SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this issue. There may be specific notes that provide guidance or patches for this error.
Related Information:
If you continue to experience issues, consider reaching out to your SAP Basis or ABAP development team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
AU170
XPRA Report RAIXPR05 - update of &1 records completed successfully
What causes this issue? &1 appropriation requests, for which there is no ID that uses a coding mask, were found in the database. For these record...
AU169
XPRA Report RAIXPR05 completed successfully
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
AU172
Report date is in a closed fiscal year
What causes this issue? The report date is in the past. Here the report date is allowed to be the end of the year as well as any period end during th...
AU173
Account '&2' could not be determined for area &3
What causes this issue? The system could <ZH>not</> find account '&V2&' for company code &V1& and depreciation ...
Click on this link to search all SAP messages.