Designing approval process scenario

Hello All,
We need to design an approval process where the line manager and the cost center owner need to approve the expense report.
With the available options we were only able to define a process that leads to a situation that an approver has to approve and expense report twice if the line manager and the cost center manager are the same. Is there an option to avoid double approvals by the same person?
Please suggest.
Thanks in advance!

Hello,
no, currently this is not possible to avoid or recognize 'double' approval, however colleagues from BTM/MSA framework team are working on a solution for the near future.
Regards,
Peter.

Similar Messages

Renaming SharePoint 2010 Designer Approval Process Action Variable Name

Hi,
I am creating a 7 level(Mutiple) Approval Workflow in SharePoint 2010 Designer.
Whenever i add a new Approval Task Process action it adds 14 to 15 varialbes like Duration Unit,Duration Description,IsApproved,IsDeleted,EnableContentTypeApproval etc.
Since i am adding 7 Approval Task Process actions i am getting the variables added as Duration Unit1,Duration Description1,IsApproved1,IsDeleted1 etc in the Workflow.
I want to rename them to track it in a better way so that i can change them like Duration Units-Level1,Duration Description-Level1,IsApproved-Level1,IsDeleted-Level1 etc.
I am able to rename all the varaibles except Duration Unit and Duration Description. I see the Local varaible type as Duration Unit for Duration Unit varialbe and i am not able to modify it since i don't see a Type Called Duration Unit in Workflow variables
type properties.
For Duration Description i can rename it but while publishing i am getting the error as mentioned in the below blog.
http://spnovice.blogspot.com/2012/12/spd-workflow-error-path-needs-to-point.html
It's hard to track this varible with names like Duration Description,Duration Description 1,Duration Description2,Duration Description3,Duration Description4,Duration Description5,Duration Description6 etc.
How to rename these two variables in Approval 2010 Designer workflow.
I see varailbes like CC and Approvers which i dont need.Can we remove the unused vaiables also so that i can have limited no of vaaibles in my workflow.
Please help.
Thanks, Vijay Arockiasamy

Scott,
I have created 7 different approval workflows on a single list.Just followed the recommendation from
Keith Hudson, J.D in this blog.
https://www.linkedin.com/groups/sharePoint-designer-2010-multilevel-approval-136589.S.5824115633184350208
But as per this blog the workflows triggers only when a new item is created not when a an item is changed.
I have few questions on these 7 workflows on a single list.
1.If the Approver rejects the request the request needs to reubmit it with some changes.In this case if the requestor edits the existing list item the workflow will not trigger.
2.I am using Wait on Field action.For Example if Level 1=Approved and Level 3 is pending then level 2 approval workflow will trigger.
In level 2 workflow i am using update list item action and updating the Level status=approved.Int this case level 1 workflow will also trigger if i am executing the workflow on both item created and item changed event.
Could you please help on this.
Thanks, Vijay Arockiasamy

When a task is expired in SharePoint Designer Approval Process?

Hi,
i set an approval workflow (with a few stages) in designer and set duration of 1 day for a task.
It seems that in case i set exact due date - the logic of task expiration does work - and the user get mail that task is overdue.
But when i set the duration of 1 day to a task - althogh after a day the task wasn't completed - no "task overdue" mail is being sent to the user.
What should i set? is there any workflow variable that i should set?
thanks
keren tsur

Hi Keren,
Thank you so much for your post.
As per your post, I understand that if we set exact due date, the user will receive the overdue email, and if we set the duration to 1 day,
the user won’t receive the overdue email although the task isn't completed, please feel free to correct me if I misunderstand you.
Given this situation, I would love to suggest we check the following information,
Please check if you have set Overdue Repeat to Daily not Off.
2.
Please also check if you have set OverdueRepeatTimes to -1, specify -1 to repeat indefinitely.
If the issue persists after we check above settings, it would be highly appreciated you can share with us the detailed steps for how to reproduce
this issue, and I will test this issue in my lab again.
We look forward to hearing from your update.
Sincerely Yours,
Serena Li
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Approval Process: Manager Resource Approver

