PR item release workflow issue

Hi All,
I have 1 issue with PR item workflow. We have PR itme based workflow with different agents for each line item.
The issue is when approver goes to execute the work item, all the other items are available to the approver to edit or release other items as well. We want to disable other items being available to the approver for which he is not the approver.
Thanks and Regards,
Srikar

Hi Srikar,
You can do this by using parallel processing in workflows. I am giving you the scenaio we use. We use this in invoices with multiple line items.
This scenario is implemented using a sub workflow. In the main workflow when you insert a multistep task, go to "Miscellaneous" tab to implement parallel dynamic processing. here you have to pass a multi line container element containing line item numbers. Your sub workflow will trigger one for each entry in multi line element. Do not do any changes to you PR object with in Sub Workflow just get the results of decisions taken by user back to main workflow. Like (App - for approval, Rel - For release, Rej - for rejecetion, etc). When you have all decision collected and returned to main workflow, pass the results in a multi line container element to an activity. Then based on results decide weather you want to release or reject.
Doing this if one person releases his line item, it will not effect the other workitems which have gone to other approvers.
We do agent assignment based on profit centers.
Best of luck.
Regards
Anuj Nagpal.

Similar Messages

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.

Purchase reqistion Release workflow issue

Dear experts,
My PR release procedure works well for releasing useing ME54N. All configs are correct & works well.
Now while trying to activate workflow for just the Director & VP level I have followed the configuration steps under SAP help.
But it does not work as I could not get email to be sent to SAP INBOX of user ( Director/VP)
I am listing steps that I have configured below using SAP help documents. Please guide what I am missing.
1. Under PR release procedure with classification ---> workflow -->
Created new entry for my Rel grp (M1)/ code (s4) / VP / plant 3010/ object - US (user) / SAP user id of VP
2. Under (Netweaver- SAPWAS) Basis --> Business Management --> SAP Business Workflow --> Perform Task-Specific Customizing). Next selected Materials Management --> Purchasing --> Assign Agents
3. The task TS00007986 ( Release Purchase Requisition) --> Create Agent assignment --> Select User ( SAP user id of VP)
Please advice the correct steps to activate workflow for PR release.
thanks,
Ram

Hi Ram
In SWI5 transaction, check whether a work item has got generated for director and VP or not.....
You will find the work items in SAP Inbox if system has generated a work item for director or VP....
That will narrow your analysis
Regards
Virender Singh

Issue in PO Release Workflow WS20000075

Hi All,
We have activated Std. PO release Workflow WS20000075 for two step release levels. When New PO created with release strategy this workflow will trigger and send workflow items to Agents to release Purchase Order. Up to this it's working fine.
But the problem occurs to trigger Workflow again after PO price change. We have release change indicator with 5% variance of price. That means when some one changes the Price or Quantity and if the total values variance more than 5% of price variance then Release strategy will activate again in PO. But in this case Workflow WS20000075 not sending workflow items again to the agents.
Is there any workflow setting causing the issue?

Hi Sivaparvathy ,
As far I can understand in SWEL event trace for the second time the event is getting triggered but there is no appropriate receiver for that event. Can you please specify the event name. If it is any event other than RELEASE for eg lets say if it is CHANGE, in the workflow WS20000075 header you will have to bind the workflow with this event and activate linkage for this particular event as well(without changing the previous configuration for PO release event). So that the workflow is triggered for this event as well..
Hope this helps
Regards
Anik

PR item level Release WorkFlow

Hi Experts,
I have activated PR item level release WorkFlow WS00000038. My MM consultant has configured release strategy with ME51N. The Work flow works fine On releasing it sends notification work item to initator but on release Refusal it don't send notification work item to initator. Can anyone guide me how to resolve this issue.
TS00007986 SINGLERELEASE
4 Outcomes of release
1) Positive Confirmation
2) Negative Confirmation
3) Confirmation Release Cancelled
4) Purchase requisition item significantly changed
Now 1) posative confirmation is working fine.
but when we reject release then in that case also the workflow log it is going in undefined output that is significantly changed.
can anyone help me to resolve this issue.
Regards,
Hari

