N - Step BADI Approval Flow - Reminders & Dead Line monitoring

Hi,
I am on SRM 5.0 and we are using N-step BADI workflow for Shopping cart. We have coded the logic to pull the approvers and we got additional requirement of sending reminders to the approvers multiple time for example: 1st reminder on 3rd day and second reminder on 7th day and finally on 10th day the Shopping Cart should be moved to next level of approval.
So here there are 2 things that I need to achieve
1. Sending multiple reminders to approver on different days. 3rd day, 6th day etc..
2. Moving the Shopping Cart to next Approval Level if the existing approver has not approved it in specific duration of time.
Your inputs of achieving my requirements would be of more help.
Regards,
Satya

Hi Satya,
Workflow functionality Deadline Monitoring would be useful to you in such a case.
You can add a 'Requested End' condition to the workitem you need to monitor.
When the deadline is reached you can perform the desired operation. I your case you need repeated reminders. For this in the requested end branch, add a Loop step and send reminder mails as desired. Add a terminating condition for loop to say 10 days to stop sending reminders there after.
I had a similar requirement and this approach worked for me.
Hope thie helps!
Regards,
Saumya

Similar Messages

Dead Line Monitoring for Shopping cart approval(SRM 7.0 Process controlled)

Hi Friends,
I am using SRM 7.0 Process controlled Workflow. I need to do below.
Dead Line Monitoring details are given below.
If the approval workitem is not addressed in 3 business days by Approver, the approver would get reminder email notification. If approval Workitem is not addressed in 5 business days by the approver, then an email notification is sent to requester,approver and the workflow administrator.
How to obtain this. Please help me.
Thanks,
Balaji.T.

Hi Masa,
Thank you for your input.
You mean, shall we use BADI BBP_ALERTING for deadline monitoring.?
Infact, i have used
SRM Server->Cross-Application Basic Settings=>Event and Event Schema for Alert Management->Define Event Schema
In that i specified
WF_COMPL_LATEST_END->Message(low)->APPROVAL_DEADL_NOTIFIC_NEW : 24 hours.
But it is not triggering for dead line Monitoring(24 hours Later).
If any body faces this same problem, Please let me know.
Thanks,
Balaji.T.

Back ground job for dead line monitoring.

Hi all,
In Production, job name: SWWDHEX is scdhuled for dead line monitoring.
I want to know the condition periodic schedule of background job,
i am not able find out in Sm37. it is executing three in times in day, two times in one day, two, three days it is not executing.
can you please suggest me that what is periodic time is needed for this job.
Thanks,
Surya.

Hi Kjetil,
You are absolutely correct and I firmly believe scheduled deadlines is the way to go for the following reason:
A few years ago I was driving into the mountains to go fishing. It was a Friday and my project was finished and I was looking forward to catching some trout. Unfortunately I received a call from a customer with whom I had no contact who had gone live with HR/ESS that morning. basically their system had ground to a halt at about 10am. They were desparate so I turned around and went back.
The problem was they had set deadlines to 5 minutes in their testing system and this had gone to Production. And their 20 thousand staff had been sitting on their leave and overtime requests for a month. All processes in their system were either running SWWDHEX, or scheduling to run SWWDHEX.
Anyway, not a big deal to fix although the had to stop their EP and kill the outstanding processes before transporting the correct deadline timings and setting for scheduled deadlines. But I was too late to join my compatriots up in the mountains.
So:
A happy customer - 1 day;
Reputation in workflow - 10% better;
Not being at the best fishing in living memory (the party caught 20) - priceless.
Cheers
Gareth

N Step BADI Approval Workflow Error in SRM 7.0

Hi,
I have implemented SC Workflow Approval based on line item(sequential approval). I implemented process controlled workflow for this using N step Badi. Necessasy configuration done for each level at schema. All steps are executed per line item and agents determined using N step Badi /SAPSRM/BD_WF_RESP_RESOLVER.
Even in SC after the document is ordered, in approval overview tab i see the all level sequence with approvers name for that line item.
But when approved by first approver, it doesnot move to the next level for approval and the SC is approved bypassing all approvers in the following levels.
For example, if there four levels of approvals for one line item. as soon as the first approver approves the SC is approved and in SC Approval Overiew tab that contained four level of approval in it is now reset to one level with SC marked as appproved.
Have anybody come across this error.
Not able to figure out why it is happening so... need some expert advice.
Thanks in Advance.