Hi,
I want to design approval process for a resource and after several efforts I can't make it done.
Can anybody list a stab-by-step guide how to design a typical approval process for a resource, here is the scanario:
*1.* User requests a resource
*2.* Request is created and goes to first approver : user's MANAGER
*3.* After manager's approval, request goes to second approver : resource approver (group assigned to resource as approver)
*4.* After approver's (p.3) approval, request is completed.
I want to do that in Design Console , not in web workflow designer.
Thanks in advance!

Go to Process Defn > Create new > Select Resource > Type = Approval
Save it.
Create three tasks
Approval1
Approval2
Approval3.
Go to Approval1 > Task > Responses Tab
Select Approve Response and below in Task to Generate > Select Approval2 here.
Go to Approval2 > Task > Responses Tab
Select Approve Response and below in Task to Generate > Select Approva3 here.
Now go to Approval1 > Assignment Tab > Select Target User Manager as Approver.
Do the same for all the tasks Approval1, Approval2, Approval3.
You are done.

PO approval process in ECC for extended classic scenario

Hi All,
At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.
So our requirement is :
User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
Thanks in advance.
Regards,
Jennifer
Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

Hi Jennifer,
Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
Thanks and regards,
Ranjan
Ranjan Sutradhar

High-level design for business process scenario

Hi all, I have a business process scenario for which CRM and ECC has to be used. The scenario is like this:
There are 2 subsidiaries of a company - A and B, which are into trading of materials.
Between A and customer there is sales agreement. Between B and vendor there is purchase agreement.
Whenever customer requires materials, it will send request to A. So, A creates a sales order. B in turn sends a request to vendor for which a purchase order is created. The vendor ships the goods directly to customer. The vendor bills B for the purchase order. B adds some margin and then it goes for inter-company settlement with A. A bills the customer for the materials. In this entire process, both A and B earns profit through margins.
It has to be noted that CRM has to be used as contact point with customer.
Now I have the following questions:
1. How would the high-level business design be like?
2. How would be the document flow?
3. How can inter-company settlement and billing be done?
All constructive comments and feedback will be rewarded.

Hi Animesh,
The thumb rule to CRM process designing is stick to customer process...
Thus u jst hav to stick to process design of company A and its interaction with Customer.
We are not concerned with how the material will be purchansed,but we are concerned with how we will be delivering it to end customer.
Thus, once customer place an order to company A, our process would suggest a sales order for the customer with one of the partner function "Vendor" as B with the required material. Now later process in R/3 would convert this sales order with customer as soldtoparty to purchase order with vendor as B and one of the secondary partner soldto party as our original customer.
And billing would happen the way it is... ie. based on sales order.. thus u will have some inflow.. again u will be raising a purchase requisition to company B thus that would be your outflow..
That was a really good scenario to think about.
Best Regards,
Pratik Patel
<b>
Reward with Points!</b>

Remove the last task of the stand approval process workflow in SharePoint Designer

Hello,
I am building a workflow in SharePoint Designer. I have added the standard approval process that comes stock in SharePoint. I also have the approval set up to handle change requests. This is where my issue is. A user can eather approve
a document or request changes(according to some limitations i have in place on the InfoPath form). If they approve, the workflow is complete. If they request a change, a request change task gets assigned to another user. This other user then
completes their review and submits their response. this then kicks off the approval process again to the original user to approve.
1. User A recieves approval form - requests a change
2. User B recieves Form - submits that changes have been made
3. User A recieves another approval form - then can approve
I am looking for a way to eliminate step number 3. I want User B to be able to complete the approval when he submits the changes. I tried copying and pasting the approve button from the default infopath view onto the view that UserB
sees, which has a data submit action when the button is clicked. This did not work.
Any ideas would help

