Release Strategy in SCN

HI MM Consultants
Is it posible to maintain release strategy in SCN
pls help its urgent

Hi,
You should under stand what is release strategy..
whenever there is going to be a liability,as just incase of Purchasing documents we will set the release process so that the user's responsible for that liabilty should approve or Reject..
As for shipping notification(inbound delivery) is considered it's an information in Advance.. So there will not be any liability..
Thx
Raju

Similar Messages

PO release strategy report

Dear Experts,
we are creating one report.
PO release strategy report for Audit purpose.
Who created
When created
TIme should be display
user id and user code.
for example, we have 4 levels for PO release.
All 4 persons should approve for this PO.
we need to know level wise when they released who released.
how to take this

Moderator message: Basic frequently asked question - Please search forum for answers and read the docu in help.sap.com
See as well our rules of engagement: http://scn.sap.com/docs/DOC-18590
This blog describes how to use the SCN search:http://scn.sap.com/community/about/blog/2012/12/04/how-to-use-scn-search
Another good way to search the forum is with google. See this blog with details for a good search
http://scn.sap.com/community/support/blog/2012/04/16/getting-the-most-out-of-google-optimizing-your-search-queries
The discussions are not a replacement for proper training
Thread locked

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Import container contains errors issue for Release Strategy workflow

Hello Experts,
I have copied the standard workflow WS20000075 for PO approval on Release step.
the copied workflow works fine in sandbox system, but in the test system I get an error saying 'import container contains errors (are any obligatory elements missing?)' I guess 'ReleaseCode' is not getting passed to the Workflow from the PO creation T-code.
I went thru few SCN post, did check all the Linkages as said, everything seems to be ok. but still cannot trigger the workflow.
need guidance as to where I may be going wrong.
Regards,
Jibran

Hi Jibran
If the WF is working in sandbox, it means that your definition, linkages etc are correct.
Please check if the following note is relevant for you or not:
1770720 - PO workflows run into error SFW_RUN594 - Import container contains errors
It's about correcting the settings in SWEC and SWE2 (correct for your custom workflow definition)
If not, then confirm with your MM consultant if the release strategy is configured correctly or not....take hints from the following SCN thread:
http://scn.sap.com/message/14682486#14682486
Regards,
Modak

Release strategy on PS module over budget

Dear All,
I want to configure release strategy on PS module over budget and it should be value based upto 4 level.
Kindly tell me object and procedure to config for PS module only.
Is it possible to release on activity based or network based releases strategy??
Regards
Sanjeet Kumar

Hi Sanjeet,
Please refer the following thread
https://scn.sap.com/thread/1745541
Regards,
Amit

Release Strategy not triggered in PO

Release Strategy not triggered in PO and also in PR. Release Strategy stimulation is working fine but release tab is not coming in Po and also Pr.
What step I have to do after release strategy stimulation.
Regards
cns

Hi,
Unless you provides details, difficult to suggest an answer.
What are release criteria's you selected for PO and PR release strategy?
What are the release characteristics you have for PO and PR release procedure?
If you configure perfectly the PO and PR release strategy, did you transfers the "Vital Release Values" with your release strategy with release group and release class.
Refer few threads , may help full to you!
http://scn.sap.com/thread/1973324
http://scn.sap.com/thread/3212400
Also refer SCN wikiblog
https://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards,
Biju K

PO Release strategy Workflow issue

Hi All Workflow Experts,
I need a help in one of the workflows in our project.The workflow is for PO Release Strategy.The problem is in the Production environment and is as mentioned below:
''Users are complaining of irrelevant mails with subject "PRD: PO auto release code" delivered to their lotus notes inbox from SAP workflow. Mail does not carry any further details like whats the PO number etc. In some cases this mail should not be delivered to the recipients as they have nothing to do with PO release strategy approval process.''
As I am not very old in Workflows I want to know where should I start from? I mean what all are the possible
areas where I should look into? Also this issue cannot be replicated in QA environment? So is there any environment specific thing I should do?
Please advice.
Thanks,
Saket.

Hi Saket,
Check who are set as the Recipient types of the workflow mail "PRD: PO auto release code". Also check the condition when the mail is getting send. Check at occurance of what event is the mail getting send to the users. Debug the workflow to fidn out these details and check where the issue really is.
Do post your comments if you find any confusion about the same.
For assistance on workflows, the following links would help you:
http://****************/Tutorials/Workflow/Workflow.htm
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/workflow%252bscenario
/people/sapna.modi/blog/2007/02/19/workflows-for-dummies--introductionpart-i
Hope this helps!
Regards,
Saumya

Can we implement workflow for release strategy in 4.7

can we implement workflow for release strategy in 4.7 for PO's please provide some documents.

HI,
Check the links
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30c81e21-cd00-2c10-bbba-edb8ce4961be?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70fef212-b6cb-2c10-e085-c84b80d7068e?quicklink=index&overridelayout=true
Regards
KK
Edited by: Kishore Kumar Galla on Mar 19, 2010 3:40 PM

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 in SCN

Similar Messages

Maybe you are looking for