Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: FINS_ACDOC_CUST - Unified Journal Entry - Customizing
Message number: 470
Message text: This report cannot be used in a production system.
In a production system, you cannot use this report to update existing
transactional data with the currency key and amounts for a new currency.
The <LS>Manage Currencies</> tool allows you to introduce new, flexible
currencies for company codes and ledgers that are already used in your
production system.
Note: This tool can handle only currency types that not CO relevant.
This means that it can handle only currencies that are not written to
the BSEG document table and that don't belong to the CO currency types.
Start your currency introduction project using the
<DS:SIMG.FINSVC_IC_PROJ>Create Project for Managing Currencies</>
activity.
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.
FINS_ACDOC_CUST470
- This report cannot be used in a production system. ?The SAP error message FINS_ACDOC_CUST470 indicates that a specific report or transaction cannot be executed in a production environment. This is a common restriction in SAP systems to prevent untested or development reports from being run in a live production environment, which could lead to data inconsistencies or other issues.
Cause:
- Development vs. Production Environment: The report or transaction is likely still in a development or testing phase and has not been approved for use in the production environment.
- Configuration Settings: The system may have been configured to restrict certain reports from being executed in production to ensure data integrity and stability.
- Authorization Issues: The user may not have the necessary authorizations to run the report in the production environment.
Solution:
- Check Report Status: Verify if the report is still in development or testing. If it is, you may need to wait until it has been properly tested and approved for production use.
- Transport Request: If the report is ready for production, ensure that it has been transported from the development environment to the production environment using the appropriate transport requests.
- Authorization Check: Ensure that the user has the necessary authorizations to execute the report in the production environment. This may involve checking user roles and permissions.
- Consult with SAP Basis or Security Team: If you believe the report should be available in production, consult with your SAP Basis or security team to review the configuration settings and user authorizations.
Related Information:
If the issue persists after following these steps, it may be beneficial to reach out to SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
FINS_ACDOC_CUST469
This system is a Cloud system; no updates were run.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_ACDOC_CUST468
Acctg princ. &3 of ledger &1 doesn't match acctg princ. &4 of CoCode &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_ACDOC_CUST471
Changes to FI currencies are not allowed for productive company codes.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FINS_ACDOC_CUST472
New GL is not active, use of universal journal not possible
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.