Hi Masa .. thanks for your reply.
Was on vacation so could not reply.
I have below settings in SRM for SC
Process Level definition should be like this.
Level Eva.ID ; Resolver Task ID Decision Type
100 L100 R100 40007953 Item-Based decision for Partial Doc.
200 L200 R100 40007953 Item-Based decision for Partial Doc.
300 L300 R100 40007953 Item-Based decision for Partial Doc.
I have implemented /SAPSRM/BD_WF_RESP_RESOLVER for R100.
for grouping we are using line item number ... so each line item is a group.
Below are issues that i am facing now.
For say 2 line item in a SC... with 3 level of approvals for each line item. I am not able to approve one line item in a sequence. For example: If for first line item, when I approve level one .. then the workitem doesnot move to 2nd approver's inbox for that line item. Now if second items (asssuming there are only 2 line items in SC) first approver has approved then i see all second level of approvers available for all line item.
In short system waits for all one level approvers to approver for all line item and when all the line items are approved at one level then the workitems are available for seconds level of approval.
Is this the standard behaviour?
As per our requirement we wanted one line item shoudl follow the approveral sequence without being dependent on other items approval.

RFQ Dead Line Monitoring

Hi
The requirement is if the RFQ dead line for Quote submission is PAST DATE, but the quote recv from vendor after the dead line specified in the RFQ and when we try to enter the quotation price in ME47 system want to give error
How to do this?
Regards
Ram

Hi all
Any input?
Ram

N-step BADI approval SRM workflow

Hi,
I am implementing N-step approval badi for SC approval using header level workflow (WS14000133) in SRM 5.0. My requirement is to determine the financial analysts responsible for each line item and then the mangement approvers based on their approval limits. Financial analyst need to approve the SC concurrently before the management approvers receives the SC. I developed the code in the BADI to populate the approval table. First time when the SC is created the approval table looks as follows,
Index    Branch    Approver
1         1        FA1
1         2        FA2
1         3        FA3
2         1        MGMT approver1
3         1        MGMT approver2
FA1, FA2 and FA3 recieves the SC. The approval preview looks great. Since this is not item level workflow, FA will approve the SC at the header level.
Here is the Issue--
When FA1, FA2 or FA3 approves the SC, the approval index is incremented by 1 in the workflow, the SC is sent to MGMT approvers based on he index by skipping all the FA approvers.
In this scenario, how to develop logic to send the SC to MGMT approvers only after the FA approvers approves it. I mean how to control the index and branching in BADi. I am using header level workflow.
Any suggestion would be highly appreciated.
Thanks
Venkat

Hello,
You won't like my answer, but this behaviour is not possible with standard workflows.
First WS14000133 does not handle parallel processing with badi.
You could try the template WS14000141 that was at a time handling the branch number in approval table, but it is not officially support. I mean this is obsolete.
This only parallel processing is provided with template WS14000015, but it's at item level: separated item can be sent in parallel, but it's not working well if you try to send the same item in 2 branch.
You cannot send the same object in a parallel process, the reason is that the application layer cannot properly handle this.
Rgds,
Pierre

Workflow approval - 'n' step BADI, Approval hierarchy problem

Hi,
Description of the issue:
For a shopping cart approval, the approver's list determined by the 'n' step approval BADI does not include the user who is the immediate in the org. hierarchy. Rather the work item goes to the superior authority (say MD) for approval, which must not be the case.
Pre-requisites checked:
1. Checked the org. hierarchy - Proper.
2. Checked the Roles maintainence for shopping cart approval - All is fine
3. Checked for approval/spend limits also - All is fine.
4. Tested BADI/Business Object - Approval Table is empty & Approver_administrator is 'WF-Admin was informed'.
5. Workflow log (technical details) - Checked in the containers for 'Approver's list'.
6. Checked table HRUS_D2 for any substitutes assigned - All seem fine.
This is the org. hierarchy,
(A - Requestor) --> (B - 1st level approver) --> (C - 2nd level approver) --> (D - MD final level approval)
The approver's list shows two names instead of 3, that is only B & D and not C. Hence the work item goes to D directly than going to C.
Please suggest.
Best regards,
Harsh Dave

