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

Similar Messages

Operating Concern -COPA.. urgent!!

Hello friends
I've created a couple of new value fields in an operating concern in development box. Also generated the operating concern. It didn't prompt me for any transport request though.
How do I create a trasnport request to transport the new fields to the QAS?
I've tried creating them manually in QAS, but it wouldn't let me to.
I'm sure there are some special transports need to be done in COPA to get the desired results, but don't know what they are..
Can someone help please to resolve this issue?
Thanks a lot.
Message was edited by: Fico Able

Thanks for ur answer, but I cannot retransport the operating concern. The op.concern was established 3 years back and I wouldn't risk touching it.
My question is how would I create a trasnport when i create new value fields in an operating concern, so that I can have the same new value fields in QAS as well.
Thanks very much

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

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

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

How many copa tables created after creation operating concern?

Hi gurus
How many copa tables will be created after just creation of OPERATING CONCERN?
This is question being asked in interview.
Regards
Hari P
Edited by: Hari Peddi on Feb 15, 2009 11:22 AM

Hi,
As the previous comment says, CE1XXXX, CE2XXXX, CE3XXXX and CE4XXXX are created. But this is if you are using Costing-based profitability analysis, However, if you're using account-base PA then no tables are created and CPEP, COSP, COSS and other standard CO tables are used.
Regards,
Kenneth

""selected font failed during last operation." and " there is a problem with generator" application error

For PSDs I have created in older versions of Photoshop CC 2014 I am getting errors when opening / trying to save. They seem to be either Generator or font related. Interestingly, PSDs created in newer versions of PS CC 2014 have no issues, even when using same fonts.
I am getting the error messages:
When I open the older PSD files, (again created or saved in older versions of PS CC 2014) I am asked to update fonts. If I do I get the error.
'Selected font failed during last operation'
When I try to don't try to update fonts and then I try to play with the file I get the following error.
'There is a problem with Generator. Please quit Photoshop and try again. If the problem persists, remove any third-party plugins or try re-installing photoshop.
I don't have any third party plugins that I can see.
I have re-installed multiple times.
I need to use this program and I am paying for your services. I am actually on the phone now with 'help desk' and have been on hold for 22 minutes.
Please Help

When I installed the Apple programs, mobile device application did not uninstall by itself. I had to go to c://program files/common files/apple/mobile device application (or something like that) and manually delete the contents and the folders. I have a 64 bit version so I also had to visit c://program files (x86)/common files/apple/mobile application device (or similar) and also manually delete the files and folders. I had to delete the files before I could delete the folders. This manual part is probably tripping everyone up, because it's not as easy as simply hitting uninstall in the control panel. But the instructions are there. I hope this helps you.

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

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

COPA 2 Operating Concerns - how to model?

Hello,
I have two operating concerns in COPA, I understand I will have to create 2 different datasources.
What is best practice should I have separate Infocube for each or 2 ODS and roll them up in 1 Infocube
1 operating concern's data volume is one-fourth of others..
any suggestions based on your experiences... please advise ... thanks

Hello,
do you know the How to paper?
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/how to set up connection co-pa - extraction
I believe this helps.
Kind reg.
Michael

Account based copa - operating concern currency significance

Hello All,
we have implemented Account based copa and the operating concern currency in EUR.
no other fields in KEAo is activated like the company code currency and other fields.
the company code currency and the controlling area currency is SEK (Swedish Kroner)
sap note 69384 specifies that For account based PA, the operating concern currency is unimportant.
when we are trying to post a FI document, it is not asking for conversion from SEK to EUR
i tried posting to cost center and it got posted without asking for the conversion rate from SEK to EUR.
but when we are trying to post a controlling document(Account based COPA), it is asking for a converision rate from SEK to EUR.
can some one please clarify on why the conversion rate is required for account based copa.
Kind regards
SAP student

Hi
As far as posting to cost center is concerned, it is concerned with your controlling area.. It has nothing to do with your op concern.. Since your comp code and contr area currency is same, it does not ask for exchange rate
But the moment you post into COPA, where in you have specified another currency EUR, it asks for a conversion reason being your comp code currency is not same as EUR...
Even though op concern currency not reqd for account based COPA, but since you have specified it as EUR, it wud ask for a conversion rate
Hope this clarifies
Ajay M

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

COPA - Operating Concern

I seem to have accidently partially activated the S_AL operating concern which in turn created additional fields in structures ACCTSD and COPAFIELDS, this was all done in our Dev client. Our Dev client is now not in line with our QA and Prod clients. Is it possible to reverse what I have done and remove the additional fields created?
Thanks
Greg

Hi,
Go T.code: KEA0
Go to Change operating concen and them go to Data structure.
Then go to value Value fields and select fields that you have created and not required in the left hand side column (data structure) and move them by clicking on arrow to right side column (transfer from).
Assign points if helpful.
Regards,

Condition VPRS value in operating concern currency.

Hi,
We've encountered the following problem. I was wondering if anyone of you had a similar one and how did you go about it:
1. We've defined second local currency for our company codes = currency type 30 = USD
2. CO-PA stores both company code currency = currency type 10 and op. concern currency B0=USD
3. When we post goods issue to a customer, COGS is posted in FI in both currencies 10 and 30.
4. Then when we run billing COGS condition VPRS is transfered to CO-PA in company code currency and operating concern currency. The value in company code currency is equal to the value during goods issue posting, however the value in operating concern currency (B0=USD) is calculated using the current exchange rate type 'M'. As a result VPRS value in CO-PA in B0=USD is not the same as the value of COGS in FI for currency type 30=USD (as the exchange rate is different during billing).
It makes it impossible to reconcile COGS between FI and CO-PA in USD.
For direct posting to CO-PA from MM and FI, SAP provides notes 604936 and 1066394 which solve the issue if B0=30. However those notes do not provide solution for billing documents and VPRS.
We were advised that this problem can be solved using CO-PA enhacement COPA0005.
Have you ever done it? Any tips on codeing this user exit? Any sample code?
Regards,
SZ

Hi,
Currency options in operating concern enables you to view the data in copa. Activation or deactivation of the additional currencies here wont impact base data from any documents.
If u r business doesnt have the profit center valuation or group valuation u can deactivate other currencies.
Regards
Sudhakar Reddy

Transport KE30 reports between operation concerns

Dear all,
I have a problem with the transport of some profitability reports between 2 operation concerns. The reports are confirmed and approved in the first oc, but there's still a dummy copy of these in the second oc.
So here's my process...
I set at first my oc in KEBC. Then I select in KE30 the reports for transport. I chose report definition, report form, key figure scheme and transport all languages. 2 transport requests appeared (customizing and workbench) and they have objects inside (SE01). After that I went to KECP for copy specific objects.
Here's now my problem that I can insert only one transport request. I tried both in separated steps but it didn't work. Also I created a "transport of copies request" in SE01, included the objects of both requets. Also the import from the first to the second oc didn't work.
Can you please give some inputs?
Thanks!
Kind Regards,
Rafael

hello,
did you check
1. Verified that the tnsnames.ora contains a single line entry for the Reports server.
2. Verified that the port is used only once.
3. Verified that the default domain in the sqlnet.ora matches the Reports server entry (.world).
4. Deinstalled and reinstalled the Reports server service.
5. Verified that the Reports server account has a default printer assigned and is set up as a "Use this account" account.
regards,
the oracle reports team

Problem in generating operating concern - COPA

Similar Messages

Maybe you are looking for