---
title: "Impact Likelihood for an Entry Point"
slug: "how-does-panaya-calculate-impact-likelihood-for-an-entry-point-1"
updated: 2022-01-04T21:12:21Z
published: 2022-01-04T21:12:21Z
canonical: "success.panaya.com/how-does-panaya-calculate-impact-likelihood-for-an-entry-point-1"
---

> ## 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.

# Impact Likelihood for an Entry Point

This article is for Oracle users. We also have [this article for SAP users](/v1/docs/how-does-panaya-calculate-impact-likelihood-for-an-entry-point).

Panaya calculates the **Impact Likelihood** for each Entry Point, according to the following set of rules-

**High** Definite impacts such as code impact and direct Entry Point change

**Medium** If an entry point is calling an object that has been changed (Patch or customization) OR, If an entry point is calling an object that is calling another object

**Low** Objects in your system where no apparent impact has been found, but reside in modules impacted by the Patches. [Click here to learn how to scope in entry points with low impact likelihood](/v1/docs/how-to-scope-in-entry-points-with-low-impact-likelihood)

## Related

- [Impact and Risk Analysis for Oracle EBS](/how-to-analyze-impact-and-risk-for-oracle-ebs.md)