Cekko

hi experts
We need to add actual price difference For release strategy of PO.
the structure cekko is not available in user-exit exit_sapmm06E_012 where we have the prices. (KOMV)
is there any way to calculate price difference and use it for release strategy in the 4 fields available for user fields in cekko.
thanks,
Amit

there is a way to access the global memory of the program. so even if it is not in the program scope but exist in the memory stack u can use it.
for this u only need to know the program name where this structure exist then use the field symbols
FIELD-SYMBOLS <f_cekko> type cekko.
ASSIGN ('(PROGRAM_NAME)CEKKO') to <f_cekko>.
then use the field symbol as a normal variable.
Edited by: Craig Cmehil on Jul 9, 2008 2:49 PM

Similar Messages

Add new field to CEKKO in exit EXIT_SAPLEBND_002

Hi,
Can i include a zinclude in the structre of CEKKO in exit EXIT_SAPLEBND_002.
I have to assign KTOKK filed from LFA! table to CEKKO structure.
I have an inclue in the structure CEKKO as ZCEKKO_KNTTP,can I include the new field there.
please advice.
Thanks.
SOLVED.
Edited by: p317980 on Mar 2, 2010 9:25 AM

SOLVED

PO release strategy based on Material Group (CEKKO - MAKTL)

Hi Experts,
I have configure the Rel strategy based CEKKO-MATKL (material group) for purchase order, but when i raise the PO Rel strategy is not affecting, Can any body tell me why.
Regards,
Kumar

You can set Release strategy based on Material group & other Line item specific fields..
You better follow a suitable and hinder less process..
For PR use Material group & Account Assignment based Release process..
then for PO use a Release Process based on Header level fields like Doc type, Amount, pur Group etc..
So that the approved PR line can be converted into PR and then the PO also subjected to Release before sending it to External Vendor..
Even if you want you can make that the PO can not be created without referencing PR for SOme users or All users..
based on your business requirement..

Extenet the communication structure CEKKO for over delivery tolerance

Hi Boss,
I like to set the Purchase order release strategy based on the over delivery tolerance. But when i checking, the over delivery tolerance filed UEBTO is not in the communication structure CEKKO. Can you please help me how should i extend the CEKKO with field UEBTO.
I do not have the ABAP experience, please guide me with coding.
Thank you,
Siva

There are lot of fields which can be set as Charecteristics for Release Strategy. I dont know why you want to Set the Over delivery Tolerance as Charecterisitic.
What is your Requirment??
Any way You can also use CEKKOZZ Communication Structure: PO release for User Exit
Go thru the Link which will guide you
http://help.sap.com/saphelp_40b/helpdata/en/dd/2d547bb435d1118b3f0060b03ca329/content.htm

PO release strategy based on Account Assignment Cat (CEKKO - KNTTP)

Hi Experts,
I want to configure the release strategy for PO on account assignment category.when i maintaining a characteristic for account assignment cat by inputing CEKKO- KNTTP , sys throughs error message. I looked in to CEKKO but I could not find the field .Kindly tel how maintain teh same .
Regards,
Kumar.

Hi Kumar,
Account Assignment Category and Item Category belong to the item level and not to the header level of a purchase order (table EKPO). Therefore,   neither Account Assignment Category nor Item Category are available in CEKKO.As work-around you can use the following user-exit:
MM06EF0S_STRATEGIE_CEKKO
(enhancement M06E0004, EXIT_SAPLEBND_002, ZXM06U22).
In this user-exit the data are available in structure I_CEKKO.   The hand-over from I_CEKKO to the calling program is via structure E_CEKKO.   In the user-exit I_CEKKO has to be copied to E_CEKKO , e.g.
E_CEKKO = I_CEKKO.
Please also see our FAQ note 365604, it is worth reading.
Regards,
Mauro

Release Strategy for New & Change PO's - Using characteristic CEKKO-REVNO

