Need to activate release strategy for PR from PS(a/c assignment N)

Dear experts,
I need to establish release strategy in PR raised from Project System. PR account assignment in 'N'= network. PR will be differentiated PR value wise . Please help in this regards,
Thank you.
Kind regards,
Zusen

Hi
You already have account assignment category (KNTTP) in communication structure CEBAN. You can use it to define your release strategy. If you wan to use field which is not there in CEBAN then you need to append CEBAN with the help of apaper.
Use this link as an example for release procedure and create your own with KNTTP.
http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards
Antony

Similar Messages

Release strategy for info records

Hi All,
Can I have a release strategy procedure for Inforecords to create PO?
Please suggest some answers My client want to configure info record release strategy.
Thanks in Advance,
GANESHA

Hi,
Inforecords are master data and we need not have release strategy for that.we have release strategy only for the purchasing documents .
thanks
Roopavathy

Release strategy for RFQ

Hi,
Please let me know,how to set release strategy for rfq.. i'VE ACTIVATED MY RELEASE STRATEGY FOR po USING TABLE cekko... iF I WANT TO ACTIVATE RELEASE STRATEGY FOR rfq... WHICH TABLE AND FIELD NAME I WANT TO USE... PLS EXPLAIN..

For RFQ also we can use the same communication structure CEKKO, but for differentiation between release startegy of Contrcats Purchase orders & RFQ's better to use the Charcteristic Document category i.e CEKKO - BSTYP - Purchasing Document Category

Release strategy for PREQs created from PM work order

Hi All,
I have an issue with determining release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
We have activated release strategy for Purchase requisition based on the following characteristics:
CEBAN_PLANT
CEBAN_COST_CENTER_GROUP
CEBAN_MANUAL
Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding cost center goups.
In the user exit we have consider to cases:
The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
We have defined for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
Best Regards,
Desislava

Hi,
For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
Regards,
Raj

Release Strategy for reservation created from PM and PS

Dear All,
How to configure the release strategy for reservation generated from PM and PS.
Regards,
Atanu

do you talk about release strategie for requisitions, or really reservations?

Release Strategy for contracts.

Hi gurus,
Good day,.
Please help on this.
We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
Example.
Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
Thank you.

Dear Acel,
The example you given was working just fine and correct.
a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
-> The release strategy will only be reset if the total net value for the contract was higher the previous
value but not lower.
As your example, quantity was updated to 1200, then it will reset when changing from 1000
to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
In system, it always assume if you had approved for the total value of the higher 1 before, then
it should be fine for the lower total net value for your management and therefore not need to re-approve
again for redundancy job. This was very logic in common business scenario in many companies.
However, like in your example , if you had define a different release strategy for a value that met the
the 1100 quantity, it will redermine the different release strategy. For example:
USD 1 for every quantity = 1
Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
USD 1200 for quantity = 1200.
Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
Release strategy C for 1200 , characteristics from USD 1200 onwards
Then if you change the quantity from 1200 to 1100, it will redetermine the release
strategy B which means from Release strategy C to Release strategy B. If you
only had Release strategy C that had a characteristics from 1000-1200, then
it will keep the Release strategy C as released and it won't be reset unless
if you had change it and the condition of the total net value was higher than any value
before.
Hope this will explain the logic.
Ian Wong

MM:Release Strategy for Release Order again Approved Contract

Hi,
Release strategy for Release Order is required or not against approved contrat??
As fas as I know once the contract is approved, release order is not required to approve again.
This is the standard setting from SAP or We need to do some setting for this??
In my support project I have studied the release procedure and found that, same release strategy and release Group has been used for Purchase Order and Contract.
Please let me know if anyone have faced this rquirement or I have to go for Z development for this requirement.
Thanks you.

Hi Lalita,
Thank you for your quick suggestion.
yes definitely the release stratergy and release group should be set up separately but here both are same
that is the reason this is picking of the same release procedure again evenif the contract is approved.
we have following release characterstic for the release procedure.
1) Purchasing Group
2)Total Net Order Value
3)Order Type
4)Purchase Organisation
5)Material Group.
I think for the above characterstic we must a separater value for PO and Contract but Currently all are merge
in this only
But Can you tell me "Release Order should be subjected to release procedure" this is correct or not .
If yes then what is the base for this, I mean is it working on the concept that " If do relevent
release characterstic value is found then no release procedure and this is treated as autorelease in sap"
Thanks you.

Purchase Requisition Release strategy for MRP based Requisition

Hello Gurus
We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
Thanks
Nick

Hi,
If you want include the MRP related PR in Release strategy.
You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
But it will not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
I think first one is best suited.
rgds
Chidanand

Release Strategy for Condition Records

Hi,
This is a requirement from my client. The client needs to give 4 levels of release strategy for the condition records created. The selling price for the products will be entered by person 1. This has to be approved by the sales execute (person 2); then by the sales manager (person 3); finally by the General Manager (Person 4). The selling price of the products ranges from 10 lakhs to 40 lakhs. so, the release strategy is needed. This type of release strategy is available in MM for PR and PO. Please let me know whether similar facility is available in SD. Any alternative is also solicited.
Regards,
K Bharathi

Hi,
Thanks for your valuable reply.
I defined 3 Processing status (Menu path: SPRO >> SD >> Basic Fn >> Pricing >> Define Processing status). They are EU-End user, KU-Key user, MD-Final authority. These processing statuses are assigned to Release status. First two processing status EU, KU were assigned to A (Blocked). The third processing status MD was assigned to Blank (Released). The purpose is: at processing status EU one person will upload the price master. Second person will check the price and will change the processing status to KU if he satisfies with the accuracy of the price master. The third person (final authority) will check the price and set the Processing status MD. Once the condition record gets the status MD, the prices can be used for creating sales order because it is released.
In the condition record for PR00, when I enterthe processing status EU or KU the release status shows 'Blocked' release statuses. When I enter MD in the processing status, the release status show 'released'.
My question is how can assign the responsibilities of changing the processing statuses EU to KU, KU to MD to two different persons.
Regards,
K Bharathi

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 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 for Scheduling Agreement(SA)

Dear Forum,
This issue is with regards to the release strategy for Scheduling Agreement(SA)
Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
Warm Regards
Nainesh
SAP ECC 6.0

Hi,
What's the SA Type that was created via MRP.
If it's LP (without release document), release will not do anything BUT
If it's LPA (release document), then you will not be able to Post the GR until release is affected.
Thanks.
Scheduling Agreement can be categories as
1) LP (without release document) and
2) LPA (with release document)
If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
Thanks.
NanoSAP
Posts: 58
Registered: 1/5/09
Forum Points: 6
   Re: release strategy for Scheduling Agreement(SA)
Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply
Dear Mr.Satish,
Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

Release strategy for Release POs

Hi Every one,
We have a requirement.
A contract is created and approved as per the regular strategy.
The releases (POs) are created against it and sent directly to the vendor.
As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
But the business wants the PO releases too to follow the release strategy.
Can you please look in to this and let me what changes we need to make this happen.
Regards
Pavan

As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
So that the Release Process is applicable to PO's created w.r.to Contract also..
For ex: if you use the field purchase Doc category as a Character in the Release , it differentiates whether it is PO or Contract..
So that you can define different Release Strategy for PO & Contract
Or if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
then the release strategy applies to PO also..

Need to activate release strategy for PR from PS(a/c assignment N)

Similar Messages

Maybe you are looking for