Create Operating Concern vis-a-vis Controlling Area

Hi Experts,
I have a defined a Controlling Area, but NOT an Operating Concern.
How will this affect my CO postings? Can I use CO without Operating Concern?
What is the best practice?
Thanks!

As you have not created an operating concern you will not be able to get Profitability Analysis (COPA)
However it is not likely to affect your controlling in any other way
If not required then there is no need to create any operating concern.
Regds
WDC

Similar Messages

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

Controlling area & operating concern must have same fiscal year variant

Dear Experts,
Whether i can assign two controlling area with different fiscal year variant to one operating concern.
Getting error 'Controlling area & operating concern must have same fiscal year variant'
Fiscal year variant must be same or Number of posting period must be same.
regards
RR
Moderator: Please, search before posting

Hi ajay,
I did the testing also,
System is showing error msg' Controlling area & operating concern must have same fiscal year variant'
But someone told me. number of Posting period must be same not fiscal year variant.That why i am confused.
I assigned all company code same posting period variant in different controlling area.Still facing same error.
That why i have posted in SDN.
regards
RR

Change the currency of Operating Concern COPA

Hi,
In my SAP environment there are 4 controlling areas. Only one of them is assigned to Operating concern. The remaining 3 have COPA inactive.
I would like to extend the existing operating concern to remaining 3 controlling areas, but before I do that I need to change the Operating concern currency as the one currently set is only relevant for only one controlling area and company code which is GBP. I need to change it to group currency - USD.
When I use F1 help on currency field in Operating Concern settings in configuration, I get information that 'once data has been posted, however, a change in the operating concern currency would cause the existing data to be interpreted as if it were posted in the new currency (for example: USD 1000.00 in old currency -> DEM 1000.00 in new currency).'
Even though we have transactional data posted in that operating concern , it is not being used by any department and we are quite happy to have existing data interpreted in USD instead of GBP. No reports are being generated in COPA currently so it will not be an issue for us. We want new data to be proper and constistent.
When I try to change the currency in operating concern config, the field is greyed out. I believe there is more complex workaround for that, but the only note I found on this is 651142 which says that SAP provides different tools to reorganize operating concern. But no further details are included.
If anybody managed to change operating concern currency, please help me with that.
Regards,
Karol

Hi Karol
I read the note given by you.. It asks you to contact the SAP for SLO Service (System Landscape Optimization )
This is a chargeable service by SAP... In case you decide to go ahead with this, do share your experience with us
Create an OSS msg and give ref of this note... I would suggest to go with SAP service and not with any one else's experiences... The tools that SAP is talking about are available only with SAP..
You may try to archive the existing data from COPA tables and then see if the currency field opens up for editing.. Am not sure about it..
Regards
Ajay M

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.

Creation of Operating Concern after Controlling Area

Hi SAP Gurus,
Need your help on this one:
Our client is implementing FICO in phase 1 without COPA & Product Costing. COPA will be taken up in Phase 2 when MM & SD are also implemented.
Will I have to create an Operating Concern now in Phase 1 along with the Controlling Area? or will I be able to create an Opearting Concern alone later in Phase 2?
Points will be assigned to useful answers.
Thanks & Regards,
Sangeeta

Hi
Operating Concern is at above the Controlling Area.
You can create Operating Concern later. There won't be any impact.
Because, no where you are going to assign the Operating Concern. So, it'll not impact the settings.
VVR

Assign Company Codes to new Credit Controlling areas after going live.

Dear FI Experts;
Our Status Now:
We Have 3 Company Codes, CC 1000, 2000, 3000 and one Credit Controlling Area Code 0001, and the Customers are assigned to this Credit Controlling area with no problems and we are live since about 9 months ago.
Requirement:
We have a requirement to split the Customer Credit limit between companies, which means we have to create more credit control areas for example CCA 0002, and 0003, and though assign our 3 company codes to the new credit control areas, as follows:
CC 1000 to CCA 0001
CC2000 to CCA 0002
CC3000 to CCA 0003
And my Question is, what is the procedures to follow to do that (Not a Customization Procedures, I mean the How the Customers would be affected and the open items for them and how to resolve that), since as mentioned above we are already live since 9 months ago, and credit management is active and all our customers are assigned to our old Credit control area 0001, and also what is the consequence of doing that new assignment since we are live, thanks for your reply

You will need to manage to create new credit master data under new credit control area. System should reorganize existing credit data after reassignment, that is when you change master data (create credit master under new credit control area), new credit exposure is calculated based on AR in company code and existing open orders will get rechecked for credit under new credit control area & new risk categories assigned to them.

