Comp Planning - 2 Level Approval

Hi comp gurus ( I am coining a new Variation of Guru here ),
System Landscape
ECC 6.0
ECM ( Enterprise compensation Management)
EP 7.0
Currently we have deployed the Enterprise compensation management module. We have a standard compensation scenario where the comp planners use the comp planning screen( Via MSS) to perform the comp planning and the comp approvers, use the comp approval screen to approve the planned(submitted) compensation.
But we have a slightly different scenario where we want to have 2 levels of approvals before the comp record is set to 'Approved' status in IT 0759.
Let me explain it in detail
Lets assume that we have Manager A who is the manager of B, B is the manager of C and C is the manager of D.
C performs comp planning for D. A record is created in IT0759 for D in planning/submitted status. B can now log on and approve the comp planning/submitted comp records by C. Here we do not want the planning record to set to "approved" status when it is approved by B. But we want this to go to Manager A who can then give the final approval and only then should the record in IT0759 status be changed to Approved.
The matters gets more complicated by the fact that, the comp planners and approvers see the data(in MSS) based on OADP and not based on any workflows. Obviously I cannot create a new status for the IT0759 records. Based on your experience what is the best way to handle these scenario.
Any suggestions
regards
Raj
Edited by: Raj Kishore on Jul 10, 2008 2:46 PM

Santosh I really appreciate your inputs.
I just think that this approach would bring in a lot of enhancements
I would have to change the underlying FMs to trigger WF rather than the IT0759 "status" change FM. Build WFs. Change OADP "status" update FM, and other changes which I may get to know when we start designing the solution if we go this way. But I would (infact am) surely consider this option. But I will be really suprised, if I will have to go thsi route. Adding another approval level seems to me a pretty common requirement and if this involves a major development and maintanance effort, the clients will not be happy
Can others also please provide your inputs here.
regards
Raj

Similar Messages

Comp Planning - 2 Level approvals

ECM i so tightly integrated in MSS that I am trying my luck by posting this message in this forumn as well
Hi comp gurus ( I am coining a new Variation of Guru here ),
System Landscape
ECC 6.0
ECM ( Enterprise compensation Management)
EP 7.0
Currently we have deployed the Enterprise compensation management module. We have a standard compensation scenario where the comp planners use the comp planning screen( Via MSS) to perform the comp planning and the comp approvers, use the comp approval screen to approve the planned(submitted) compensation.
But we have a slightly different scenario where we want to have 2 levels of approvals before the comp record is set to 'Approved' status in IT 0759.
Let me explain it in detail
Lets assume that we have Manager A who is the manager of B, B is the manager of C and C is the manager of D.
C performs comp planning for D. A record is created in IT0759 for D in planning/submitted status. B can now log on and approve the comp planning/submitted comp records by C. Here we do not want the planning record to set to "approved" status when it is approved by B. But we want this to go to Manager A who can then give the final approval and only then should the record in IT0759 status be changed to Approved.
The matters gets more complicated by the fact that, the comp planners and approvers see the data(in MSS) based on OADP and not based on any workflows. Obviously I cannot create a new status for the IT0759 records. Based on your experience what is the best way to handle these scenario.
Any suggestions
regards
Raj

Have you looked at using the 'Implicit Enhancements' options available in the function module HR_ECM_CHANGE_PROC_STATUS? I think you can reset the status from 'approved' to 'submitted' at the end of the standard code & send out an email to the next level manager. I'm guessing there will not be a need to change anything else.
~Suresh

Project Workflow Extension for Multi level approval

Hi,
We have a requirement of 2 or 3 level of approval on Project Workflow for Project Status Change. We are planning to use the Seeded extension provided by Oracle to get the Approver for Project Status Change.
The extension procedure provided pa_client_extn_project_wf . select_project_approver has only one out parameter that is Approver id. This means it's only possible 1 level of approval.
Please help me to find out the way how can i make this work for multi level Approval.
Regards,
Ram

