Creating a system copy: Procedure for AEB add-ons for SAP®

If you copy an SAP source system to another SAP target system, some settings and data from the source system are usually copied as well. This article describes the procedure for copying the production system to a test system as an example. The instructions also apply to copying other SAP systems with AEB add-ons for SAP.

With regard to the AEB add-ons for SAP, please note the following:

1. First, deallocate all AEB jobs.
2. The connection settings that were set up in the customizing of the add-ons (SM59 or SOAMANAGER) must be changed after copying. Only then do these refer to connected test systems and no longer to a connection to the production system that may have been copied.
   • Note: Both the connection user and the password for the test system must be used.
     If you are still using the Connectivity Service, it is sufficient to change the connection in SAP to the test connection maintained there. In this case, the connectivity service must be restarted so that the connection is re-established correctly.
3. If a server group with the logon group /AEB/DEFAULT was created in transaction RZ12, check whether the assignment is still correct after the copy. It may be necessary to switch to the correct instance here. The status should then be green.
4. Product-specific information on AEB applications:
   
   • In the Trade Compliance Management Add-on for SAP, the client and the profile may need to be adjusted in Customizing under Connection. This is only necessary if you use different clients in the test and production systems.
   • For the Customs Management Add-on for SAP, a reset of the add-on must also be carried out in the test system.
     Depending on the operating variant used, use the /AEB/AA_ET_RESET report (legacy interface) or the /AEB/AES_ET_RESET report (Customs Management interface).
     To find out which operating variant you use, see the article Customs Management Add-on for SAP®: Types of interfaces.
   • Note: The report can only run in the foreground and may only be executed in the test system. If this report does not run successfully, please contact AEB Support.
5. Schedule all AEB jobs again.