Hi,
According to your post, my understanding is that you wanted to add a “request a change” button in the Task Form.
If you can cutomize the task form, I recommend to add button directly and then add conditions and rules to the button.
After you add the “request a change” button, the workflow is similar to the
Multiple Approval Workflow.
Here is a great blog for your reference:
Implementing Workflow using InfoPath 2010 and SharePoint designer 2010
Best Regards,
Linda Li
Linda Li
TechNet Community Support

My designs are not showing, how long is the approval process

My designed personas are not showing, how long is the approval process
== This happened ==
Not sure how often
== Next day after uploading

A few days to a week, give or take.

Approved invoices can not be edited - Approval process

Hi Experts -
I have recently raised an incident with SAP about Approval process - the complete message and support reply is as follows - but i believe we need a change in the approval process - if the approval required is only one but you have defined two people (Either or OR) in the approver list - the system should allow the document to be edited if one of the approvers reject it.
please let me know and i believe we need a change in design - unless otherwise a solid reason is given to justify the existing design
10.07.2009 10:32 Description (English) by SRS Manian
     We have created approval procedure for all the invoices which are entered into the system., The
'Accts' user enters the invoice into the system - the invoice comes for approval to 'Manager' user.
When the Manager opens the invoice via Alert window - he/she wants to modify certain information
(lines as well as Sales person) and approve it.
The invoice which gets opened from the alert window - does not allow the user 'Manager' to modify at
all. All the information on the invoice are greyed out.
The system should allow the user 'Manager' to modify the information. Since the manager has full
authorization to the system.
10.07.2009 10:35 Info to Reporter by SAP
     Dear Partner/Customer,
We have received your inquiry and are currently processing it.
You will be contacted with a solution or an update as soon as possible.
For further details regarding the phase your message is in at the
moment please refer to:
http://service.sap.com/%7Esapidb/011000358700000575782007E
Kind regards,
SAP Business One Product Support
10.07.2009 10:59 Reply to Reporter by SAP
     Dear Manian,
Thank you for contacting us.
When the originator sends the document for manager's approval, note that the at that stage, the document is still in the 'Approval Process'. This is because the system is waiting for the 'Manager' to 'Approve or Reject' the document. Hence, looking at the Document, it is still in 'Draft - Pending' Status.
When the document is in 'Draft-Pending' Status, the document is not available for editing, because the system considers that it is still in the waiting process. In your case, the manager cannot edit t he document.
To amend the document, an action is required from the approver either to reject it first. Once rejected, it can be amended and re-sent for approval.
I have checked our knowledge base and noted that there is an article which describes the approval process. Please refer to the Expert on Phone Wiki Article (March 2009) with title: Why a draft documen t in an approval process cannot be modified by the originator?
The link will provide the explanation:
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=88735894
I have also attached Notes 1321234 and 1111431 for your reference.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 11:59 Reply to Support Center by SRS Manian
     Thanks for the reply. The scenario is when the Manager receives the
document for approval, he wanted to edit and add it. Your reply (and
documentations) states that it needs to be rejected first before it is
available for editing. When it is gets rejected - the person who
orignated the document gets an alert and he can edit it. Here the
Manager must get an alert so that he can edit the Rejected document.
When the 'manager' rejects the document, and goes back to the alert
window to open the document - it is still greyed out !!
How does the 'manager' reject the document and edits it ?
regards
Manian
10.07.2009 12:11 Reply to Reporter by SAP
     Dear Manian,
