Automatic Quality Control
Most SAP installations are customized to support changing processes and market conditions. These important customizations are built with teams that may be around the corner, or on a few time zones away. To ensure compliance to quality standards, HAWKEYE can establish an automatic quality perimeter around development to prevent sub-standard code from getting through. With the developer tools, HAWKEYE can also help developers conform to these rules so they don't have to re-write their code.
How Does it Work?
Step 1
Baseline Your System
Isolate legacy code from new development. Legacy issues have been accumulating since the start of the SAP implementation. With HAWKEYE, you can easily establish accountability and buy-in to corporate standards for all new development.
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.
After a complete assessment, an interactive dashboard will give you access to all you need to know about your customized SAP environment. It will also establish a "baseline date" that isolates legacy objects which developers are not accountable for. Once the baseline date has been established, the development team can easily conform to all coding standards for everything they add or modify in the SAP system.
- One transport in DEV
- Configurable quality rules
- Leverage SAP tools
- Over 700 rule patterns
Step 2
Configure the CoE
Rules in HAWKEYE Monitor are combined from various sources, including customer CoEs, SAP, and proprietary HAWKEYE Monitor rules. Each rule is classified according to potential harm to the business (security, performance etc) and severity of the impact. In order to customize these rules, you can upgrade, downgrade or inactivate the rules.
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.
Give us a shout
POWER UP your SAP team. With our complementary scan of your system, you will know more about your implementation than you ever thought possible.