hi,
Well the approver list is created from the badi for n-step approval in SRM.
If you say that approver list is empty when testing the badi, then you have to check which workflow is used in your environmennt.
It could be that someone decided to create their own logic.
so start by finding out which workflow template is used in this scenario, also you can set external break-points for users in teh approval badi which would be executed if you you use the approval preview in SRM (I'm guessing it is SRM since it sounds like it)
Kind regards, Rob Dielemans

Dead Line monitoring is not working

Dear Friends ,
I have the belwo issue in my workflow . Deadline monitoring is not working in my workfloow.
Details of the Issue : --
I have a Dialogue step in my workflow , which sends workitems to the user .
Once workitem has cometo the user's SAP inbox it is in ready status . The user has not taken any action on that .The time perido mentioned in the " LATEST END" is 2 minutes , so the workitem should show " The follwoning deadline was missed latest end " for that workitem in theuser's sap inbox .
But this is not happening .
I have used this deadline monitoring concept many times , but i do not know wht is happening here .
Can any body please help me on this to sort it out .
Reagards
Prabhudutta

Hi Prabhudutta,
I think you have done all the necessary steps!
In such case what I feel the problem could be because of some minor thing that we might be missing...
Can you please check the below link and confirm if you have followed all the steps that it states:
http://****************/Tutorials/Workflow/DeadlineMonitoring/DM1.htm
Hope this helps!
Regards,
Saumya

Need help on Dead line monitoring

Hi,
I am facing some problem with deadline monitoring.
We have a workflow in which i have used latest end to trigger deadline monitoring.Its working fine.
I have to set a condition like whenever the amount is less than or equal to 10000usd,then only we should trigger the deadline message.
Please suggest how to do this?
I have tried using conditions tab.But its not working.
Thanks.

I think you made some typo's. You say the task goes to the first approver when the amount is greater than ( > ) 25000 usd (twenty five thousand US dollars). after a deadline has passed the amount should be checked and if it is equal or less ( <= ) than 10000 usd (ten thousand US Dollars) then it should go to the second approver. How would this be possible?
But if your equations are valid and you just missed a zero or something use a modeled deadline. Do the necessary checks there and take the appropriate actions (like do nothing or end the current workitem and go to the second approver).
Although I don't know why I answer this, because you already marked the problem as solved, so I take it you solved it already.
Regards,
Martin

Regarding Dead line monitoring & Background Job

Hi Dear PMs,
plz let me know regarding Deadline Monitoring (IP30) for Maint plan. Why it is requires? only for scheduling multiple plans at a time or is their any other reason?
What is the meaning of,
1. Interval for Call Objects
2. Rescheduling included
3. Immediate start for all in IP30 screen.
Why we need to run Back ground job? - only for scheduling open & save daily in background....or for any other reason?
requested you to giv in detail...
Thanks in Advance...
Amol.

In short, as the name suggest deadline monitoring is used to monitor deadlines so that any due activity could be done well in time. Deadline monitoring helps you to automatically schedule entries that are due within this period. With the help of Deadline Monitoring, you could schedule multiple Maintenance Plans at the same time from the same transaction with respect to Plant maintenance. For different modules it could used for different purposes. In MM/WM, it could be used for mass changing the batch status. It is also used in Workflows. W.r.t PM, Using IP10, you are able to schedule maintenance plans individually, so to reduce time delays and increase efficiency, Deadline Monitoring is used.
Using F1 help on each of these fields should be helpful.
Interval of Call Objects specify the duration for which you want to execute monitoring of due entries. For example, mentioning 1 mon here would show me all the maintenance plan due for the complete month.
Immediate start for all: You can use this indicator to show whether the maintenance plans that correspond with the selection criteria are to be scheduled immediately, or whether a list of the selected maintenance plans is to be displayed.
Rescheduling Inc: You can use the automatic deadline monitoring to schedule a maintenance plan again or for the first time. If you need to reschedule any maintenance plan after having scheduled it, this indicator must be checked:
The following link might help you understand:
http://help.sap.com/saphelp_erp60_sp/helpdata/EN/3c/abb350413911d1893d0000e8323c4f/frameset.htm
Executing in Background helps as it does not bother you to open up the ip30 screen and then print the document. The Document is printed automatically without you having to bother about it within the period u specify behind your background job settings. It could be monthly, daily, weekly, yearly etc. etc.
Edited by: Usman Kahoot on Apr 5, 2010 10:34 AM

Approver skipped during approval process in N-step BADI workflow

Hi,
I am some problem in n-step BADI approval process. For some reasons one of the approvers is skipping during approval. And later in the approval preview it observes that the approver, who is just above the skipped approver, is appeared twice.
I am not able to simulate this issue though this is happening in the system frequesntly though it is not for all.
Can you please let me know what is the problem in the system and how can we rectify this issue?
Thank You.
Regards,
Krish

Hello
sorry search for the n-step WS14500015 is the item based...
Another thing, you can try with testing to restrict the case to special conditions. Are there any added-approver there? Is there any approver who makes some changes to the SC? etc..
Daniel

Work item forward when dead line reached

Hi Every one,
I got change request to deploy the dead line monitoring for the purchase requisition workflow.
The workflow existing start with the agent determination step which will determines the approver and after that it has a custom user decision step( Dead line monitoring must be implemented for this task ) which will call the ME53N and if we say back it will give a pop-up with 3 options which are 'Approve' ,'Reject','Cancel'.The user will select one of the option and after that there is multiple decision step which have 3 branches will select one of the branch according to the user selected option and the flow continues so on.
Business Requirement:
If level 1 does not release requisition in one day, then it must go to Level 2.If level 2 does not release that requisition within three days then it must go to Level 3, escalation stops at level 3 and the work item must stay until unless level 3 make the action on the work item.
The work item forward must be happen when escalation takes place not the notification.
Please let me know the information aforesaid is not clear at any point.
Regards,
Rajesh
Edited by: bhupathyraju rajasekhar on Jul 9, 2010 1:06 PM
Edited by: bhupathyraju rajasekhar on Jul 9, 2010 1:23 PM

You can do this in many ways. This is one of them:
- Create a loop that goes around for the number of approval levels (so, 3-level approval means loop 3 times)
- Inside the loop, create a 2-branch fork with only one mandatory branch to complete: one for approval and the other waiting for "expired" event
- Set up modeled deadline monitoring for the approval step. Once the deadline is reached, you need to fire the "expired" event which will process the other fork branch.
- After the expiration branch is executed, you can add any tasks to change the status, etc.
Hope this helps,
Abdullah

BADI n-step SC approval - Approval Index and Data Change Problems

Dear forum gurus,
We are implementing SRM 5.0 (SRM SERVER 5.5 SP 9) in Extended classic. I am developing the BADI's to use the n-step SC approval workflow WS14000133.
Our approval process is as follows:
1. Cost Centre approver (based on CC with the largest value in the SC)
2. Financial approver (based on the total value of the SC)
I have done this now and it works as long as every step is approved!
I have implemented the BADI 'BBP_WFL_EMPL_WI_BADI' - method 'CHECK_REQUESTER_WI' to send back any changes to the cost centre to the shopper to review. The standard also sends back total value changes to the shopper in the same way.
My problem is that if the main CC or the total value of the SC are changed, the logic goes back to the shopper and then if the shopper 'Accepts changes', the logic skips the first apporver again and goes directly to the second (financial approver).
I think there are 2 options:
1. After the shopper accepts chnages, to restart the WF so a new WF template is generated. Then my logic will show the new CC and FI approvers again.
2. I change my logic in the 'GET_REMAING_APPROVERS' method so the apporval index is not assumed to be 1 or 2 only. I guess I will have to work with logic to read the history and apporval index, but this seems very complex.
Option 1 - I can't get this to work. After the shopper accepts changes I can't get the WF to restart in the 'BBP_WFL_SECUR_BADI'.
Has anyone fixed this?
Option 2 - The logic for checking apporval index and apporval history tables seems to me very complex. Has anyone done this and can they explain the logic to me if so? The problem here is that the sample code for this BADI assumes the approval indexis always 1 for the first step and 2 for the second step, but this is not the case!
Thanks in advance,
Best regards,
Nick

Hi,
I feel setting the parameter BBP_WFL_SECURITY for the Approver should do the trick.i.e. Restart the workflow adn the same approval process should be followed again.So plese adjust the value of this parameter for the Approver role in trascn PFCG.Also if you want to overwrite the settings of this paramtere(as maintained in PFCG),you can implement the BADI "BBP_WFL_SECUR_BADI".
For more info,refer the foll links:
http://help.sap.com/saphelp_srm50/helpdata/en/37/830b3b7e7ef74de10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/f7/a6a3415e34b05fe10000000a1550b0/frameset.htm
BR,
Disha.
<b>Pls reward points for useful answers.</b>

Complexity of using N-step BADI in SRM 7using Process controlled Workflow.

Hi,
Just as a big thought,
I have a Shopping Cart requirement, Here i am asked to develop a Custom workflow for SRM 7.0.
And the client is looking for us to use Process Control Workflows i.e(BRF integrated one).
I need to understand the complexity of using a N-step BADI.
How would be the complexity level if I use a N step BADI( ie Multiple approval levels on Line Item Based).
Kindly tell me the complexity of Using it and if any one has come across some requirement like this, then explain me that how did you face the situation.
Expecting an Earliest Response.
Thanks,
Shanky

Hi,
Is your project SRM 7.0 implementation project then you have to go for Process Controlled Workflow and if your project is upgrade then you can still go with Application Controlled Workflow but down line this has to switch to Process Controlled Workflow.
Best Regards,
Saravanan

User decision Dead line

Hi Experts,
I am having a user decision step type and for that i have deadline for 3 days it works fine as long as the person dosent click the work item.
In some cases the agent clicks the user decision workitem but dos't take any action for more than 3 days. In such a case also i need to send a dead line notification mail how to do this.
In this case the normal dead line is not applicable as he had already clicked the user decision but did not take any action.
kindly advice me on how to do this.
Regards,
Dheepak

you can keep a activity step after the user decision step and write the code which calculates the number of days passed and use the appropriate FM SAP_WAPI* to set the status of the workitem to "Ready" Status.
or
keep a wait step for 3 days and if the decision step is not in completed status, keep a "send mail" step which can remind the approver that the workitem is still pending for approval.
Hope others might give a better design...
Regards,
PR.

N - Step BADI Approval Flow - Reminders & Dead Line monitoring

Similar Messages

Maybe you are looking for