CATS multiple level approval

Hi,
Is there a possibility of having multiple level approval for CATS workflow to be initiated from ESS using Java WD application.
Much Appreciated.
Karthik.

Hi,
We have a similar requirement . I have developed a workflow and dummy task to trigger the workflow . But since it is a background task this cannot be maintained in the config.
Secondly how can i retrieve the pernr and key date from the CATS DB table.
Can you please let me know how this can be achieved.
Thanks,
Saujanya

Similar Messages

Multiple level approval for overall PR release

Hi all
is there a template for multiple level approval for overall PR release ?
is there some alternative if there is no template ?
thanks in advance .
Naval Bhatt

Hi NB,
there is no std template for multiple approvers for PR release.
Create a copy of std template and implement ur logic to it.
Aditya

Configuring multiple level approval workflows

Hi,
1. I would like to know how to configure multiple levels of approval in a workflow.
For example, when a user self registers himself, the request must be sent to level1 manager and after his approval it must be sent to level2 manager for final approval.
2. I would like to know the difference between "provisioning" and "provisioned".
Path : Process definition->task->TasktoObjectStatusMapping
Thanks in advance

Hi,
For question no 1.
1.You need to create a approval process.
2.Create a approval task for example "Approve by Manger1". assign this to Manager level 1.If its not static assignment then you need to create task assignment adapter.
3.Create another approval task for exmaple "Approve by Manger 2" assign this to manager level2.
4.Have the 2nd task depends one first one so that until one is completed 2nd one will not start.
For question 2.
Provisioning status refer to when provisioning process is not complete.
Provisioned status refer to when provisioning process is complete.
You can map this status on the completion or rejection of any task.Usually provisioned status is mapped with success of create identity task.
Let me know if you have any more questions.
Regards
Nitesh

Why Template, request and operation level approval from 11g?

Hi All,
I''m very new to OIM 11g and could not understand the logic behind having three categories of approval workflow, sucn as Template, operational and request level approvals? In 10 g, on the contrary, we can achieve multiple level approval using one approval process against a resource object. Having said that, i think we can also achieve a multi level approval in one BPEL process using the serial or parallel type of approval. So, a single approval process, say request level approval process can be configured to catered to multiple level of approvals. If this is the case, i could not figure out the reason behind the availability of 2 further categories template and request level approval. Can anyone please shed light on the actual usage with a context and also render reference to a 10 g functionality for these approval categories.
Thanks,
Srini

Request Level & Operation Level :
Re: Difference requestlevel and operational level
Template Level : It is also same as Request Level where you can reject the complete request in one shot. In latest version of OIM i.e. OIM 11g R2, you won't find this Approval Level.

Multiple Levels of Approval Workflow in SPD

Hi-
I'm building a workflow that has multiple levels of approval behind it. I know how to set up the multiple levels of approval, but sometimes this workflow needs to have 2 approvals and sometimes it needs to have 3 approvals. I'm hoping to pull
the info in from a SP List, but am not sure to do with the different number of approvals needed. Does anyone have any suggestions?
Thanks a lot!

Yes you can create a column in SP List containing the Approver names. This should be a People/Group field or Single line of text can also work.
In your SPD workflow you can track the status of the previous Approver and based on this you may allow the workflow to move to next or stop it. Assuming that you will create a Status column having two values - "Approve" and "Reject".
If Approver selects "Approve" then workflow proceeds for next approval or else the workflow stops or if Approver chooses "Reject" then you may create a new task for the previous Approver and send him an email - Just a suggestion if you
have back and forth approval system.
If it is a simple sequential approval then can go for out-of-the-box Approval Workflow available. If there is some level of conditions then SPD workflow is an option.

Two level approval in Cats

Is it possible to have two level approval of timesheets in cats? If yes How to do that?

Hi,
Its not possible to have multi level approval process in current set up of SAP.
If you look at the current process flow time entry>approval> transfer (depending on the time entry profile some profile does not require approval level and direct transfer to receiving objects).
considering the present flow, approved time is waiting to be transferred to receiving objects. it means only one level was set up.
If you want to go for two levels please develop custom transactions from beginning of time entry to transferring. Else you can raise OSS note to have such functionality.
Thanks,
Sudhakar

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

