Cost center release strategy

Hi all.
We have approximately 100 cost centers each with a different hierarchy of managers that must approve the requisition item.
What is the best way to setup the release procedure. Should we:
Add cost centre to the release strategy. A separate release code will be needed for each cc t/ approved to ensure workload works.
Setup a purchasing group for each department and have a separate release code for each purchasing group.
Either way ad there are over 100 different people it the organisation that can approve requisition items do we have have 100+ release codes?

The best way is to create a Z-Table and maintain the level of approvers for each cost center in that table,
Use the customer enchancement exits for determining the Approvers based on the cost center from this table.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
In this way you will be left with only less data maintenance. Creating release codes for each cost center is a huge task and the number of cost centers keep increaising if you increase the number of plants / Company codes.

Similar Messages

PR Cost Center Release Strategy for Item Level not Working

Hi All,
I have a class with 2 Characterictics, CEBAN-ESTKZ (Creation indicator) and CEBAN-KOSTL (cost Center) and I have 2 release strategies the first one should trigger when MRP creates a PR ( ESTKZ=B and KOSTL=No input) this strategy is working fine, but the second strategy should trigger is if manually I create a PR and it is relevant to a cost center (ESTKZ=R and KOSTL=XXXX) This is not working, I dont know why sistem is not triggering the release strategy if everything seems to be ok.
I know ceban structure has kostl field, but I checked and this field is not in the EBAN table, maybe this is the reason but then how will this work and as far as I know, this is standard field.
I checked in CL24N and all the objects are assigned to the class, all hace status released (1) and and the "OK" check mark
I checked in CL30N and if I enter in the ESTKZ characteristic=R and KOSTL=XXXX Then it finds the correct and only strategy, so I don´t know why this is not working, the only strange thing is that in CL30N if I only enter value R and leave empty the cost center, the system finds and shows me the 2 release strategies, this is strange.
Is it mandatory to include the acc assignment field in the release strategy?
Please give some guidance.
Thanks
Edited by: Julio on Nov 14, 2011 12:14 PM

Hi, thanks for your reply,
I have entered with leading zeros to complete 10 characters and is not working, I really don´t understand what is going on here, It should work even if I just have 1 characteristic assigned to the class right? this characteristic is CEBAN-KOSTL but this is not working.
Any more ideas?
Regards

MM Release Strategy with Cost Centre

My characteristics for the release strategy is Accnt Assigmnt (KNTTP), Cost Centre (KOSTL) and Amount (GSWRT). I link all to the ceban straucture, and for the cost centre, I entered in the value tab the cost centres that I am using, and I entered the cost centres in the release strategy. Everything seem OK for the release strategy, but the release strategy is only selecting the strategy according to the values and not considering the cost centre, what can I do let it consider the cost centre and the value. I have been struggleing with this problem more than a week now. I tried everything that I can think of. Can someone assit me in this matter. I am on ECC 6.
Thank you.

Refer OSS Note :: 52225
Solution ::
Summary
Symptom
Purchase requisition release strategy with classification does not work as expected when the characteristic for cost center KOSTL is included.
Message ME297 is displayed.
Additional key words
CEBAN-KOSTL, KOSTL, Cost center, Release strategy, OMGQ, ME297
ME51, ME52, ME53
Cause and prerequisites
Numeric values used for the cost center characteristic in the purchase requisition release strategy with classification is not recognized. CEBAN-KOSTL is a CHAR field of length 10.
Solution
Enter leading zeros for the cost center value in the release strategy. eg. If the cost center value is 123456, while entering this value for the cost center in the release strategy, enter it as 0000123456.
Cheers !!!!!!
Biswajit

Cost Center based Release Strategy for PR's

System :4.6c
At this time, we have PR release strategy with classification configured for over all release.
Created a new characteristic for cost center , assigned the values for the cost center characteristic, with zeros at the beiginnig.
Now when I create a PR with multiple line items and with multiple cost centers, the system is not deriving the release strategy defined. But if I create multiple line items with the same cost center, the system is able to find the right release strategy.
Does it have to be the same cost center in all the line items to trigger the right release strategy?
Thanks.