If after the Manager rejects it and still the document is not editable (greyed out), it means that the document may still be in the 'Approval Process'. When it is greyed out, what is the status of the document in the header? Does it say 'Rejected' or 'Pending'?
If it is still in 'Pending' mode, please verify the number of 'Approvers' set in the 'Stages' tab of the 'Approval Template - Setup' window. If there is more than one user listed as 'Approver', and o nly 1 approval is required, the system provides an opportunity to other 'Approvers' to approve or reject the document. If in your case, the number of approvers is 2, and manager 'rejected' it, the sys tem still keeps the document in Pending status as it waits for another approver's decision to reject or approve it.
Also, verify the number of 'Approvals' required. If the number of 'Approvers' who have not rendered their decision is greater than or equal to the 'Approvals' required (e.g. approvers - 2, required ap provals - 2) the system keeps the document within the approval process. This is to allow the other 'Approvers' to decide on the document.
I hope this clarifies the behaviour. If you can provide us a step by step screenshot of the issue, this may help us to provide a more accurate response.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 12:28 Reply to Support Center by SRS Manian
     Hi:
The status of the document in the Header says 'Pending' and the status
below the document number says 'Suspended' - it is not showing as 'Draft'
Regards
Manian
10.07.2009 12:42 Call to Customer / Partner by SAP
     Performed on: 10.07.2009 10:41:59 (UK)
Contact person: SRS Manian
Status of discussion: Customer not reached
Subject:
Called the partner but currently engaged on another line.
Would like to hold a webex.
10.07.2009 12:42 Reply to Reporter by SAP
     Dear Manian,
I'm trying to call you but there was no response on your mobile.
When the header says 'Pending', then it means the document is still within the approval process. Please check the Approval Template and see the number of approvers and the number of approvals require d.
The number of approvals and approvers may be greater than 1. In this case, the system waits for other approvers to approve or reject the document. Once all the approvers have rejected the document, th en the document will be released and available for editing.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
10.07.2009 18:11 Reply to Support Center by SRS Manian
     Hi:
Thanks for the reply - i tried this and found out the following:
1 - In the approval templates - we had mentioned number of approvals
required as '1'.
2 - in the number of approvers - we had mentioned two users
Though the template requires only one approvals (Either or OR) the system
expects both of them to approve or reject -
Can u please let me why is this behaving like this - or is this is the
way it is designed ? - if this is the way it is designed - i beleive it
is wrong - weneed to give a solution to the customer
regards
Manian
11.07.2009 05:52 Reply to Reporter by SAP
     Dear Manian,
Thank you for the information. The behaviour is a current system definition documented as per Note 1321234. I have attached the said Note for your reference. When only 1 approval is required and there are 2 or more persons are allowed to approve the document, the document does not get automatically rejected when 1 person 'rejects' it. The system waits for other approvers to render their decision b ecause a person may still approve or reject the document.
The design is not an application error. If you would like to change this design, please post your requirement in our SAP Business One Product Development Collaboration
forum. You can find the forum in this link:
/community [original link is broken]
The forum is beingmoderated by members of the Solution Management team specialized in certain areas, according to the folder you are in. Partners can impact the design of specific features by posting suggestions and feedback at this forum. Kindly refer to Note 1028874 which describes more on the above process.
As the request will be handled through another process, we kindly request that this support message be closed.
Thank you for your understanding.
Best regards,
Lorna Real
Support Consultant
SAP Product Support for SAP Business One
SAP Ireland
11.07.2009 09:02 Reply to Support Center by SRS Manian
     Hi Thanks for the reply - however, the solution given doesnot address the
problem we are beingfaced with our client
Is there a Development Request we can raise so that this problem is
addressed in future
I am going ahead and confirming this Message though
regards
Manian
11.07.2009 10:04 Reply to Reporter by SAP
     Dear Manian,
Thanks for the information. I understand the customer's requirement. As previously mentioned, please log a development request in this link:
/community [original link is broken] This is from Note 1028874.
Unfortunately,we at the support centre does not have access to the list of development requests. Hence, kindly follow the process in Note 1028874.
I'm sending the message back to your side for confirmation.
Best regards,
Lorna Real
Support Consultant
Product Support for SAP Business One
SAP Ireland
SAP Notes
Number     Short text
0001035200
Issue can be solved via existing documentation
0001111431
Deleting rejected draft documents.
0001167635
Maintenance Policy (L)
0001321234
Status of a document rejected within the Approval Process.

