Skip to Content
Technical Articles

SAP Add-On Assembly Kit


If you develop industry-, company-, or country-specific enhancements to SAP solutions, the SAP Add-On Assembly Kit can help you plan and deliver those enhancements as software add-ons. The SAP Add-On Assembly Kit guarantees quality software development by using a standardized process flow from planning to delivering the add-on. The delivery tools work smoothly with SAP’s maintenance strategy, helping you integrate new developments into your existing environment and providing maintenance throughout the enhancement’s life cycle.


The SAP Add-On Assembly Kit and its comprehensive documentation help ensure high-quality product development from the planning phase. The add-on tools also help you efficiently install, update, and maintain the enhancement.


The documentation of the SAP Add-On Assembly Kit can be found in the SAP Help Portal.

It is also available as PDF document.

Video Tutorials

1 Reserving a Namespace

2 Reserving an Add-On

3 Creating a Delivery

4 Performing an Object List Check

5 Releasing a Change Piece List

6 Creating a Component Piece List and an Exchange Component Piece List

7 Assembling an Installation Package

8 Installing an Installation Package

9 Creating an Attribute Change Package (ACP)

10 Uninstalling an Add-On via ACP

You must be Logged on to comment or reply to a post.
  • Hello Herald:

    I have successfully created Change Piece.

    Attempting to release Component Piece List and I don’t see the GREEN icon. 

    The issue seem to be that there are two errors under undeletable tables.  I am on AAK 5.0.  How do I get rid of these two errors.  Please help.


  • Hello Mr. Gadde

    1. In general always use the newest available SPAM/SAINT update in your system (SPAM 63)

    2. In your case it is probably sufficient that you update your SPAM/SAINT version in your assembly system and set SPAM/SAINT version 63 as requirement for your Add-On. In case the addon has already been delivery you can deliver the new requirement via an ACP.

    3. In case of uninstallation errors you cannot just get rid of them by deleting the entries. You
    have to understand the content or get in contact with your development. Maybe the corresponding
    object/table entry is required or has to be a part of the final delivery.
    In such a case you have to deliver and provide a Plugin Class. This Add-On specific ABAP class calculates dynamically and decide how the object is handled during uninstallation
    -> Page 90
    with kind regards,
    Thorsten Scheyter

  • Hello Harald,

    thank you for detailed description and videos.

    I have more organizational question.

    I am a freelancer consultant/developer. So actually I was using my customers developer license to solve the problems. Now I am ready to present my own solution and I want to distribute it as an Add-on.

    In order to create add-on with the Add-on Assembly Kit I need a developer license. For this I am about to register a company.

    Please advise what are steps for new company to get a developer license for ABAP and the Add-on Assembly Kit to start distributing the my solution?

    Thank you in advance.

    Best regards,

    Dmitry Istomin



    • Hello Dmitry,

      I would suggest to get into contact with our SAP Integration and Certification Center (ICC) at or via mail: This team provides (besides other services) access to the add-on assembly kit (via a paid license). In how far the use of the ABAP platform itself, i.e. a NetWeaver system, has to be licensed separately I am not sure but I would guess so. Please check with my colleagues from ICC.

      Kind regards


    • Hi Hasnain,


      Thanks a lot for making me aware of this issue. I will change the links in the upcoming days.

      As a temporary workaround please use the only link still working:

      From here you can reach the other documents mentioned above.


      Kind regards



  • Dear all,

    Hasnain has made me aware of (most of) the links not working anymore (Thanks!).

    I have now corrected the links to their new values, so that they should be working again.


    Kind regards



  • Hi Harald,


    I was wondering if you could help me with the following. I’ve created a PAT file for the first version of my development – AOI. If I now want to create a fix / support pack ( AOU ) for the development do I have to create a new release of the software component or do I use the existing release? If I can use the existing release what is the process for creating a PAT file just for the changes?

    Many thanks in advance

    Graham Day




    • Hi Graham,

      I briefly contacted the AAK development team and they would recommend to use for fixes rather Add-On support packages (CSP). The Add-On Upgrade (AOU) type would be used when delivering new features and functionality.

      In my understanding you would not need a new release for a CSP and the PAT files would be created during the step ‘Creating Deliveries’ as described in this SAP help document.

      Kind regards



      • Hi Harald,


        Thanks for the reply, much appreciated. Just have one more question when creating CSP.

        Create Delivery Request (SSDC) with Delivery Type – PATCH Support Package

        1. Create Change Piece List and add the request/s ( just the fixes to the initial Add On Delivery Request)
        2. Create Component Piece List which includes both the fix Change Piece List and the Component List of the original Add On – is that correct? So that Customers who already have the original Add On only need the Change Component while new Customers would need both.
        3. Then in the SDA, would I then create 2 new PAT files – one for Change List fix which would be a CSP and one for the new Component List which has the full new product (AOI)?

        Again thanks is advance for your help,

        Kind regards



  • Hi Harald,

    In case SAP standard add-ons, SAP is restricting through downloading access via S-user license. If we develop custom Add-on and giving to one customer, the customer may give the Add-ons to their own internal/other  customers. How to use licensing model for custom add-ons to avoid redistribution or resell? I may want to generate license key based on installation/customer number and enter it to activate the add-on and it must check installation number and allow to activate the add-on or allow to install. Any options available for this.


    Many thanks,