Process Flow for Rush Orders

Does anyone have a process in place for users to request that an order be rushed? Several RQC users are asking for a field that would allow them to make this distinction on requisitions. We discussed using the "Priority" field, or creating Minor Purchasing Classes for users to select either Standard or Urgent. The priority field seems the most logical, however, we haven't used this field before, so not sure what all it impacts. Any wisdom/suggestions are appreciated!

Find more posts tagged with

Comments

Legacy Contributor

We have a rush process flow, and base it on PO Code (RUSH), steps are:
- Req Approval
- PO 23 PO Creation - only one vendor allowed per rush
- Email sent to buyer(one buyer specified for rush orders) and requester
- Order manually places, and buyer responds to email with confirmation to buyer, often interacts with discussion on freights
- We also have standard comments for required delivery time, overnight - 8am, overnight 10am, Next day...
We had used priority code previously, but PO Code gave us visibility for monitoring on the dock and for reporting, we needed to be able to quantify, management wanted to make sure we didn't increase shipping costs inappropriately and we challenged the process and got things delivered ontime

Legacy Contributor

We use the Priority field. If the req priority is set as HIGH then we have a process flow set to send these orders to a Purchasing LBI dashboard report. The orders will have to be worked from the dashboard by Purchasing staff at this point.
We also run monthly reports to see the priority 1 orders processed. We can pull these numbers from the ODBC tables as well.

pcesarz

We have the requester call their buyer if they have a rush order. We found that if we didn't do that, the requesters made everything a rush. They still try to by putting today's or tomorrow's date as the delivery date. But unless they physically talk to their buyer, the buyer will have the item shipped regular delivery.

0911060553270289.pdf

Legacy Contributor

We also have the requester call the buyer for expedites. Our requesters are far removed from Purchasing &, like Pam said, they would make everything a rush if they could. We also require a "conversation" take place as voicemail & email is not allowed when requesting expedited delivery. We have 4 delivery codes that are entered in a User field in PO20.2 that we use for reporting.

Legacy Contributor

We had AVAAP custom map the priority and adjust the RQC Config file. The drop down now shows different values (Standand Overnight, Second Day, etc) and the process flow triggers a PO Header Comment Code.

The altered priority allows us to run a PO100 and leave the POs unreleased so the buyers see them and can verify issue method prior to release. Basically with the PO Comment - it should be a matter of just changing EDI and release.

AVAAP is having some issues with the format and the comment codes - so it's still very much a work in progress.

Copyright © 2025 Infor. All rights reserved.