There are two inactive company codes in the customer development system. To increase system performance, both company codes must be deleted. The deletion includes the transaction and master data (G/L accounts, customers, vendors and assets) as well as all the customizing settings with the corresponding dependencies. The sequence of the data to be deleted must be observed.
The prerequisite for deleting transaction and master data is removing the productive indicator in Customizing. The first step is to check the scope of the transaction data for all areas (G/L accounts, debtors, vendors, assets) using the appropriate tables. SAP offers standard transactions for deleting transaction data, in which a test run is started beforehand and the transaction data to be deleted is checked. The same procedure takes place in the second step with the master data of the respective areas. If these two data types are completely deleted, the customizing settings can be deleted in the third step. Each organizational unit has its own standard deletion program. It is important to ensure that both company codes use a common controlling area. The prerequisite for deleting the controlling area is that you archive the account assignment objects and then delete them.
The deletion process only takes place in the customer's development system. Since the two company codes are inactive and contain large amounts of data, it is advantageous to remove these two company codes in order to improve system performance.