Adding a ValueField to an existing Operating Concern?

Gurus,
I'm new to CO-PA. I need to add a new Value Field to an operating concern which is already live in CO-PA.
Please let me know the impact of it on an operating concern and the existing reports if any.
Create the new Value Field in KEA6
Add the new field to Data Structure of the new Operating Concern in KEA0.
Are there any other steps that need to be taken care of ?
Any help in this regard is greatly appreciated.
Thanks,
erp warrior

Hi
1. Create the VF in KEA6
2. Add it to the data structure in KEA0 i.e. push it from list on the right side to Left side
3. SAVE and CLick on the CANDLE icon to activate the data strucutre
4. Press back
5. System would give a pop up to generate the OP concern again.. Confirm it and regenrate the op concern
6. Now, generate a transport request from KE3I.. Select all the indicators under "Operating Concern"... Transport the work bench and the customizing requests to prod client
make sure that all users are logged off while you transport the requests
Regards
Ajay M

Similar Messages

Impact of adding new value fields in ongoing operating concern.

Hi All,
Want to know the steps of adding new value fields in the existing operating concern in COPA?
What is the overall impact of addition of New Value fields in the running Operating Concern?
How do we test the addition of new value fields?
Is the addition of New Value fields to the running Operating Concern advisable?
Your support and advice is highly anticipated and appreciated.
Thanks & Regards
9819528669

HI,
please search in SCN forum before you post:
Re: Adding a ValueField to an existing Operating Concern?
Best regards, Christian

Add value field to existing/ productive operating concern

Dear All,
I need to create a new value field and add it to an existing operating concern, which is already in use (there is already transaction data in the live system).
In my opinion I have to do the following steps:
1. Create new value field (KEA6).
2. Add value field to operating concern (KEA0).
3. Activate operating concern (KEA0).
4. Transport operating concern (KE3I).
Is that strategy ok?
Is it ok, to transport an operating concern, when the system is already "live" and there is transaction data in the system?
Thanks for your answers,
Regards,
Michael

Hi,
first create new value field in KEA6. then take those new Value field in your operating concern Data Structure in t-code KEA0. Then generate the operating Concern.
Regards,
Sreekanth

Impact of Addition of New Value Fields in the existing Op. Concern-COPA

Hi All,
Want to know the steps of adding new value fields in the existing operating concern in COPA?
What is the overall impact of addition of New Value fields in the running Operating Concern?
How do we test the addition of new value fields?
Is the addition of New Value fields to the running Operating Concern advisable?
Your support and advice is highly anticipated and appreciated.
Thanks & Regards
9819528669
Ohter details are as follows...
VALUE FIELDS : Defines the Structure of your Costs & Revenues. (Op. Concern 120 Value Fields)
1)     The client requires three new value fields to be created. Value fields for :
-     Other Airport Charges - International
-     Cargo Commission Cost
-     Personal Cost (Direct)
2)     What are the Steps involved in creation of new value fields? The steps are :
1)     Before creating new value field we need to check whether we can use already existing UNUSED value fields (There are 62 value fields created for the op concern 1000, in production the value fields TBUL1-L7 i.e. to be used (I assume) screen shot1 provided. My predecessor has used value field VV291, VV292, VV380 original description being TBUL3, TBUL4, and TBUL1. I believe he has changed the description in development client and created a transport request ref screen shot 2)
2)     You can create new value field thru T-Code KEA6 (4-5 characters beginning with VV) u2013 My predecessor has reused the value fields originally created he has not created new one I believe. please provide give your comments)
3)     Specify whether this field is for Currency or Quantity (currency defined in attribute of op concern and quantity defined by its own field u2013 unit of measure) u2013 My predecessor has configured the three value fields as Currency.
4)     Describe how the values in this field are aggregated over characteristics. (SUM, LAS, AVG) u2013 My predecessor has aggregated all the three value fields as SUM and they are in Active status.
5)     After the value field is created you have to add the value field (active status only) to the operating concern by Editing the Data Structure. (I guess this is done in the next step)
6)     Assign newly created Value fields to the Operating Concern u2013 T-Code KEA0 (In development client the value fields are assigned to the op concern 1000 refer screen shot 3. In the production client also those three value fields exist (does it mean they are assigned? your comments please.) As they have the original description TBUL3, TBUL4, and TBUL1 refer screen shot 4.
7)     After the Data Structure is defined you need to activate them. (creates plan vs actual database) u2013 Go to the data structure tab and Choose Activate. The status in dev client is Active with correct description but in the production client it is Active with the OLD description. After addition of the value field you need to regenerate the operating concern. T-Code KEA0 u2013 right?
8)     Condition Types are assigned to Value Fields? Donu2019t know u2013 T-Code KE45 (I think this is NOT required in our case u2013 Please give your comments)
9)     Define and Assign Valuation Strategy u2013 Cost assigned to Value fields u2013 T-Code KE4U (I think this is also NOT required in our case)
10)     Define PA Transfer Structure for Settlement u2013 T-Code KEI1 (This step is crucial u2013 I think I have to to include newly created value fields, but am not aware how to do it and what is the connectivity or what happens after this is done)
Note: My predecessor has created a Transport Request No# KEDK902167 for the value fields created by him.
3)     Whether my predecessor has performed all the steps for value field creation? How to test it and check that?
4)     If yes then, Do I need to perform additional configuration or can I proceed to transport it to Production?
5)     What is COPA Allocation Structure & PA Transfer Structure? Where and Why It is used?
6)     What are the different methods of cost and revenue allocations in SAP?
7)     I have checked the status of the value fields across clients, It is as followsu2026
     Value Field     Value Field For     Description     Development      Quality     Production