Hi All,
I have the following requirement/scenario
1. If PO is created manually no reference to PR, then the PO needs to be approved through a release strategy.
2. If the PO has been created automatically either from a req or through SRM (for,eg) then the PO needs to be approved only if this PO has been changed. So this would need to go through a second release strategy.
To distinguish between the two, we are using Version number field CEKKO-REVNO in the communication structure CEKKO to be a characteristic in the release strategy.
This is what I hoped for would work after doing the necessary config,
For create PO's, in my classification I have CEKKO-REVNO as >=0. So any PO whose version number is >=0, will trigger relase strategy S1 (for e,g).
For change PO's in my classification I have CEKKO-REVNO > 0 And whenever you change PO, it will generate versions 1,2,3 and so on, and hence the release strategy will trigger.
The problem
Whenever I use CEKKO-REVNO as one of my characteristics, the release strategy is not triggered at all no matter what the conditions are on the PO. When i removed the REVNO from my classification, release strategy is getting triggered as per plan. I have also activated version management and done all the necessary config. I would like to know why release strategy is not getting triggered when REVNO field is used from communication structure CEKKO. Have any of you experienced this issue before??
Is their any other identifier I can use to address the requirement above? Let me know.
Thanks
Ashvin

Thanks Charlie for your response.
The conditions in the PO is not equal.
On one occasion when I create the PO, I have given the classification as REVNO >=0 with a document type ZB for create (S1). So when I create the PO manually, the version starts with 0, so condition should satisfy here
On the other when I change the PO (with/without reference to PR), I have given the classification as REVNO as > 0 with document type ZC (S2), so when the PO is created initially it will not satisfy strategy S1 as doc type is different for S1. When I change the PO created with ref to req, S2 should take into effect because when i change the version will change to 1 and S2 should trigger because REVNO is > 0 and doc type matches.
So I dont know where the release strategy matches in both S1 & S2 for the system to not propose the release startegy.
Let me know your thoughts.
Thanks for your feedback.

CEKKO and CEBAN for PO or PR release strategy??

hi all
Can any body explain me about the below details in PO and PR release startegy.??
In release streatgy, sytem check CEKKO and CEBAN for PO or PR release .
while define characterstic, in Additional Data....there is table and field name..???
Than ks
SAP-MM

HI,
CEKKO is for PO release.
In characterstics, GO to Add Data..gives Table Name as CEKKO and field name as per Required.
Suppose your Release Streatgy is based in plant and Value and Document Type
Then In create a charactertics as suppose PO_Plant
Go to Additional....Table Name As CEKKO and field name as WERKS. Now go to CL24N and maintain Value for Plant.
By this maintain rest of the parameters required for release.
Go to SE11, put table name CEKKO, here u can find the fields u can use in release streatgy.
Same is for PR , here table name is CEBAN. PR release can be at header level as well as item Level
Hope Clear U !
Regards,
Pardeep Malik

Release procedure table CEKKO addition of field names

Hi,
What are the ways I could add the fields in the PO release procedure table CEKKO, say I want to add the field MEINS( unit of measure) which is not available.
Can anyone explain in detail.
Our requirement is for some unit of measures say EA, PC etc., our release procedure should trigger.
Basically this is at the item level and so how to proceed?
best regards,
Thamizh

hi,
Release procedure for PO is at header level. I dont think adding unit of measure to CEKKO table would help.
If your PO has a single item then probably you can add a zfield in CEKKO which would be an input field while you create a PO. That is this z field should appear in EKKO also. And you maintain the unit of measure in this field same as your PO line item.
Then you can create a release strategy for this. This will work ONLY if the PO is having single item.
But I really dont understand as to why you need the release at Unit of measure level ?
generally release is required if the quantity is very high in PO or PO value is high....but it is NOT triggered by Unit of measure.
regards
Seema

Verison Management with PO release strategy - CEKKO-REVNO

Hello,
I'm a bit stuck... I'm trying to do a PO release strategy using version management, were the PO goes through a release strategy if the PO gets changed (not the intial PO creation).. So once the field RENVO is greater then 0, it should go through R.S.
I've read to create a characterstic CEKKO-REVNO and then assign it as a valuet <0... I intital;y created it with a NUM Data type, but the ABAP dictonary overides it with a CHAR instead... So I read to mark the value as a default value (<0)
However, after I add it to my class, I go to the define release strategy - classifcation section (to add the value <0) I'm getting a value inconsistency check.
How do i setup this characterstic so I can use it in release strategy?

