Presenter: Fahrettin Kerem Bozbıyık

1. Installation of
Custom CIC Certified Add-On client systems
Fahrettin Kerem BOZBIYIK
April 28, 2018

2. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 2Confidential
Agenda
• What is AAK ?
• Certified Add-On Creation Pre-Requisites
• System Landscape for Add-On Development
• Creating an Add-On
• SAP CIC Certification Process
• Checklist items before Add-On Installation
• Add-On installation experiences on client systems
• Hints & Useful reports for Add-On’s
• Q & A

3. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 3Confidential
SAP Add-On Assembly Kit (AAK)
• What is AAK ?
SAP Add-On Assembly Kit to develop industry-specific, country-specific, or enterprise-specific enhancements to
the standard SAP system, plus customer and partner projects, while taking advantage of the full range of add-on
techniques.
SAP Add-On Assembly Kit provides you with a toolset that supports you throughout the entire software lifecycle of
your add-on.
• This toolset named as “Software Delivery Composer”

4. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 4Confidential
Software Delivery Composer Infrastructure & Package Types
SAP ECC Gateway SAP SRMSAP CRM
 Software
ComponentRelease
DevelopmentsBC Sets
UPINS
Delivery .PAT
file
CRTPATCH
AOFTOOLS (AAK 4.0/5.0)
SOFTWARE DELIVERY ASSEMBLER
ACP: Attribute
Change Package
AOI: Add-On
Installation
Package
AOP: Add-On
Support Package
AOU: Add-On
Support Package
AOX: Add-On
Exchange
Package
CRT: Conflict
Resolution
Transport
CSP: Component
Support Package

5. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 5Confidential
Certified Add-On Creation Pre-Requisites
• Become a SAP Partner
• Purchase a development namespace from SAP ICC
• Development and Consolidation systems (min 2 systems connected via TMS)
• AOFTOOLS Add-On must be installed where the .PAT files extracted system (Consolidation system)

6. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 6Confidential
Development namespace
• Development namespace

7. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 7Confidential
AOFTOOLS Add-On overview on consolidation system
• AOFTOOLS Add-on must be installed by Basis team in order to create an Add-On on consolidation system

8. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 8Confidential
System Landscape for Add-On Development
For each add-on release and each supported SAP release, you require two system for add-on
development:
 A development system (for software development and documentation and customizing)
 A consolidation system (for translation and delivery. Do not make repairs or customizing settings here.)
Create a consolidation route from the development system to the consolidation system and schedule regular

9. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 9Confidential
Setup of the Further Development Landscape for the Non-Modifying
Add-On

10. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 10Confidential
Creating an Add-On
• Add-On Creation steps

11. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 11Confidential
Creating an Add-On
• Custom Add On (AAK Delivery) = ABAP Objects + BC Sets
• = Development requests + Customizing Requests

12. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 12Confidential
BC Sets
• BC Set is a management tool that allows user to record, save and share customization settings
BC Set Creation: Tcode: SCPR3

13. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 13Confidential
BC Set Overview

14. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 14Confidential
BC Sets Activation
• Tcode: SCPR20

15. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 15Confidential
BC Sets Activation Logs
• Tcode: SCPR20PR

16. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 16Confidential
Content of SAP Tables vs New Tables on BC Sets
SAP Tables
If you want to deliver entries in SAP tables, use BC
Sets.
If you deliver table entries directly, without using BC
Sets, this counts as a modification that cannot be
adjusted.
These entries can be overwritten at any time and
without warning in your system and in the customer
system by SAP support packages or upgrades.
New (Custom) Tables
If you want to create a new table, make sure that you
assign it the correct delivery class. The delivery class
specifies the transport behavior of tables. Only tables in
the delivery classes E, G, and C support BC Sets.

17. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 17Confidential
Creating an Add-On
• Add-On Creation steps & sequence

18. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 18Confidential
Creating an Add-On
• Tcode: SSDC – Software Delivery Composer

19. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 19Confidential
Creating an Add-On
• Sample Delivery:
• Version: 200_740

20. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 20Confidential
Creating an Add-On
• Result of Object List Check of Add-on
• Version: 200_740

21. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 21Confidential
Creating an Add-On
Tcode: SSDA - Software Delivery Assembler
.PAT file (EPS File):

22. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 22Confidential
Creating an Add-On
Tcode: SSDA - Software Delivery Assembler
.PAT file (EPS File):

23. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 23Confidential
Creating an Add-On
Important Add-On Attributes:
o Extended Attributes: *REINSTALL_ALLOWED parameter is so important. If it is not set “T” you can not remove the Add-on
on the system.

24. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 24Confidential
Creating an Add-On
Important Add-On Attributes:
o Import Conditions: *VALUE parameter is so important. If it is set “M” that Add-On can install minimum level regarding
components on the client system.

25. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 25Confidential
CIC Certification Process and Mandatory Checks by Test Plans
• SAP CIC examine the custom Add-On via test plans.
• Test plans consist of 2 types of checks:
• 1) Syntatic Requirements and Checks
• Requirements
• Modifications
• Enhancements
• Database Tables and using SAP Objects
• Customizing
• Documentation
• Installation
• Performance
• 2) Semantic Requirements and Checks
• Test Cases (Business Scenario Dry Run with SAP ICC Consultant)
• PPMS Data Collection (The partner is required to fill out the provided PPMS data sheet.)

26. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 26Confidential
SAP CIC Certification Process
SEND Add-
On to ICC
• .PAT file
• Documentation
SAP ICC
Answer to
Partner
• Confirmation of
Add-On
• Success or Not
Success
SYNTATIC CHECK
• Modifications
• Enhancements
• Hard Code Check
• Repair Check
• Running SCII – Code
Inspector
SEMANTIC
CHECK
• Test Cases
• PPMS Data
Collection
Add-On Evaluation
by SAP ICC
• Add-On test report
execution by SAP ICC
Evaluation

27. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 27Confidential
The most important things during SAP Certification
• Add-On could not have modifications standart SAP objects such as repair !
• Therefore, no modifications / changes to the standard functionality are allowed, including modify Basis objects,
delete or rename core objects. This is checked automatically by the AAK.
• Within Add-on ABAP programs/includes/BADI/class etc. could not have hard code values such as IV_VKORG =
1000. “1000” constant within the include is not acceptable by SAP ICC !
• Therefore there would be a hard code parameterization structure on the Add-on in order to read constants and
customizing values accordingly.

28. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 28Confidential
SAP CIC Certification Confirmation

29. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 29Confidential
Checklist items before Add-On Installation
• 1) SCC4 client parameters settings: 000 client

30. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 30Confidential
Checklist items before Add-On Installation
• 2) SE03  Set System Change Option Namespace Prefix would be X – Modifiable

31. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 31Confidential
Checklist items before Add-On Installation
• 3) SE03  Display/Change Namespaces: Namespace Role have to be “C – Receipt”. Otherwise you
could not finished up Installation Package steps on SAINT.
•

32. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 32Confidential
Checklist items before Add-On Installation
• 4) SAINT transaction should be run on the background without DDIC or SAP* users

33. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 33Confidential
Add-On installation experiences on client systems
• Check out the the minimum Software Component
Release between client system and Add-On
• Client System:
Add-On Minimum Release for Software Component
have to compatible with client system release.
Otherwise installation could not complete on SAINT !

34. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 34Confidential
Add-On installation experiences on client systems
• Pricing objects have not to be in the ECC Add-On such as:
• Pricing conditions, access sequences, condition tables pricing procedures, field catalogs etc. (VOK0)
• For these pricing objects should be created under different Add-On or developing a custom switch SFW5 –
Switch Framework: Business Functions !

35. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 35Confidential
Add-On installation experiences on client systems
• If you create a custom Add-on and clients have a SAP CRM system:
• Do not include the Web UI configurations (Screen configurations) into CRM Add-On. Unfortunately
there is no transport !

36. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 36Confidential
Add-On installation experiences on client systems
• Do not include the conditions for actions (Action configurations) into CRM Add-On. Unfortunately
there is no transport !

37. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 37Confidential
Add-On installation experiences on client systems
• Set type and attributes on CRM system (Tcode:
COMM_ATTRSET)
• Set types have to be created under Z* namespace.
(Namespace is not accepted by the system)
• Furthermore attribute set creation on client CRM
system have to done before the Add-on installation
eventually !
• Otherwise Add-On installation would be getting error
!

38. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 38Confidential
Add-On installation experiences on client systems
• Fiori side, Gateway system is not allowed to make deploy on client system belong to namespace
apps.

39. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 39Confidential
Add-On installation experiences on client systems
• Fiori side, do not take into consideration LPD_CUST and /UI2/SEMOBJ Launchpad customizings
within Add-On
• Launchpad customizings should be done manually on client systems

40. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 40Confidential
Q & A
• Q & A