Steps in the screenshots correspond to the numbers in the headings.
Once the SCS Releases the Requisition to the Buyer, s/he cannot make any changes to the quantity requested. The BUYER can make changes up until the time they POST it.
1. In our example, the Buyer sees the PO Text in this Released Requisition: "May not need to order the Adapter... think we have several in stock. Bill is checking. 1/31/2020."
2. They notice this is an Inventory PO, so it is not tied to a Work Order.
It is NOT the Buyer's responsibility to confirm this. The SCS should NOT have released the Requisition with that Text in the PO field.
3. In checking Inventory > Stock, there is a Min/Max of 1/1 on the Part, and 0 on hand. No Stock Authorization Form is present.
There is nothing that the Buyer can see to show that the Item should be ordered.
4. The Buyer unchecks the Release box.
5. From the drop-down menu under Workflow, the Buyer selects Blocked.
6. The Buyer then clicks Save in the header.
The PO has not yet been posted at this point, so changes will be able to be made.
7. An event record is created and tracked in the Event Log.
The Buyer lets the SCS know that the REQ is blocked and why.
8. The SCS searches in the CLIENT for "Blocked Reqs Go to Inventory > Purchasing > Purchase Order.
8.1. Click the red chevron in the search field to expand it.
8.2. Under the General tab, enter your Ship To Place (ST#).
8.3. Use the drop-down arrow to select Proposed under Status.
8.4. Click the Groupings tab.
8.5. Use the drop-down arrow under Workflow to select Blocked.
8.6. Click the green magnifying glass.
8.7. The blocked records load.
9. Once the issue has been resolved, the SCS can make the necessary changes.
10. The SCS reviews the new requisition for the new quantity, saves, then checks the Release box to send it back to the Buyer.
Please communicate with your Buyer that the Req is back in their Queue.
11. The PO status still shows Blocked, but the Req will release successfully, as shown in the screenshot below.
0 Comments
Add your comment