Maintain Operating Concern (KEA0)

Hi,
I have created a new value field via KEA0. The problem is how can i transport the changes to production system? Thanks.

Use KE3I to transport your Operating Concern. Then use KE0A to regenerate it. Always test in QA first.
pls assign points if helpful as a way to say thanks.

Similar Messages

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

Maintain Operating Concern

We are only tracking expenses & revenue by products. My question is , while maintaining Operating Concern, do we need to choose the Characteristics. Because I do not see the Characteristic "Product" there. All we have there is "Product Hierarchy". How do we get to choose Product in "Maintain Operating Concern"?

Hi Sheena,
In KEA0 Product is a Fixed charachteristic provided by SAP. The technical field name is ARTNR and origin table is MARA. You can check the field once you click on extras - Fixed fields in data structure view of KEA0.
Hope it helps.
Regards,
Abhisek

Operating concern for two company code with different currency

Hi,
We are merging two company code into one SAP server.
We decide to use on chart of account, and to use one operating concern.
For company code A: the currency is CNY, for company code B: the currency is TWD. The operating concern currency is:CNY.
So i need to in KEA0(maintain operating concern) active company code currency, right?
So every posting in company code B will be posted in TWD and CNY to COPA same item, right?
In KE30 report, where to add characters: Currency type that i can show company code B report in TWD?
Thanks.

Dear David,
Yes. If you have different compancy codes within one controlling area, you have to maintain currency type with 10-Company code currecny and while maintaining the operating concern also you have to choose the company code currency only. Then only you will get the reports with respect of your company code currecny level. This will be basing on your company code-sales organisation, plants and other charcters assignment basis in your configuration.
All the best,
Dharma Rao. Yekula.

If no COPA then no need of configuring Operating Concern

Hi All,
Pls tell me if I am not implementing COPA then I don't have to configure Operating Concern. Pls also tell me the importance of Operating Concern with Example and how to configure it. Points will be rewarded.
Thanks & Regards,
JC

Hi JC
If you are not using PA then no you do not need to configure the Operating Concern.
The OpConcern is the organizational unit that holds COPA data, the overall structure being:
Opertating Concern(CO-PA)
               ¦
...............¦
Controlling Area (CO-OM)
               ¦
...............¦
   Company Code (FI)
               ¦
...............¦
       Valuation Area/Plant
You define an operating concern in customizing, t-code KEA0. Go to SPRO -> IMG -> Controlling -> Profitability Analysis -> Structures -> Define Operating Concern. You will find the supporting documentation
here also.
I copied a brief part of the IMG documentation below in case you dont have access:
=============================================================================
In this section, you create an operating concern.
In order to use Profitability Analysis (CO-PA), you have to define operating concerns. An operating concern is an organizational unit in Financials. The structure of an operating concern is determined by analysis criteria (characteristics) and the values to be evaluated (value fields).
In a first step, you have to define the characteristics for your operating concerns. You define characteristics in the Customizing activity Maintain characteristics. For costing-based Profitability Analysis, you also need to define value fields. You do this using the activity Maintain value fields. These characteristics and value fields can be used in several operating concerns. Their definition applies to all clients.
After this, you have to define the structure of your operating concern in the activity Maintain operating concern. You do this by selecting the desired characteristics and adding them to the data structures of your operating concern. If costing-based Profitability Analysis is active, you also need to select and add the required value fields. The structure of an operating concern is valid in all clients.
In the step "Maintain operating concern", you also specify the attributes of your operating concern (fiscal year variant, currencies). By maintaining the attributes, you make an operating concern "known" in the current client. The attributes are client-specific.
==============================================================================
Hope this helps.
Elaine

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

Remove Value Field from Operating Concern

Hi all,
I created a new value field in DEV and assigned it to the corresponding Operating Concern.
Now, after some discussions, it is not necessary this value field.
I want to "un-assign" from the Operating Concern they use.
No data is being posted to this value field and nothing has been transported to QA yet.
Is this possible? Any ideas?
Thanks and Regards,
Flower.

I guess you can delete the value field as it was not transported to QA and PRD.
Here is some information given by SAP.
Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.
Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):
Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.
For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.
To delete characteristics or value fields, perform the following activities:
1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings. You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs. However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during the conversion.
A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function. You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services -> Jobs.
Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.
12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
If you want to transport the operating concern into a different system, see the section "Notes on transport"
Note
Hope this helps
Thanks,
Reddy
Edited by: reddy sap on Sep 11, 2009 6:58 PM
Edited by: reddy sap on Sep 11, 2009 7:00 PM

Delete COPA characteristics which not used in any operating concern

Hello SAP experts,
Please advise me on how to delete PA characteristic "WW001" created by mistake that we are hoping to delete if possible. However, when attempting to delete in KEA5, the error log appear as
Data element RKEG_WW001 is used in these table/view
CACS_S_COND_MA
JVKOMP
KOMG
KOMGF
KOMGFNEW
KOMGFOLD
KOMP
KOMPAKE
STR_KOMG
TRCON_IT_KOMP
WB2_EKOMP
And does not allow the deletion
WW001 have already been delete from the operating concerns.
Please shed some light on how to do this?
Thanks in advance for your help
Yang

Hi,
In order to delete a characteristic you should perform
the following activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services -> Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
It is not possible to transport information about 'deleting of
characteristics (value fields)' with transaction KE3I. Only
characteristics and value fields included in operating concern (to be
transported) are transported with KE3I. Deleted characteristics and
value fields are ignored. You have to delete these characteristics and
value fields manually in each system.
Best regards,
Maria Luisa

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

Attributes for operating concern

Hi..
Please state me all the steps or menupath for maintain the Attributes for operating concern.
Bye.

KEA0 you can use for the Operating Concern.
COPA settings can be maintained within ORKE transaction.
Regards,
Johan

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

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

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

Amount field in Operating Concern

Hi,
What is the field name for the Amount in the Operating Concern?

Nagi,
Check the data structure of your operating concern at KEA0 and look for the value fields available. Typically is the sales quantity, but you could define or add other quantity fields, as needed.
Hope this helps.
Regards,
GG

User Defined Characteristics for Operating Concern.

Hi All...,
I got the total list of characteristics from the core team for the Operating Concern.
Now some of the characteristics are there in the possible entries or Selection Box. Where as for the rest, we have to create manually with User Defined Parameters.
While creating the new characteristics in KEA0 with User defined option, it is not allowing me to enter the ORIGIN & CHECK TABLE, where it is taking the one default value T25**.
Now how can I create the new characteristics.
Regards.,
Raja

Hi,
When you create the new Characteristic, just input the Description, Short text & heading & the data type & length. When you click on save, system prompts you with a message " New check tables should be created for certain chars.
How should the entry of numbers for this table take place?"
Click on Automatic and the system will populate the ABAP dictionary & the Check Table, Text Table & Text field values.
If you create a Characteristic with reference to a SAP table, the Origin table & the Origin field values will get populated automatically. Origin is not relevant , if you select the User defined option while creating new Characteristics.
Assign points if useful.
Regards,

Maintain Operating Concern (KEA0)

Similar Messages

Maybe you are looking for