Implementing SAP S/4HANA

The implementation methodology for all SAP S/4HANA implementation projects is SAP Activate. The SAP Activate Methodology includes a structure of project phases, tasks, and deliverables that vary based on the solution you are implementing.

You will find this methodology structure in the SAP Activate Roadmap Viewer. It is the central tool that guides your SAP S/4HANA implementation project by providing specific instructions and supporting accelerators to help you execute tasks and deliverables throughout each implementation phase and after go-live. Content is continuously updated to provide current and accurate information.

SAP Best Practices for Public Cloud provide the Scope Items for each solution. For deployment model Public Cloud all available processes are pre-configured via the corresponding scope item.

The following graphic contains an overview of the available business processes and the corresponding scope items.

Scope Items for SAP S/4HANA Asset Management Public Cloud are:

• Corrective Maintenance (BH1)

  Standard process for breakdowns or failures.

  This scope item has been deprecated as of SAP S/4HANA Cloud 2302.

• Emergency Maintenance (BH2)

  Unforeseen and urgent maintenance work by processing notification and order in a single app (Report & Repair Malfunction).

  This scope item has been deprecated as of SAP S/4HANA Cloud 2302.

• Improvement Maintenance (4VT)

  Perform and track work that leads to improvement of assets such as redesign, upgrades etc. - integrated with Project Management (Supports the phase model).

• Operational and Overhead Maintenance (4WM‏)

  Record activities such as training, development, documentation, routine work, and so on (Supports the phase model).

• Preventive Maintenance (‏BJ2‏)

  Perform regular inspections and maintenance activities.

  This scope item has been deprecated as of SAP S/4HANA Cloud 2302.

• Proactive Maintenance (‏4HI‏)

  Same as Preventive Maintenance - in addition supports the phase model.

• Reactive Maintenance (‏4HH‏)

  Same as Corrective Maintenance - in addition supports the phase model.

• SAP Maintenance Assistant (‏4RV‏)

  Mobile solution (Cloud) that enables a maintenance technician to perform their daily tasks related to asset management in SAP S/4HANA Cloud.

• Maintenance Resource Scheduling (‏43R‏)

  Monitor workload and plan work based on schedules.

• Integration with Asset Central Foundation (‏3YE‏)

  Connect with cloud-based applications of Intelligent Asset Management.

The green check mark in the graphic means that the process is generally available.

SAP Central Business Configuration (CBC) is a tool that will make it possible to configure business processes spanning multiple SAP cloud solutions from one central place.

SAP CBC will become the mandatory entry point for business configuration of all cloud systems (both 2-System- (2SL) and 3-system landscape (3SL).

It supports you in the following steps:

• Define Scope
• Set Up Organizational Structure
• Perform Product-Specific Configuration

For deployment model Private Cloud / On Premise you can use the available scope items for automatic configuration or use the Implementation Guide to manually configure the process.

Scope Items for SAP S/4HANA Asset Management Private Cloud and On Premise are:

• Corrective Maintenance (BH1)

  Standard process for breakdowns or failures.

• Emergency Maintenance (BH2)

  Unforeseen and urgent maintenance work by processing notification and order in a single app (Report & Repair Malfunction).

• Preventive Maintenance (‏BJ2‏)

  Perform regular inspections and maintenance activities.

• Proactive Maintenance (‏4HI‏)

  Same as Preventive Maintenance - in addition supports the phase model.

• Reactive Maintenance (‏4HH‏)

  Same as Corrective Maintenance - in addition supports the phase model.

The green check mark in the graphic means that the process is generally available.

In the Private Cloud and On Premise deployment model you can activate a number of Business Functions to extend your functionality.

Business Functions enable you to considerably simplify the process of introducing and using SAP S/4HANA. This technology enables you to selectively introduce individual features and to optimize selected business processes.

With business functions, SAP provides features in self-contained units to enable you to use specific features and enhancements for your various business processes.

The business function concept has two aspects:

• The business function as a self-contained entity comprising special features.

• The business function as a technical object in your ABAP-based system. Along with this object, you also activate the features in your ABAP-based system using transaction SFW5.

When you have activated a business function, the following changes and additional features are visible:

• New menu entries

• New fields on the user interfaces

• Customizing activities required for the implementation

• New table entries in Customizing tables and system tables

Before activating Business Functions you must consider that some of the functions are always active and others have to be activated. So the following groups must be considered:

• S/4HANA Always On Functions

  Functions such as LOG_EAM_POM / LOG_EAM_POM2 (Project-oriented Maintenance / MEB) and LOG_EAM_ROTSUB / LOG_EAM_ROTSUB2 (Reburbishment / Subcontracting).

• Enterprise Business Functions

  Functions that you can activate individually.

The usual naming convention for Business Functions in Asset Management is LOG_EAM_XXX_XX. The available Business Functions can be divided into the following groups:

• LOG_EAM_CI_xx - continuous improvements for SAP GUI
• LOG_EAM_SIMPLICITY_xx - web applications for Asset Management
• LOG_EAM_xxx_xx - individual Business Functions containing new functionality

The simplification list is a collection of single so-called simplification items - that is, a list of applications, transactions, functions etc. which in the future will no longer be supported.

The impact of each customer-relevant item is listed in the specification list. A simplification item can have a business impact and a technical impact. For example, if the data structure is simplified, the related custom code needs to be adapted. In other cases, functionality is replaced by a new, and simpler, successor application — possibly even based on an unchanged data structure.