Hi,
Looking at your question it seems you are using overall release strategy. If the characteristic value is not same for all line items then during overall release strategy determination, the system uses "BLANK" value for this characteristic.
In order for a release strategy to be found, when you have different
cost center in different PR items you need to add a blank value to your allowed characteristic value for the cost center in your release strategy. Also use Account Assignment Category (KNTTP) as one of your characteristics and define K as an entry, so that release is triggered only when it determines cost center blank with account assignment K.
But if for diff cost centers there is diff strategy then you better opt for Item level Release.
Please give this a Try.
Regards
Chandra Shekhar

Assign right cost center to PR release strategy

in purchase requisition order type, how to assign cost center for release strategy? i.e. for different release strategy, i want to assign different cost center.

Create a new Charecterstic Using Table CEBAN and KOSTL. Here Select Multiple Entries and Maintain your Values (in Values Tab Maintain all the costcenters you are making use of).
Assign it to class and Continue with your Normal Release Procedure.
Revert any issues.
Thanks,
Shiva

Cost center based release strategy.

Hi Gurus,
Could anyone explain about cost center based release strategy?. Thanks.

Hi,
There are two options i have mentioned below.
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
Siva

Re_detemination of release staretgy after changes to cost center

We have a problem in redetermining release stratergy
AA -> released
AB -> released
AC -> not released
AD -> not released
When we change a item cost center, there release stratergy is not redetermined (cancelling all previous releases ).
When there is a value (price)change, the release stratergy is redetermined, but not for cost center.
Both CC and total value are mainatained in class char.
Any suggestions.
Thanks.
Edited by: MIKE JO on Sep 1, 2010 5:20 PM

Hi,
The release strategy does not get reset because there is no change in any of the values in CEKKO straucture. Please note that while creating po release strategy in all the char CEKKO structure will be reffered. For change in cost center u will hav to use user exit.
Regards
Naveen

Release strategy based on Total landed cost

Dear Friends
My client has the following requirement.
Release strategy should be triggered based onthe Total Landed cost which include taxes, insurance, octroi and freight.
we tried with the user exit but could not achieve the target as the Total landed cost is nowhere updated inthe EKPO table.Help inthis regard is appreciable.
Regards
Bapears K

Hi,
While defining characteristics please link up to standard dictionary i.e.
Cost Center CEBAN - KOSTL
Item Value CEBAN - GSWRT.
If you want account assignment also a controlling paramenter, then define Acc Assgnmt as a characterstic and assign the same to the class.
Assign these characteristics to a class.
Regards
Satish

Cost Center Error while releasing Billing document to Accounting

Hi SAP Gurus,
Our user raised an issue that when he had released billing document to accounting, the system threw error message
"Cost center xxxx (CO area)/xxxx(Cost center) does not exist on date 11/16/2011". Message No. KI 222.
But the cost center xxxx does not exist in the system at all. The user does not want to create the cost center eirther. Cost center was not entered in Sales order, Delivery and Billing. I have checked 'Default account assignement' (OKB9) settings, Default account assignment in cost element master record and assignment of cost center to sales organization (OVF3). But cost center xxxx was not configured in the above settings. I have checked validations/substitutions, user exits and BAPIs, there is nothing specific to the cost center. This is not a cross-company code scenario. I have made field status to optional for cost center. But still the problem persists. Accounting document did not get generated because of the above mentioned error message. User applied SAP notes 315350. But it did not resolve the issue.
Would anyone let me know 'why the system showed the cost center xxxx that does not exist, while releasing the billing document to accounting'?
Thanks in advance.
Best Regards,
K.S.K

Hi Friend,
I think this link help for you
Cost center XXXX does not exist on 15.09.2010.
or check the OVF3

Release Strategy-estimation cost and po cost

