Increasing release strategy levels/steps

Dear gurus,
We recently added a release code (FC) on our release strategies for our purchase requisitions. The condition is that all Pru2019s have to be released and/or checked by the Financial Controller prior to being released by the process leaders.
Challenge
It has since been discovered that the last release code on each strategy can no longer release once the approval has been affected by the first release codes in a given strategy. How and where can this be sorted?
regards,
Chansa.
Edited by: DAVIES BWALYA CHANSA on Mar 16, 2011 9:58 AM

i assume you have now 2 heirarchy levels to approve the PR
to ensure that release is effected only after l1 and l2 are approved and also that L1 approval happen before L2 you may have to ( 1) check mark the box in release pre requisites , ( 2) in release status make the status released only for the level where both L1 and L2 are checkmarked. other lines to have blocked status. both are avialable under release strategies in OLME

Similar Messages

Revoke Release Strategy (Reverse Steps)

Hello Experts
Please help with following revoking issue:
In Release Strategy, every release code is authorized for its own release, however revoking of release can be done by any release code available in hierarchy on above level.
Example:
Release Group: PR
Release Code: S1 (Initiator), S2 (Head1), S3 (Head2)
Release Strategy: 01
When Release Strategy 01 triggers S1, S2 & S3 release codes comes for approval in the correct order which has been configured that S1 will initially release a document, S2 will be able to release the document when it has been already released by S1, S3 will release when the document has been released by S1 & S2 respectively.
Following is the problem:
Document released by release code S3 higher authority can be REVOKED by release code S1 or S2. We want is there a way we can restrict that S2 can only revoke release when S3 has revoked the release similarly S1 can revoke the release when it has been already revoked by S3 & S2 respectively.
Regards-Amit Bali

Hi Amet,
The concept of the Release procedure is the Approving the external document electronicaly....(insted of manual)
as per your case...
you have set up 3 stages for approval...S1,S2 & S3...
If every thing in the document is fine, it will follow the sequece of approval as per your configuration S1 ---> S2 ---> S3...
If any one feels it is not meeting the requirement they can reject... so that it will go to PO creater for correcting the things in the PO....
and again it will follow the flow of approval .... S1 ---> S2 ---> S3...
Hope this is clear to you..
Thanks & regards
Anand

ME54N Release strategy question over delivery tolerance limits

I set up a release strategy base on the over delivery tolerance level. My problem is when a Purchase requisition is saved as rejected, and i click on the button cancel reject it deletes the last release strategy level because now it is looking at the actual total value disregarding the over delivery tolerance level.
It works fine when the Purchase requisition is not rejected, and i can cancel or reject the purchase requisition without saving it and it does not delete the last line of the release strategy taking into account the over delivery tolerance level. I am using the user exit ZXM06U13.
Can someone give me some insight into this ? Thanks.

Hi Siva:
You should request the development key for this structure under your SAP system, then you can add the extra fields in CEKKO.
Good luck
Z.T

Workflow - Purchase order Release strategy

Hi All,
Good Morning
I had created workflow for Purchase order release strategy with steps(To Determine Agents, Release of Purchase order, Release of PO effected) and in Me21N I created PO and PO came to my SAP inbox(SBWP) and I released that PO and saved it.
but My problem is after releasing PO when I checked my Inbox again still that PO is sitting there, it is supposed to disappear from there
Can anyone please assist me to resolve this issue .
Thanks in advance.

Hi,
In standard SAP workflow, SAP is sending a mail item (notification) to SAP mail inbox. There is no action is required from there. So mail will remain their as mark as read. If you want to remove it than one needs to delete it from respective mail box.
Best Regards,
Bhagat

Shoul order type be part of release strategy or WF logic?

Hi,
In our release strategy for purchase order we have set up anything that is > £500 needs approving. This kicks of the standard PO wf, but the workflow should also only start if the order type = NB or 8000.
Can anyone tell me if the order type should be part of the release strategy or the workflow logic?
Thanks
Forhad

Hi,
See its purely based on the requirement, if you maintain at the release strategy level then the release strategy itself will not be available for those kind of PO's.
so its better to restrict this at Wf level thru start conditions.

PR release strategy with material group