Hi Hari,
When you reject a PR, 2 events are getting triggered (Significantly changed and rejection_started). You check this in Transaction SWEL by rejecting PR.
The reason why output is going to Significantly changed branch is in SWEL you can see that 1st Significantly changed event is getting triggered and then Rejection_started.
Solution1: Deactivate the Significantly changed event in termination events tab.
Solution2: Create an attribute(Database object) for your business object. This attribute should be of type EBAN-BANPR. Check if BANPR = 08 and then send the rejection mail.
I hope this clears your doubt.
Please Revert back to me if you have any queries.
Regards,
Gautham Paspala

PR item Release with Workflow

Hi All,
If anybody has worked on PR item release with Work-flow please share the process ...i know how to set up the PR release strategy but not aware of Work-flow setting...If anybody has the document please share......
I searched a lot in the Forum...but not getting the correct information..
Thanks in advance

Hi John,
The standard workflow template provided by SAP for PR Release item level is WS00000038. You can view workflow in transaction SWDD. You need to activate this template in basic data from u201Cstart eventsu201D tab.
In order to send notification mails from SAP to other services, such as Outlook, Lotus Notes etc, you need to configure SCOT.

Workflow for Requisition item Release

Hi All,
I need to create a workflow for Requisition item Release but I wish to receive one work item for the whole requisition and not for each item
and the method of the task will be collective release (leads to me55) so that the user can choose which item to release. Is that possible?
Thanks and Regards,
Inbal

Hi All,
I think i found the answer but i need help to do it.
Every time a work item is created, the system needs to check if there is another work item with the same Requisition No. and same release code in status=ready.
If not, it will send the work item.
result:
The first work item (first line in Requisition) will be sent, and as for the others (other lines in Requisition), as long as there is no work item with the same Requisition No. and same release code in status 'ready' the system will send it.
Anybody can help me?

Combine item-release & head-release PR

Hello,
I was wondering if it is possible to combine the two workflows for PR-release.
(header-release and item-release)
The requirement is the following : The user creates a PR, and the flow for item-release is triggered. If every item has been approved, a second flow should be started for an overall release on total amount of the pr..
Is this possible ?
thanks in advance !!
kr
Björn

Hi Kjetil,
sorry to react this late, I was on another project and didn 't had the chance to catch up on the issue.
I'm afraid it isn 't possible. I find it a bit a strange request from the client also. Requirement is that first, there's a workflow triggered based on material group (item), and after this is ok, a second flow is triggered on total amount of the PR.
The problem is that, when you want a header-release, Overall release of purchase requisitions has to be checked, and when this is checked,it 's not possible to use item-release.
I'll search further on this matter. But whenever there's someone who has an idea to solve this, please let me know.. It will be appreciated
kr
Björn

PO Release WorkFlow Error

Hi Experts,
I have a scenario with purchase Order 5 level Release. I have activated Standard workflow, Now for first level it works fine and first level user is able to release and also a notification is also sen't to the initator after. this is for release code A1.
But work item is not going to second level release at all.if i go and check the Workflow after first level release.WorkFlow is in deactivated status.
Plz help me to resolve this issue.
Regards,
Hari

