Has Anyone Noticed a Change in Purchase Order Approval Rule Evaluation Logic? Need Your Input!

Hi Community,

I'd like to raise a discussion around Purchasing approval rule evaluation logic specifically around how the system handles purchase orders where multiple approval rulesets must be triggered because we have been encountering an issue about a critical change in Oracle Fusion Purchasing approval behaviour.

The issue in simple terms:

When a purchase order has multiple lines, each requiring their own approval rule, what happens if one of those lines has no matching rule defined?

Previously observed behavior:

• System fails and shows an error: "The approval history can't be displayed because this task couldn't be assigned to any approver."