We'll be working on re-designing our procure-to-pay process in PeopleSoft and would like to talk with other users about how they have configured their workflow and overall process. Some issues that we're currently facing and would like to better understand include:

Ideal timing and routing of purchase requisitions in order to optimize the procurement process and approvals

Information required for purchase requisitions (to simplify the process for requestors) and use as a work intake process for procurement requests

Controls on purchase orders to ensure changes to POs are appropriately approved

Controls on multi-year purchase orders to ensure payments only occur within the intended year

 


Lara Kelso
Procurement
The Regence Group
503.721.7009
lekelso@regence.com

Views: 28

Replies to This Discussion

Last time I looked, Peopletools 8.49.22 and above has 3 versions of Workflow. The latest is the Approval Workflow Engine (AWE) which runs in ePro and other processes. I still see Virtual Approval run some of the non-Self Service SCM apps like the standard Requisition, PO Workbenches,etc. The old PS Workflow with the Business Process Maps are mostly disabled and are just there for reference for most of the apps. I am not sure which functionalities in FS still use it.

For the AWE for ePro, you just need to turn it on and configure the rules (called Criteria in AWE) and develop (code) the routings (called Paths in AWE) if your approval process is not role-based.

If you are porting functionalities where there is no PS-delivered AWE and therefore working from scratch, you will need a developer to extend Application Package classes into your specific application to start and go through the process of Registering, Configuring your new workflow structure. That would be like a whole new implementation type of work.

The code set to implement AWE is different for Peopletools 8.49.21 and below.
Thanks for the feedback. Just to clarify - we actually use a pretty sophisticated workflow (PS 8.8, PT 8.46) already, but the business side wants to determine from a business process perspective if the workflow process we have is the most effective. We're looking to compare what others do with what others do.

RSS

© 2012   Created by PSoftPros.

Badges  |  Report an Issue  |  Terms of Service