Hi Paul,
Thanks for your suggestion.
By comments field I'm assuming OfficeTask.Comments field. Problem is, this field is always null. I tried accessing this field in CheckExitCondition activity as well as in OnTaskCompleted but in both the cases, it was null only(I wrote comments while approving
the task).
I used a code activity within OnTaskCompleted activity and following code for accessing Comments and Description fields:
public string officeComments;
public string officeDescription;
private void TaskCOmplete(object sender, EventArgs e)
CodeActivity Sender = (CodeActivity)sender;
Microsoft.Office.Workflow.Actions.OfficeTask ofctask1 = ((CompositeActivity)Sender.Parent).Parent as Microsoft.Office.Workflow.Actions.OfficeTask;
officeComments = ofctask1.Comments;
officeDescription = ofctask1.Description;
Please tell me if I'm doing anything wrong here, I'm very new to Workflows. Also, do I need to set any specific property of officeTask for retriving comments?
Thank you

AME Line Level Approval -- Oracle Quality

Hi All,
In Oracle Quality module I have create one parent plan and a child plan is associated with it. After multiple lines are entered in the child plan (Approver details is stored as one of the collection result in this plan) and later when the parent plan is saved, line level AME approval based on the approvers in the child plan should initiated. The final e-signature status should be at the header level, such that once all the lines have been approved i.e. parallely approved, the header record status should change to "APPROVED".
I had tried the header level approval approach, but in this case the approval flow for approvers could be done, but the only issue is that it was done serially.
Is there a way to achieve this in AME? Kindly help.
Thanks.