Hi
Client issu like...in RS
We are maintain our estimation cost in Ztable(Zdev).Purchase order net value is Actual Cost.
My Purchase order cost is less then Estimation cost .NO Problem. We config the RS some Level.
But My PO cost is Greater then Estimaton Cost ,that time client wants some RS in purchase order.
How will i configure Release Starategy Negative Deviation occur in comparison Statement?
Example estimation is RS 10000 (ztable)
Actual PO cost is RS 13000(Ekko)
Now Run Zreport (ZComp) The system Will give 3000 is negative deviation
Nagative dev RS 3000
Above The RS 3000 ,How will i configure Release Strategy In PO?
Rds
Kavi

Hi kavi,
can you please eloberate your issue,
as i under stood you are setting the releasestrategy for PO price.

Purchasing Release strategy in Shipment Cost

Hy collegues,
i need some information about Purchasing Release strategy in shipment cost.
1° question: Release strategy on Service entry sheet document
Is it possible set the Release strategy on Service entry sheet document?
I have just created a release strategy on Service entry sheet but when i transfered the costs with transfert field on Shipment Cost document in VI02 the system didn't feel the Release Strategy on service entry sheet and trasfered the cost in FI/CO.
2° question: Release strategy on Purchase document
Because of the point one I try to set a release strategy on Purchase Order (on purchase order type that i create when transfering the shipment costs).
When i transfered the costs with transfert field on Shipment Cost document in VI02 the system felt the Release Strategy. Infact the purchase order was create without service entry sheet document and good receipt but, in this case, i lost the link from Shipment Cost and the created purchase order.
This in correct, this is a standard behavior???....if this is correct, how will the user (that release the purchase document) release the document if he don'tknow the Shipment cost linked??
Thanks for your precious help.
Piera

Dear Piera,
Please refer note 844752.
This note removes former OSS note 611846. As a result, the automatic
processing of shipment costs should be used WITHOUT release strategy.
This will be STANDARD now for releases 46B, 46C, and 470!!
The release strategy will not be triggered if the KZABN = X,
this is the standard functionality.
I hope this note will clarify your doubt.
Regards,
Rakesh Ojha

Make Cost center in grey mode after releasing order

Dear Guru,
At the time of creating order [IW31] I have made Cost center as Mandatory under Location Tab.
My requirement is after releasing order the Cost center has to be in Grey Mode
Is there any Configuration settings available or any alternativea are available.
Please suggest
Regards
Honyal

HI
Check with the following links:
http://help.sap.com/saphelp_47x200/helpdata/en/13/05b3ae635611d2b43b006094b9c9b4/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/13/05b3ae635611d2b43b006094b9c9b4/frameset.htm
Thanks

Report for release strategy

Hi,
Is there a report for PR/PO release strategy?
Thanks in advance!

Hey
In that case you must query the tables from release strategies, i suggest to you:
T16FS - to get release group, release strategy, and releases codes.
AUSP / KLART=032 - to get Cost Center or others characteristics.
More detailed information get from tables T16F... C/D/E/G/H/K/L/M/T/V and KSSK.
Cya
Jony

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.

Number of chars in the PR Release strategy

Hello gurus
How many chars are allowed in the PR Release strategy? , Is it possible to set up the PR Release strategy with item wise and overall release.
Thanks
JJ

Hello:
You can calculate this value using the variation calculation. For exapmple: if N is the number of positions and M is the number of characters (or leters) teh Variation is
V(n,m) = n! / (n-m)!
where the operation n! = n * (n-1) * (n-2) .... 3 * 2 * 1
In your case you have 10 positions for cost center and 26 leters plus 10 numbers as characters.
V(36,10) = 36! / (36-10)!
V(36,10) = 36!/26!
V(36,10) = 3635343332313029282726! / 26!
V(36,10) = 363534333231302928*27
V(36,10) = 9.22393E+14 possible cost centers
Best regads,
Jose Luis

Cost center release strategy

Similar Messages

Maybe you are looking for