Skip to Content
avatar image
Former Member

Third Party AAK Installation Conflict


As a SAP Partner ISV we deliver our software via AAK. Over the years, our portfolio has grown and we deliver different products with the same namespace, hence one software component. We now need to deliver each product as it's own software component. Namespaces are reserved, new AAKs are created, so no problem...

However, when a product is already installed on a customer system, we get a conflict message in SAINT for each development package .

Conflict with other Add-On-Software Component(<OLD>, Package/DevClass /old/xxx)

I've searched for hours for a solution.

One community post from 2008 came close, but doesn't appear to be resolved.

Conflict Resolution Transports also don't appear to be the answer. According to the AAK 5.0 guide

"Conflict resolution transports (CRTs) are not required for non-modifying development Projects."

So what options do we have, for changing the software component of our already installed products?

Any help would be greatly appreciated.

Rob Shandley

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Dec 07, 2016 at 02:05 PM

    Hello Rob,

    I have not yet understood completely your current setup.

    Have you delivered unintentionally old content with the old namespace in the new Add-On?

    Does the new Add-on have the same software component name as the old one?

    Nevertheless you have different options in order to circumvent your issue.

    Case 1. Old Add-On can be an optional prerequisite for the new Add-on.

    You can define an optional import conditions between the Add-Ons. It has to be maintained for both Add-Ons.You can deliver the new conditions via an ACP if required.

    - see documentation below

    Case 2. New Add-on replaces the old Add-On. But it does not delete it.

    You can define a Delete conditions. The new Add-On will replace the old one. But the old content stays in the system.

    - see documentation below

    Case 3. Old Add-On is removed and then the new Add-On with all dependent Add-Ons are installed.

    You have to test and verify, whether the old Add-On can be uninstalled. This will also delete customer data in the system.

    with kind regards,

    Thorsten Scheyter (AAK Development Support)

    *------------------------------AAK Documentation-------------------------------------------------------*

    • If you would like to specify that a component in a certain release can exist (but does not have to), specify the component and release, and select O(ptional).

    You can only use the O option for the following package types:

    • AOI (Add-On Installation Packages)
    • AOU (Add-On Upgrade Packages that were not included in the SAP system upgrade)
    • AOX (Add-On Exchange Packages)
    • If you want to delete the administrative information of the component during the import procedure, enter the component and an asterisk (*) (release-independent) for the release and choose the option D(elete).

    You can use the D option only for the following package types:

    • AOI (Add-On Installation Packages)
    • AOU (Add-On Upgrade Packages that are not included in the SAP system upgrade)
    • AOX (Add-On Exchange Packages)
    • CSP (Component Support Packages; only with SDA administration authorization)

    Note: You can use the D option if, for example, you change the name of your component or want to merge two components together. Note that only the administration information for the component is deleted from the system by using this import condition. To also delete the objects of the components to be deleted from the system, you have to deliver these as deletions with the new component. (See also Add-On Assembly Kit documentation.)

    When the package is imported, the Add-On Installation Tool behaves as though you had selected O. If the entered component exists, the package is imported and the administrative information is deleted. The system does not check for conflicts with the specified component. If the component does not exist, the package is imported too.

    If you want to ensure that the component is only deleted in a specific release or from a minimum release status, you can also enter the component (and release) with the options T or M. Note that the packages cannot be imported in this case if the component does not exist in the system.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 05, 2017 at 01:02 PM

    Hello Thorsten,

    Again, many thanks. We used the D option and it works perfectly.

    You refered to the AAK Documentation in you answer. We have the Public User Guide:

    SAP Add-On Assembly Kit 5.0 Support Package 1.1

    Document Version: 1.0 – 2016-05-23

    I find no mention of these options in the User Guide.

    Is there another version of the AAK Documentation?


    Rob Shandley

    Add comment
    10|10000 characters needed characters exceeded