Apologies for the late response, have only just spotted the question.
You will need to register "line-item job-level chains of approval" under payables transaction type before you can select it from the picklist:
Setup\Action Types\"Use Existing Action Type" button, then select action type and continue.
Hope this helps (if you haven't already resolved yourself)
James

Leave request is not coming in 2nd level approval in MSS NWBC

Hi all,
I am getting the leave request for 2nd level approval in MSS work item.
But I want that in MSS Leave approval () .
Is there any configuration to do for this.?

I am getting the leave request for 2nd level approval in MSS work item ?
your getting leave request in POWL Application i.e Bulk approval list. This is correct only.
But I want that in MSS Leave approval () . ?
Can you explain little more clear.

Purchase Order Workflow message for previous level approver

Hi folks!!
We are implementing PO workflow through which we want to notify the next level releaser as well as we also want to notify the previous levels releaser as well as Purchase requisition creator (if PR has been used as reference document to create PO).
I have already successfully implemented the workflow, in which next level of approver gets the notification in his/her SAP Business Workplace as soon as the PO gets approved by the previous level.
But my requirement is on final approval of PO, notification should also send back to the previous levels approver of PO and Requisition creator.How can I achieve it, please help.
Best regards

Hi,
A check can be made during final level of approval for which e-mail will get triggered to the previous approver and the requisitioner. you would need to provide a Logic to your developer with the message body whihc will trigger an e-mail during final approver and mail recipients will be the previous approver and the Requisitioner which can be picked from Line item in Purchase Order.
Prashant

Issue with PO release (multi level approval)

Hi,
Need help regarding PO release. I am working with 4 level approval process.
Information:
it is sequential release as I can see in workflow log, a new workflow gets generated for next level only after previous level executes the workitem.
Facing following issue at 2nd Level :
Level 2 releases item and it goes to Level 3, but workitem doesnt disappear from inbox.Once Level 3 releases item, an acceptance mail goes to Level 2. But along with the mail, updated workitem (i.e. showing release by 3rd level) also appears in inbox of Level2. Now two work items appear in Level2 Inbox.
In Workflow Log, this is how its behaving:
WORKFLOW STARTED-->
1st WF appears in WF log.
Level 1 releases WI ->
2nd workflow appears in WF log +
1st workflow with (in process status)
Level 2 releases WI ->
3rd WF appears +
2nd workflow with (in process status) +
1st workflow with (in process status)
Level 3 releases WI ->
3rd WF appears +
2nd workflow with (in process status) +
1st workflow with (in process status)
ISSUE: As soon as Level 3 sends back acceptance to Level 2, updated WI item appears( i.e. with latest release status which in this case is: released by level1, Level2 and Level3) along with the mail.
Level 4 releases WI ->
4th WF appears +
3rd WF appears (in process status) +
2nd workflow with (in process status) +
1st workflow with (STATUS COMPLETED)
ISSUE: As soon as Level 4 sends back acceptance to Level 2, updated WI item appears( i.e. with latest release status which in this case is: released by level1, Level2, Level3 and Level 4) along with the mail.
Result:
PO gets released.
In workflow log 2nd, 3rd and 4th workflow appear with IN PROCESS STATUS. All of them show process stopped at LEVEL2.

Hi Kjetil,
Release strategy is being used. Configuration for release strategy is given as following.
RGroup Rcode   Workflow     Agent
Z6          R1         1                Blank
Z6          R1             1                Blank
Z6          R1             1                Blank
Z6          R1             1                Blank
Release is sequential.
For column 'Agent' mentioning position or User is not really useful because we are getting agents through Z table. Reason is: current org structure supports 1 position with multiple users from same department. In our scenario we need to find initiators department then find relevant approval levels for that departemnt. So I cannot mention any position in 'Agent' Column as release code will be locked against one position and one departetment.
Agents picked through Z table. Table has fields Agent/ UserID , level, department.
Logic to pick agents( Object and method created ):
When workflow starts, it finds department of the initiator.
For that department-> find approval levels available(L1, L2, L3).
For these levels -> Find Agent mentioned for that level.
Onece Agents are found for all levels -> Pass them to WF container.
In task activity, These agents are passed back to the rule and the task comes to know which agent it should go to.
Result : Four workflows start in sequence. When last level releases, only 1st workflow shows COMPLETED status. Rest three hang at level 2. If I see Me29N , release for that item is shown completed. To me it seems triggering of only first workflow is enough for release. Is there any way I can avoid trigerring of other three workflows?
Edited by: User112 User112 on Jan 25, 2008 6:30 AM
Edited by: User112 User112 on Jan 25, 2008 6:31 AM

SRM 7.0 SP05 - BRF Item level approval does not work

Hi Experts,
I am working on process controlled workflow for shopping cart approval process. I have defined necessary process levels and workflow works fine for a single item SC.
I have selected decision type as "Item-based approval for partial document" for each process level and hence expect each line item (according the start condition) should have it's own set off approvers, but instead of this, system determines approvers at header level and hence item which does not really need approval undergoes approval as well.
Could you please help me to resolve the issue?
Thanks in advance.
Best Regards,
Amit

Hi Bharat,
Yes, we are using the copy of the standard implementation. We are looking into the BADI implementation and trying to assign a separate AREA GUID to each line item. Hopefully, when different aggents are assigned to these AREA GUIDs, it will enable the item level approval. I will keep you updated.
Meanwhile, it would be really helpful if you could share some sample code of such badi implementation which can help me to understand it more clearly.
Thanks & Regards,
Amit

N level-Approval for contract workflow (WS14000148) in SRM

Hi SDN'rs
I want to activate N level-Approval for contract workflow (WS14000148) in SRM
When I am creating the contract in SRM I can see the approvers in the approval preview.
But when I release the contract and look at the approval privew there are no approvers
and the status of the contract is released.
We are on SRM Server 5.5 and SP 07.
Here what I did
1. I implemented the BADI 'BBP_WFL_APPROV_BADI' using the sample implementation and populated the approvers.
2. I activated events SAVED,CHANGEVERSIONSAVED for WS14000148 in OOCU transaction.
3. I see event linkages for WS14000148 for both events SAVED,CHANGEVERSIONSAVED in SWE2 transaction.
4. I assigned role SAP_EC_BBP_PURCHASER to for subworkflow N step for contract WS14000147.
( User who is creating contract has this role)
5. Consistency check for WS14000148 is green and WS14000147 is yellow in SWUD
6. Event simulation for BUS2000113 and events SAVED,CHANGEVERSIONSAVED shows WS14000148 successfully started.
I see dump in ST22 with errors TSV_TNEW_PAGE_ALLOC_FAILED and SYSTEM_NO_SHM_MEMORY with WF-BATCH is this any thing to do with that?
If any one know what are the steps I am missing please let me know.
Thanks
A S

Hi
Please refer to these OSS notes which might help.
Refer to following OSS Notes ->
Note 735026 - Memory problems at BBP_GETLIST_INDEX_FILL
Note 932836 - BBP_GETLIST_INDEX_FILL: Activation not possible
879528 WS14000148: Send mail to initiator incorrect
901200 WS14000148 dia wrk item despite NO_FURTHER_APPROVAL_NEEDED=X
879873 BUS2000113: The Object_ID attribute may be empty
903015 BAdI Workflows: Events and parallel steps
901068 BAdI Workflows: Enhancement of Note 896556
769458 Dynamic workflows: No adjustment after document change
972757 Occurence of the SYSTEM_NO_SHM_MEMORY runtime error
741864 FinBasis: Termination TSV_TNEW_PAGE_ALLOC_FAILED
864473 Deactivating the shared memory when searching by prefix
928642 Container factory: Shared memory dump update
Refer to these links.
http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/26/0f8b41ed891609e10000000a155106/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/6b/eca441eea7ef0be10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/f7/a6a3415e34b05fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/6b/eca441eea7ef0be10000000a1550b0/frameset.htm

Also raise an OSS message with SAP as well.
Regards
- Atul

2 level approval

hi gurus,
i am developing a workflow wherein there's a 2 level of approval. 2 possible conditions are to be considered. 1, if the requested date and the filed data falls on the same day, it should be approved by a sup and a manager. if the request is more than 1 day from the filed date, then it will only be approved by sup.
im thinking of creating conditions to check if the created date is the same as the requested date and create a task under it for sup approval. im having a hard time now inserting the task for the manager. can anyone help me? any suggestions?
thanks!

Hi,
Write your conditions in a custom method or in a virtual attribute and based on that set a flag.
Now check for this flag.
Say for condition '1', your flag value is blank, then design your workflow for two level approval (Call Subworkflow 1).
For condition '2', your flag value is "X', then design your workflow for single level approval (Call Subworkflow 2).
Make use of subworkflows to minimize the no. of steps to be used in workflow.
Hope it helps.
Regards,
Raj

Material Plant Level or Planning Plant Level

Hi Experts,
May i know what ever the material lying in the warehouse whether it is showing the stock at Maitnenance Plant level or Planning Plant level.
Also is it possible to keep the inventry at Maintnenace Plant level.
Please provide your valuable information.
AR

Hi Experts,
You mean to say if there is no planning Plant we cant make the inventory ? Please correct me if i am wrong.
Also i want to know is it possible to maintain the stock at Maintenance Plant level.Because we have four Maintenace Plant 8000,4000,1000 & 6000 and all four are assigned under one Planning Plant 2000. Here i want to know is it posssible to maintain the stock under all four Maintenance Plant if yes then what i have to do for the same.
AR

Line Item Level Approval For SC-SRM7.02

Hi Experts,
I am working on the line item level approval based on cost center. can some one help me in achieving this?
i have few doubts regarding this
1) we are using application controlled workflow is it feasible to achieve this functionality ?
2) will separate PO will be created for each line item?.
some pointer would be really helpful.

