How Does SAP Activate Methodology ensure faster Implementation?

Accelerated SAP Implementation Methodology (ASAP) was widely used as SAP Implementation methodology. But, with advent of S/4 HANA, SAP Activate methodology is introduced which ensure agile project implementation. ASAP used to include five project implementation phases i.e. Project Preparation, Business Blueprint, Realization, Final Preparation, and go-live & support; mapping existing business processes done in blueprint , and assessing fit-gap analysis used to take anywhere from few weeks to months in ASAP.

In SAP Activate, business blueprint phase is not conducted, instead fit-gap analysis is conducted and leveraging from SAP best practices and rapid deployment framework to assess the feature & functionality gap if any. In addition, Activate uses four project implementation phases instead of five in ASAP.

1.      Prepare:

In this phase, business users explore SAP best practices along with standard SAP Business Processes such as order-to-cash, procure-to-pay or hire-to-retire in HR module. Sample scenario is executed in SAP Sandbox server for business users to evaluate how closely standard system meets their respective company’s process

2.      Explore:

Here the business & SAP implementation team agree on different configurable objects related to organizational structure & transaction data i.e. company code, plant and sales organization. A complete fit-gap exercise is carried to identify gaps that standard SAP is unable to offer. In this context, a fit-gap strategy is devised in which it’s decided if a system enhancement, a customized application or activating business add-in will address the gaps.

3.      Realize:

In this phase; agreed configurable objects in explore phase are configured. In addition, company-specific scenarios are created for testing business processes. All custom-developed objects are also tested in this phase.

4.      Deploy:

A detailed integration testing is done between various SAP modules/components to see data/information flow is complete & correct. User trainings are also conducted in this phase followed by cutover activities in which company transitions from legacy system to SAP.

Thus adopting above four implementation phases; project implementation timelines are greatly reduced.


Preventing Supply Chain issues with EWS

Early Warning System (EWS) is built on SAP logistics information structure that allows you to monitor & receive alerts for specific configured exceptions. It can help various logistics departments personnel’s like production manager, procurement manager, material planner & Quality supervisor to optimize their business processes & have better decision making.

In real world; due to lack of coordination & availability of data at real time, numerous supply chain problems rises. Following and numerous other business processes can be avoided if simple functionality of EWS is implemented:

1.      Negative sales trend for particular group of products lasted for couple of weeks; however; senior management only got aware of this trend in quarterly sales meeting.

2.      The scrap quantity of high value product never exceeded more than 3% but yet it already crossed threshold value of 7%. Production manager only came to know about it long after the loss already incurred.

3.      Procurement of certain raw materials shows a decreasing trend but procurement manager was unware of this due to which he was unable to take advantage of falling price by ordering more.

4.      A vendor repeatedly misses delivering target which in turn effected inventory of raw material. Management only came to know of this development once significant production/procurement losses had already incurred. Timely information would help management find other source of supply.

Configuring EWS is fairly simple with absolute no involvement of ABAP; the first step is identification of key figures (Production Scrap, Delivery date etc.) you want to monitor for any deviation, monitoring of key figures can be configured as trend (positive or negative) or by threshold value. You can then group these exceptions based on color-coding, the last step is to define periodic analysis in which we set the frequency based on which the user will be informed if any deviation has occurred (E.g. Daily, weekly or monthly)

As you can determine it’s fairly easy functionality that can be implemented and high benefits can be reaped out of it.

For more details about our company services please visit (https://3qubeconsulting.com/)