Release strategy of PO creation under contract

Hi,
if PO creation without any contract, release strategy is required. However, if PO is created from contract, no release strategy should be used. Pls advice how to configure it. thanks

The best option is you differentiate the PO document type i.e. create a seperate document type (ZNB) for those PO which are created wrt contract...Now while creating PO release strategy use PO document type (BSART) as one of the characteristic and there don't use this new PO document type (ZNB)
Regards,
Indranil

Similar Messages

Release strategy not applied for some contracts..

Dear All,
At my client place,In some of the contracts release strategy is not applied.
I have tried evrything...in classification plant,purchasing group,net value and order type (MK and WK)everything is added.
but some of contracts release strategy is there and for some it is not applied...what could be the reason?
Please help.
Amit

Dear All,
Please reply....

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.

Contract Release strategy

Dear Guru,
We have three types of contracts like A type, B type, C type......with these three types of contracts we have release strategy with different conditions.
               For A type of contract : Release Strategy should trigger on cost center and value base.
               For B Type of Contract : Same conditons like above.
               For C type of contract : it should trigger on duration base like.....if contract create for one year itshould trigger manager........if one year to two years it should trigger to director........if above two years it should trigger to CEO.
          This is my requirement.....how to configure this pls explain me.
Best Regards,
Bhaskar.

Hi,
You can only have one class and so you will have to use all of the characteristics from each type of check that you want.
So you would need a characteristic of Cost centre, one for Value and one for start and end date. (in addition to whatever characteristic you are using to determine if the contract is type A, B or C.)
With the release strategies you need to ensure that for type A and B contracts the date range characteristic is not checked and so you need to specify that all date ranges are included (so if the difference between the two dates is one day to 999 years).
then on the release strategy for the type C contract, make sure that the cost centre and value characteristics are set to include all too (so cost centre 0000 to ZZZZ and value from 0.01 to 9999999, if you don't want either to be checked).
this should work, the basic idea is that you ahev to have ALL characteristics included in every strategy but you use the values to make sure that you ignore certain characteristics in certain situations.
Steve B

Work flow in release strategy..?

Hi experts
Can anybody expalin me what is Work flow in release strategy .
Exaplain me with some examples for Work flow in release strategy.
Thanks
SAP-mm

You have to carry on the following activites:
1) Define Organisation Struture
2) Application specific customizing
A) Define Characteristic values
B) Define release codes and make them Workflow relevant
C) Define release strategy
Based on the characteristic values the Purchase Order will be applied to a particular release
strategy and will fall under specific catagory to pass through different level of approvals
D) Assign release codes to corresponding Orgnisational Objects with ID
3) Task specific customizing
A) Activate the event linkage for the standard workflow WS20000075
B) Do the agent assignment for the TS20000166
C) Make other two tasks as General Tasks (TS20000168,TS20000167).
4) Delete the row for event "Releasestepcreated" from SWEC (OSS Notes: 797775)
Hope this will help you

Release strategy for Future validity period- (Outline agreements)

Dear All,
I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
How to set up release strategy in the above case.
Thanks in Advance.
Regards
Amar

Hi Amar,
1) if you maintain a target value (EKKO-KTWRT) in the header of the
contract this value is the basis for the determination of the release
strategy. If the target value is 0, the system will cumulate the
values of the items and will use this value for the determination.
2) So if the target value is 0 and you change the price of a condition
with a validity period in the future the system will react in the
following way:
Example:
   the contract contains one item with quantity = 100 and a net price
of EUR 5,-.
   all contracts with a target value from EUR 0 - 1.000,- should be
subject of a release strategy
   the contract is created and released on October the 1st
   ME32K -> October the 2nd you define a new price of EUR 7,- with a
validity period from 03.10.09 - 30-10.09 -> you save the contract
-> the release strategy is not reset, as the start date is not
reached yet (system date < startdate of validity period)
   ME32K October the 3rd you change a field in the contract -> the
release strategy is reset
This is system design that a release strategy can only be reset through
an action by the user. The determination of the release strategy can't
be triggered automatically in the background.
If you create a document which is subject of an overall release strategy
(e.g. p.o., contract) the determination of the release strategy takes
place when the user hits the 'save' button or chooses the 'check'
function.
So there must be a kind of event that tells the system that something
has changed.
Regards,
Edit

Release Strategy or work flow in BI Content

Hi !
Do we have Release Strategy or work flow in BI Content of BW Release 3.5 ?
I have to display a history of purchasing requisitions and orders that was uploaded from SRM.
Thanks !!!
Zelda

You have to carry on the following activites:
1) Define Organisation Struture
2) Application specific customizing
A) Define Characteristic values
B) Define release codes and make them Workflow relevant
C) Define release strategy
Based on the characteristic values the Purchase Order will be applied to a particular release
strategy and will fall under specific catagory to pass through different level of approvals
D) Assign release codes to corresponding Orgnisational Objects with ID
3) Task specific customizing
A) Activate the event linkage for the standard workflow WS20000075
B) Do the agent assignment for the TS20000166
C) Make other two tasks as General Tasks (TS20000168,TS20000167).
4) Delete the row for event "Releasestepcreated" from SWEC (OSS Notes: 797775)
Hope this will help you

PR Workflow for release strategy

Hi,
Could you please let me know the steps how to configure the workflow for the PR release strategy for both item level as well as header level.
Thanks in advance
Shp

