Workflow Release steps

Hi,
We have 4 approval levels for PO. Once I create the PO and save, a mail is sent to the 1st approver(requisitioner). After the first level approver approves then it should go to the next approver and same for other approver levels.
my problem is once the first approval is done then all the other 3 approvals are done in background immediately without waiting for other approvers. I tried checking but unable to find the rootcause of the problem. can some help to fix this problem. Thanks.
Regards
MS

Hi MS,
I am not very sure if I understand the issue completely, but I guess you are facing the issue that after the 1st approval all the next 3 levels of approvers get the workitem for approval at the same time.
If yes, then please check the workflow template design as to how the approval flow is made. The approval flow should be designed sequentially so that the workitem goes from one approver to another after the preceeding approval is done.
Regards,
Saumya

Similar Messages

Additional PR release step while using standard workflow WS20000077

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. Release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the 1st release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise is it possible and how to implement the additional release step. Thanks.

Thanks for your quick response.
I also think about this to keep workflow side untouch by including one additional release code in MM release strategy configuration. Unfortunately material group is item-wise, material group of item 1 may not be the same as item 2 (unless we restrict all items' material group to be identical by user-exit). Otherwise, I'm not sure how to incorporate this into a document level overall release strategy.

SC workflow - "set status to released" step tRFC error

Hi All,
We have a "Shopping Cart without approval" workflow defined in our SRM system.
The workflow is working fine in Develpoment scenario however in Production it is stuck at "set status to released" step.
Checked that step and its a backgroung step with tRFC Object type.
When we click on tRFC Object Type it opens up "Transactinal RFC" screen with msg "error during tRFC call" and tRFC destination field as WORKFLOW_LOCAL_500.
Any help is this regard will be highly appreciated.
TIA
Regards,
Richa Sinha

Hi RS,
havent worked on SRM WF's,
check with BASIS on the Automatic WF Settings in SWU3 tcode, as you maintain RFC there, may be the RFC node in SWU3 is not active or something.
Hope it helps.
Aditya

Additional approval/release step req in WF20000397 (Rel. prc. blocked inv)

Hi Workflow Experts,
I am curretnly using SAP standard WF 20000397 for the release of (price) blocked invoices. The concept behind this wf is the following: Starting event is IncomingInvoice.blockedPrice (BOR is BUS2081). The system then determines the purchasing group entered in the purchase order an sends the workitem to the assigned users of the respective purchasing group. The receivers can than clarify the blocking reason and either mark invoice as not clarifiable or release the invoice. The WF ends then.
Problem/requirement: Due to compliance the puchasing group should not be able to release a vendor invoice for which they were the responsible purchasers. However, those guys are the one with the most knowledge about the purchase and therefore best capable of clarifying differences with the vendor.
The idea now would be to let them clarify things and do a first "release" and add another final release step after this task that is done by some superior. However, I have no idea how to solve this problem.
Thx in advance for any help. BG. Jo

Hello,
You can put some condition in workflow which will check if approver was involved in purchasing. In case yes then go for 2 level approval - 1st level by purchaser and 2nd level by superior. In case no then complete worklfow after 1st level of approval only.
Hope this helps.

How to approve or release a Custom workflow release strategy using a prog.

Hi There,
I am working with a custom transaction with release strategy using custom workflow. I am done with the module pool and workflow templates. And also I can able to start workflow using the FM SAP_WAPI_CREATE_EVENT.
My actual Issue is I have set of buttons in the module pool screen with names Approve (1 to 5) and Reject (1 to 5). When I press the "Approve 1" release strategy of the first person need to approved. Is there any Function Module or Classes for approving the workflow release strategy using buttons in screen.
Thanks in advance,
Viruman

Hi
Make use of the function module SAP_WAPI_DECISION_COMPLETE. To this function moduel pass the workitem ID and pass decision parameter value as 0001 for approve and 0002 for rejection action. You can check in this forum with this function module you will find lot of threads.
If its not a decision step then you can make use of SAP_WAPI_EXECUTE_WORKITEM or SAP_WAPI_WORKITEM_COMPLETE.
Regards
Pavan
Edited by: Pavan Bhamidipati on May 26, 2011 11:43 AM

Additional PR release step in current release strategy

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the first release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise how to implement the additional release step. Thanks.

Hi Arghadip,
Thanks for your reply. My intention to create different doc type is for separate set of release strategy.
In current release strategy, for example, if doc type = NB, creation indicator = manual and the total value of PR is $1K, then the PR requires release code A1 for approval and the approval is align with the company finance policy. The manager (with release authority A1) of the PR creator then selected by the user exit and assigned with workflow task.
For the request for additional release step, if doc type = ZS, creation indicator = manual and the total value of PR is $1K, then the PR requires release codes AA and A1 (new release strategy). The user exit will assign a dedicated position/user (not necessary the manager of the PR creator) for release code AA, and then assign the manager of the PR creator for release code A1. Therefore, even the total value of PR is also $1K, but since the PR item contains material group 80501, then the PR require an additional approval on top of the $1K financial approval.
Your comment is welcome. Thanks again.

BUS2012 Release Step Event triggered twice

Hi Guys,
When a PO is created the BO BUS2012 Release Step event is triggered twice.
I am using a condition for my workflow based on the release code.
What could be the problem.Kindly Clarify..
Rgds,

Hi,
Actually I think the problem is with my Start Condition. I have given a start condition(SWB_COND) in my workflow is follows.
Release code = A1 or Release code = A3.
When i check the event log two times event is triggered with an exception and with the following information.
1.Start condition returns 'FALSE' for object [BO,BUS2012,4500000131]
2<b>.Operator 'EQ': The value of the left operand cannot be determined.</b>
I think the second one is the problem. Any idea how to avoid it..
Rgds,

WS20000075: work item of 1st release step stays in status In process

Hi All,
I have activated and set up standard flow WS20000075 but the work item of 1st release (PO release strategy with 3 levels) step stays in status In process. The work item for the 2nd and 3rd release step are completed as expected.
What could cause only the work item of the 1st release step to stay In process?
Thanks a lot in advance

Hi,
I cannot see in what field the release code is filled in EKKO.
See here SWEL after 1st release:
And SWEL after 2nd release:
EKKO after 1st release
EKKO after 2nd release
release strat
Release strategy

Perform check after release step of purchasing requisition

Hi,
does anybody have a suggestion where to place best some logic which needs to be performed after a release step is performed successfully.
background: we use different types of Purchase requisitions, while each one is assigned to a static release strategy. I like to change it in more dynamic way by adding certain logic after a release step is performed.
example: if preceeding release step was 10 and purchase requisition is of type x then check purchase value and account assignment in order to process the current stepo automatically.
Currently the logic runs during a nightly job, but I would like to add it immediately after a release has been performed. I would imagin something like user exit, BusinessAddIn, or an event which I can use assign the job.
Can anybody suggest something?
Thanks in advance
Best regards
Torsten
Edited by: Torsten Hübsch on Apr 29, 2011 10:36 PM

Hi,
Enhancement M06B0005 is relevant for PR in case of overall release
Check on trx SMOD :
Enhancement        M06B0005
Short text         Changes to comm. structure for overall release of requisistion
--> Function module                Short Text
EXIT_SAPLEBND_004              Changes to Communication Structure for Over.
Enhancement        M06B0002 is for item-release
Short text         Changes to comm. structure for purchase requisition release
-->
Function module
EXIT_SAPLEBND_001
BR
Nadia Orlandi

Create a purchase order strategy with four release steps.

Hi all,
how can I create a purchase order release strategy with 4 release steps?
The steps have to be the following:
AC (Buyer);
CO (Controller);
FI (Finance);
AD (CEO).
I couldn't configure and add entries in "Release prerequisites" (trx.OMGS).
Best regards

Hi ,
The implemantation steps as follows ;
Materials Management -- Purchasing -- Purchase Order --Release Procedure for Purchase Orders
1 . Edit Characteristic ; You must create characteristics that related your strategy first . IN additonal data screen use "CEKKO " as table and appropriate field as field name .
2. Edit Class ; Create your class with class type - 032 . And enter your characteristics that created first step .
3. Define Release Procedure for Purchase Orders
                a.Create Release Groups and enter your class
                b.Create release codes related with Buyer , controller etc.
                c.Create Release indicator
                d. Create Release Strategies ; Enter your release codes and in classificaiton area , you must enter your values that related with characteristics that created step 1.

Problem in Workflow matching step

Hi,
I am facing a problem in Workflow matching step. I have user kaushikb assigned to it.
Execution Type: Any Single, Assignee Type: User and Execution Type: Any Single.
Match Record Scope: Records vs Records, Strategy: MDM_NAME.
This Strategy: MDM_NAME is based on 3 rules: MDM_NAME1, MDM_NAME2 and MDM_NAME3.
MDM_NAME1 is done based on transformations MDM_NAME1[XFM], MDM_NAME2[XFM] and MDM_NAME3[XFM].
Now my problem is even after matching and merging a large number of records it is not going to
the next step. Do I need to match and merge all duplicate records? If the Matching process is rerun
the score becomes less as the same records are compared again. After this the link assume gets activated and then clicking it activates the next step.
Regards
Kaushik Banerjee

Hi Kaushik,
Match step is an Automated step in the MDM workflow.On selecting this step you need to mention the strategy that needs to run on the records to match them.When you reach the Match step you need to Perform the step to run the mentioned Strategy .
When you Perform the Match step it will display the Matching result provided you select the Matching mode in MDM data manager.
You can merge or not merge the matched records Once your Matching is performed by the system, You can move your Workflow to the Next step which is Process.
When you are selecting Any single as your execution type it means you have more tahn one user for executing this task but you want any single one of them to perform it.
So whenever you have selected Any single as the excution type for any process .The user accepting to perfrom the task needs to Accept the task .
So when User1 wants to perform the task he will have to select Accept and then proceed with the task.
When the owner of the workflow is testing the entire workflow he needs to Assume the task as he is not the Assigned user but the Assumed one.
So if you have build your workflows correctly and moving in step as explained you should be able to select the next step
You can follow the below link to understand the process better:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0be83e4-a1e6-2a10-c1be-8395ae948844
Hope It Helped
Thanks & Regards
Simona Pinto

CK40N - "still open" material in "release" step

Hello everyone,
We have just released our 2008 standard cost. We use CK40N to do the whole thing, including the marking and releasing of the costs.
Under the "release" step, the status is green, there are no errors, but there are materials "still open" indicated. I can't figure out how to get the list of these "still open" materials.
Under previous steps (from selection all the way through marking, there are no open materials).
My question:
1. What's the easiest way to find out if there are indeed "still open" materials?
2. If there are, how do I fix them? Especially since everything seems to be processed all the way to marking.
3. If there really is no open material, then what does this number mean?
Any suggestion or help is really appreciated, since this really confuse us.
Thank you,
Suri

It seems that occasionally there are some issues (tho i still cant find what they might be) which prevent SAP from Marking or releasing a standard cost for a material. Resulting in the material appearing in the "Still open" statistics on the cost run.
In order to resolve this, try the following;
Firstly, try just re-executing that stage of the cost run by hitting the execute button for that step.
If this does not work then try the following;
Whilst still in the Edit cost run screen, in the transaction box, enter the transaction =CKSU and hit enter. SAP will run for a few seconds and re-calculate the statistics so that the Still open Quantity is added to the Errors column.
Then re-execute that step of the cost run by hitting the execute button.
SAP should re-process those entries which were not marked / released previously.
Hope this helps!
Phil

Workflow start step performs Exclusive checkout

We need to upload data to records that are in workflow and checked out by the workflow start step. Unfortunately the workflow start step performs an Exclusive checkout of the record which means that the background MDM Impor Server user cannot automatically join the checkout, the user first needs to be invited to the checkout, which needs a manual step of modifying the join permissions of the checkout, which is not what we want to do.
I have also noticed that when an existing record is checked out Exclusively the user's roles are pulled through into the permitted roles section of the join permission screen of the checkout. When a new record is checked out Exclusively the user's roles are not pulled through to the permitted roles section of the join permission screen of the checkout. This looks like a bug to me.
We are using MDM 7.1 SP08.
Please advise any workarounds to this problem. I can think of a few, but none are very elegant, e.g.:
1. Use API to invite import user to checkout before import is started (requires coding)
2. Get the user that owns the workflow to manually invite the import user (not guaranteed to remember)
3. Complete workflow and stat new wokflow without chekout before import is started.
Any advice will be appreciated.

Hi Johann,
I got you point.
Its not a bug in MDM these are the constraints in MDM :(.
To understand more read section CHECKOUT AND WORKFLOW FAILURE CONDITIONS of the import manager refernce guide.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/72b8e7a42301bae10000000a42189b/MDMImportManager71.pdf
In our lanscape we too have a scenario where we are creating/ records in MDM leaving Material Number Blank (Record Add workflow).
But once this record with balnk Material Number is syndicated to source system we stop this workflow.
Now from source system through change pointer we get a file immediately with material Number and MDMID.
which we process through MDIS and trigger another workflow(Record Import)
I guess this matches with the third option you described to start and stop workflow and trigger import.
Regards,
Neethu Joy

Excute workflow from step 3 by abap code

hI,
i want to excute workflow from step 3 by abap program. My workflow send mail from approval at 3 step.When approval is made then it will go for further processing.
please give me code if possible.
Regards,
Gurprit
Message was edited by:
GURPRIT BHATIA
Message was edited by:
GURPRIT BHATIA

hi Guprit,
based on my experience you must trace why your workflow is wait.
is it because the workflow is waiting for certain events ?
or is it because of an error occured in the step 3 of the workflow ?
if the worfklow is waiting for certain events, you can force it to continue with triggering the events that workflow wait ( transaction code SWUE )
if an error occured in the step 3 of the workflow, you need to trace it what kind of error .... and for certain case after you fix the error you can continue the workflow by using tcode SWPR and restart the workflow after error.
but unfortunatelly based on my experience, some times the workflow just stuck in the middle of the process and no error occured
it this happens, ussually i re-triggered the workflow
hopes it helps
cheers

Experiencing problems with workflow- validate step

I am experiencing problems with workflow->validate step in Hyperion FDM.
I am not able to export unmapped dimension members to Excel.
Earlier everything worked fine.
But now all of a sudden it has become a serious problem.
when I click Export to Excel,processing starts and it's never coming to an end.
Every thing is getting stuck up.
Could any one suggest solution to this as it is delaying my deliverable.

Try opening excel first, then doing the export from FDM.

Workflow Release steps

Similar Messages

Maybe you are looking for