Budget - fixed and variable cost blocking in cost center level.

[Former Member]

Hi,

Kinldy tell me how Budget for fixed and variable cost to be locked at the Cost Center level. Actual expenditure will be less than or equal to budgeted level. We can restrict budget wise value through Internal Order in KO22 against particular financial year. The actual amount will not post if it exceeds than budgeted figure against Internal Order. This is one way entry through Internal Order - Budget. But my requirement is if I put value in KP06 in combination of Cost Center and Cost element against either fixed cost or variable cost it will blocked automatically when actual entry exceeds than this plan figure. I have tested actual entry and caompared with plan figure i.e, KP06. But it has found that actual entry exceeds than plan figure in report S_ALR_87013611. Is it possible this type of blocking for fixed and variable cost in cost center level ?

Kindly need your valuable suggestion.....

Regards,

Samrat

[iklovski · Accepted solution]

Hi,

There is no standard solution in CO for your requirement. If you want to manage your budget in a way you describe, you have to do it not in CO, but in FM (Funds Management).

Regards,

Eli

[iklovski]

Quite so... I saw this kind of development in one of the projects I was involved: it was tough! Certainly, not recommended...

You should pass this message to your client.

[ajaycwa1981]

Hi Eli

They are operating it successfully for the last 4 years atleast.. So, no issues with it... Recently they had an upgrade from ECC 5 to EhP4 on ECC 6.0... All went smooth

Regards

Ajay M

[iklovski]

I don't know... All this is called 'bricolage', and 'bricolage' in SAP is not a good idea. I cannot understand why inventing a bicycle if there is standard SAP solution, which does not require additional license (PSM-FM).

[ajaycwa1981]

I agree with you.. PSM-FM was not in scope of the project.. So, we ended up doing a Z...

Though we thought its better to do a PSM-FM, though out of scope.. But, there is an animal called PMO which does not allow you

Regards

Ajay M

[iklovski]

Hunt it down!

[Former Member]

Dear Ajay and Eli,

Thanks both of you for excellent suggestion. I would request you to Mr. Ajay kindly send me the code to id which is being shown.

Regards,

Samrat

[ajaycwa1981]

Hi Samrat

I sent the code to your mail

Use Ctrl+F and search for "FORM us250 USING b_result"

Code is written here... It has both the codes - One for annual control and another for monthly control..

The code for annual control is currently commented i.e. inactive.... ( From "Begin of Annual Control" to "End of Annual Control" )

The code for periodic control is active (From ** Periodic Control to ** Periodic Control)

Regards

Ajay M

[Former Member]

Dear Ajay,

Thanks for sending the code to me. It means I have to first use Validation from OKC9 then apply this user exit on this validation programme.

Regards,

Samrat.

Edited by: Samrat Roy on Sep 25, 2010 1:55 PM

[Former Member]

Hi Ajay,

For Cost Center Fixed & Variable Cost Blocking we need to restrict users from booking cost exceeding the plan values, As mentioned in the above thread I have tried writing User Exit for the same but its not working in our case.

It would be of much help if you could forward the Code as mentioned for Periodic Control in KP06

We have evaluated option of FM, but client is not ready to implement the same.

Please provide the said code if possible.

Regards,

jaymin r. bhatt

[Former Member]

Hi Mr. Maheshweari,

One of my clients has asked for the same requirement, "budget" control with respect to the plan values of the underlying cost center, which is determined via KP06 transaction.

Could you send the sample code for the validation?

Best regards,

Eren Esgin

[ajaycwa1981]

Hi

As Eli said, standard design in CO does not deliver your requirement

You need to either go for FM (Funds Management) or go for a user exit based logic based on your planned values

I did it once based on KP06 values using validation exit u100 (RGGBR000).. However, I wud recommend to go for FM rather than exit as it is a standard solution

Regards

Ajay M

[Former Member]

Dear Ajaya,

As per current status our client Fund Management implementation is not possible. Without implementing Fund Management you mentioned one validation exit u100(RGGBR000). Can you kindly mentioned in detail regarding that programme and how to find it....

Regards,

Samrat

[iklovski]

Hi,

The reference here is to validation. Hence, you can develop a complicated user-exit in standard validation functionality which will read planning data of the relevant cost centre/cost element and check if the posting could be proceeded. Technically, it's possible, but this user-exit must be quite complicated in order to deal with all possible scenarios.

Regards,

Eli

[ajaycwa1981]

Hi Samrat,

You need to write a Validation in CO in OKC9...

Pre requisite of validation will be: If COBL-BUKRS (Comp Code) = XXXX and COBL-KSTAR (Cost Element) = YYYY

Check: Here, you will call your user exit... Use exit US250 (not U100, as I mentioned earlier)... This exit US250 is a form which is a part of user exit RGGBR000

Here in this exit, you can write your logic... Call table COSP which stores the Plan Costs of KP06... Before posting to any cost element mentioned in the pre-requisite, it will check that Amount in the transaction is not exceeding the value stored in COSP

You have 2 options.... You can check that AMount in the transaction is not exceeding total annual plan value (OR) that amount is not exceeding the monthly value

Depending on your requirement, you can do that

If your User id displays your contact info, i can send the code to you

Note that For YYYY, you can create a SET in GS01 and include your cost ele range here in

Regards

Ajay M

[iklovski]

If you are working with commitment management in CO, then this user-exit will become much more complicated.

[ajaycwa1981]

Hi Eli,

With or Without Commitment Management, working with this user exit is a great pain in itself...

Clients dont realize when we ask them not to go for it, as they feel we are trying to avoid development.... Later on they realize and depending on when they realize, their degree of suffering varies

I ignored the commitment values in this exit and simply checked true postings happening into CO objects...

In another client, we infact gave another solution, which is still better than using this exit...

1. We created a Z table where in we mapped related GL accounts to one group.. This group was a Z field...

2. Statistical Internal orders were created where nomenclature of those IOs represented like XXXX YYYY ZZ..

XXXX = Bus Area, YYYY = Group and ZZ = Period

In this case, client wanted to have budget at company code level and that too not on individual cost ele, but based on group of cost ele

3. We use FI exit U100 to Identify the GSBER and Posting period and GL account from the transaction.. This GL was replaced by the group in Z table and this XXXX YYYY ZZ was populated in the IO field.... This way, budget was checked at Higher level than cost centers and a higher level than GL accounts

@ Samrat - You can think of this approach as well

Regards

Ajay M

[Former Member]

Dear Ajay,

Appreciate if you can forward the code you used to implement.

Kind regards,

Sharif

[Former Member]

Hi Ajay,

Can you please share the code related to this tread. It will be use ful for me a great extent.

rnougatla@gmail.com

Regards,

Ram

[Former Member]

Hi Ajay,

Can you send me that code on my email?

omkarws@yahoo.com

Regards,

Omkar

[sivaprasad_r]

Hi,

By definition, Plan values are not meant for used for Budgeting.. Plan values are meant for analysis and comparision against actuals.

In CO module ( Internal Orders) , the Availability control is available against Budget only, not against planned data.

Njloy

Siva