Release strategy challenge

hi all.
our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
their release is based on several factors:
1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
2) amount 2001>6250 it must be released by the following:
WC1and/or Maintenance manager
or
WC2 and/or maintenace manager
or
WC3 and/or maintenance manager.
the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases, the Preq is released.
anything >6250 must be released by the maintenance manager.
our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2.
can someone help?

Hi Alisa,
Your Requirement is very Complex,
first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
for that you need to have different Release codes assigned to the user in the roles.
for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
Please revert back.
Regards,
Yawar Khan

Similar Messages

Challenge for release strategy in Preq

hi all.
our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
their release is based on several factors:
1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
2) amount 2001>6250 it must be released by the following:
WC1and/or Maintenance manager
or
WC2 and/or maintenace manager
or
WC3 and/or maintenance manager.
the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases first the Preq is released and there is no further need to release by WCn.
anything >6250 must be released by the maintenance manager.
our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2: how can i set the strategy in such a way that it can perform the release and/or?
can someone help?

Hi Alisa,
Your Requirement is very Complex,
first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
for that you need to have different Release codes assigned to the user in the roles.
for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
Please revert back.
Regards,
Yawar Khan

Workflow for PR Release Strategy

Hi Expert,
   Is there a way the scenario given below will be possible to achieve..
   All the needed config for the PR release strategy has been define... (release code, group,release strategy,class & characteristic)
Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager ( Release Code :PM)
The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

Hi,
Thanks..but i have completed all the setting in PR release strategy .. -
Am looking for alternative/ ways that i can incorporate the partner function from SO using the sales order
as the link from the PR (charge to sales order) to trigger where the notification will flow through...
This is more i think in the workflow or userexit or abap, but i took the libertly of posting it here perhaps some of the member had this requirement before and how it was accomplished..

Re: PR Release Strategy with workflow

Hi Expert,
   Is there a way the scenario given below will be possible to achieve..
   All the needed config for the PR release strategy has been define... (release code, group,release strategy,class & characteristic)
Parameter : Doc Type,
                  Amount
                  Acct Assignment Cat ( K,A,C)
                  Cost Center
                   Sales Order
The challenge is that when the given
               Doc Type - NB
               Amount - >0
               Acct Assignment Cat = C
               Cost Center - Empty
               Sales Order - 9999
The PR will be subject for release strategy of Project Manager ( Release Code :PM)
The PR should be sent to the approver (through workflow) which can be found in the partner function maintain in the Sales Order
9999..Partner Function   ZM - Proj Manager. which contain Employee No ( from HR)
She

hi
i think u need workflow for release strategy
Steps involved are :
1) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Release Codes > here assign Workflow indicator as "1" against each Release Code
2) SPRO > MM > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders > Workflow > Here against each release code assign OT as US and respective User ID's for Release Codes.
3) Go to OOCU > here under MM, go to MM-PUR,
4) Click on "activate event linking"
5) Go for "WS 20000075" and for BUS2012 RELEASESTEPCREATED, click on Detailed view button. Activate "Event linkage activated" and also activate "Enable usage of event queue"
and Save.
6) Click on "Assign agents" and proceed all above steps.
BUS2012 is the relevant business object and Releasestep created is the event for the same.
7) Check SWETYPV transaction for the WF you have activated for BUS2012 and confirm.
Test the same by creating a PO and check the SBWP for SAP Mail of respective Users
take help of ur BASIS person
hope it clears
regards
kunal

PR Release Strategy tab processor field is not getting displayed

Hi Experts,
While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
release strategy - Release code -work flow 1
That processer name is not displaying
Thanks
chandoo

This is the workflow forum.

Release strategy for purchase requisition does not kick in

Hi Gurus!
I've been struggling with this issue for some weeks now.
I have set up the release strategy configuration for purchase requisitions with classifications.
However, if I create a purchase requisition the release functionality is not taken into account by the system.
See below some more information regarding my configuration:
1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
4. I have 5 release codes. Grp: T1, Code: 01....05
5. I have 2 release indicators:
"R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
"X = Blocked", Changeabil: 4, Value chgs. 100,0
6. I have 1 release strategy:
"T1 with Grp T1"
- one release group, 01 Manager
- release prerequisites not applicable because of only one release group
- release status, nothing marked = blocked, 01 marked = released
- classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
I intentionally kept the configuration as simple as possible so I can try to get it working first.
Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
Could you please assist in getting this working?

Hi,
Have you checked in CL30/CL30N if your release strategy is derived successfully?
See section 3 of Note 365604. A small section of it:
You can use transaction CL30 search for an object using the data
of the purchase requisition/purchase order. Here, it is important
that the object search determines exactly one strategy. If this
is not the case, this indicates that there are overlapping
strategies in the system or that the release strategies in
Customizing do not correspond with those from transaction CL24.
See the previous point. If the object search returns more than
one result, the system subsequently determines an incorrect
release strategy or no release strategy at all.
If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
The following assignment statement has to exist within activated SAP
enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
for purchase requisitions:
E_CEBAN = I_CEBAN.
Regards,
Purnima.

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

Hello everyone,
I've run into an interesting problem:
We have defined several PO release strategies. Most of these work in the traditional manner, requiring manual approval by a given user. One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
What would cause this discrepancy? The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
Thank you ahead of time for your help.
-Jarrod

Configuration issue/user error.

PO Release strategy

