Deleting Accounts with Existing Postings for Testing Purposes

[Former Member]

I was wondering if there are any implications with deleting accounts with already existing transactions in the scenario that they were setup incorrectly? I know the process is to mark it for deletion and then run a background job to actually delete the account but I wish to further understand the implications of this.

I posted earlier to see if it was possible to transport in accounts from another client to try to obtain the correct settings but received a response that it cannot be done through that method depending on how the account was configured (e.g. auto-posting).

Any insight would be greatly appreciated thanks.

[Former Member · Accepted solution]

Hi

If there are postings for the account I don't believe you would be able to archive it.

Thanks

Anupam

[Former Member]

I guess my final point would be is this a sufficient strategy to use during testing in the DEV and QA clients before loading them into production? This way the client will not need to create a new account if it is initially setup incorrectly during testing.

[Former Member]

Every thing will be messed up in FI and CO

So better dont try this in production

[Former Member]

I guess to re-phrase my question I was wondering what happens if you delete an account that contains postings and then try to recreate it in the same client with different master data settings. Would SAP limit the settings you could use for the 2nd or 3rd time you tried to setup the account? Will the transaction tables for BSEG / FLEXA get messed up in any way? If I need to provide additional information please let me know.