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
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
MSReddyFirst 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 -
Attributes of Operating Concern
What are the various attributes of Operating Concern?
Regards
SamirHi,
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 -
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.,
RajaHi,
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, -
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,
shashiHI,
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,
GerhardHi 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. -
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.
-
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. -
Reports for two costing Area With one operating concern
Hi,
What are the reports I can get if I am having two different costing area for my comapnies with same operating concern
Thanks in advance for your input
CHEERSThanks Sreekanth ,
I want to what are the reports that will be generated. And what cannot be done if we have two controlling area instead of one.
CHEERS -
1 Operating Concern for Account Based and Cost Based COPA
Hi,
We are using Operating Concern 3000 for Account Based and Cost based Profitability Analysis. However when i try to extract data from the account based Operating concern it gives me an error in extraction : error 09.
Could it be that we cannot use one operating concern for both types or COPA?
ThanksHi
Have you deactivated any of the characteristics used in Account based COPA
Check KEQ3 and you may have activated only for Costing based COPA
S Jayaram
Edited by: S Jayram on Dec 18, 2007 3:24 PM -
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.BHello 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 -
Same operating concern for multiple controlling area
Dear all,
We have a senario in which multiple controlling area is defined with multiple currency. Is it feasible to use same operating concern or different.
Thanks & Regards,
VishalHi
As long as the Fiscal Yr Variant is same between the two, you can use same Op Concern
I dont think the above reply is valid because in my opinion, there is no restriction with regards to Currency
br, Ajay M -
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,
JCHi 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
Maybe you are looking for
-
I have a Mac mini server edition that I'm using just for media. I got the server because I want as much storage as possible. It is refurbished, and is running Snow Leopard server, I don't need it to be a server, if I purchase Lion, can I just "turn
-
Hi, How can control cursor posiotion in alv grid, plz help me. Regards, venkat.
-
Hello all. I have a listbox that i am using to design cycles and add cycle steps to a table. If i make a mistake i can clear the whole table by reinitializing to default value. My problem is that i cannot figure out how to remove the last step in the
-
SEGV in Using of Tertiary Operator
Hi, My Question here is that - Is there is a problem with "?:" operator on solaris systems ?. ie: [ both the values passed must be of exactly same type not a type that can be converted to the other type. ] I am trying to compile & run the following R
-
Is it possible to update QT 7 to higher version? I ran the update once and all the Pro features were disabled with the message: Your Reg Key is for QT Version 7 only. I uninstalled the new QT version, and reinstalled the old QT 7 but the Pro function