Hi,
I have a unique requirement in PO release strategy. The requirement is if the PO doesn't have any contract it should be subjected to 2 step release process. If there is a contract then it should be subjected to 1 step release process.
Now i have created 2 release strategies one with 2 step release and the other one with 1 step release with the same charecteristic values. The only exception is i have used the 'USER DEFINED CHARECTERISTICS' - USRC1 with the value of X in one step release strategy and the value of BLANK in 2 step release strategy.
After doing all these settings Release strategy is not trigerring at all. Firstly it has to trigger the release then using the exit we can change the release strategies depending upon the conditions.
Any suggestions are highly appreciated to fix this issue.
Regards
Sudhakar

Hello,
After you have done config for the release strategy please execute " Check Release Strategies". This will also help you in giving first round of check/errors in your config.
regards
anand

Release strategy for quantity contract

Hi Gurus,
In quantity contract .. target value will not filled by the value(in header details) as it is quantityt contract.
We may have different line items with different cost..
my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
please explain/clarify
regards
subbu

Hi,
The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined based upon the total net value of the entire purchasing document.
Cheers,
HT

Contract & PO Release Strategy

Hi All,
We are in the process of designing the release strategy for contract and PO. I would like to know whether we can have the different release conditions for contract and different release conditions for PO. For example.
The release conditions for Contract required are
1)Porg
2)Pgroup
3) Value
Also, for quantity contract how can we make the release strategy trigger based on value.
The release conditions for PO required are
1)Porg
2)Pgroup
3)Material Group
4)Value
The release strategy is not getting determined if we create po with two line items which belongs to two different material group. Is there any way out to solve this issue?
Request your help.
Regards,
Kannan

Hi Kannan
Yes your requirement is possible...
While creating Charectristics in CT04 for External Purchase Documents...Create one more Value for your Document Category...ie) Table as :CEKKO and Field as BSTYP and choose the Purchase Doc. Category values K and F.
Then create Charecteris for CEKKO - EKORG, CEKKO - EKGRP and CEKKO - GNETW, CEKKO- MATKL... and assign these all 4 Chareteristices in your release class.
And Configure your release statergy according to your requirement...
Reward if useful
Regards
S.Baskaran

Release Strategy for SA/Contract/PO

Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
Prabhu

Hi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards

Release Strategy for Contract is not getting picked whereas it is ok for PO

Dear Experts,
I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
Kindly resolve the issue.
Satish

S0004830404 wrote:
Dear Experts,
>
> I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
> I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
>
> Kindly resolve the issue.
>
> Satish
hi,
use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
Thanking you

Issue with retriggering Release Strategy

Hi all,
We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
16. Question :
Why is there no release strategy determination when a program changes in
background a purchasing document which corresponds to the classification of
a release strategy ?
Answer :
This is the system design that a release strategy determination can only be
triggered through a user action and not by changes made in background
process.
If you create a document (e.g. PO, Contract, etc), the determination of the
release strategy takes place only in case of a user event like checking or
saving the document.
Kindly suggest any best practise to retrigger release strategy for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
Regards,
Anand Sampath

Hi Arnand,
After investigation by searching customer messages database ,I found
other customer has similar problem as the release strategy has changed
after creation of the SES please review the explanation from developer
:(whose release code is 03 )
When you try to revoke the acceptance of the service entry sheets
in ML81N or ML81, the 'Enter release code' pop up window appears, but
entering the code that is determined via the menu path Goto -> Entry
Sheet -> Release Strategy (which is the 03), the SES remains the same.
Nothing changes. The status does not vary and no error or warning
message is issued.
Checking the customizing for the release strategy, the release code
03 should have never been assigned to the SES 800024272 as the values
for the relevant characteristics were not included under that code.
I do not know how it was managed to accept the SES.
Now, when you try to revoke it, it seems that no release
strategy can be determined, not even including the values RCARESANO
and 012 between the valid values for the characteristics of the release
code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS
(CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).
The only Possibility is to change now the SES so that the release
strategy can be re-determined by the system.This is the Only possible
way that the system can redetermine the Release Strategy , but it will
not be possible to do so as the SES is already accepted with the Old
strategy and it does not admit any further changes.
To be able to change it you would need to revoke the SES first,
but this Will also not be possible as the Release Strategy was changed
and the system still applies the old rules for determining the Release.
Solution to our Problem
The Only way to revoke the SES is to Restore back the Old Strategy that
was prior to 03 in the customizing.So now what will happen is that by
applying the Old Rules the System will be able to revoke the SES that#s
using the Old one. Once the necessary SES are revoked then go back to
customizing and apply the new strategy as it was did now, and
Change the SES and save , the new value of the Release Strategy will get
updated in the table ESSR and the field frgsx will now have 03.
Problems associated if the Release strategy is changed
Actually the release strategy is not supposed to be changed when there
are some documents in the System that uses it and even if you change the
Strategy the Old records will not get AUTOMATICALLY UPDATED by the
system.The Release Strategy routine has to run again to update the
values. This is Possible by changing the document SES ,
This change will happen only if the SES is not accepted and if its
accepted then you need to revoke and to revoke you need to restore the
old strategy , revoke and then change the SES , and have to go back to
customizing and Start using the New strategy from now on by doing so the
Routine will update the old record with the new strategy.
b) You may want to use CEKKO-BADAT(Requisition Date) or any other
structure in CEBAN or CEKKO and create a new release strategy
to differentiate the old release strategy.
Hope this helps,
Kind Regards,
Matthew

Purchase order release strategy report

Dear Gurus,
We are using purchase order release strategy with classification.
We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
How to get it ?
Please provide ur help for the same
Rgds,
Saurabh

Hi,
Basically in EKKO table there is a field name FRGZU -
Release status based on that we can write a logic take the report.
for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
Just tell him the logic to ABAP person they will develop
Rehgards
Murugan J

Release strategy challenge

Similar Messages

Maybe you are looking for