Hello,
If you wish to work with procedure 1, define the following:
Release codes
Release indicators
Assignment of release indicators
Release prerequisites
Determination of release strategy
1. Release codes
Create the release codes.
2. Release indicators
Define release indicators and branch to the detail screen. Here you define whether fixed purchase requisitions may be changed by Materials Planning, for example, and whether an RFQ or a purchase order may be created from the requisition.
You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you specify whether a requisition may be changed after the release procedure has begun. You specify whether the strategy has to be redetermined after changes, or whether the release procedure has to start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For example, previous releases are not cancelled if the value of the requisition item after the change does not exceed plus 10% of its original value.
Attention:
Be sure to create a release indicator (e.g. B for "blocked") that serves as the starting point for subsequent indicators. Do not set the indicators for release for the issue of RFQs and PO on the detail screen for this indicator.
Also create a release indicator characterizing the released status. Set the indicators for release for the issue of RFQs and PO on the detail screen.
3. Assignment of release indicators
Assign a release indicator in dependence on the status of the release.
Example:
You create a release strategy S1 consisting of two release codes 01 and 02. Release with 01 is a prerequisite for release with 02. If release has been effected with 01, the requisition has been given the "all clear" for the issue of RFQs.
You have created the release indicators B (blocked), 1 (cleared for issue of RFQs) and 2 (cleared for RFQs and PO).
Now enter the following as assignment:
Strategy   C1 C2 C3 ...
S1                           B (blocked)
S1         X                1 (RFQ)
S1         X   X            2 (RFQ/PO)
4. Release prerequisites
Define which release codes are involved in a release strategy. Specify whether a code is set for a release status following release, and whether one release status is a prerequisite for another (+).
Example:
Strategy   Code C1 C2 C3 ...
S1         01    X
S1         02    +   X
5. Determination of the release strategy
Determine the conditions under which each release strategy is assigned. The criteria are account assignment category, material group, plant, and value of the requisition item.

How to set the Release Strategy without classification for PR

Hi,
I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
I crated the Release Codes, however not able to find what options to choose in the following steps :-
Release indicator
Assign Release Indicators
Release Points: Prerequisites
Determination of Release Strategy
Regards,
Yogesh

1. Release codes
   Create the release codes.     For Purch. Officer, Manager and Sr. Manager
Like PO, MG, SM
2. Release indicators
   Define release indicators and branch to the detail screen. Here you
   define whether fixed purchase requisitions may be changed by Materials
   Planning, for example, and whether an RFQ or a purchase order may be
   created from the requisition.
   You can also determine the field selection here.
In the area "Changes after the start of the release procedure", you
   specify whether a requisition may be changed after the release
   procedure has begun. You specify whether the strategy has to be
   redetermined after changes, or whether the release procedure has to
   start all over again from the beginning.
This parameter bears a relation to the parameter "Value change". For
   example, previous releases are not cancelled if the value of the
   requisition item after the change does not exceed plus 10% of its
   original value.
Attention:
   Be sure to create a release indicator (e.g. B for "blocked") that
   serves as the starting point for subsequent indicators. Do not set the
   indicators for release for the issue of RFQs and PO on the detail
   screen for this indicator.
   Also create a release indicator characterizing the released status.
   Set the indicators for release for the issue of RFQs and PO on the
   detail screen.
You can use sytem defined indicator in this case you dont have to do anything
3. Assignment of release indicators
   Assign a release indicator in dependence on the status of the release.
Example:
   You create a release strategy S1 consisting of two release codes 01
   and 02. Release with 01 is a prerequisite for release with 02. If
   release has been effected with 01, the requisition has been given the
   "all clear" for the issue of RFQs.
   You have created the release indicators B (blocked), 1 (cleared for
   issue of RFQs) and 2 (cleared for RFQs and PO).
   Now enter the following as assignment:
Strategy   C1 C2 C3 ...
   S1                          B (blocked)
   S1         X                1 (RFQ)
   S1         X   X            2 (RFQ/PO)
4. Release prerequisites
   Define which release codes are involved in a release strategy. Specify
   whether a code is set for a release status following release, and
   whether one release status is a prerequisite for another (+).
   Example:
Strategy   Code C1 C2 C3 ...
S1         01    X
S1         02    +   X
5. Determination of the release strategy
Determine the conditions under which each release strategy is
assigned. The criteria are account assignment category, material
group, plant, and value of the requisition item.
Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
E.G if you will not define the Material group here but it will default in req in that case this will not work thats the reason you have to work with Classification.
<b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

Contract Release Strategy - field Requisitioner

Hello,
I will start to use the Contract release strategy and I need the field Requisitioner (EKPO-AFNAM), because this field is part of my PO release strategy.
This field isn't available in the transactions ME31K and ME32K.
Can you tell me, if it's possible to show it in these transactions?
In other case, where can I fill this field? How is the BAPI, BADI, etc?
Thank you,
Meire

Hi,
Please, be so kind to refer to note 373361. This field was only
available in purchase requisitions and due to requirements of
SRM (formerly BBP business tons business procurement ), it has
been added into the new enjoy transaction
ME21N/22N/23N for purchase orders.
It is not available for contracts.
The contract is not the last document in the procurement.In bussiness
process the requirement of requisitioner in contract is less important.
It is enough if you don't know the requisitioner at the time of contract but
you know it at the time of PO creation.
This is the standard SAP design.   Please do not use this field in the contract release strategy: create a new release group for the contract release strategy, delete the value entry for EKPO-AFNAM in the "Change view - release strategies - classificaion". The characteristic for EKPO-AFNAM should appear as black and not as blue on the screen. Save your strategy.
Regards,
Edit

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.

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

Release strategy of PO creation under contract

Similar Messages

Maybe you are looking for