Hi Experts,
Release strategy for Purchase requisition already configured with characteristics Document type and Total net order Value.
For fulfill new requirement we have created New character with Material group.Our requirement is for Two material groups separate release strategy has to be trigger and remaing other material groups old release strategy has to be trigger.For exple if X and Y are two material groups ,which require seperate release strategy.Other than X and Y material groups requir old release strategy.
all the material groups assigned to character.Blank material group also assigned to the character.In release strategy level in classification view we have assigned two material groups( X and Y ) for separate release strategy and remaining material groups and Blank material group to old release strategy.
   At the time of creation of PR if i give two material groups ( X and Y)for different line items, seperate release strategy is not triggering, where as old release strategy is triggeringIf i create PR with single material group( X) for all line items it is triggering seperae release strategy properly.
   For other material groups (other then X and Y )with different line items it is triggering old release strategy properly.
      Kindly help me to resolve the problem.

Hi,
Please add Blank material group to the new release strategy also.
Maruthi

PR Item Level Release WF not working after Release Strategy change

Hi Experts,
           I did PR item Level Release Standard Work flow and it was working fine now due to client requirement we changed the release strategy and now when the PR workflow triggers it gives the Below mentioned error.
I really don't understand y after changing the release strategy workflow is not working and giving the following error.
Even if i restart the workflow in SWPR the same error is occuring.
Exception occurred    - Error when starting work item 000000390118
PROCESS_NODE     - Error when processing node '0000000003' (ParForEach index 000000)
CREATE                   - Error when creating a component of type 'Step'
CREATE_VIA_WFM - Agent determination for step '0000000003' failed
EVALUATE_AGENT_VIA_RULE - Error in resolution of rule 'AC00000148' for step '0000000003'
AC00000148             - Object type 'TS' not valid
Executing flow work item   - Work item 000000390118: Object FLOWITEM method EXECUTE cannot        be executed
Executing flow work item   - Error when processing node '0000000003' (ParForEach index 000000)
Regards,
Hari

Hello Hari,
please set a breakpoint at function module
ME_REL_GET_RESPONSIBLE
and see what happends in section
    CASE t16fc-frgwf.
* keine Ermittlung
      WHEN space.
        RAISE nobody_found.
* Ermittlung über T16fW
      WHEN '1'.
If using the T16FW-table, it should go to '1', otherwise it may that a user exit under '9' is used. So please check this.
Best wishes,
Florin

Processor of PR item level release strategy

Hi All,
I need to pass the Processor determined from an item level Purchase Requisition release strategy to a WF container. The event is RELEASESTEPCREATED in BUS2009. I have created an import element container called 'Processor' from ABAP dict. data type MEACTOR.
In the binding for the WF trigger RELEASESTEPCREATED I cannot bind the 'Processor' wf container to the Event Object.
What are the steps which I must follow to add the 'Processor' to the RELEASESTEPCREATED event?
The release strategy in SPRO for item level Purchase Req release is complete and the Set-up procedure for Workflow is complete.
Thanks
Mike

Hi,
Go to SWO1, enter BUS2009. Click on create subtype icon there. Then enter all fields as say ZBUS2009. Now save your new BO. then implement and release it , i.e;
Edit> Change Release Status> Object type> to implemented. Again Edit> Change Release Status> Object type> to Released. Then go to events in this objects. Click on event RELEASESTEPCREATED. Then click on event parameter and create a event parameter.
Hope this solves your problem.
Don't forget to delegate ZBUS2009 with BUS2009 in SWO6.
Let me know if you have any queries.
Regards,
Raj

Purchase Requisition release WF with multi-level release strategy

