on 04-04-2014 2:43 PM
Hi,
We have activated workflow WS90000011. I have also activated
application FITV_POWL_APPROVER. The intention of the latter is for
user to approver the expense claims via the FITV_POWL_APPROVER instead
of via UWL. The key reasons are that user can enter the rejection reason and also see all the details in 1 screen.
In our workflow WA90000011, we route the workflow item to reviewer and approver by
referencing a customized table rather than via the HR org structure. The routing as shown in UWL is correct. However, when I go
to FITV_POWL_APPROVER screen, I do not see the work item there for approver.
Illustration
HR Org structure: A -> B -> C
Customized table: A -> C
In UWL, after A submits the expense claim form, C receives the notification in UWL. It is correct. However, when I go to the application FITV_POWL_APPROVER, I see the work item under B and not C.
Why is this so? We did not make any change for FITV_POWL_APPROVER. It is as per standard. Also, after B clicks on 'Approve'
in FITV_POWL_APPROVER, the expense claim is approved. It does not route to C?
Has anyone attempted to use FITV_POWL_APPROVER before?
Thanks.
Hello
As far as I know FITV_POWL_APPROVER is not linked at all to any workflow.
The approver is determined by personalisation via appl id CO-CCA-TR. The function module PTRM_WEB_PERNRS_GET is used to determine all the pernrs related to an approver.
POWL and UWL are very different component :
- UWL is based on workflow (like a SBWP with filter).
- POWL is based on coding (via ABAP class) and could be completly used without any workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
of course, here is the general idea :
- Customizing of POWL is done using POWL_COCKPIT transaction
- Behind every POWL query (in your case FITV-POWL-TRIPSFORAPPROVAL) there is a feeder class. This is an ABAP OO class with methods defining actions and list of objects to retrieve. You will need to enhance this class (or copy it and change it in customizing). The standard class is CL_FITV_POWL_TRIPS_TOBEAPPROVE.
- Now you will need to override the most important method which is GET_OBJECTS, this is the method retrieving the list of trips to approve.
-In your case you will need a custom Z table to record the "validation path", then read this table to find who is the next approver. Until it is the last one just update a status in your custom table, when it is the last one use the standard approval method to set the approved status. (if it is a rejection you can alway use the standard).
Hope this helps
Yes it can be done with specific coding. As I said in my previous message :
- Customizing of POWL is done using POWL_COCKPIT transaction
- Behind every POWL query (in your case FITV-POWL-TRIPSFORAPPROVAL) there is a feeder class. This is an ABAP OO class with methods defining actions and list of objects to retrieve. You will need to enhance this class (or copy it and change it in customizing). The standard class is CL_FITV_POWL_TRIPS_TOBEAPPROVE.
- Now you will need to override the most important method which is GET_OBJECTS, this is the method retrieving the list of trips to approve.
-In your case you will need a custom Z table to record the "validation path", then read this table to find who is the next approver. Until it is the last one just update a status in your custom table, when it is the last one use the standard approval method to set the approved status. (if it is a rejection you can alway use the standard).
Which part isnt clear ?
Hi,
I wanted clarifications on the last point. Is there any further configuration setup to enable 2 level approver or it is purely controlled via the program to check against our customized table?
In your previous implementation, do you have a customized table to track who is the next approver per expense claim number?
Thanks.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.