Importing AEB components via transports

Please pass on the following notes to the base administrators of your SAP system:

Do not import any transports if the AEB components have already been imported into the SAP system using the add-on installation tool (SAINT or SPAM). Otherwise, the system will be in an inconsistent state.

Only download the product-specific files that are relevant for your SAP system according to the AEB consistency check (/n/AEB/CONSISTENCY transaction). Otherwise, unwanted version changes may occur. Due to different SAP systems in your landscape or ongoing projects, transports may be displayed for download that are not relevant for the respective SAP system. Contact AEB support if you have any questions on this.

Deactivate all jobs that run /AEB programs before running the import, as blocking problems and program terminations could otherwise result.

Never import AEB components to the SAP production system if data and documents are still being created, as the program may be terminated or locking-problems could otherwise result.

In this context, also check the optimization described in SAP Note 1454536.

The current transports are cumulative, i.e. they always contain the complete status of the base and the respective product. When updating, it is therefore sufficient to only import the latest transports.

Downloading AEB transports

  1. Log in to the AEB Download Center with your user and password.

    2. Contact your AEB representative if you do not have login data yet.

  2. Select Add-ons for SAP®.
  3. Select one of the following categories matching your SAP version:
    – SAP ECC 6.0: Transports
    – SAP S/4HANA from 2020: Transports
  4. Download the file for the "Base - Build" as well as the product-specific files that are relevant for your SAP system according to the AEB consistency check (transaction /n/AEB/CONSISTENCY).
  5. Copy the unzipped files to the central transport directories:

Adding transport requests to the queue

  1. Click on the truck icon in the STMS_IMPORT transaction. This is how you get to the import overview window.
  2. If the transport is not immediately visible in the import overview: Add it via Extras – Other requests – Add.

Importing requests

  1. Select the request and go to Request – Import (not: Queue – Import).
  2. Select target client
  3. In the Options sheet, activate the option Ignore non-matching component version.
  4. Then run the import.

Completely import all downloaded transports (basis and the product-specific transports) in order that all solutions remain functional. However, pay attention to the order, i.e. always import in the basis transport first.

Once this has been completely imported without errors, you may import the other product-specific AEB transports in any order or simultaneously.

Only after the product transports, install any service packs available for this transport status. Pay attention to which build the respective service pack requires.