Hi Gordon - thanks for the reply - i am sorry i never realized that the message i raised could be messed up like this - the following is a clear message with some paragraphs:
Hi Experts - I have recently raised an incident with SAP about Approval process - the complete message and support reply is as follows - but i believe we need a change in the approval process - if the approval required is only one but you have defined two people (Either or OR) in the approver list - the system should allow the document to be edited if one of the approvers reject it. please let me know and i believe we need a change in design - unless otherwise a solid reason is given to justify the existing design
SRS Manian We have created approval procedure for all the invoices which are entered into the system., The 'Accts' user enters the invoice into the system - the invoice comes for approval to 'Manager' user. When the Manager opens the invoice via Alert window - he/she wants to modify certain information (lines as well as Sales person) and approve it. The invoice which gets opened from the alert window - does not allow the user 'Manager' to modify at all. All the information on the invoice are greyed out. The system should allow the user 'Manager' to modify the information. Since the manager has full authorization to the system.
Reply to Reporter by SAP Dear Manian,
Thank you for contacting us. When the originator sends the document for manager's approval, note that the at that stage, the document is still in the 'Approval Process'. This is because the system is waiting for the 'Manager' to 'Approve or Reject' the document. Hence, looking at the Document, it is still in 'Draft - Pending' Status. When the document is in 'Draft-Pending' Status, the document is not available for editing, because the system considers that it is still in the waiting process. In your case, the manager cannot edit t he document. To amend the document, an action is required from the approver either to reject it first. Once rejected, it can be amended and re-sent for approval. I have checked our knowledge base and noted that there is an article which describes the approval process. Please refer to the Expert on Phone Wiki Article (March 2009) with title: Why a draft documen t in an approval process cannot be modified by the originator? The link will provide the explanation:
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=88735894
I have also attached Notes 1321234 and 1111431 for your reference. Best regards, Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland 10.07.2009 11:59
Reply to Support Center by SRS Manian
Thanks for the reply.
The scenario is when the Manager receives the document for approval, he wanted to edit and add it. Your reply (and documentations) states that it needs to be rejected first before it is available for editing. When it is gets rejected - the person who orignated the document gets an alert and he can edit it. Here the Manager must get an alert so that he can edit the Rejected document. When the 'manager' rejects the document, and goes back to the alert window to open the document - it is still greyed out !! How does the 'manager' reject the document and edits it ? regards Manian
Reply to Reporter by SAP
Dear Manian, If after the Manager rejects it and still the document is not editable (greyed out), it means that the document may still be in the 'Approval Process'. When it is greyed out, what is the status of the document in the header? Does it say 'Rejected' or 'Pending'? If it is still in 'Pending' mode, please verify the number of 'Approvers' set in the 'Stages' tab of the 'Approval Template - Setup' window. If there is more than one user listed as 'Approver', and o nly 1 approval is required, the system provides an opportunity to other 'Approvers' to approve or reject the document. If in your case, the number of approvers is 2, and manager 'rejected' it, the sys tem still keeps the document in Pending status as it waits for another approver's decision to reject or approve it. Also, verify the number of 'Approvals' required. If the number of 'Approvers' who have not rendered their decision is greater than or equal to the 'Approvals' required (e.g. approvers - 2, required ap provals - 2) the system keeps the document within the approval process. This is to allow the other 'Approvers' to decide on the document. I hope this clarifies the behaviour. If you can provide us a step by step screenshot of the issue, this may help us to provide a more accurate response.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi: The status of the document in the Header says 'Pending' and the status below the document number says 'Suspended' - it is not showing as 'Draft'
Regards
Manian 10.07.2009 12:42
Reply to Reporter by SAP
Dear Manian,
I'm trying to call you but there was no response on your mobile. When the header says 'Pending', then it means the document is still within the approval process. Please check the Approval Template and see the number of approvers and the number of approvals require d. The number of approvals and approvers may be greater than 1. In this case, the system waits for other approvers to approve or reject the document. Once all the approvers have rejected the document, th en the document will be released and available for editing.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi: Thanks for the reply - i tried this and found out the following: 1 - In the approval templates - we had mentioned number of approvals required as '1'. 2 - in the number of approvers - we had mentioned two users Though the template requires only one approvals (Either or OR) the system expects both of them to approve or reject - Can u please let me why is this behaving like this - or is this is the way it is designed ? - if this is the way it is designed - i beleive it is wrong - weneed to give a solution to the customer
regards
Manian
Reply to Reporter by SAP
Dear Manian,
Thank you for the information. The behaviour is a current system definition documented as per Note 1321234. I have attached the said Note for your reference. When only 1 approval is required and there are 2 or more persons are allowed to approve the document, the document does not get automatically rejected when 1 person 'rejects' it. The system waits for other approvers to render their decision because a person may still approve or reject the document.
The design is not an application error. If you would like to change this design, please post your requirement in our SAP Business One Product Development Collaboration forum.
You can find the forum in this link:
/community [original link is broken]
The forum is being moderated by members of the Solution Management team specialized in certain areas, according to the folder you are in. Partners can impact the design of specific features by posting suggestions and feedback at this forum.
Kindly refer to Note 1028874 which describes more on the above process.
As the request will be handled through another process, we kindly request that this support message be closed. Thank you for your understanding.
Best regards,
Lorna Real Support Consultant SAP Product Support for SAP Business One SAP Ireland
Reply to Support Center by SRS Manian
Hi Thanks for the reply - however, the solution given does not address the problem we are being faced with our client Is there a Development Request we can raise so that this problem is addressed in future I am going ahead and confirming this Message though
regards
Manian
Reply to Reporter by SAP Dear Manian,
Thanks for the information. I understand the customer's requirement. As previously mentioned, please log a development request in this link:
/community [original link is broken]
This is from Note 1028874.
Unfortunately, we at the support centre does not have access to the list of development requests. Hence, kindly follow the process in Note 1028874. I'm sending the message back to your side for confirmation.
Best regards,
Lorna Real Support Consultant Product Support for SAP Business One SAP Ireland

