My Defects and My Defect Corrections

The My Defects and My Defect Corrections applications, together with My Test Executions, enable the processing and correction of defects found during the execution of test plans.

By passing information about the project and wave from the test plan to a defect and then from the defect to the corresponding defect correction, these applications support the collaboration between testers and developers.

  • If a test case fails, the tester can report a defect in My Test Executions. This creates a defect containing information from the test plan, such as information about the project and wave, in My Defects.

  • The defect can then be further specified, analyzed, and processed in My Defects.

    If it turns out that the implementation of a change is necessary for the defect, a defect correction can be requested in My Defects. This creates a defect correction in My Defect Corrections that automatically contains information about the release. You can assign defect corrections to developers.

  • The defect correction is processed and documented by the assigned developers in the My Defect Corrections application.

    If a developer changes the status of a defect correction, for example by providing a solution for the defect, this is reported to the tester by a status change of the corresponding defect in My Defects.

Defect Correction for SFT/AT workflow:

When a developer has finished their correction assigned to a defect correction that was created for a single functional test (SFT) or an acceptance test (AT), the developer triggers the Set to Retest with Transport action. This releases the original transport request, and the defect correction is set to the new status In Delivery (shown on the top right in the defect correction area).

Normally, the import to the QAS system is scheduled and performed periodically by the Release Batch Import program /SALM/BATCH_IMPORT_TRIGGER with the import variant /SALM/QAS. When the import is successful, the Release Batch Import program automatically sets the target status Transport to Testing.

Defect Correction for FIT/RT workflow:

If you require a defect correction for a functional integration test (FIT) and a regression test (RT), execute the Release Batch Import program /SALM/BATCH_IMPORT_TRIGGER with the following variants in the order shown:

Import variant /SALM/INTEGRATION_TEST_QAS for the import to the QAS system.

Import variant /SALM_INTEGRATION_TEST_PRE for the import to the pre-production system.

Select the Check for complete WP Import radio button for the program /SALM/BATCH_IMPORT_TRIGGER with the import variant /SALM_INTEGRATION_TEST_PRE.

The target status Transport to Retesting is only set if the import to the pre-production system was successful.

If you run the Release Batch Import program in dialog mode, you must leave the program completely after the protocol for the import run is displayed. Otherwise, the CRM documents are locked.

Flow diagram: Focused Build Defect Correction Workflow

Focused Build Defect Correction Workflow
Focused Build Defect Correction Workflow

My Defects

The My Defects app shows all defects that have been reported by you for a test case in the My Test Executions app or for which you have been assigned as a processor and all defects assigned to your team. You can use the My Defects app to further specify, categorize, and process defects. You also use this application to request defect corrections.

You can open the My Defects application from the SAP Solution Manager launchpad.

Analyzing and Documenting Defects

Choose the defect in the list under Defects. On the tab pages, you can do the following:

  • Details

    The Details tile shows the active defect correction

    • Further specify or categorize the defect

    • Assign the defect to a message processor or support team

  • Texts

    Read and add texts that document the defect

  • Attachments

    Attach files, such as image files or document files

  • My Defect Corrections

    If you have requested a defect correction: Navigate to the defect correction that has been created for the defect

  • Relations and Related Test Case

    The Relations tile shows the entire docflow (active and inactive defect corrections)

    Check related transactions or the related test case

  • Actual Effort

    Document the tasks and the time that you spent on the defect

Changing the Status of Defects

To process the defect, change the status of the defect by choosing Action in the tool bar and selecting the appropriate CRM action to set the wanted follow-on status. For example, you can set a newly created defect to In Process to start working on it or you can withdraw the defect. Once the defect is set to In Process, you can do the following:

  • Forward the defect to another team if you or your team is not responsible

  • Propose a solution for the defect

  • Request a defect correction

    To request a defect correction for the defect, choose Action and select Create Defect Correction. This creates the corresponding defect correction in the My Defect Corrections application.

    You can only create a defect correction in the action menu of the My Defects app if no defect correction has been created yet, or if no active defect correction exists. A defect correction with user status Withdrawn is classified as inactive. This ensures that only one active defect correction related to a defect can exist at any point in time.

  • Request additional information from the testers

Finally, you can close the defect by setting its status to Confirmed. Prerequisite for this is one the following cases:

  • The solution has been accepted by the tester.

  • The retest of the correction assigned to the defect correction has been successful.

When you confirm a defect, the defect and the corresponding defect correction are both confirmed if the assigned transport request has been imported into the target system successfully.

A defect which is set to the status In Process can be withdrawn. A defect can also be withdrawn in statuses New and Tester Action. Prerequisite: You can only withdraw the defect if you are also assigned to the partner function Reporter.

If you are not authorized to withdraw the defect, you receive the following error messages:

  • Status was reset by system.

  • Withdrawal of defect is not allowed. Current user is not the reporter.

My Defect Corrections

The My Defect Corrections application shows all defect corrections assigned to you or your team. You can use this application to check and document information about the defect corrections, create transport requests for the defect corrections, and change the status of the defect corrections.

On the tab pages, you can do the following:

  • Details

    • Find information about the release

    • Describe or categorize the defect correction

    • Assign the defect correction to the responsible roles

  • Texts

    Read and add texts that document the defect correction

  • Attachments

    Attach files, such as image files or document files

  • Documentation

    Assign, unassign and move Solution Documentation structures, and change the status of a test step

  • Transports

    Create transport requests for the defect correction

  • Relations

    Check related transactions such as defects, work packages, or releases

  • Efforts

    Document the tasks and the time that you spent on the defect correction

To process the defect correction, you change the status of the defect correction by choosing Action in the tool bar and selecting a follow-on status. For example, you can accept a newly created defect correction and start working on it or you can withdraw the defect correction. Using the status control, you can also request additional information about the defect or request a retest for the solution that you have provided.

Automatic E-Mail Notifications

The system sends automatic e-mail notifications for Focused Build defects. This feature is not active by default. If you want to receive automatic notifications, complete the following steps:

  • In the action profile for S1DM (Focused Build Defects), set the automatic PPF actions S1DM_SEND_MAIL_REPORTER and S1DM_SEND_MAIL_PROCESSOR to active. Each automatic defect e-mail notification type is an automatic PPF-Action.

  • Create customer-own mail forms for each automatic e-mail type and assign them to the corresponding automatic PPF action via the expression MAIL_FORM_TEMPLATE within the method call.

  • Add a sender e-mail to each automatic PPF action via the expression DEFAULT_SENDER_EMAIL. The sender must be authorized for sending e-mails.

  • Please perform all further configuration steps in the FocusedBuild_ConfigGuide_900, Chapter 7.2.9 ‘My Defects: Configuring automatic Actions for Email Notification’.

When the status of a defect changes, an automatic e-mail notification is sent out to the corresponding Focused Build recipient user.

The new automatic PPF action S1DM_SEND_MAIL_PROCESSOR_CHG is introduced with Focused Build SP9. Please perform the same configuration steps for this new automatic PPF action, as described above.

When a new message processor is entered in the defect (without a user status change), an automatic e-mail notification is sent out to the corresponding Focused Build recipient user.

Related Information