How to Implement N-Level Approval for Bid,Live Auction,PO,Contract ?

Hi Experts,
I am new to SRM 5.0. My requirement is how to implement N-Level Approval for Bid, Auction, PO and Contract? Which steps should I follow for N-Level Approval? Can any one send me sample code and name of BADI where I have to implement the code.
Abhijeet Panse

Hi
Please check for <b>BBP_WFL_APPROV_BADI</b> using SE18 transaction for relevant Code as well and standard SAP documentation.
Related sample code and other useful pointers ->
WS14500015 is not working for Multilevel approval
Re: SRM / Shipping cart
Re: N Step Approval BADI - BBP_WFL_APPROV_BADI
Re: N-step BADI workflow
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/2c/e68d406b305537e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/17/40a86c773d6c41801d78af1a34b90f/frameset.htm
Multiple Implementation For BBP_WFL_APPROV_BADI
Re: Help needed on N-Step Approval WFL for SC
Re: N-Step 14000109 workflow - Unable to identify Approvers
Do let me know.
Regards
- Atul

Multiple levels escalation for deadline monitoring

Hi all,
We have a business requirement to perform multiple levels escalation in one of the workflow steps. If the approver does not approve the work item(WI) after one day, a mail notification will be sent to the approver. A second mail will be sent again if approver still doesn't approve WI after 48 hours. Then the third/fourth mail will be sent to approver and approver's boss if approver still doesn't approve WI after 72 / 96 hours. The fifth mail will be sent to approver's boss's boss if WI is not approved still after 5 days.
I know how to do simple and modeled deadline monitoring in workflow builder. But I don't know whether our business requirement can be achieved in workflow builder( and this is a step in dynamic parallel processing). Other option I have is to create an ABAP report to go through the table stores workflow run time data and make this report run several times a day in the batch to send mail notification reminder.
Did anybody have a similar business requirement like ours? What's the best way to handle it - build it in workflow builder or write an ABAP report?
Thank you in advance,
Merta

Hi Merta,
We had a similar requirement and this is how I achieved it:
1. Pleace your approval task into a loop (while not approved) and create a container element as the approval flag. This allows you to get out of the loop when the item has been correctly actioned. Also create a DL element to hold your calculated deadline value;
2. Create a method and task to determine the next escalation point based on how many loop passes the instance has had, ie:
Pass 1 - DL = sy-datum + 1 day;
Pass 2 - DL = DL1 + 1 day, and so on.
3. Create a method to determine who should get what. Link this to a condition so you know whether to send a mail or escalate the entire workitem. Create the notification as a send mail within the condition;
4. Change the Deadline parameters in your step to "Refer.date/tim" = Expression and bind the DL element;
5. Set the processing obsolete property to ensure the workitem is killed when a new pass (and therefore and new deadline/agent etc) is started.
See the following:
This one handles the loop/obsolete concept.
http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4b97e453d11d189430000e829fbbd/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/bc/ecdd5ad24e11d2b494006094b9ea0d/frameset.htm
Regards
Gareth

PR release workflow - issue in mulitple level approval

Hi Experts,
I have developed a new workflow for PR release strategy.
Business object: BUS2105 ( Purchase Requistion )
Triggerring event: ReleaseStepCreated
Step1: Workflow started ( Releasestepcreated)
Step2: Approve PR ( Agent1)
Step2a
If yes --> Released to next level (Agent 2 )
Step2b
If No --> Rejected and notified initiator
If Yes --> Notify intiator and exit
Step3b.
If no --> based on next release code and release
group get the next level agent and go to
step2
Step4: Workflow ends.
Issue:
For single step PR release, workflow is working fine.
When PR created with multiple level release, a workflow triggers and notifies the 1st level agent, when the agent releases the PR at 1st level and saves it , workflow is not proceeds to further steps to find the next level agent.
Here i am using the FM to fetch the approvers and assigning the same for release codes.
Please guide me...

Hi
''workflow is not proceeds to further steps''... do you mean that RELEASESTEPCREATED event is not triggered for next step ?
you can check this in SWEL that whether event is getting triggered after first release.
If yes then the issue is in configuration of release strategy where for all release code you need to mark workflow parameter 1.