PO approval process in ByD

We have been doing approvals of PO based on cost centre and value and happy with the way it works.
We now want to also do PO approvals based on Project Tasks and though on the PO you can "see" which cost centre is defined against that Project Task the approval process does not "translate" or recognize the relevant cost centre.
Is anyone creating PO's where the details are project task based rather than cost centre and how do you make the approval process work for these?
Grateful for any help
John

Hi Jennifer,
Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Offline approval process in ECC

Hello All,
Is there any way to achieve offline approval process in ECC the way it is in SRM?
We want to replicate the same process in ECC as in SRM, with mail being sent to the user with approve/reject buttons, and on clicking any of the options provided, the same need to be updated in SAP.
Any help will be highly appreciated.
Thanks in advance
Regards,
Razia Shaheen.

Hi Jennifer,
Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
Thanks and regards,
Ranjan
Ranjan Sutradhar

OIM Approval Processes

I have an approval process configured to go to the target user's manager first and then to a resource owner for the final approval. If a user request the resource the workflow works as expected, goes to their manager for approval and then to the resource owner. The issue I am having is when the user's manager request the resource on thier behalf OIM then sends the approval to the manager's manager which is not what I was expecting. I was expecting the manager's approval to be auto completed since it was the manager of the user who was submitting the request. Has anyone run into this?
Thanks

I found that the result I am seeing is actually how OIM was designed to handle such scenarios in the 9.1 release. Their logic is that a requestor should never be an approver which makes sense but I would have expected that if a manager requested a resource for a direct report the approval request for a target user's manager would get auto completed since it is the targets user manager making the request. Looks like I will have to write custom code to get the desired approval process.

