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

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.

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

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

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

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,

Defaulting operating concern in KE24

Everytime we go to KE24 with each login, the pop up window comes up asking for operating concern. How ot make it defaulted , so that it doesn't ask everytime. And how to make it defaulted for other users too so that they dont have to enter operating concern everytime they login and go to KE24.

When system prompts for operating concern in KE24, please enter it and click on the 'Save as user default' (Ctrl+S) icon, instead of clicking on the green check mark. This will save the setting for that user. Now all of the users could do the same as a one-time activity in each client-instance so the settings is saved in user parameters (SU3). Alternatively, please check with your security team if they can push the setting for parameter ID ERB (as your default controlling area) to all users en masse.

New operating concern - order settlemement - runtime error KE499

Hello all,
we created a new operating concern 8000 and changed to the operating concern in KEBC.
Now when we try to do an order settlement in KO88, it is working for new orders created after the operating concern change, but for old orders, we do get a runtime error KE499:
Profitability segment number 0000183221 does not exist in operating concern 8000!
Appearently this is caused by the operating concern change, because the old orders are still "connected" to our old operating conern 2000.
Now I was wondering, is there a transaction to fix this, something that would transfer the values for the order from the old operating concern to the new one?
Thanks
Anne

Hi,
I am also getting the exact same error while running CO88 for settlement of production orders, The note recommended above deals with inconsistencies in the sales data. We had changed the assignment of the operating concerna and now we are facing the error where we are not available to pass even one settlemsnt of the production order. I cannot go and individually delete the orders and have to run settlement as a mass transaction.
Please advise innwhat to do.
Ariel

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

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

What's the diff. between Operating Concern & Controlling Area?

Dear Experts,
Can some body tell me about the difference between Operating Concern & Controlling Area?
how these 2 are defined?
what is the logic to be followed while defining the CO-Org Structure?
regards,
shashi

HI,
see
http://help.sap.com/saphelp_erp60/helpdata/en/02/30793485231774e10000009b38f83b/frameset.htm
within this link check "organization in controlling" and there the docu for operating concern and controlling area.
Best regards, Christian

Why is there only one Operating Concern defined in GBI?

Hi all,
I have the following question: when looking at the CO structure of the GBI case study, why is there only one, global operating concern defined? According to the definition of an OC, it is the level whereupon profitability analysis is performed. So why is in GBI that has two very distinct business areas not at least two OCs defined (one per business area), if not more (per product)?
As a follow-on, what is then the relation between OC and Controlling Area? I am looking for a plain English explanation that I can also use for teaching purposes.
Thank you in advance for reading!
Regards,
Gerhard

Hi Gerhard,
I hope my reply is not too late.
I agree with you. Profitability analysis is typically done at a detailed level - by market segments, which may be defined by geographical segments, customer groupings, product groupings, salesforce grouping, etc. CO-PA does support profitability analysis at such detailed levels.
After defining an operating concern and activating it, the system generates a series of database tables for the operating concern. I took a screenshot of the (partial) structure of the "master" table for the global GBI operating concern, GL00, from the GBI 2.2 system I am using, below:
As you can see, with such a table structure, CO-PA is capable of capturing profitability information at a very detailed level for reporting and analysis.
You may also notice that operating concern is not a field in the table. The reason is, the entire table (as well as its related tables in the same series) is used only for operating concern GL00. Its name is even hard-coded in the last 4 characters of the names of these tables. When CO-PA reports are executed in SAP ECC, they retrieve data from only one series of tables, i.e., only data of only one operating concern can be reported.
Back to your question: Why is there only one operating concern and not two? The wisdom of defining one global operating concern is that profitability data of both controlling areas (Europe and North America) will be updated into the same series of database tables and reported together. If there had been two separate operating concerns for the two controlling areas, there would have been two series of database tables, making profitability analysis across the two areas difficult, if not impossible.
Let me know if you need further clarifications.

Assignment between profitability segment and operating concern

Hi,
When i get error like, Profitability segment (with some number say 002345) does not exist in operating concern. Then what are the Tcodes i should check in controlling?
Thanks
Swetha

use se16,
enter the table name ce3****
- Operating concern.
In this table u can view all the profitability segments.
assign points if it is useful.
guru

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

Attributes of Operating Concern

What are the various attributes of Operating Concern?
Regards
Samir

Hi,
Definition
An operating concern represents an organizational unit in your company for which the sales market has a uniform structure. It is the valuation level for Profitability Analysis (CO-PA).
Structure
You structure an operating concern by selecting
Characteristics
You should ask yourself at what level your analyses should be performed, such as the sales organization, region, product, or customer level.
and value fields (only in costing-based Profitability Analysis)
You should ask yourself which values and key figures should be analyzed, such as revenues, sales deductions, costs, or quantities.
as well as G/L accounts (only in account-based Profitability Analysis)
This structure may vary greatly from one company to the next. For example, the structure of total production costs in a manufacturing company differs from that in a wholesale or retail company. Consequently, you need to "model" CO-PA in Customizing by defining the characteristics and value fields that you want to analyze.
Regards,
Ravi

KE24- No Attributes exist for operating concern

Similar Messages

Maybe you are looking for