Your UX is waiting ...interact, engage, explore in Las Vegas at CloudWorld 2023

Learn more
Business use case for splitting a requisition line — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Business use case for splitting a requisition line

Received Response
55
Views
6
Comments
edited Dec 18, 2019 3:11PM in Self Service Procurement 6 comments

Summary

Business use case for splitting a requisition line

Content

Customers / Support

A quick note to capture one of the key use cases where splitting a requisition line is very helpful from both the requester and the buyer's perspective.

Context:

Recently, a customer had the following conundrum:

The requisition contain a line for 1000 items. The buyer that ended up processing the line for 300 items. The buyer then expected to find the remaining 700 back in the Process Requisitions queue for further processing. This was not to be. The customer then wanted to understand how this could have been achieved.

Premise:

In this specific use case, the buyer admittedly wanted to process the remaining quantity on a different order. Although we did not get the specific reason why, it could have been due to various business reasons:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!