Approval process (Release strategy of scheduling agreement)

Hi,
Recently we are trying to implement the approval process of scheduling agreements.
Client requirement is when ever there is a change in price irrespective of the following
1. Retrospective price change in any line item
2. Current price change in any line item
3. Future price updation in SA in any line item
4. New addition of line item
the system should trigger the release process (i.e. Approval process).
Our idea is to design the approval process based on document type and net value of SA. Based on which trigger should happened. But when we test it we find the following issues.
1. Trigger is not happening for future date price change or price for new period as the net value of SA is based on validity time.
Becuase the net value change will happen only on that onwards..
Also we are not using any cumulative pallned values in agreements.
Any can suggest the best solution to over come this..or Any user exit is avaliable to handle this issue.
regards,
K.Sundaresan.

Below are the (changed) item fields :
Purchasing Document Item Change Date AEDAT
Item Delivery Date EINDT
Schedule Line is "Fixed "FIXKZ
Below are the (changed) header fields :
Release Indicator: Purchasing Document FRGKE
Release status FRGZU
Purchasing document processing state PROCSTAT
Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on document type level ,I am also confused on this .
Please assist on this

How to use a pwa group in CREATE A TASK PROCESS in SPD 2013 for project server workflow approval process

I am working on a Project Server 2013 workflow. I am creating this using Sharepoint Designer 2013. In this workflow I am using approval process at one stage. I have created a security group SalesManagers in PWA. I want to use this group for workflow approval
process. I want all users of this group get approval tasks.
For this I used START A TASK PROCESS activity in the SP Designer. I clicked on
this user and created task process. But here I could not find SalesManager group which I created in PWA. I was only able to find the users. I can also see
Administrators for PWA . But couldnot find SalesManager or any other security group created in pwa.
Can anyone suggest how I can get the security group created in pwa.

NBDevelopment,
I believe SPD only recognizes the SharePoint Groups and not the project server security groups.
The Administrators for PWA, and few other groups like Project Managers for PWA etc., are synced SharePoint Groups with the security groups, which is why they show up in SPD.
You could create a SharePoint Group for the Sales Managers group and use that in SPD.
Cheers,
Prasanna Adavi, Project MVP
Blog:
Podcast:
Twitter:
LinkedIn:

Error during approval Process flow in Process controlled workflow

Hello Experts,
We are in SRM 7.0 classic scenario using Process controlled workflow.WE recently connected a new backend R/3 system to our SRM system i.e we now have 2 R/3 backend system connected to SRM system
It is regarding the two new additional account assignment categories that came into picture when we connected the new R/3 backend system to our SRM system, i.e. Asset and Network.
There seems to be some problem with the approval workflow for those SHC, that have such Acc *** Cats.
Please find below my obeservations:
- if you have just one line item in the SHC, and this item is either booked on Asset or on Network, than everything goes fine. After the Acc *** approval, the PR is created in R/3
- if you have SC with a mix between an "old" Acc *** Cat (Cost Centre, WBS and Order) and one of the "new" Acc *** Cats, than the workflow is not working as required --- the manager, that is responsible for the accounting approval of the two positions (e.g Cost Centre and Asset) gets only one work item in his approval overview --- in that work item, the two positions are there, but the Asset one is grayed out --- so, the Manager approves only the Cost Centre positions and than the SC is no longer with the approver --- if you observe the SC now from the requisitioner point of view, the status of the line items in the approval process overview of both(!) lines is "approved", but the overall status of the SC is still "in approval"
Can you all experts plz let us know why this is happening and how this can be resolved?
Any pointers will be highly appreciated.
Thanks & Regards,
RKS

Hi,
What is Resp. Resolver Name and Decision Type in your Process Level Definition? Did you create custom agent BADI implementation?
Regards,
Masa

Designing approval process scenario

Similar Messages

Maybe you are looking for