1     VV291     Other Airport Charges International     TBUL3     Exists      DNE     DNE
2     VV292     Cargo Commission Cost     TBUL4     Exists      DNE     DNE
3     VV380     Personal Cost u2013 Direct     TBUL1     Exists      DNE     DNE
#DNE : Does Not Exist (assumed since the description given to value field is not the same as in development client.)

HI sree,
ofter creation value field and saving that time reqwest number appeare copy the reqwest number and go through the se01 select that reqwest number select and transport click the truck symbole, and draft a mail to basis guyw.
Thank You!
Best Regards,
pradheep.

Change the currency of Operating Concern COPA

Hi,
In my SAP environment there are 4 controlling areas. Only one of them is assigned to Operating concern. The remaining 3 have COPA inactive.
I would like to extend the existing operating concern to remaining 3 controlling areas, but before I do that I need to change the Operating concern currency as the one currently set is only relevant for only one controlling area and company code which is GBP. I need to change it to group currency - USD.
When I use F1 help on currency field in Operating Concern settings in configuration, I get information that 'once data has been posted, however, a change in the operating concern currency would cause the existing data to be interpreted as if it were posted in the new currency (for example: USD 1000.00 in old currency -> DEM 1000.00 in new currency).'
Even though we have transactional data posted in that operating concern , it is not being used by any department and we are quite happy to have existing data interpreted in USD instead of GBP. No reports are being generated in COPA currently so it will not be an issue for us. We want new data to be proper and constistent.
When I try to change the currency in operating concern config, the field is greyed out. I believe there is more complex workaround for that, but the only note I found on this is 651142 which says that SAP provides different tools to reorganize operating concern. But no further details are included.
If anybody managed to change operating concern currency, please help me with that.
Regards,
Karol

Hi Karol
I read the note given by you.. It asks you to contact the SAP for SLO Service (System Landscape Optimization )
This is a chargeable service by SAP... In case you decide to go ahead with this, do share your experience with us
Create an OSS msg and give ref of this note... I would suggest to go with SAP service and not with any one else's experiences... The tools that SAP is talking about are available only with SAP..
You may try to archive the existing data from COPA tables and then see if the currency field opens up for editing.. Am not sure about it..
Regards
Ajay M

Adding new value fields to an existing and productive operating concern

