Ansicht
Dokumentation
SIMG_TLS_0011 - Deleting JVA Data
ABAP Short Reference SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
In preparation for converting to a productive system, you may delete all existing data for a JVA company. There are three levels of data that may be deleted:
- Transaction data
- Master data
- Customizing data
These options are dependent on one another in the following way: If you choose to delete transaction data, only expense postings to JVA ledgers will be deleted. JVA master data (JOA's, JV's, equity groups) and customizing data (company configuration, configuration master data, posting rules for JVA processes) for the company will be preserved.
Postings in standard SAP modules that feed data to JVA will not be affected by the deletion of transaction data from the JVA ledgers (see below under Requirements).
If you choose to delete JVA master data, you must also delete transaction data, or have previously done so. This option will also delete references to JVA master data in CO cost objects.
If you choose to delete customizing data for the JVA company, you must also delete both transaction and master data, or have previously done so.
Before deleting transaction, master, and customizing data in JVA, you should first execute the appropriate corresponding tasks for a productive start in feeder systems (i.e., FI, CO, AM). For example, before deleting transaction data from the JVA ledgers, you should first delete the documents in FI that were the source for JVA postings.
Deleting customizing data for a JVA company essentially means deleting the JVA company; therefore, before you can delete JVA customizing data for the company, you must deactivated the JVA ledgers for the company.
CL_GUI_FRONTEND_SERVICES - Frontend Services CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 1966 Date: 20240523 Time: 153240 sap01-206 ( 46 ms )
