What is the general flow of requisitions in Procurement Operations Desk (POD)?

Requisitions are published based on approval nodes and the general expectation is that the Buyer Procurement Desk Agent group is in the approval flow one time for the document to appear in POD. A requisition will appear in Procurement Operations Desk by the following sequence:

1. A purchase requisition (PR) is created in Ariba Buying.
2. The PR is submitted and requires approval(s).
3. If the active approval node belongs to a POD user or group (generally this is the Buyer Procurement Desk Agent group), the PR is published to Procurement Operations Desk.
   • A scheduled task runs every 5 minutes(as needed) to publish documents from Buying to POD.
4. Once it is published, the request is checked against the queue rules.
   1. If 1 matches, that queue is used
   2. If multiple match, the queue with the highest priority (which is the lowest number) is used
   3. If none match, the PR will be unassigned

The requisition will appear for the reason the approver is a member of the Buyer Procurement Desk Agent group.

Both the below conditions should be satisfied for a non-requester user to be able to see a PR in POD:

1. User must have at least one POD group assigned AND.
2. User must be part of the active POD approval node.

For members of the Buyer Procurement Desk Manager group, this is achieved by satisfying the prerequisite requirement of also adding them to the Buyer Procurement Desk group as mentioned in Prerequisites for Procurement Operations Desk for SAP Ariba Buying and SAP Ariba Buying and Invoicing.

See Procurement Operations Desk for Buying Solutions guide for more information.

KB0401782 - Why is my Requisition not showing on Procurement Operations Desk (POD)?

Core Procurement > Core Administration > Procurement Operations Desk