PR Release Strategy for Assets

Dears,
We have PR Rel Strategy with characteristics Cost Center and total value, it is working fine. But now the requirement is that PR for Assets to be included. For this we have included characteristic 'A/C assignment category", but it is not working. We have maintained in cl20n. How to activate the release for 'Assets'?
Thanks,

Hi,
Steps - if already done then please recheck it
1. Maintain values for new characteristic - Account assignment
2. Assign new characteristic - A/C assignment to CLASS.
3.In CL24N check the status of all release strategies - Green check - symbol should appear against each strategy.If its green then release strategy tab gets triggered if all pre requisites are satisfied.
Regards,
Uzair

Similar Messages

Release Strategy for Asset Purchase order

Hi,
I have the following client Requirement.
1. PO document type will be anything but Po created is for Asset
2. In such case, Release strategy should be approved only be certain groups only. Anyway the Account assignment category will be "A"
As we cannot control the PO Release by Account Assignment category, it has to be controlled via User Exit.
I.e., combination of Acc Assignment category and Purchasing Group should result in a particular strategy.
Can you suggest relevant user exit? This is importantly needed. Please help.
Thanks

Hi,
Please do the following changes,same is tested by me in Our dev server and works successfully in PO.
Go to Se11 ,open structures -CEKKO (You will find KNTTP-account assignment field is missing)
Click on append structures ,system will ask you object name ,give as anything,then put a description /
Then system will ask you to add new field in CEKKO structures.
Add field KNTTP and save ,system will generate request for the same.
Now create a characteristic as CEKKO_KNTTP and save ,don't give table name here
Once saved,re-open the CEKKO_KNTTP ,here you need to give table name as CEKKO and field name-KNTTP. Define values an save.
then add the same in class ,and then select the required assignment in CL20N ,save.
And check the PO effects,it will works.
Regards,
Sandesh Sawant

Release procedure for ASSET

Hi SAP guru
I am having the requirement for release procedure as follows
Purchase order with Asset (Item category)   - Value Up to 50,000/- will be approved by GM
                              Asset (Item category)   - Value more than 50,000/- will be approved by Chairman.
Purchase order other than ASSET
                                                    Value Up to 100,000/- will be approved by GM
                                                    more than 100,000/- will be approved by Chairman.
I checked in CEKKO, the field KNTTP - Account Assignment Category component is not available.
Could you please tell me how to solve this issue?
Good suggestion will be rewarded with full points.
Thanks in advance
Anand

Hello Anand:
The release strategy for PO only contain fields on the purchase order header (EKKO) and the account assignment is at item level (EKPO), however you can add the account assignment as customer field on structure CEKKO (CEKKOZZ structure) and fill the information on this field with the user exit M06E0004 (transactions SMOD, CMOD)
Keep in mind that the CEKKO structure has the value of all the purchase order (CEKKO-GNETW), not item by item. It means that you could not check on the release strategy the value of all the assets included in the purchase order.
Additionally check if there are cases in your installation where a purchase orders could contain several items for more that one account assignment.
I hope this help, if you have any question please let me know it.
Best regards,
Jose Luis

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

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 Schedule lines in SD

Hello All
Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
Thanks in advance.

Hello,
I think you are in the wrong forum. Please choose the right forum category and post it there.
Matthias

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

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.

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..

Reset Release Strategy for any change in the Purchase Order

Hi,
Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
If so, where do we need to make the configurations.
I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
Thanks in Advance.
S.Raghavan

hi sandesh,
sorry, i know it's too late.
i tried your suggestion, it works blocking the purchase order after release strategies are setted.
sandesh, raghavan:
i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
regards
f

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

Release strategy for PO on Payment terms..

Dear friends,
Is it possible to have Release strategy for PO on Payment terms.....
I checked in CEKKO, no field availble for payment terms.
Is there any other way..........
Plz help
Rgds,
Navin

Hi,
You can append Communication Structure "CEKKO" and add Payment Term (ZTERM)
Use User Exit "M06E0004" (Changes to communication structure for release purch. doc.)
Function module "EXIT_SAPLEBND_002" (Changes to Communication Structure for Release of Purchasing)

PR Release Strategy for Assets

Similar Messages

Maybe you are looking for