Hi,
I would like to have 5 new value fields active in 4 out of 6 operating concerns that I am working with.
Is it correct that I could do this one of the following ways:
1. Use a value field that exists already in an operating concern and rename it?
In this case is it necessary to regenerate the operating concern?
Do I transport the change ?
2. Create an entirely new value field, and assign it to the operating concern?
Is it necessary to regenerate the operating concerns in question?
Do I transport the change?
3. Select a value field that is currently in the system but is not assigned to any operating concern eg some kind of SAP delivered value field? How do I assign it to the op con? Do I need to re gen the op con?
Which way is the best or is there a 4th option?
Thanks for your help in adviance
Regards
Aisling

Hi,
This note is a catalogue of notes of consulting notes where SAP tell you steps, reports to use and son . If you read them (these notes and related notes) you have the steps, guides, reports that you must use. Better advice. Try a solution with all steps in mind and check it in a quality enviroment. As you know there a lot of things in CO-PA concern (you have your own tables, with your own fields, your reports as KE2Rxxxx, and so on), your secondary indexes, etc.. , the best is try the solution in your Quality Enviroment (a quasi-clone of your production enviroment) and check the results (create SO, invoices, after modifications to check possible problems,...).
Regards,
Eduardo
pd: I forgot. If the size of tables (CE4xxxx, CE1XXXX, ...check them with DB02) are so big, get the opinion of a Basis Consultant. Surely in the before note there notes about this issue.
Edited by: Eduardo Hinojosa on Apr 23, 2010 2:41 PM

Maintaining operating concern after adding new value field

Hello,
I added a new value field to our live operating concern,maintained the data structure throguh KEA0(Maintain operating concern).The changes are transported from Development to Quality,Changes were reflected in Q system.After testing in Q system transports were pushed to production system.The new value field is added to the operating concern. When i check the log for KEA0 in production system it displayed one message like:
Field VV088 was added to the reference structure
Message no. KE782.You probably either changed the operating concern or SAP-EIS aspect, and added the field VV099 to the definition.
The added a CO-PA value field:
In this case, the field is added to the definition or the summarization levels. This invalidates all existing levels. Consequently, you need to activate them again and fill them with data.
In production system maintaining operating concenr or KEAO is only in display mode.Is it needed to regenerate the operating concern once again in production, how to do it. Is the message talking about the KEDV summarization levels.?
thanks
rahul

Hi,
No no ....KEDV is nothing to do here....that is creation of summarization in CO-PA.
Since you added new value field you necessarily have to Regenerate the operating concern...
Use Tcode KEA0...go to Environment tab...there the status of Cross client part and client specific part both will be in RED....now just click on the Cross client (candle button)...now the system would regenerate the operating concern...once it is over do the same for the client specific...
Beware when you do regenerate the operating concern no body can enter any transaction in that server since it is cross client table ...hence better do it after business hours.
Hope this helps!
Running KEDU with rebuild is relevant only when you already have created summarization and called up the same in the CO-PA report "options" tab. If you did not created the summarization you are nothing to do with KEDU.
Next: The new value field has to be transported to PRD and hence even in PRD we have to do the regeneration manually.
Regards,
Velumani
Message was edited by: Velumani Arunachalam
Message was edited by: Velumani Arunachalam

Profitability segment number 02209 does not exist in operating concern ESAA

Hello Experts,
Please help us on one issue which we are facing here that
"Profitability segment number 02209 does not exist in operating concern ESAA"
please could you please let us know why are facing this issue and where to check if this Profitability segment number.
Thanks and Regards,
Mangal Modi

HI,
This can occur if you have deleted data from table CE41001 and have
already assigned data to profitability segments in this operating
concern.
Check the OSS note: 93051, hope it may help you..
Thanks

No attributes exist for operating concern

Dear Friends:
In our configuration client, the operating concern is active and has attributes were defined and transported. But in Unit testing client, the system says
"No attributes exist for operating concern"
How to over the problem?Please advise?
How should i reward the answers?
Regards
MSReddy

First try regenerating the operating concern in KEA0 in the envirionment tab. Select the activate buttons. If that does not work then retransport your operating concern using tcode KE3I.
pls assign points if helpfu;l as a way to say thanks.

KE24- No Attributes exist for operating concern

Dear Gurus,
while iam generating the ke24 report, am getting the error message as No attributes exist for operating concern.
Please help me out in this problem.
BR,
Deepak.

