Regeneration of Operating Concern

Hello All, I have assigned 3 existing values fields to 3 new condition types. My question to you all is, is there a need for regeneration of operating concern, & under what circumstances we have to regenerate operating concern. I heard if we create new values fields or Characteristics then we have to regenerate. Can some one pls advice.
Regards,
Sachin

Hi Sachin,
     Your basic query has already been answered that after any structural changes to the data structure the operating concern needs to be regenerated.
    However you have a secondary query: Under what circumstances should the operating concern be regenerated ?
   You should also regenerate the operating concern after any upgrade as explained in the KBA
https://support.wdf.sap.corp/sap/support/notes/2002480
regards
Waman

Similar Messages

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.

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

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

Info about a new value field in a live operating concern

Hi Team,
I'm working on 4.7 system.
I have a live Operating Concern with 120 value fields in "Active" Status.
Some of them never have been posted until now. I need a new "Quantity type" value field, but I can't create another one because I already have 120.
In addition, the value fields that have not been used until now are "Amount type" ones.
Is it possible to delete or modify one of these value files and create another "Quantity type" one, considering that Operating Concern is productive? And how can I do it? What kind of problems could I have?
Best Regards,
Gio

Hi Gio,
Good evening and greetings,
Please go through the SAP Note No.21207 on Deleting a Characteristic / Value Field from an active Operating Concern. This should clarify your questions.
Please reward points if the note is of some use to you.
Thanking you,
With kindest regards
Ramesh Padmanabhan

Error when create Operating Concern

Hi Experts;
At the time of creating a new operating concern after i have defined Characteristics and Value Fields, and checking the status I received the following error:
Error generating table KOMPAKE
Message no. KE434
Diagnosis
An error occurred while Table KOMPAKE was being generated.
Procedure
Analyze the error using Transaction SE11. Use the function 'Check'.
Then I wen to SE11 to check giving the table name as mentioned above, I found the following and could not fix the error;
Then after opening the Long Text it gave the following message:
Enhancement category for table missing
Message no. DT192
Procedure
Maintain the enhancement category in the table or structure maintenance in the ABAP Dictionary.
Then by opening the ((enhancement category)) link i received the following message then STOPPED where I could not do anything more!!!
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.
For more information, refer to the online documentation (pushbutton "i").
Thanks in advance;
Best regards;
Ahmad Mahmud;

Hi Mahmud,
You may need to refer this issue to ABAPer..
Regards
Mohit

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

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

Operating Concern - Transport

Hi All,
I'm trying to create a New operating concern, new characteristics and value fields in the gold client. But these customizing changes are not "automatically" collected in a transport request.
Can someone tell me what is the right way to go about with configuring CO-PA Organizational elements and Data structures in the gold client and collect all these settings in a transport.
Many thanks for your help
SB

Hi,
For transporting Operating Concern please use transaction code KE3I. You need to create a manual transport request. Many of the CO-PA requests can be included in transport request from this transaction. While incorporating the characterstics and value fields excercise caution and check the transport request regarding the objects included.
There is also an OSS note on CO-PA transports. You can check the same.
Thanks
Murali.

Operating Concern -COPA.. urgent!!

Hello friends
I've created a couple of new value fields in an operating concern in development box. Also generated the operating concern. It didn't prompt me for any transport request though.
How do I create a trasnport request to transport the new fields to the QAS?
I've tried creating them manually in QAS, but it wouldn't let me to.
I'm sure there are some special transports need to be done in COPA to get the desired results, but don't know what they are..
Can someone help please to resolve this issue?
Thanks a lot.
Message was edited by: Fico Able

Thanks for ur answer, but I cannot retransport the operating concern. The op.concern was established 3 years back and I wouldn't risk touching it.
My question is how would I create a trasnport when i create new value fields in an operating concern, so that I can have the same new value fields in QAS as well.
Thanks very much

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 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

Problem in generating operating concern - COPA

Hi COPA gurus,
When activating operating concern BPUS through T-Code KEA0, following are the error details we found :
The system is not allowing to activate the operating concern and saving it with following error "Error saving data structure CE1BPUS", Message no. KX655
The error details with Data Structure are
"Reference field CE0BPUS-REC_WAERS for CE0BPUS-VVR10 has incorrect type"
Table CE0BPUS was activated with warnings
As we analyzed the above error in Structure CE0BPUS, the field REC_WAERS and VVR10 is referring to each other, but the data type is different. For REC_WAERS data type is CUKY and the No. of Character is 5, where for VVR10 the data type is blank and the No. of Character is 15.
Same error we are getting for Table CE1BPUS which is updated after updating the structure CE0BPUS.
Please help.

Hi Sangram,
There looks to be some issue with the value field VVR10. Please remove the field from operating concern and try again. There must be some changes to the value feld which created this inconsistancy.
Best Regards,
Abhisek

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

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

Regeneration of Operating Concern

Similar Messages

Maybe you are looking for