
Automatic Quality Control
How Does it Work?

Step 1
Baseline Your System

Step 2
Configure the CoE

Step 3
Set up the Quality Perimeter
The development team will have access to tools to help them confirm to quality standards. Only transports that conform to the quality rules will be allowed to be released.
Step 1
Baseline Your System
A lot of custom ABAP code has been built up over the years to respond to the changing needs of your company. The technology has evolved, development teams have changed, and quality control is becoming more and more important. Establishing a baseline of your ECC or S/4 implementation helps HAWKEYE distinguish between legacy issues and new development, and helps management introduce a quality control mandate consistent with SHIFT LEFT policies.
- One transport in DEV
- Configurable quality rules
- Leverage SAP® tools
- Over 700 rule patterns

Step 2
Configure the CoE
Step 3
Set up the Quality Perimeter
A quality perimeter will prevent sub-standard ABAP from leaving development. You can decide whether you want a zero-tolerance policy where all rules are followed, or whether you want to create exceptions based on circumstances.
In either case, HAWKEYE will prevent transports from being released unless they pass all our tests. HAWKEYE provides insights into the development process through the automatic Executive Report; developers and tech-leads have everything they need to comply with corporate quality standards, without costly and time-consuming technical code review meetings.