Hi Deepak
You can access change logs in KEA0 by accessing Extras -> History log. I guess this would only be available in Dev client though.
Secondly you can also try regenerating the Operating cocern by activating it under the Environment Tab in KEA0
Alternatively, you can also try reimporting the operating concern by using KE3I
Hope it helps
Regards
Mustafa

New characteristic in the existing Op, Concern

Dear gurus,
Can we add up a new Characteristic be it fixed or non fixed in an existing op. Concern that is been in use(means its got data in it)?
If yes How?
regards
sayeed

Sure. If the characteristic already exists just add it to your operating concern with t-code (KEA0). Go to change mode and click on the Data Structure button. The available characteristics wil appear in the list on the right hand side. Just select the ones you want and then activate and generate the operating concern. You will need to transport the operating concern to your production client with t-code (KE3I). If your characteristic does not currently exist you will need to first create it with transaction code (KEA5) before adding to the operating concern.
thanks,

Operating concern for CO-PA Datasource

Dear Experts,
i need to enhance the CO-PA datasource,as we know we cannot ehance the same where we need to create the new datasource KEB0.when i tried the same with providing the operating concern,i am not able to see the option to add the new field.
i think we need to add the new field in the operating concern.Please correct me if i am wrong and let me know the transaction to check theoperating concern.
Regards,
Sunil Kumar.B

Hello Sunil
Did you check all the tables of that particular Op concern?
I mean 1.Segment level 2. Segment table 3. line items 4.Value fields
If not available there then it needs to be added to Operating Concern. Transaction code to maintain Op concern is KEA0
But enhancing operating concern is the job of CO-PA consultant . Do you manage both COPA and BW?
Regards
Anindya

Operating concern not able to activate in CO-PA

Dear All,
I created some new Characterstics and value fields in the CO-PA. After that I have taken my required Characterstics and value fields in my data structure in Operating concern. When Click on Check tab button ( i.e. Cntr+F2 ) it is giving the message structure definition is O.K.
After that I am able to SAVE that.
BUT when I want to activate the data structure is giving the DUMP ERROR.
The message is " What happened?
     One of the columns addressed in a table or view does not exist in the database.
     table) exists in the ABAP/4 Dictionary, but not in the database.
Short text
    SQL error in the database when accessing a table.
It's critical issue in my development client and my whole work has stopped.
Kindly do the needful.
Thanking You
Regards
K. S. Sai Kumar

Hi,
Sayeed,
Even I am not able to change the Characteristics and Value fields like previous condition.
I mean If I want make the change in operating concern it is giving the message " No Objects Reset " Message no. KX473
I have to solve this problem very urgently.
KIndly do the needful.
Thanking You
Regards
K. S. Sai Kumar

Add value field to operating concern

Hello,
I have created a new value field VV955 and want to add it to my operating concern in transaction KEA6.
I go into change mode for all value fields for my operating concern and add a new line with my value field. When I hit the save button, it says "Field VV955 exists as Val. fld in field catalog -> choose another name".
Also when I go into change mode in KEA0 where you can drag value fields from left to the right, the value field is blue which means I cannot assign it to my operating concern.
Any suggestions?
Thanks
Anne

Hi,
While creating value field it will only consider long text. Inoperating concern Data structure in KEA0 you can assgin value field it will display in blue first, when you select to data structure you can see value field and save the value field.
Regards,
Sreekanth

Definition of a new operating concern

Hi experts,
We have a question about transporting a new operating concern.
To transport customizing settings of the new operating concern we used Tcode KE3I.
We defined new characteristics and value fields for the new operating concern.
In the customizing request we can see that for the tables TKEF and TKEFD all entries (old and new) were included.
But all old fields already exists in the target system of the transport request.
Should we keep the old fields (existing characteristics and value fields) in the customizing request or should we delete them and leave only the new ones ????
Thanks.

Cincean:
By old entries you mean the SAP delivered entries/characteristics??
Or the characteristics you previously created?, if so, just keep it that way and transport
Vj
Assign points if info helps

Adding a ValueField to an existing Operating Concern?

Similar Messages

Maybe you are looking for