Hi Mano,
1. Yes, but would suggest to use new process controlled workflow.
2. No, Cost center is not a split criteria for PO creation. Of course you can overwrite it with ABAP.
Regards
Konstantin

Determining second level approver for travel expense claim workflow

Hi Experts...
In Travel Expense claim workflow,we are using two level Approval.The employee has to enter his data for expense claim through ESS..Then expense claim is submitted and sent via workflow to the Travel department. Travel Dept verifies the expenses against the bill and approves the claim by selecting the next level approver and attaching the scanned copies of the bill.
I made copy from the standard workflow WS20000040.
How can i select the next level appover in first level approval step???
Is there any FM or BAPI or BADI???
Please help me ...
Thanks in Advance
Regards,
Hemalatha.

Hi Hemalatha,
I have small tricky workaround to find out the second level of approver.The Standard Rule available can reused again by passing manager's Position.i.e
After first level completed , store manager position in container variable and pass it to the same task rule so the task is sent to the manager's approver .
Message me if needed more details.
**Award Points if useful

Is it possible Line level approval in AME for purchasing requisition?

hi
is it possible Line level approval in AME for purchasing requisition ?
so that send each line to separate approver ?

If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
Thanks
Shree

Is it possible Line level approval for purchasing requisition in AME?

hi
is it possible Line level approval for purchasing requisition in AME?
so that send each line to separate approver ?

If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
Thanks
Shree

Comp Planning - 2 Level Approval

Similar Messages

Maybe you are looking for