Header and item level approval using N level BADI

Hi Experts,
I beleive we can use either header level or item level approval workflow (WS14000133 and WS14500015) using N Approval-BADI. Please advise what information approval will be able to see if we will be using WS14000133 (Header level approval). Can he see all line item information or header level only.
Regards,
Kamal

In SRM the same BADI is used for SC, PO, Invoice and others as well.. If you see the example implementation provided by SAP, you can see the use of CASE statement with different Business Objects and code under it.
Irrespective of the Header level or Item level approval workflow the same BADI has to be implemented.
The difference between Header and Item Level approval is
1) In Header level, approval or rejection is done for the whole cart (there can be 1 item or multiple items).
Approver will be able to see all the items in the cart.
2) In Item level, approval or rejection is done for each and every line item. here is an example ---
Line item 1 has Cost Center as Account Assignment Category and has to be approved by Users A and B.
Line item 2 has Internal Order as Account Assignment Category and has to be approved by Users C and D.
Item 1 goes to user A and once approved, it goes to B. they will not be able to approve or reject item 2. but we can restrict user A and B to see item 2 or not by setting a flag..
Item 2 goes to user C and once approved, it goes to D. they will not be able to approve or reject item 1. but we can restrict user C and D to see item 1 or not by setting a flag..
The SC will get released only after all the items are approved.
For Header Level approval, you need to fill the APPROVAL_TABLE.
For Item Level approval, you need to make use of APPROVAL_TABLE, ITEM_APPROVAL_TABLE and ITEM_APPROVAL_OBJ.
Examples provided by SAP might give you an idea how to code for Header and Item Level.
Hope this gives you some information .....
Regards,
PR.
Edited by: PR on Nov 25, 2008 10:50 PM

Converting WF to Multi level approval.

Hi,
I want to convert my standard WF to go Multi Level. I dont want to make any changes in standard. How can I achieve this and make my WF approvals n rejection go Multi level Approval.
Himanshu.

Hi...
What workflow are you talking about. Can you be more clear on your requirement.
If you dont want to make any changes in the workflow, but still you want mutliple approvals then i guess it will be difficult. For some workflows standard SAP has provided configuration in SAP IMG which will handle multiple approvals with a single workflow design.
Please let us know what scenario are you talking about.
Regards,
Gautham Paspala

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

Need multi level approval for Leave request workflow in ESS

Hi All,
Our requirement is for 5 levels of approvals for the leave request raised in ESS means After employee raises leave request ,it has to be approved by 5 managers one after the other. In standard system only 1 level of workflow and approval is available so please anybody suggest the solution . Thanks in advance.

in addition to the above content your workflow consultatn have to create this ask him to
refer this document
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
for multiple level of aproving the leave reqest and and orgstructure have to be well formed
ravindra

SRM 7 WF - Multi level approval

Hi ,
Currently I am struggling at one requirement in SRM 7 process-controlled WF.
Requirement goes like this.
Lets say . In SC there are 10 items
depending on some logic they are grouped like 3 + 3 + 4
This is achieved using area creation badi.
Also first level approvers for each area are assigned using agent determnation BADI.
Here comes the interesting part.
Depending on the approval limit of the approver next level should get created .
But it may be possible that area 1 ( 3 items ) and area 2 ( 3 items) are approved ate first step itself.
And area3 ( 4 items) may go to multiple level as the value of these 4 items exceeds the approval limit of the approver.
In short,
at first level I need a fork.
and depending on the group (area) value that perticular area only should flow thru multiple steps.
Guys,
I have achieved multilevel and fork parts separately but combining both is really a tough task for me .
Is it possible to achieve such results ?
Pls help me getting through.
Thanks in advance,
Ganesh.

Ganesh
Refer to this document on PC Workflow if this could help:
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/procurement/supplier-relationship-management/process%20controlled%20workflow%20%26%20custom%20brf%20expressions%20for%20complex%20approval%20processes%20in%20srm%207.0
Regards
Virender Singh

CATS multiple level approval

Similar Messages

Maybe you are looking for