SAP Knowledge Base Article - Public

1818505 - Requester attribute in Purchase Order approval process

Symptom

How to use the requester attribute as a condition in the Approval Process setup for Purchase Orders.

Reproducing the Issue

 You have edited the Approval Process for Purchase orders in the Approval Processes activity.

(This activity can be found in two places:

  1. Go to Application and User Management work center.
  2. Choose the Approval Processes view under Task Distribution header.

or

  1. Go to Business Configuration work center
  2. Choose Overview view and choose Show activities.

Find Purchase Order Approvals activity)

You have setup a condition using the Requester attribute in the drop down menu but the approvals do not get routed according to this condition.

It seems the Requester attribute is not taken into consideration by the system

Cause

You have not used the "Requester" attribute correctly.

Resolution

The Requester refers to the field found under the Delivery tab at the item level, not the creator of the Purchase order.

What is more, the system looks for the Employee ID as opposed to the User ID or Technical ID of the employee.
If you look under the Business Users view of the Application and User Management work center, you can easily find that information under the General Data tab.

This is the information that should be populated in the requester field under the delivery tab.

This is the only data that will be recognized by the system and that will make this condition work.

Note that there is no need to insert " when entering the Employee ID in the condition.

Keywords

KBA , requestor , purchase orders , approval process , AP-POP , Purchase Order Processing , How To

Product

SAP BUSINESS BYDESIGN 1611 ; SAP BUSINESS BYDESIGN 1705 ; SAP BUSINESS BYDESIGN 1708 ; SAP Business ByDesign 1608 ; SAP Business ByDesign 1702 ; SAP Business ByDesign 1711