Purpose
This document defines the meaning of WRICEFUM and how it is applied in conjunction with SAP’s Clean Core principles.
Summary
The WRICEFUM is a center piece to manage, track and measure custom development requirements. Clean Core principles need to be applied to each WRICEFUM object based on feasibility.
WRICEFUM Definition
WRICEFUM stands for
- W – Workflow
- R – Report
- I – Interface
- C – Conversion
- E – Enhancement
- F – Form
- U – UI
- M – Metric
It is SAP’s classic way of categorizing custom requirements. It is a 4 to 5 digit number.
Sample: U-1234
The WRICEFUM will be used in the functional design (FD) document title, the development package name and needs to be assigned in all L5 business process steps in Signavio.
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:
Tier 3: Classical ABAP development (deprecated legacy code with exceptions where still required).
Tier 2: Cloud API enablement (custom wrapper to use unreleased APIs in Tier 1).
Tier 1: On-Stack (Developer Extensibility) and Side-by-Side (BTP ABAP Environment) with full ABAP Cloud compliance.
ABAP Cloud is the programming model for cloud compliant custom developments. Implementing with ABAP Cloud ensures that the code will be considered clean core and is upgrade stable.
3 Tier Technology Mapping
Based on the above definition of clean core the following table contains the main development tools and approaches used categorized as tier 1/2/3.
Tier 1 | Cloud ready / Cloud native |
Workflow | SAP Build Process Automation / Flexible Workflow |
Report | Fiori Elements Report / SAC Report (with Datasphere integration) |
Interface | Standard integration proxies and services in S/4HANA / Custom released APIs |
Conversion | Standard Migration Cockpit objects |
Enhancement | Released Badi / UI Adaptation project / Key User UI Adaptation / ABAP Cloud / Custom Application Job |
Form | Adobe Form with Fragments |
UI | Fiori UX with RAP based service in backend / Web App on BTP with RAP based service in backend |
Tier 2 | Cloud enabled / Clean Core / mandatory use of legacy tech |
Workflow | N/A |
Report | Business Objects Report / KPI report / AFO Report |
Interface | Custom web service proxy object in S/4HANA |
Conversion | Custom Migration Cockpit object |
Enhancement | Tier 2 wrapper / Unreleased Badi / Customer exit / Routine exit / Standard (Web) Dynpro enhancement |
Form | Classic Adobe Form |
UI | Fiori UX with existing Gateway service and clean core compliant code |
Tier 3 | Classic |
Workflow | Business Workflow |
Report | ABAP Report with custom transaction code |
Interface | ABAP Program with direct service calls |
Conversion | LSMW / ABAP Load program |
Enhancement | Implicit Enhancement / ABAP Program with user access / Dynpros |
Form | SAP Script / Smartform |
UI | Custom ABAP dynpro / Custom Web dynpro |
WRICEFUM Request
Each business process step that requires a custom development in S/4HANA or GTS will need to classify the WRICEFUM type and the clean core tier.
Tier 3 needs to be justified in detail before approval. It is legacy and considered deprecated, but in certain circumstances classic ABAP development must be used due to lack of clean core replacements.
Tier 2 needs to be justified in detail before approval. SAP is still adding clean core compliant APIs and enhancements each release and using tier 2 offers the needed flexibility to achieve the successful implementation of a business requirement.
Tier 1 is clean core compliant and upgrade stable. No detailed justification is needed.
All tier 2 and 3 WRICEFUMs will be logged in a deviation tracker and need to be revisited during upgrades to see if a clean core compliant replacement is available.
Custom developments in SaaS systems do not require a WRICEFUM.
WRICEFUM Count
Every S/4HANA or GTS custom development requires a WRICEFUM. All will be counted. SAP considers all custom code as a core change. The type of WRICEFUM is irrelevant.
Standard interfaces or workflows require a WRICEFUM and FD to describe the business requirement and to cover the needed technical configuration. These will not be counted.