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

Similar Messages

User Exit for getting Purchase Requisition Release Strategy

Hi Experts,
When a user creates a PR I need to know the user exit I need to implement so that the First Approver (Processor) text in the Release Strategy is populated from a custom table. I have seen that the field is MEREL_S_GRID1-STEXT. I also need to know if I can implement a user exit so that it pulls the release strategy for a PR for assets (Acct Category A) since it is pulling for Acct Category K (Cost Centre) and the Release Strategy tab is appearing in this case.
Kind Regards,
Darlington

Hi Meenakshi,
Thanks for the very useful answer. It has given clues on how to resolve this issue. I have resolved this issue for the Asset item category using the following thread: user exit for requisition release strategy, and also SAP Note 365604.
However, I have another issue, the release strategy for Stock Items, (item category blank) is not pulling through. I need to use the same method above but would like to know how it determines the funds centre for a specific stock item. I couldn't find where that is implemented in the material master and I need info on how to determine the account assignment for stock items based on the funds centre.
Regards and Thanks.

Older Toshiba Hardware and Drivers for Coming Windows 10 Release

Toshiba Qosmio F60Currently running Windows 7 Home Premium Hi All Long time Toshiba user here and very happy with the products I have purchased I must say. These for me personally have always been very reliable pieces of hardware. With the upcoming release of Windows 10 on July 29th I am wondering if their will be device drivers made available for those of us still running older Toshiba models? I am currently being notified that a reserve copy of Windows 10 is available for me through Windows Update and am currently considering the transition, although I am somewhat hesitant to move away from Windows 7 which for me is quite familiar and a reliable OS. My main concern here is that I would still obviously want ALL of my devices to work without issue and am wondering what Toshiba's stance is on supporting those who take this path. My Qosmio F60 is still a fantastic machine and runs without issue and with this being the case I am not about to purchase a newer model just that I can replace an OS which works well but is at some stage going to lose support and be outdated/superceded by Windows 10. Can anyone explain in simple terms what the ramifications would be in completing the upgrade in relation to support for drivers from Toshiba please? I apologise if this information is already available and would appreciate if anyone could direct me towards the relevant information if that is in fact the case. Thanks.

Most Windows 7 machines should be upgradable to Windows 10. However, I can't say all, and this list is finalized. We don't have an official announcement at this time, but I wanted to share what I know.
With out of warranty machines, as most Windows 7 models are, if you do run into problems, I can't guarantee you'll be able to get every device working. Even if the laptop works fine with Windows 10, it's possible that some accessories could be incompatible.
Many Windows 10 drivers will be offered by Windows Update, but we'll be posting some soon.

Problem with purchase order release strategy

Hi Guru's
    i am dealing with problem of service purchase order release strategy , when i making the service po , i am not giving any over fulfillment tolerance , after release & making Service entry sheet of PO ,   when i go to the change mode and change
over fulfillment tolerance say 90% , system allow me to make , and not applying release strategy again , so there can be a miss use of this Scenario , so is there any possibility that release strategy , will appear again when change the tolerance ,
0r any other idea from your side , to avoid this ,
your suggestions are really always helpful to me , please guide me for this also
Thanks & regards
Neha

Hi Neha,
A reset of the release strategy only takes place if
- the changeability of the release indicator is set to '4' in
   case of a purchase requisition and '4' or '6' in case of
   another purchasing document (purchase order, request for
   quotation, contract, scheduling agreement),
- the document is still subject to the previous release
   strategy,
- the new TOTAL NET ORDER VALUE is higher than the old one.
The total net order value is linked to CEKKO-GNETW for a purchase order,
CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
for a purchase requisition overall release.
If you have maintained a Tolerance for value changes during release
(V_161S-TLFAE), the release strategy is reset when the value of the
document is higher than the percentage you have specified and if the
document is still subject to the previous release strategy.
Review the SAP note 365604 and 493900 for more
information about Release strategy.
Regards,
Ashwini.

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.

Release strategy for PO and Service Entry Sheet

Hi
I maintain characteristics- Plant, Doc Type , Order Value & Purchasing Group for PO release strategy.
should I maintain the same characteristics for service entry sheet ?
the approval will be the same for both

