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

Similar Messages

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

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

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

Hi
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

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

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.

Language change to Operating Concern in KETR

Hi,
I have one operating concern for all company codes it is the global operating concern it was maintain in EN language ,and other languages also,
But when user lo -gin in FR(French Language) when he was doing Top down Distribution in (KE28) he is getting an error that is
"Operating concern"1000" was not maintained in FR Language"
Now i want to know how to change the the operating language to FR(French language) any one please suggest me the required steps ,
Thanks in advance
Naresh
Edited by: Gadupudi naresh on Jan 2, 2012 4:58 PM

Hi Naresh,
First you need to log in to your system in French. Then in transaction KETR you can select target and source language. Select operating concern, charachteristic and value fields. After this you can exacute the transaction. Please remember to regenerate the operating concern after this operation.
Regards,
Abhisek

Company code and operating concern currency in COPA

Dear experts,
I have one controlling area and one operating concern for indian and foreign entitiy with INR as currency for controlling area and one operating concern.
but outside india i have sgd as company code currency.
So i ticked company code currency in operating concern.so while posting revenue in billing .system store in company code as well as operating concern currency.
But all my expenses for outside india entity will store(cost center) in company code currency 'SGD' and controlling area currency 'INR'.
while doing copa assesssment cycle- whether system will store data in copa table in SGD and INR or only INR as operating concern currency.
i need report on operating concern currency as well as company code currency.
regards
Raman Rana

Hi,
If you have ticked 'company code ccy' in KEA0 then all COPA postings (including COPA assessments) will happen in both currencies i.e. company code ccy and operating concern ccy.
regards
Waman

More than one country assign to one operating concern

Dear Experts,
I have created one controlling area for dubai entity and one operating concern for dubai.
now i am planning for country roll out so i have 10 countries for roll-out and all countries head office belong to dubai.
so i am planning to maintain USD as controlling area currency as well as operating concern currency along with company code currency tick in operating concern and assign all other countries to dubai operating concern and dubai controlling area.
Becoz management want to see reporting in USD as well as company code currency.
but reporting in CO comes under controlling area currency and most of the CO transaction reflects in controlling area currency like assessment and allocation where system takes controlling area currency by default .
any other point i am missing? and also how to see all CO reports in company code currency and how to do assessment in company code currency as well.?
your help will be highly appreciated.
regards
RK

Hi
All CO reports are visible in both currencies i.e. Contr area and Comp Code currency.. Just select company code currency in RPC0 for Cost centers and RPO0 for Order related reports
After executing Allocation, you can use the menu options and choose a layout for Displaying in OBJECT CURRENCY which means Comp Code currency
While calculating activity prices, you need to click on the settings Tab and tick the check box "Iterate amounts independently"
You can adopt single contr area provided all companies have same Fiscal Year and Chart of Accounts...
If any of the company has a different FYV, its better to have a separate contr area for them. Though using new GL you can have single contr area in that case also - My personal exp says its better to have separtae in that case
br, Ajay M

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
CHEERS

Thanks 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

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,

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

No attributes exist for operating concern

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

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

KE24- No Attributes exist for operating concern

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

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

Do I need to rebuild the operating concern once again.

Hi,
I have added extra field to the COPA data soruce (1_CO_PA_XXX) and written CMOD code to populate the data. But I am not able to see the newly added field while trying to fill the data through RSA3.
1. Why am I not able to see the newly added field.
2. Do i need to rebuild the operating concern once again? If yes, Do i need to resbuilt in every system or can it be transported?
3. I am also seeing another data source (1_co_pa_xxx_oc). What's the difference between data sources 1_CO_PA_XXX and 1_co_pa_xxx_oc?

When you're doing a test extraction in RSA3, is the column there but with no data or is the column not even showing up (you may have to right-click on the columns and click on Show... to get the new column to show in RSA3)? Try deugging the 1_CO_PA_XXX DataSource in RSA3 on your R3/ECC source system to determine why the code in CMOD isn't being invoked, or not providing the data. We have been able to modify our 1_CO_PAXXX DataSource by enhancing the extraction structure with an append and then creating code in CMOD, so you shouldn't have to recreate it.
As for the 1_CO_PA_XXX_CO DataSource, it appears that someone has created a second COPA DataSource. It could be that one was created opposite of the 1_CO_PA_XXX DataSource in that it's account-based v. cost-based or it could be the same basis with different fields.

Operating concern for CO-PA Datasource

Similar Messages

Maybe you are looking for