Based on adding 00000000 the release strategy will work when its version 0 (intial). However, I'm trying to have it so it goes through a release strategy when the version is 1 or greater...
It seems like I cant get the strategy to work for more then one version... I can get it to work for version 0 but no others, or version 1 and no others etc...
I need to have it some it works for anything greater then zero, in which i tried <0000000 and even >000000
I also tried adding 000001, 000002, 0000003, 0000004 etc.. An although the release strategy tab is still applying, it will NOT result to a blocked status...
I cant get this to work... How should the characterstic value look to get this requirement?
Edited by: farmerj3 on Feb 20, 2012 3:16 PM
Edited by: farmerj3 on Feb 20, 2012 3:43 PM

USRC1, USRC2 in CEKKO table for Release Strategy.

Hi all,
Can anybody shed some light on how i can make use of USRC1 and USRC2 in CEKKO table for Release Strategy?
I see it in the table but i have no idea on how to use them.
Thanks all.

Hi,
SAP has given user defined fileds in CEKKO communication structure which you can use by using user exits to fill in CEKKO.
These fileds you can use as characteristics for release strategy.
Details of user exit:
M06E0004 Changes to communication structure for release purch. doc.
EXIT_SAPLEBND_002, Changes to Communication Structure for Release of Purchasing Documents
Description: User exit that control the values in CEKKO for the Release Strategy.
Regards,
Shailesh Mackwan

How to check value CEKKO-GNETW4

Please help
Try to use CEKKO-GNETW4 for value check since release strategy in PO is header level
thanks

Hi,
To have check on Total net order value in PO (CEKKO-GNETW)
In IMG, navigate through
Release Procedure for <i>Purchase Orders--> Define Release Procedure for Purchase Orders --> Release Strategy</i> (or) use T-code <b>OMGS</b> then Release strategy
Under Classification tab you define the value for Characteristic "Total net order value" (CEKKO-GNETW). Which actually determines the release strategy based on value check defined.
Regards,
Siva Prasad

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

PO release strategies with Contract

Hi,
implementing a PO release strategy (SAP-MM module)I need to consider the case in which a PO is assigned to a Contract.
If so, different release strategies should be selected according to the PO value.
Possible cases:
S0-strategy 0: Contract does not exist, PO value>=0eur
S1-strategy 1: Contract exists, PO value>=100eur
S2-strategy 2: Contract exists, PO value>=200eur
Is someone aware if it is possible to activate such release strategy without defining manually in the characteristic for CEKKO-KONNR field all possible contract single values (entire range)?
Thanks a lot for helping!
Regards,
Elisabetta Rizza
Please contact me at following mail addresses:
[email protected]
[email protected]
Hi Elisabetta,
I've moved this here because it is a more appropriate thread. BPX is the place for discussing the role of the buisness process expert. This is a MM question
Message was edited by: Marilyn Pratt

Dear Amit,
Requirement: If GR posting date exceeded 45 days than delivery date set in PO, then delivery date in PO has to be changed to current system date and at the same time New Release Strategy (B1) has to be triggered with one release code (02) automatically.
So in that case the values in Release Strategy (A1) and (B1) would remain same,,, as you suggested we will assign the value 01 u2013 USRC1 to Rel Strategy (A1) and 02 u2013 USRC1 to Rel Strategy (B1) and the same we will try to incorporate in the coding of Exit u2018'M06E0004'
We will check the process and confirm the same.
Thanks for your suggestion.
regards,
Urendra Kumar

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

Which field is the workflow trigger for a Contract Agreement ?

Greeting everyone,
I am not sure if this has been answer before or if this is the correct forum. If not, apologies in advance and do direct me to the appropriate topic/forum.
I have an inquiries with regards to Contract Outline agreement and workflow trigger.
Based on my company configuration, the trigger is based on the changes in value and release strategy.
What I am unsure is that which field the workflow-trigger checks?
Does SAP checks the field "Target Value" in contract header, or the sum of net value in each of the contract items?
Thank you

Hello Sek,
In contracts, the target value is used for the release strategy determination and not the net contract value. If you maintain a target value in the contract header, this value is set in field CEKKO-GNETW to determine the strategy. If no target value exists on header level, a cumulation of the target values of the items is carried out and used for the release strategy determination.
Regards,
Mauro

Cekko

Similar Messages

Maybe you are looking for