Hi,
The Po reselase strategy can be set up separately from the entry sheet release strategy, so you can use even different characteristics for your entry sheet release strategy. These are not connected!
Please read note 672719 question 5 - How can I set up a release procedure for service entry sheets?
Note: The release strategy must be based on the structure CESSR.
The PO release strategy is based on the structure CEKKO.
For the SEs release strategy you must create a different class.
Regards,
Edit

Configure of New Release strategy in PR for ERSA Mat type

Dear Friends,
Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
Regards,
Ask

ashokkumardash wrote:>
> Dear Friends,
>
> Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
Hi,
Create Characteristic for Material type and Communication structure CEBAN and a create class with 023 and assign character to class and create Release group and code for MRP controller and finally assign this particulate role to the MRP controller User ID and he release the same.

PO Release Strategy not triggerred for particular Total Net Order Value

Dear,
I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
Please suggest for solution.
Thank you.
Warm Regards.

Dear All,
While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
May I know how the value for this field gets calculated.
Thank you.
Warm Regards.

Class and release group and code in release strategy??

hi experts ,
Can some body explain me..
I have created Characteristics and Class for for release strategy.
But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
I m using the same class what i have created for my company..
So how to over come this issue
Thanks

Release Prerequisites
Definition
The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
Release Indicator
Definition
When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
What does the release indicator determine?
Requisitions...
External purchasing documents....
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether an RFQ or a PO may be created with reference to the item
Whether the document may be changed by Purchasing after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether the purchasing document is released for transmission
Alternative Release
Definition
Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
Release w. Classification (PReqs./Ext. Pur. Docs.)
Use
The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
Operation of Release Procedure w. Classification
The characteristic values from a requisition or external purchasing document are passed on to the classification system.
The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
The persons responsible for the release codes process the document in the sequence defined in the release strategy.

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

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

No release strategy for service PO

Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
Shailendra

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

Release strategy based on costcentre for PR

Hi Experts
I want to add Cost Centre as my release criteria in the existing release strategy . Presently I have Purchase grp and amount as my release criteria . Pls advise me how to proceed on this . Kindly also let me know how the user can be mapped to cost centres for approval as the user wants to have different approvers for different cost centres. We have searched for the authorisation obj for cost centre but could not get mor information .Pls help .
Thanks
Edited by: Devashish Lenka on Sep 6, 2010 2:10 PM

Hi,
Option-1:
You can create release characteristics with field KOSTL and add this characteristic with release class with other release characteristics. And you can design your release strategy based on requirement & then limit the cost center via authorization object K_REPO_CCA
Option-2:
Create Purchasing Group (OME4) as Department & assign the department to Cost center(KS02/KS01). Now create purchasing group as release characteristics with field EKGRP add this characteristic with release class with other release characteristics. And now you can design your release strategy based on requirement.
Regards,
Biju K

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

MIR7 doesn't get PO and PO release strategy

I can see PO item 10, 10000 MYR in ME23N, and it is already released.
In MIR7, PO reference tab, I put PO number and item number, but mesages says no item number. and it didn't populate item from PO.
what's the reason?
also I create PR and released PR, but when I run ME59N and input PR number, it says No suitable purchase requisitions found
Message no. ME261? I can't generate PO automatically. I have to use ME21N, what's the wrong with my system?
I tried one purchase group and PO can't be released, but when I change purchase group, it is ok, may i know the SPRO configuration to define certain purchase group for release strategy?
also how can we set certain PO document type with release strategy and some PO document type without release strategy ?

Hello
For first question, Please check in the PO line item level Invoice tab, whether GR based invoice verification is checked. If yes, then system will allow you perform MIR7 after Goods receipt.
Second question:
ME59N should display the open PRs for PO creation. Please cross check once agian the input selection parameters.
Third Question
Yes, you can configure the Release procedure based on Purchasing document type/Pur group. You need to define the paramter as Charactetristic and assign to the Release class.
warm regards
Ramakrishna

CEKKO and CEBAN for PO or PR release strategy??

Similar Messages

Maybe you are looking for