Anyone else experiencing performance bottlenecks or functional gaps in the new Redwood Supply Reques

Hi Community,

We are currently testing/adopting the new Redwood Supply Requests interface in Oracle Fusion Cloud SCM. However, we have noticed significant behavioral and functional differences when comparing it to the Classic UI:

Key Differences & Issues Observed:

Line Information Requirement: When adding a line, all required line information and attributes now need to be fully defined/populated up front at the moment of adding the line, whereas Classic allowed a more flexible step-by-step entry.

Destination Organization Selection: The new interface does not allow users to directly select or edit the Destination Organization freely; instead, it restricts input to system recommendations/suggestions.