...
The Development ID is a centerpiece to manage, track and measure custom development requirements. Development IDs are lower level than WRICEFs to define and document the needed artefacts. Clean Core principles need to be applied to each Development ID object based on feasibility to keep the Total Cost of Ownership for custom developments manageable and explicit.
| Table of Contents |
|---|
Development ID Definition
"WRICEF" was the traditional way of categorizing business requirements that will be implemented with custom development, where each of the letters in the acronym stands for Workflow, Report, Interface, Conversion, Enhancement, and Form, respectively. Typically the letter of the acronym is used in combination with a running number. But in the several decades since this acronym entered into use, SAP development has evolved significantly. There are now many more types of developments which cannot meaningfully be combined into an "Enhancement" and treated equivalently; similarly it is sometimes not easy to assign a meaningful category to a development.
...
- Enhancement (incl. Conversion)
- Form (Output)
- HANA CDS View
- Integration Process (custom)
- Integration Process (standard)
- Metrics/KPI
- Mobile App
- Modification
- Program
- Report/Analytics
- System Interface
- User Interface
- Workflow (custom)
- Workflow (standard)
- Application Job (Custom)
...
Conversions are not required to have a Development ID. The Master Data Register number will be used. A Development ID for conversions is only needed if a custom object, such as a load program, needs to be created.
Examples
For example, a Development Request ID 1234 of type User Interface has been approved. The UI development requires a UI5 app and an oData service. That means 2 Development IDs will be created.
...
Sample: SaaS: 1237 (Type System Interface)
SAP 3 Tier classification in Clean Core
Clean Core is SAP’s concept to achieve modern, flexible and cloud compliant custom solutions. SAP came up with 3 tiers of custom developments:
...
SAP BTP is the platform for SAP SaaS extensions or cross-system processes.
SAP 3 Tier Technology Mapping
Based on the above definition of clean core the following table contains the main development objects and approaches per type of development.
| Type of Development | Tier 1 | Tier 2 | Tier 3 | |
| Conversion (Load only)N/A | Released standard APIs called from Syniti |
| N/A | |
| Conversion (Transform + Load) | N/A |
| N/A | |
| Enhancement |
|
|
| |
| Form (Output) |
|
|
| |
| HANA CDS View | Custom Released CDS entity | N/A | Custom CDS view | |
| Integration Process (custom) |
| N/A | ||
| Integration Process (standard) |
| N/A | N/A | |
| Mobile App | Custom Neptune app (on Open Edition) | Custom Neptune app (on SAP Edition) | N/A | |
| Modification | N/A | N/A |
| |
| Program | N/A | Custom Classic ABAP program to run as part of CLOCO or custom print program for Adobe Forms* | Custom Non CLOCO / print program | |
| Report/Analytics |
|
|
| |
| System Interface |
|
|
| |
| User Interface |
|
|
| |
| Workflow (custom) |
|
| Flexible
| N/A |
| Workflow (standard) |
| N/A | N/A | |
| Application Job | Custom class for Application Job | Custom class for Application Job calling a Tier 2 wrapper | N/A |
- Actually Tier 3, but due to limited availability of Tier 1 alternatives it is considered Tier 2
Non-SAP SaaS Customization Tier classification
For Non-SAP custom development it is also important to stay within the means of provided tools and technologies applying best practices to achieve and maintain a clean core.
The customizations are approached similar to SAP developments and categorized in Tiers if possible.
Salesforce
The two key technologies that are used to enhance the Salesforce standard today are Apex and Lightning Web Components (LWC).
...
Either one of these tools needs to be used with best practices in mind. More details are captured in the Development Guidelines. The Guideline is kept up to date. By applying the Salesforce Development Guidelines only tier 1 and tier 2 classification applies.
Icertis
Icertis as a SaaS system does not allow access to DB and code. Only enhancements allowed are via the provided framework and UI driven.
...
Only the Tier 1 classification is applicable.
Clean Core Deviation tracking
All Tier 2 and 3 Development IDs are logged in the Clean Core Deviation Tracker. During upgrades, these items are revisited to see whether a Clean Core-compliant replacement is available.
...
| S No. | Pod / Functional Area | L3 Process | L4 Process | System | Development Type | Development Id | Requirement title | Priority | Gap Classification | Extension Tier Classification | Technical Details |
Development ID Counting Rules
Every development requires at least one Development Id. SAP considers all custom code as a core change. All development IDs will be counted. The type of it is irrelevant with the following exceptions:
...