Skip to Content
Product Information
Author's profile photo Roshan Fernandies

Resolve internal problems by using the 8D Methodology

Resolve internal problems by using the 8D Methodology

In this blog post you will get to know the latest feature released in SAP S/4HANA Cloud 2002 – Resolve internal problems by using the 8D Methodology.

Blog Applicability

SAP S/4HANA Cloud Release


Target Audience

Business Users, Key Users, Consultants

Target Industry

Manufacturing Industry

App used to solve the Generic/Internal Problem


How do I get this app?

To your user in the SAP S/4HANA Cloud system, you should have the following roles and catalog assigned.

Business Catalog


QM – Internal Problem Processing

Business Roles


Quality Engineer

Business Background

8D stands for the 8 disciplines for solving the problem. 8D typically used when there is major, critical and recurring problem. This may not be applicable if the root cause of the problem is known, if the problem is non-recurring.8D methodology is adopted to increase the effectiveness of problem solving in production and development areas. 8D approach is based on a team working together to solve a problem. It contains three types of actions: containment actions, corrective actions and preventive actions. If there a Nonconformance with a quality requirement and contains a request to take appropriate action.

Start Problem Solving Process

Quality Engineer would trigger an 8D from a defect. Currently we can create the Problem-Solving Process from Generic and Production defect. It’s only possible to create one Problem Solution Process per Defect. As soon as Quality engineer triggers the Problem-solving process. The Problem-solving number gets generated. Defect is linked with the problem-solving number. In general, problem-solving processes shall support the definition and processing of several actions of different types, like for example containment, preventive or corrective actions in an 8D process.

Actions to be performed during a problem-solving process shall be represented by Quality Task. The fact that a Quality Task instance is related to a problem-solving process shall be reflected by a new Quality Task origin. The different types of actions shall be represented by additional task types.

This feature is currently available only S/4 HANA Cloud as of now.

The 8D method comprises eight problem-solving steps:

D1 Team

D2 Problem description

D3 Containment actions

D4 Root causes

D5 Chosen permanent corrective action(s)

D6 Implemented permanent corrective action(s)

D7 Actions to prevent recurrence

D8 Congratulate your team


You start the Problem-solving process by recording the defect using app Record Defect.


Problem Solving number gets generated against the defect number. You access the Problem-Solving number using the app Resolve Internal Problems.


D1 Team

Here you will define a team to solve the problem. This team will have a Team leader and team member with details like email ID, phone number etc. This team will carry the responsibility to perform the subsequent steps in 8D.


D2 Problem description

Now you clearly define the problem. Problem description will have the defect Defect Code Group and Defect code. This step also displays details relating to the original source defect.


D3 Containment actions

You can define immediate actions as tasks to resolve the problem. The immediate actions are provisional measures for damage limitation. You must make sure that containment action should not create any new problem. Here you can create the Quality task which is linked to your Problem-solving Process number. Against the Quality task you assign Task code Group and Processor.


D4 Root causes

You can enter a detailed cause description for each cause. Here you create the Causes linked with cause code and Cause code group.


D5 Chosen permanent corrective action(s)

For each cause you can define remedy in this step. This will avoid the recurrence of the problem and remove the root cause. In this step you can implement the Corrective Actions.


D6 Implemented permanent corrective action(s)

Here you can edit the implemented corrective actions that were created from a defined corrective action. The defined task is displayed as the predecessor task. The main purpose of this step is to verify the actions taken in step D5.


D7 Actions to prevent recurrence

In this step you can define preventive actions as tasks to prevent defects recurring.


D8 Congratulate your team

D8 allows you to recognize and assess the team’s performance.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Eric Sun
      Eric Sun

      Hi Roshan Fernandies

      How do you create partner value for the drop down under D1 tab? Reply appreciated.

      Partner value for Resolve Internal problem app | SAP Community



      Author's profile photo Saravanan S
      Saravanan S

      Do we have any alternative option to enable the Problem Solving Process in SAP S/4 HANA 2020 On-Premise edition?