Redwood SSP Requisition Is Getting Assigned to an Unexpected Procurement BU in a Shared Services PRC

Hi Oracle Community,

We have a scenario where one Requisitioning BU is associated with multiple Procurement BUs because of a shared-services procurement model.

When users create requisitions through Redwood Self Service Procurement, the requisition is sometimes associated with a different Procurement BU than the one expected based on the user's business process.

The setup appears correct at the BU level, but we are trying to understand what exact logic Fusion uses to determine the Procurement BU for a requisition when multiple Procurement BUs are available for the same Requisitioning BU.

Thanks.