Charge Account Segment Override Behavior in Manual Requisition vs Requisition Import

Summary:

We would like to confirm the expected behavior of Charge Account derivation in Oracle Fusion Procurement when using Transaction Account Builder (TAB).

In our configuration, the Charge Account is derived based on the Deliver-to Location using an Account Combination Rule. Additionally, we have a segment rule configured for the Natural Account segment to derive the value based on the Item Category.

We observed the following behavior:

1. During Requisition Import (from an external system), the system correctly overwrites the Natural Account segment based on the Item Category rule, and the final account combination is validated accordingly. If the resulting account combination is not valid, the process errors out and the requisition is not created.