---
title: "Correction Plan"
slug: "how-to-plan-the-corrections-cycle"
updated: 2025-12-11T14:40:17Z
published: 2025-12-11T14:40:17Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Correction Plan

The Corrections Plan view in Panaya provides a centralized list of all project corrections, allowing you to review the activities by their priority and usage. It helps teams manage assignments and ensure every correction is handled correctly throughout the project lifecycle.

[Panaya Impact Analysis - Correction Plan](https://player.vimeo.com/video/1119713943?badge=0&autopause=0&player_id=0&app_id=58479)

- You can filter the correction activities by their [usage](/v1/docs/how-does-panaya-determine-usage) and [status](/v1/docs/what-does-the-correction-status-mean).
- Corrections are classified by code corrections, authorization adjustments, modifications, and user-defined correction activities. [Click here to learn more about correction types](/v1/docs/what-are-the-available-correction-categories-and-types-2).
- When scoping the project activities, Panaya recommends that you consider moving some of the ***Low*** AND ***Unused*** activities (this **does not** apply to High and Unused) to *Out of Scope*to present a realistic project duration without introducing risk (activities can be re-introduced later if necessary). **High**, **Unused** activities **should still** be reviewed before scoping them out. If the project timeline is reasonable, review the **Medium** activities as well. [Click here](/v1/docs/how-to-update-several-corrections-or-defects-together) to learn how to mass edit the status of selected tasks.
- Generally, object usage, **Used** or **Unused**, is based on usage data logged in ST03n. Some objects will not have usage maintained in ST03n and if their impacted transactions are also not used, they will be classified as unused. **Unknown** usage classification usually applies to objects that SAP does collect usage for or that were not able to be connected to any impacted objects or transactions.
- You can **complement your ST03N usage with UPL data** (SAP Usage and Procedure Logging). UPL often captures runtime usage that ST03n may miss and provides a stronger basis for scoping decisions. To enable this option, please contact your customer success manager.