Since it has been "a while" from my WF course and i lack experience with WF's (this is supposed to be the 1st one i implement, finally)...
The problem I'm facing is really in planning phase of sketching up how my scenario should look like. I have to create couple of WFs for a project that involve purchase requisitions and purchase orders.
The problem i'm trying to solve is logic concerning release strategy steps for this documents. They are set-up and well-deffined in customizing, but there are couple ofrelease steps for particular strategy.
Scenario:
1. someone creates a purchase requisition (event for BUS2009 is triggered, and workitem appears for release of Purch. Req. in their workplace)
2. initiator of workflow executes his workitem and selects one of the release codes (this workitem is now complete) - i'd like for new workitem to appear in supervisors inbox automatically...
3. now i need supervisor of initiator to release same purch. requisition with another release code (how to do it?)
4. supervisor of supervisor (mentioned in step 3.) needs has the authorisation for final release with final release code.
5. now the initiator from step 1. has to be notified that requisition has been released by overall head of department.
Org structure i created looks like this:
ORG. UNIT. Level 0 for Purch. Req. (with Head CEO of Plant as final approver)
ORG.Unit. Level 1 for Purch. Req. (with Head of level 1)
ORG.Unit. Level 2 for Purch. Req. (with Head of level 2 and Clerks 2a,b,c)
So these guys (Clerk) 2a,b,c create Purch.Req. They or their Head of level 2 releases their requisitions with his release code Z1,
Head of level 1 should recieve workitem in his inbox to be able to release it with his release code Z2.
Director of the plant should recieve workitem for final release Z3, after Head 2 did his release with Z2, and then guys 2a,b,c should get notifications that their PR's are released.
I managed to get the SAP's standard for Purch. Req. Release working but it's just not enough...
Please advise me, guide me, if u have any idea, how could this be done, because i'm loosing a lot of time here, just searching and not seeing it. The problem is that we don't have any WF experienced guys that could help, so i'm kinda' stuck.
Could standard be used here at all?
Is it possible that the same task (for example. TS00007986 - Release requisition) appears more than once in the sam WF with different agent asignments?
I dont have an idea how this scenario should be built in WF builder.
BTW, i'll have 12-15 plants, does that mean 15 different WFs and Org Units?
Help WF gurus.
Thank you in advance,
BaX

Its' a while since I last time worked with PRs, but I'll give a try...
This part is a bit confusing:
>1. someone creates a purchase requisition (event for BUS2009 is triggered, and >workitem appears for release of Purch. Req. in their workplace)
>2. initiator of workflow executes his workitem and selects one of the release >codes (this workitem is now complete) - i'd like for new workitem to appear in >supervisors inbox automatically...
>3. now i need supervisor of initiator to release same purch. requisition with >another release code (how to do it?)
Why do you want that the initiator (the creator of the PR) needs to go the business workplace and release the PR (or select the release code). Isn't this an unncessary step? Shouldn't it worked like this:
1. Someone creates a PR
2. PR "gets" a release code automatically with some logic defined in customization
3. PR release work item apears in the supervisor's workplace
4. Initiator gets the mail
If I recall correctly, the standard solution works like this, or has quite similar approach.
Whatever way you decide to build your workflow, you won't most probably need a workflow for each plant, but you'll need several org units. But this all really depens on how you decide to do it...

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.

Customizing steps of workflow for Release strategy

Hi Experts,
Iam looking for step by step customizing details of workflow for Release Strategy for Purchase Requisition.
I need necessary classification and Customizing settings for a release procedure in the purchase requisition to the workflow.
I am looking for the steps, in which the purchase requisition can be edited straight from the workflow inbox.
Regards
Nani

Hi Nani,
First you have to confirm what kind of release it is in Purchase req you have Item level release and over all release.
Item level release - WS00000038
Over all Release - WS20000077
Now please confirm with your MM consultant that he has done the release Strategy and tesed it Ok.
Escecially things like assigning plant, Assigning Agents,Release codes and so on when everything is done by him in SPRO.
Now your work starts If it is just release use the standard workflow.
If they need additional notification mails and things like that copy the standard workflow and do the customization in the copied version and deactivate the standard workflow.
You can also do dead line monitering (Factory Calander) and many more things.
also please go through these 2 links you will get better idea.
http://www.****************/Tutorials/Workflow/POReleaseStrategy/Details.htm
http://www.****************/Tutorials/Workflow/PRRelease/PRRelease1.htm
If you have any othere queries please feel to ask.
Regards,
Dheepak
Edited by: dheepak on Dec 1, 2008 7:48 PM

PO and SchdAgreem Release Strategy at Item Level

Hello!!
I have the request to setup a the release strategy for the PO and Schedule agreements at line item level....
as far I know for PurReqs is possible to do that... but for PO and SAs it is only at header level...
Do you know if is possible to do that in configuration??

Hi,
Release strategy for PO & SA is only at Header level, since these documents are external purchase documents.
But, PR is internal purchase document and release strategy is possible at both item and header level.
i think, it is not possible to do release strategy at item level for PO & SA as you said,
Regards,
Srinu.K

Release strategy determination for PO item level characteristic value

Hi Experts
I have user material group as release characterstic for PO.
I have created two line items with two different material groups.
How the release strategy determination occurs when the two different material groups are linked to two different strategies?
regards
ramSiva

