Thursday, November 21, 2013

Purchase Requisition Approvals in Peoplesoft

I have been getting asked to show how we have designed our Approval process for Requisitions in PeopleSoft Finance.  First of all, I did not design this process.  I was just asked to come in and make it work. 

How we associate the signing authority to the user.  Oddly enough this is done in HR, we have a bolt on page within the JOB_DATA Component where we store Corporate Functions, HR is responsible for maintaining this data, so it makes sense within our organization.

This is our Corporate Functions Grid:

The Level 3-Up to $100,000 dollars is the Signing Authority for this User.  The initial work the consulting company did, failed to get this information into FIN, when we pressed them about it.  The told us that we needed to update in both FIN and HR.  So I used Integration Broker to send this information to FIN.

In Order to maintain the Approval Chain, we populate the PSOPERDEFN's ROLEUSER_SUPR in HR and use Integration Broker to send this to FIN.  We have a process that runs every fifteen minutes looking for changes and it maintains our PeopleSoft User Profiles and updates our Identity Management System, Novel Access Manager.

The on the FIN side, the consulting company built a configuration page to track the signing authority levels:


 They used this information from HR Corporate functions, the User Profile roleuser supervisor to populate a table called ZZ_WF_AUTHORITY.






The View within my Dynamic User List joins the signing Authority Configuration and the table above.:


SELECT A.OPRID
 , A.EMPLID
 , A.DESCR
 , A.EMAILID
 , A.ZZ_SIGN_AUTHORITY
 , A.SUPERVISOR_ID
 , B.MERCHANDISE_AMT
  FROM PS_ZZ_WF_AUTHORITY A
  , PS_ZZ_SIGN_AUTH B
 WHERE A.ZZ_SIGN_AUTHORITY = B.ZZ_SIGN_AUTHORITY



No comments:

Post a Comment