Prerequisite
The Prerequisite screen captures the contractual prerequisites between JDE licence components. One line per (Component, Prerequisite). Each row says: to use the component, the prerequisite component must also be licensed.
It is the catalog of dependencies Nomasx-1 applies when computing the compliance: if you have rights to a component but not to its prerequisite, the matrix surfaces the missing prerequisite as a separate compliance gap.
At a glance
Goal of the view
- Encode the licence dependency graph. Oracle ships prerequisite rules between components — codify them here so Nomasx-1 cross-checks them automatically.
- Drive compliance prerequisite warnings. Missing prerequisites surface as a compliance line item in the reports.
Columns
| Column | Source | What it tells you |
|---|---|---|
| Product | PRQ_PRODUCT — Oracle product family. | The licence family the rule belongs to. |
| Component | PRQ_COMPONENT — component requiring the prerequisite. | The dependent component. |
| Prerequisite | PRQ_PREREQ — required component. | The component that must also be licensed. |
Edit dialog
Double-click a row to edit the prerequisite mapping.
| Field | What to enter |
|---|---|
| Product | Oracle product family the rule belongs to. |
| Component | The dependent component — the one that requires the prerequisite. |
| Prerequisite | The component that must also be licensed when the dependent one is. |
Tips & best practices
- Keep the rules in sync with Oracle's price book and supplemental terms — both can introduce new prerequisites at renewal time.
- A circular prerequisite is a configuration mistake — Nomasx-1 will not loop, but the compliance computation will mis-report.
- Document each rule with a brief justification in change notes, especially for non-obvious dependencies between non-financial modules.