The second option, real-time
release and allocation, is rarely used because it is a manual method and
requires frequent monitoring. There are only two conditions under which
real-time release and allocation should be used:
| 1. | When a requester wants a
pick list printed immediately
For example, suppose a warehouse has a deadline for receiving pick lists and you have forgotten to create the order until the due date. Using real-time release and allocation, you could create the order, get it approved, and release it manually, all within the same day. You could then instruct the NCAS to print the pick list at the central warehouse immediately. This allows you to meet the deadline. |
| 2. | When a requester must know
immediately that an item shortage exists so that a substitute item can
be ordered
For example, suppose a warehouse has an unexpected shortage of an item that must be replenished immediately. Using real-time release and allocation, the requester could create an order, get it approved and release it manually. The Usage Order Release (UOR) screen would then alert the requester to any inventory shortages at the time of release and allocation so that the requester could substitute items if needed. |
In order to use real-time release and allocation, the requester must give the order a status 7 (real-time allocation). This can only be done when first creating the order header on the Usage Order Header Entry (UOHE) screen. This status overrides the auto-release and allocation default chosen at the warehouse level and prevents the order from being released and allocated offline in batch.
If an order is given a status 7 (real-time allocation) on the Usage Order Header Entry (UOHE) screen, the status of that order will immediately change to a 3 (awaiting approval) as soon as lines are added to the order. After the order is approved, the status will then automatically change back to a 7 so that the order can be released and allocated real-time.
Internal replenishment orders requiring real-time release and allocation will never have a status of 2 (approved). Instead, once they are approved, they will change from a status of 3 (awaiting approval) to a status of 7 (real-time allocation) until they are released and allocated. Assume that any order with a status of 7 has already been approved.
Once the order has been approved, it is the requester’s responsibility to release the item for real-time allocation. To locate orders requiring release, the requester can use the Order Browse Select (OBS) and Order Browse Inquiry (OBI ) screens to view orders with an order status of 7 (real-time allocation).
To release the orders, the requester must use the Usage Order Release and Allocate (UOR) screen. After completing this screen, the order will immediately be released and allocated, and a pick list can be printed immediately.
Note: When releasing the order, the Usage Order Release and Allocate (UOR) screen will display a warning message similar to the stock shortage warning if there is not enough inventory to fill the order requirements. The requester will again have the option of ignoring the warning and allowing a backorder or canceling the release.