Release strategy for PO, RFQ & Contract
Hi,
We have created release strategy for PO, RFQ & Contract.
Characterisitc is created for Target Value for Header Area (CEKKO-KTWRT)
for RFQ & Contract it working fine but for PO not triggering.
what can be the cause.
Pls guide.
Hi,
Melih is right, for POs you can not use the target value.
What you might do is to include the document type and CEKKO-GNETW as additional characteristics and then set for contract document types the GNETW blank, and for PO documet type the target value blank. Blank means any value should fit.
I hope this hint helps!
Best Regards,
Arminda Jack
Similar Messages
-
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 adviceFirst 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.
PrabhuHi 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 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
subbuHi,
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 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.
SatishS0004830404 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 -
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 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 -
Cannot reset release strategy for RFQ
Dear SAP gurus,
I set release procedure for RFQ. I set anyway that the changeability is 6, and the tolerance is zero. I expect that after it is released, whenever anyone is changing everything the release strategy will be reset.
But this is not happening. In my case, the manager already approve the RFQ but the RFQ has not been sent yet. Then someone change the quantity of the RFQ, and the release strategy is not reset. When I check again I realize that changeability 6 means the release will be reset if the value is changed; while in RFQ there is no value mentioned anywhere, it means that the release strategy for RFQ will never be reset.
Do i miss something? Is there any way to make sure that the release for RFQ is reset if someone change anything in the RFQ?
Best regards,
John.Why are you having a value based release in RFQ? And more important, why do you need release for RFQ?
However, if you still want to go ahead with release, then you need to use the user exit for purchasing document release to achieve your objective. Please search for my earlier posts on how to reset release even on decrease of PO value. You can use the same logic for RFQ also.
Lakshman -
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
-
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. -
Hello Experts
I am using release starategy for contract and using communication structure CEKKO in characteristics. I want to use other parameter such as material master number (MATNR) for characteristics. I see that CEKKO has component .INCLUDE (Communication Structure: PO release for User Exit). Does any one know how to use it in characteristics and if I use it can I design release strategy for particular materials?
Thanks
Ankitthis has been discussed multiple times on this forum - "Release strategy at item level for purchasing docs - PO/SA/Contract" not possible...
refer below threads
Why release strategies for PO at header level only
PO Release Strategy
Release strategy - item level
yogesh -
Configure Release Strategy for Contract
Hi All,
I want to Configure Release Strategy for Contract.
I have configured Release Strategy for PO. Is the process for both is similar?
What should the table & field name should we use for configuring Release Strategy for Contract.
Pls. guide.
Regards,Thanks Neeraj for the reply.
For PO, I have used Table CEBAN, Field BSART, GNETW.
Could you pls. suggest what fields should we use.
Also tell me what would be process of releasing the contract using ME35K, as the Screen seems to be different from ME29N.
Regards, -
How to avoid po release strategy replicating in RFQ
Dear Sapiens,
I am aware as we are using same class for PO RFQ and Contract the release strategy will repliacte in rest,
but I dont want PO release strategy to get repliacted in RFQ,because I dont have realease for RFQ
how to avoid po release strategy replicating in RFQ?
Regards
KanthaHi,
Yes they are same unless you differentiate by using
1> Purchasing Document Category i.e CEKKO -BSTYP
A..... Request for Quotation
F......Purchase Order
K......Contract
L......Scheduling Agreement
So if you just create a characteristics for CEKKO-BSTYP then maintain its values only for F so it will not be applied to RFQ -
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.0Hi,
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...?? -
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
PavanAs 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..
Maybe you are looking for
-
HFR - 5200: Error executing query: Invalid Item ID
Hi All, We are using Hyperion HFM application 11.1.1.3. Recently we have upgraded the Oralce Database to 11.2.0.2 and reconfigured the HFM application with this new database version. When I tried to run the Financial reporting through the HFR studio,
-
Combining mulitple image files into a PDF results in different pages sizes
Hi I prepared 150 images in Photoshop using a script. All the images are the same pixels dimensions, same resolution and same file type. When I combine them into a PDF using Acrobat XI, some of the pages are very small. I cannot see the logic as to w
-
C++ Get IPDDomNode from IAccessible
I'm recreating the pdf structure in a program I am writing. I am getting the IAccessible object for the AVPageView window in Adobe Reader and then walking the accessible children caching objects as I go. Later on I am trying to get the IPDDomNode f
-
Hi, What is the name of plant specific table. And how i know that inwhich plant,which storage location is there..? Thanks in Advance.. Yogesh
-
hello, as i was in Russia before 2 weeks, i bought a new mac book air. when i come back home in Germany,in 4 months, can i by an apple care protection plan for it?