---
title: "Correction Plan for Oracle"
slug: "how-to-plan-the-corrections-cycle-1"
updated: 2021-12-28T21:43:03Z
published: 2021-12-28T21:43:03Z
---

> ## 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 for Oracle

To view the correction plan for your project, click on the **corrections tab** **![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1640607681290.png)**

The correction plan allows you to drill down to filtered correction lists, in order to review, scope, prioritize and assign the activities.

You can filter the correction activities by their [usage](/v1/docs/what-usage-information-is-collected-by-panaya) and [status](/v1/docs/what-does-the-correction-status-mean).

Corrections are also classified by Code Corrections, Functional Corrections, Setup Corrections, and User Defined. [Click here to learn more about correction types](/v1/docs/what-are-the-available-correction-categories-and-types).

All the activities are presented according to their [priority](/v1/docs/what-does-the-correction-activity-priority-mean).

When scoping a project, Panaya recommends that you consider moving some of the *Low* and *Unused* activities to *Out of Scope*in order to present a realistic project duration without introducing risk (activities can be re-introduced later if necessary). [Click here](/v1/docs/how-to-update-several-corrections-or-defects-together) to learn how to mass edit the status of selected tasks.