[AWE] Approval Criteria Failure due to NEXT not in DB

A requisition, on submission for approval, FAILED to route using the correct Approval Process Definition and instead used the DEFAULT definition. The trace showed that the reason it failed to use the expected definition was that it selected against the CRITERIA defined as a view (just a projection) of the REQ_HDR table, and in its where clause passed NEXT as the REQ_ID, and since there was no NEXT in the database (there wouldn't be) the criteria was automatically false.

This means that the component processor hadn't yet applied the autonumber logic and saved the record to the database (even in an uncommited state) before starting the approval process.