Hi,
in this case system is NOT able to find the release startegy.
Please take care of the following explanation (see note 365604)
o For OVERALL RELEASE (purchase order and purchase requisition) the
   item fields such as Plant and Material Group will be aggregated
   to header level.
   For example you use Plant/material group
as one of your characteristics. If all
items do not belong to the same plant/material group
then
*******the relase strategy will not be found***********
unless you have maintained a blank value as one
of your allowed values for the characteristic Plant/material group
. If all items
belong to the same plant7material group
then that plant is aggregated to the
header; if one or more is different then a blank is aggregated to
the header.
If you use an overall release strategy all
characteristics which you have defined in the customizing (CEKKO-MATKL
must have the same value. If one item has material class x and the
other y the system does not know with which material class it should
look for a release strategy. Now the system sets the material class
to 'blank' and tries to find a release strategy. If you do not have
defined a blank entry in the customizing (Transaction: OMGS
: OLME >release procedure for PO > rel. strategy ) the
system won't find a release strategy.
you need
to add a blank value to your allowed characteristic values in your
release strategy. To do this you can define a blank value in your
characteristic (CT04). On the values screen leave the char.value
blank and add a description and save. Now in OMGS you can select
this value as an allowed value for the characteristic.
(Example:
To avoid this you can do the following:
- go into transaction CT04
- enter the characteristic 'CEKKO-MATKL'
- click on the tab 'values'
- set a flag in 'additional values'
- in the column 'Char. value' do not enter anything
- in the column 'Description' enter a text like 'no material class'
- save this setting
Now
- go into transaction OMGS -> button 'release strategy'
-> button 'classification'
- double click on CEKKO-MATKL' and set a flag in 'no material class' )
Please also have a look into the attached note 365604 point 2d).
BR
Nadia Orlandi

PR release strategy at header level

Dear Experts,
I have one query, I have configured a release strategy for purchase request and I have done all necessary settings. However by default the release strategy is getting applied at item level.
Could you please help why it is happening?
Thanks in advance.

Hi,
please activate overall release indicator for PR document type.
SPRO > Materials management> purchasing> purchase requisition> define document types. acitvate overall release indicator for your PR doc type.
Regards
Hari

Release strategy on doc. level isn't working because different values for B

Hi,
At my company we just created a new release strategy (3rd) for PR's. The old strategies were on item level, the new one is on document level. This is the third strategy in the system and with every new PR the strategy is decided based on the creation date (table EBAN field BADAT). For example:
Strategy 1 - BADAT < 2009.01.01
Strategy 2 - BADAT >- 2010.01.01 AND BADAT < 2011.01.01
Strategy 3 - BADAT >2011.01.01
These selection criteria are stored in the class.
This used to work fine between the 1st and 2nd strategy but now it doesn't. Whenever a new line item is added on a different day than the other line(s) the value's for BADAT will be different within the PR and the system isn't able to select a strategy. It's like no value is used for BADAT because there are more than 1 available. As a result the release tab will disappear and the PR will be ready to create a PO from it.
For example:
Line 1 BADAT 15.09.2011
Line 2 BADAT 15.09.2011
No problem releasing the PR
Line 3 BADAT 17.09.2011 added (release strategy reset)
Release tab disappears so no release can be done. However, this PR line 3 can now be converted into an PO without being ever released.
One solution we thought about is using the PR number BANFN. But no ranges are allowed in the class so it doesn't seem to work. Another option is to delete al the old strategies but what will be the consequences for all the old PR's?
We are not sure what to use. Maybe someone else worked out this issue before or has an idea?

Hi,
First of all why you want to release a PR based on Creation date ?
Anyhow, as I understand from the above explanation, since you have created your 3rd strategy @ header/document level. You are facing this issue.
If you have a strategy @ document level then why you want 2 separate strategies @ item level.
Following are the possible solutions as per my understanding
1. You can make the 3rd strategy as item level itself so that the different creation date for different items wont be a problem.
2. You don't have to delete the Old release strategies instead you can remove the characteristics assignment so that release strategy wont be determined @ item level & you can keep the new release @ document level. But in this case you cannot have creation date as a characteristic since it will result in the same issue..
Thanks & Regards,

Increasing release strategy levels/steps

Similar Messages

Maybe you are looking for