- SAP Managed Tags:
The "Reset Transaction Data" Job, that is part of the "Schedule Accounting Data Changes" App, deletes the financial postings (e.g. Financial Documents, Controlling Documents, etc.) in your Development or Test systems. Please note that it's not possible to run this App in a Productive environment.
Some configuration changes are not allowed if you have financial data, including the following:
- Want to change the assignment of Accounting Principle to Ledger
- Delete the Fixed Assets data since you have transferred legacy data (e.g. Fixed Assets) with errors to the T/Q system
- Create additional Currency Types
- Renumber G/L Accounts when you have postings in Test (3SL) or Quality (2SL). Note: Accounts that have postings in Production can't be renumbered but Reset Transaction Data can help you to remove the restriction if the accounts just have postings in the Test/Quality System.
The execution of this App has an IMPORTANT impact to the system transactional data. Please do NOT run this process without reviewing with your Business Users and Project Management Team.
Key Considerations
Please take into account the following considerations:
- This process is only available in the Test and Quality Systems (NOT available in Production!)
- In order to change configuration it in Test/Quality there should NOT be postings in the Productive environment.
- You have to delete the data from all company codes in your Development and Test systems.
- Material Stock must be booked out in the last two MM Periods. If there are pending movements before the last two MM Periods the inventory must be removed (e.g. scrapped). When the system has inventory then you'll receive the Error message "Material stock (company code xxxx) must be booked out in last two MM periods". Please refer to the following KBA that explains what's needed to remove the error message: https://me.sap.com/notes/3084794
What Does the App Do
This App will delete all the Journal Entries in the system. Please note that the original documents that created the Financial Posting will NOT be deleted (e.g. Purchase Order, Sales Order, etc.). This process will just remove the underlying Financial Document in the specific step(s) where a Financial Posting is recorded (e.g. Goods Receipt of a Purchase Order, Invoice in a Sales Order, etc.).
AGAIN! This has a high impact since the previously created transactional objects will lose the underlying Financial Document. Once the job is run there is no way to Undo the execution.
How To Execute the Process
With all those caveats and warnings shared, this is the sequence of steps that you have to follow to Execute the Process:
Schedule Accounting Data Changes Job
What happens with the Transactional Objects Previously Created
Here are some examples of what would happen to some of the Key Transactional Objects after the execution:
- Invoice
The journal entry has not yet been created
- Goods Receipt
Good Receipt - No Subsequent document found in Accounting
What Happens After the Execution of the Job
After all the financial postings have been removed and if the pre-requisites mentioned have been met (e.g. no postings exist in Production), the relevant configuration can be updated.
Additional Info
Please refer to the following SAP Help link for additional info:
https://help.sap.com/docs/SAP_S4HANA_CLOUD/0fa84c9d9c634132b7c4abb9ffdd8f06/5c13ed947bfc449ebc648cf3...
When the system has inventory then you'll receive the Error message "Material stock (company code xxxx) must be booked out in last two MM periods". Please refer to the following KBA that explains what's needed to remove the error message: https://me.sap.com/notes/3084794
Ernesto Cepeda