Hi, Hari, I assumed that you have set the workflow administrator to yourself and any errors would be sent to you...
In my humble opinion...
Is the workflow not getting the release code at all (for second level onwards) or it is having problem with finding the agents for the second level approval?
Did you check the workflow log, to see the flow of the workflow? You are using a standard workflow or? I was using a standard workflow, but the multi-level approval is set in MM configuration. Using the standard workflow for PR Release, the workflow is run 5 times for 5-level-release, which means there would be a start event and and end event for each level of release. And in my problem, there is no ending event for the first level because the PR is created wrongly and the system didn't know where to flow the PR to.
My advise is, first check MM config and workflow agents are assigned properly for multi-level approval.
Second, check if the PR is created and released properly. I have faced errors similar to yours and it was due to the incorrect entries during PR creation.
Third, trace the events and workflow log in SWEL to understand the problem better. (Or maybe you should do this first, in case you haven't).
Basically, if the workflow gets deactivated everytime, it might be due to the Behavior Upon Error Feedback in SWE2, which means there is error occured.
Lastly, if there is an error in the workflow log, you could paste it here.
Hope it helps...
Regards,
YL

PO Release Workflow Problem

Hello,
This is regarding PO release workflow(WS20000075).
I fail to understand as to how I can trigger workflow on realising PO
from ME29N, though using SWUS (Test Workflow) I am receving message
in the sapoffice mail.I am not really able to link the application with the workflow.
Secondly I dont understand why the second task i.e., Release Purchase Order Effected' does not trigger when I test the workflow.The message i receive is 'Please release purchase order no ....' and not 'Purchase order Released' when I test the workflow using SWUS.
Kindly advice.
Regards,
Sumit

The deactivation is happening as there is some error in the instances. Please change the settings in SWE2 for WS20000075 entry and change the field of Feedback after error as Do Not Change Linkage. The error might be due to some authorization issue please check from SWEL and analyse accordingly.
Thanks
Arghadip

Vendor payments release workflow!!!

Hi all
Can somebody explain to me how we setup standard workflow so that all vendor invoices greater than 100.000 can be blocked for payment automatically & released by some other user?
I tried to give the document type "KR" to the workflow variant & tried to do invoicing for the vendor. But I do not how I could release that blocked invoice...Is there any specific tcode or I have to go to the proposal & change the blocked reason from P to 'space'.
Thanks for all your time....

Hello Morgan,
Payment Release Process
Purpose
For each workflow variant, you can specify the amount from which a payment release should be triggered.
You can differentiate between one, two, and three-level release. This enables between one and three people to be involved in the release procedure, thus supporting both dual and triple control.
Prerequisites
You have made the following settings in Customizing:
Release approval procedure
(document type and amount for each workflow variant)
Assign persons with release authorization
In order to do this, you must first create release approval groups that can be entered in the customer and vendor master records.
Depending on these criteria and the release level, you can assign release authorizations in the form of organizational objects (job, position, organizational unit) in Customizing. If you do not define any criteria (such as release approval groups), the system takes the initial value of these criteria when the payment program is run. For example, if the system was unable to determine the release approval group, the release approval procedure and the employees with release authorization are determined on the basis of release approval group zero.
Process Flow
Minimum requirements:
The payment release function must be activated.
The relevant document type must be defined.
An item containing the following specifications must be created for employees with release authorization:
Workflow variant
Initial release approval path
Initial level
Maximum amount
Employees with release authorization can also be determined and assigned by user exits at each stage of the release approval procedure.
Result
If, when the payment run is made, the system could not determine an employee with release authorization, then it sends a message to the inbox of every person who has been assigned the task "payment release". Only after all these people have released the payment will the payment block be removed.
If a line item is refused for release, it is forwarded to the clerk who entered it for correction. After the document has been changed, the payment release procedure begins again. If changing the line items necessitates further actions, these must be defined within the Workflow component. The event CHANGED has been preconfigured for this purpose in the standard workflow model. If you run this event, the system assumes that the line item was rejected for payment. However, the item is NOT forwarded for correction to the clerk who entered it.
If an item is cleared before it is released, the payment release procedure is terminated (event CLEARED).
===========================================================
Workflow settings: The standard system contains several workflow models for payment release: One workflow framework (WS00400012) and three sub-workflows. In Customizing for Financial Accounting, you can specify which sub-workflow should be used when the workflow framework is run. You can also enter your own sub-workflows. They must however send and receive the same data from the workflow framework as the workflow models do.
You can use the standard sub-workflows (WS00400011, WS00400021, and WS00400022) to carry out a one, two, or three-level payment release procedure. If you require more than three release levels, you can copy the workflow models, enhance them and then enter the enhanced workflow definition in Customizing for Financial Accounting.
Event Linkage for the Event CREATED
If an amount requires a payment release, the event CREATED is triggered when a document is posted.
In this case, you must go into the workflow framework in the Workflow Workbench and enter the event linkage for this event, as described below:
Data for Event Linkage
Object type
BSEG
Event
CREATED
Receiver type
WS00400012
Receiver module
SWW_WI_CREATE_VIA_EVENT
Check Function
Receiver type
FM (function module)
Global
X
Enabled
X
Standard Tasks for the Event CREATED
The standard system contains two standard tasks that are triggered from the workflow mailbox and used in the workflow models.
Payment release (line item)
Change (line item)
Creating and Assigning Organizational Objects for Payment Release
You must assign organizational objects (organizational units, jobs, positions) to the standard tasks. These organizational objects can be created either in Personnel Planning and Development, via the Workflow Workbench, or in Customizing for Financial Accounting (assignment of release authorization to employees).
When you create organizational units, you must assign them to jobs or positions. You can then assign users to the positions.
Examples for assignments:
Organizational unit X < Position Y < User
Organizational unit X < Job Y < Position Z < User
In Customizing for Financial Accounting, you can assign organizational objects to the workflow variant, the release approval path, the release approval level, and the amount. These objects then release the amount depending on these criteria.
The organizational objects for payment release defined in Customizing for Financial Accounting are automatically assigned in the background to the standard payment release task (TS00407862).
The organizational objects for changing line items after they have been rejected for payment must be assigned to the standard task "Change line item" (TS00407864), either in Personnel Planning and Development, or via the Workflow Workbench. Alternatively, you can define the task as a general task (Additional data -> Classification).
Changing Line Items
The workflow models described above all contain a pre-configured event (CHANGED), which triggers other events in the same fashion as a rejection does. This event can be triggered by change documents. You must define it via the Workflow Workbench.
Hope I had been able to help you. Please assign points.
Rgds
Manish

Purchase order workflow issue

Hi All,
A PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.If the release strategy is for a different user,its triggering the workflow.I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Please refer the thread below.
PO Release Strategy Issue
Replies will be greatly appreciated.
Edited by: Feddie on Jan 3, 2008 11:43 AM

Hi,
This is not workflow issue(work flow is different term)
It seem problem of BADI (program written for creation of purchase order based on sales order)
Take help of ABPer so he/she can solve this issue
Kapil

FI Payment Release Workflow Agent assignment and SPRO settings.

Hi Experts,
I am working on Payment release workflow for 2 stages. So for this i have activated the main workflow WS00400012 and for First level release WS00400011 and for second level release WS00400021.
Now where should i assign the agent for First level release and second level release ? and what setting should i do in SPRO as FI settings.
Any of you suggestions will be of great help me to resolve this issue.
Regards,
Hari

Hi,
Thank you for your reply.Should i mention the main workflow number in SPRO or
just the subworkflows alone ?.
Assign main workflow number
Can i assign users directly in workflow itself insteas of assigning position in SPRO.
Don't assign users inside the workflow, if the user id you want to change then again you have to change the workflow.
Regards,
Surjith

Troubleshooting Approval workflow issues

We are getting this message from time to time and are unsure how to troubleshoot it.
It seems as though something is changing the document, what is the best way to figure out what?
Approval on DOCUMENT NAME has ended because the item that the task process is running on was changed.

Hi Daniel,
1.What message do you get?
2. Look in the Workflow History list, eg "http://sp2013/Lists/Workflow History". Do you find any errors in there?
3. Is the user account starting the workflow correctly synchronized in the user profile database?
4. Is the user account starting the workflow different from the Worflow Manager setup account? (more info at
http://technet.microsoft.com/en-us/library/jj658588.aspx#section7)
5. Are the User Profile Service and App Management Service started? See the green frames in the screenshot below, taken from Central Administration \ Manage Services on Server.
6.Are the App Management Service Application and User Profile Service Application started? Their proxies should be started as well. See the green frames in the screenshot below, taken from
Central Administration \ Manage Services on Server.
For troubleshooting sharepoint workflow issues, you can have a look at the blog:
https://technet.microsoft.com/en-in/library/cc298927%28v=office.14%29.aspx?f=255&MSPPError=-2147217396
http://blogs.msdn.com/b/vincent_runge/archive/2014/01/07/troubleshooting-actions-for-sharepoint-2013-workflows.aspx
http://ranaictiu-technicalblog.blogspot.com/2013/03/sharepoint-2013-workflow-debugdiagnosis.html
https://infopathandsharepointdesigner.wordpress.com/2013/12/13/five-top-tips-for-troubleshooting-sharepoint-workflows/
http://blogs.technet.com/b/victorbutuza/archive/2009/02/26/how-to-enable-workflow-tracing-debug.aspxBest
Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Terminating Event in PO Release Workflow. Workitem is not terminating

Hi WF Experts,
I have done Purchase Order Release Workflow with 10 level release With 2 days dead line. Since standard release supports only 8 level release i have opted for Role Resolution Via User Exit 9 . and i am picking release codes from ztable.
I was working fine till now.But suddenly end users are facing problem that workitem is not terminating even after they have released the PO.
What could be the issue what is the terminating event for PO Release workitem.
Please suggest me how to resolve this issue.
Regards,
Hari

Hi Hari,
Please check if the following links helps:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/sap%252bworkflow%252bevents
http://help.sap.com/saphelp_nw04/helpdata/en/c5/e4b590453d11d189430000e829fbbd/frameset.htm
Hope this helps!
Regards,
Saumya

PR item release workflow issue

Similar Messages

Maybe you are looking for