Controlling area does not exist in assignment ?

Hi,
I've created & assinged controlling area to the company code , But then When I used PPOME to create org unit and assign the Controlling area , It did not exist in the list ? How can i configure this
Thanks in advance

Hi,
Check in V_TKA01_GD table (assign company code to controlling area) whether controlling area is assigned to company code properly or not. If it is assigned properly then in PPOME Tcode in Account Assignment tab once you enter your company code Controlling area will be selected automatically.
If controlling area is not assigned to company code properly then you will not able to see that in PPOME. In this case you can take help from FI consultant as they only create Controlling area and assign it to company code.
Regards,
GRM

Credit Control Area incorrectly referenced in billing doc

I have made two credit control areas 1000 and 2000. 1000 is the default cca for the company code.
Now for some sales order the cca is correctly determined which is 1000 but when they reach the billing level the cca changes to 2000 which is unbelievable.
When I check out at the delievery level it is blank.
For most of the sales order it works correctly by referring the cca in the sales orer into the billing document
I am checking the cca values by the backend tables..Cant find any logical solutin
Kindly Help,
Sam

Hi
Check if:
1. The 'overwrite cc area' check box is checked in the step Enterprise structure>Assignment>FInancial Accounting-->Assign Conpany code to Credit control area.
The cc area can be over written during document posting if the option is checked
2. If the sales area related to the order you have created is assigned to the Credit control area in question in the customizing step Enterprise Structure>Assignment>Sales and Distribution-->Assign sales area to credit control area.
Hope it helps.
Regards
Madhu

How to remove characteristic or value field in operating concern?

Hi all,
As I have duplicated one value field in my current operating concern so I want to remove it from operating concern then delete it.
I use KEA0 --> change operating concern --> but all value fields are in blue color and I cant not remove it.
Thanks in advance.
BR,
Emily

Hi
Check you are in Change mode and then try Extras - Unlock Characteristics/Value fields
Thank You,
Edited by: SAP Student on Mar 25, 2009 6:31 AM

Problem in activating the environment in COPA operating concern

Dear Experts,
I got the following message when I tried to activate the environment based on client-specific part for my newly created operating concern.
<< Inconsistency in the dictionary for the structure "KOMK_KEY_U" >>
Does anyone know what happened?
By the way, the data structure is successfully created.
Regards,
Abraham

Hi Shanbagavali,
I had the same error today, when I tried to activate a transferrule based on a generic datasource.
In my case the reason was a field in the extract structure with data type "string" which is not allowed.
After removing this field from the extract structure I could activate the transfer rules.
Hope it helps.
Regards,
Stefan

Restricting Authorisations for different controlling areas

Hi SAP Gurus,
I am facing a problem in restricting authorisations for CO Transactions in different controlling ares. We have a new controlling area started recently. But the CO user in this new controlling area is able to create master data in a differnt controlling area (i.e. the old existing controlling area). we have already maintained the new controlling area as org. unit for the relevant company code.
Giving below an example.
For t.code KAH1 & KAH2, we have maintained authorization object K_CCA for New Cont Area with Cost Center group X (Where X is standard hierarchy). Even after that user is able to make changes in KAH2 for another controlling area. We also tried to put value of profit centers instead of "*". This too is not helping.
Similarly the user is able to create master data in Tr. Codes KO01 / 02, KE51 / 52, KCH2 etc where this user in new controlling area is able to create / change master data from exising old controlling area.
Can anyone help me please ?
Thanks.

Dear Prasad,
Create a new Role using T Code PFCG and assign the new controlling area and the other relevant
details and you can assign it to the users.
I think in your case that particular user is assigned many roles where he has got * value and its allowing
to make changes on some other controlling area.
Regards
Mangalraj.S

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

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

Controlling area & operating concern

hi all,
1may i know what is controlling area.
2may i know what is operating concern.
thanks

Hi,
Controlling area is an umbrella under which several reports are generated for internal purposes.
Controlling is a function which supports the business analysis and management decision making process
Check the link
http://help.sap.com/saphelp_erp2005/helpdata/en/02/30793485231774e10000009b38f83b/frameset.htm
What are Controlling component, Controlling area component code?
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).
Check the link
http://help.sap.com/saphelp_46c/helpdata/en/7a/4c38814a0111d1894c0000e829fbbd/content.htm
Hope this helps ...
Regards,
Praisty

Create Operating Concern vis-a-vis Controlling Area

Similar Messages

Maybe you are looking for